Adobe has released a plugin for ChatGPT. Users can use it to access over 70 creative tools directly in the chat window, tools that were previously tied to individual applications – including functions from Photoshop, Illustrator, InDesign, Acrobat and Firefly.

The practical effect: instead of opening an application, creating a document and searching through menus, users formulate their request as a prompt, i.e. as a text instruction to the language model. The plugin translates this instruction into a call to the relevant Adobe function.

Why this matters for businesses

Until now, getting started with professional graphics and document tools was a hurdle: licences, training, file formats. This very hurdle is what made Canva and similar providers big. If Adobe functions are now accessible in a chat interface, access shifts once again significantly – away from tool knowledge, towards the ability to describe a result precisely.

For small and medium-sized businesses, this means concretely: tasks that today end up in the queue of an agency or an internal graphics department could be handled by specialist departments themselves. A social image, a corrected PDF, a scaled image variant for the website – such small tasks tie up a disproportionate amount of time in many organisations.

The flip side: control is lost

This very low-threshold access creates new risks. Anyone who creates assets via prompt usually bypasses the review steps built into established design processes. Three points carry particular weight here.

Brand consistency. A language model does not know your brand colours, font sizes and visual language on its own. Without binding specifications, results emerge that seem acceptable individually but add up to a diffuse brand image. This often only becomes apparent when dozens of variants are in circulation.

Technical suitability for web assets. An image that looks good in chat is not yet a usable web asset. File format, compression, resolution, aspect ratios for different viewports, alternative texts for accessibility – all of this determines load times and accessibility. These requirements do not automatically follow from a prompt.

Traceability. When assets are created in chat histories, documentation is often missing: who created what, when, on what basis, with which rights. For companies that maintain image material over years and must use it in a legally compliant way, this is a real problem.

What a sensible workflow must deliver

Chat-based creation does not replace a process, it needs one. From a project perspective, four building blocks are particularly helpful:

  • Binding specifications: A concise, well-documented set of colours, fonts, image styles and formats that can be reused in prompts. The more specific the specification, the less rework.
  • Clear responsibilities: Define which asset types specialist departments may create themselves and which must always go through design or development. Campaign key visuals are something different from an internal diagram.
  • A review step before publication: Before an asset lands in the content management system, someone should approve format, quality, alternative text and brand conformity. This can be lightweight, but it must exist.
  • Storage instead of chat history: Created files belong in a central media management system, not in scattered download folders. Only then do they remain reusable and findable.

Assessment for TYPO3 and web projects

In a TYPO3 project, part of this quality assurance can be mapped technically. The system's file management allows metadata, mandatory fields and structured storage; TYPO3 handles image processing and output formats itself during delivery anyway. Anyone who consistently feeds generated raw images into this pipeline, instead of uploading pre-cropped files, regains control over performance and consistency.

It is equally worthwhile to update editorial guidelines. If image material is partly created with AI support, editors should know which details they must record and which content is off-limits – for example photorealistic depictions of people or situations that never existed.

Considered soberly

The plugin lowers access barriers, but it does not replace design decisions. What makes a layout viable – hierarchy, readability, interaction with the frontend – remains a specialist task. A division of labour is realistic: routine production and variants move into chat interfaces, conceptual work and technical integration stay where they are today.

For web and software projects, this primarily means a shift in the bottleneck. It is no longer the creation of assets that is the bottleneck, but their review, classification and technically clean integration. Anyone who now organises specifications, approval paths and media management benefits from the new speed – anyone who does not mainly produces more rework.

Sources