Back to Blog
AISeptember 24, 20267 min read

Photoshop and Firefly Now in Gemini: Edit Images in One Message

Photoshop and Firefly Now in Gemini: Edit Images in One Message
Image: Adobe

You no longer need to open Photoshop to fix a product shot. You type into a chat window. Two announcements this month change how brands relate to visual production, and they turn a question marketing teams have been asking quietly into one they now ask out loud: do we still need an agency?

Our short answer: yes, and increasingly so. Because:

  • Content volume is multiplying. As production gets easier, every campaign spreads across more channels, languages and formats. The number of visuals to manage isn’t shrinking; it’s growing.
  • Consistency is getting harder. The same brand is now produced by dozens of people in different tools. Without the rules that make it all look like one brand, identity erodes fast.
  • Standing out is getting harder. Everyone gets the same tools at the same time. What sets you apart isn’t the tool; it’s the idea, the craft and the brand voice.
  • Building the right system takes expertise. Tokens, templates, approval flows and a CMS on the web side are what let AI add speed instead of damage.
  • The risks are growing. Unapproved posts, content with unclear licensing and off-brand visuals turn into more frequent, more visible mistakes as production speeds up.

Here’s the long answer.

What happened

According to Adobe’s September 24 announcement, tools from Photoshop, Lightroom, Express and Firefly are rolling out globally across all Gemini plans. You upload product photos, describe the look you want, and lighting and color get optimized while images are cropped consistently. Social-ready versions happen in the same conversation, which Adobe says are made “preserving your branding and messaging.” Describe your campaign and audience, and Express surfaces matching templates.

The same day, Acrobat joined the Adobe plugin for Claude. It now reaches more than 80 tools across Acrobat, Express, Photoshop, Illustrator, Premiere, Lightroom, InDesign and Adobe Stock, along with a layer-based Express editor and an interactive PDF editor.

A week earlier, on September 17, Figma shipped a “Figma node” for Weave. Copy a frame from Figma Design, paste it into Weave, and it becomes a node in a workflow. You choose which text and image layers act as inputs; fonts, layout and styling stay intact. When the source design changes, connected assets can be synced. Figma’s stated use cases: new assets at scale from existing designs and brand materials, campaign variations, and localized assets for different markets.

The real shift: not the tool, the interface

Photoshop isn’t new. What’s new is that professional image editing now sits inside a chat box people use every day, rather than inside specialist software. On the Figma side, a single design frame becomes a mold that can produce hundreds of variations.

Put the two together and the picture is clear: the cost of producing a single visual is heading toward zero. Your marketing lead can adapt one product shot for five channels before lunch. That’s good news. It also creates a new problem.

When production gets easier, volume goes up. When volume goes up, so does inconsistency. Five people, five prompts, five versions of “on brand.” Six months later, your brand shows up across channels as five identities that don’t quite match. Adobe says it preserves your branding, and it may, but the brand has to be clearly defined first. AI scales a system that exists. It doesn’t invent one that doesn’t.

What it means for your brand

Opportunities

  • Speed: Simple adaptations (resizing, cropping, lighting, channel versions) get done in-house without waiting in an agency queue.
  • Scale: With tools like the Figma node, one master design can yield many language and market versions. For exporters, that’s direct time saved.
  • Budget: Money spent on routine production can move to work that actually differentiates you: identity, campaign ideas, film.

Risks

  • Brand erosion: Without clear rules, every adaptation dilutes the brand a little more.
  • Unapproved publishing: A visual generated in chat can go live before anyone looks at it. Mistakes get caught in public, not in review.
  • System dependency: Structures like the Figma node only work if the source design is built properly. Generate a hundred variations from a messy file with inconsistent styles, and you’ve copied the same mistake a hundred times.

The most common misconception is that easier production means less agency work. The opposite is true: the easier it gets to resize an image, the more it matters which visual, with which message, on which channel, represents your brand correctly. Routine adaptation moves to your team; the need for a strategic partner who manages that shift keeps growing.

Practical steps

To make AI tools speed your brand up instead of wearing it down, we recommend four steps:

  1. Make your brand guidelines machine-readable. A PDF guideline is written for people. Define colors and typography as tokens (named, reusable values), and tone rules as short, specific sentences: “No exclamation marks in headlines,” “Product shots always on light grey.” These can be fed straight into prompts and templates.
  2. Build a template library. Social, presentations, email, trade show graphics. For each format, master templates with locked areas (logo, layout, type) and open areas (copy, imagery). The Figma node’s input-layer logic is built on exactly this idea.
  3. Define an approval flow. Who creates, who approves, what can go live without sign-off? Speed shouldn’t mean no control. Even one simple rule, such as campaign visuals passing through a single brand owner, protects consistency.
  4. Connect the web to the system too. Producing visuals at scale and then building every web page by hand creates a bottleneck. With Webflow CMS collections, product, campaign or location pages can be multiplied from the same template, consistently.

Our take at Klyne

We don’t see this as a threat. We see work moving to where it belongs. Production is getting cheaper; systems and direction are getting more valuable. A brand’s worth isn’t in individual visuals but in the rules that produce them.

That’s why delivering brand identity as a logo file and a PDF guideline is no longer enough. An identity now needs to be built as a production system your team and AI tools can use correctly: tokens, templates, tone rules, approval logic. In graphic design, the weight is shifting from one-off visuals to master templates your in-house team can confidently scale.

Let your team handle daily adaptations in the chat window, while we build the system that keeps your fast-growing output speaking as one brand, and shape the campaign idea, the film and the brand’s direction with you. As the tools multiply, the agency’s role isn’t shrinking, it’s growing: it no longer just holds the pen, it also draws where the pen goes.

FAQ

Do I need a paid plan to use Adobe in Gemini?

According to Adobe, the tools are available across all Gemini plans and rolling out globally from September 24. You connect Adobe under connected apps in Gemini and sign in with an Adobe account; Adobe notes that compatibility and availability may vary.

Do variations made with the Figma node keep the brand style?

According to Figma’s release notes, the text and image layers you select become inputs while the original fonts, layout and styling are preserved. The result still depends on how cleanly the source design is built.

Can a small brand team get by without an agency using these tools?

It can handle routine adaptations on its own. But without a strong brand system, template structure and campaign idea, speed only accelerates inconsistency, and the gap widens as output grows. The most efficient model: build the system, the direction and the big pieces of work with an expert team, then let your team produce day to day inside that system.

If you want to turn your brand into a system that’s ready for AI, let’s plan it together.

Sources

  1. Adobe comes to Gemini, expands what you can do in Claude · Adobe Blog
  2. Figma release notes · Figma