Adobe Put Photoshop and Firefly Inside Gemini and Claude. Here's What Actually Changed for Marketers

Most AI-tool announcements change a feature. This one changes where the work happens. On 24 September 2026, Adobe announced that Photoshop, Lightroom, Adobe Express and Firefly are now reachable from inside Google Gemini. Claude's existing Adobe plugin gained Acrobat too, on top of the Express and Photoshop tools it already carried.

That is a real shift in where marketing production happens, not a UI tweak. It is also, on its own, not the whole story. This is a synthesis piece. We reviewed Adobe's own announcement and one independent outlet's report, not a hands-on test, and we say so plainly rather than pretending otherwise.

What's new inside Gemini

Gemini gains Adobe as a connected app. A user goes to Personal Intelligence, selects Adobe under Connected Apps, and signs in with an Adobe account (a free one works). From there, according to the announcement, Gemini can call on Photoshop, Lightroom, Adobe Express and Firefly to:

• Enhance a product photo — lighting, color, cropping — without opening Photoshop
• Adapt one piece of creative across social formats while keeping brand elements consistent
• Customize a campaign template pulled from Express

Google's Neal Pancholi described the goal as letting people "create, edit and bring their ideas to life right in the chat." The mechanism Adobe describes is an orchestration layer: you describe the outcome, and Adobe's tools handle the steps, rather than you picking a specific tool first.

What's new inside Claude

Claude's Adobe plugin existed before this update — it already offered Express and Photoshop access. The new piece is Acrobat: a full document toolkit including an interactive PDF editor for reordering and editing pages, markup and commenting, and a "Document Review" skill that reads a file and returns analysis and recommendations. Adobe says over 80 pro-grade tools are now reachable across Acrobat, Express, Photoshop, Illustrator, Premiere, Lightroom, InDesign and Adobe Stock, on desktop, web and mobile versions of Claude.

Guest access works without an account. Signing in with Adobe unlocks higher usage limits and lets a session continue where it left off — the kind of detail that matters once this moves from a demo to daily use.

The actual change: one window instead of five

Strip away the feature list and the structural claim is simple. The standard production loop runs: brief in one tool, generate in a second, edit in a third, export, paste into a fourth for review. On paper, that collapses into one chat window, with Adobe's tools called in behind the scenes.

For a marketer, that loop is where a surprising amount of a campaign day goes: not the creative decision itself, but the mechanical cost of moving a file between apps to make it real. Removing hops is a genuine productivity claim, and it is the kind of claim that is easy to overstate from a press release and hard to verify without using it.

This was previewed in May. What changed by September?

Adobe did not spring this on anyone. At Google I/O in May 2026, Adobe previewed a Gemini connector as "coming weeks" away, promising access to 50-plus pro-grade tools, multi-format generation, and — specifically — "workflow visibility with approval checkpoints."

Four months later, the September 24 ship announcement describes the same orchestration idea, a larger tool count, and a cleaner sign-in flow. What it does not repeat, in either Adobe's own post or the independent coverage we reviewed, is that approval-checkpoint language. That is not proof the feature was dropped — a launch post trims detail a preview post doesn't need to — but it is a specific claim that shipped quietly enough that neither source thought it worth restating, and that is exactly the kind of thing worth checking directly before a team relies on it for anything with a sign-off step.

What the announcement conveniently leaves out

Here is the gap none of the coverage we found addresses directly: Adobe's post and the independent reporting both describe capability, not governance. Three questions a marketing team should ask before treating this as workflow infrastructure, not a demo:

• Whose brand kit is enforced? "Keeping brand elements consistent" is Adobe's phrase for the Gemini social-adaptation feature. Neither source says what that means mechanically — a locked style guide, or the model's best guess from a prompt.
• What happens to approval trails? Claude's Acrobat tools can edit and redact PDFs inside a chat session. Neither source mentions version history, audit logs, or how a legal or compliance reviewer would see what changed and when.
• Guest mode vs account mode. Both platforms work without an Adobe account at a reduced tier, and account sign-in is positioned as the full version. For a team rolling this out, that is a licensing and admin decision Adobe is not making for you.

None of this means the launch is hollow. It means the parts that make a tool safe to hand to a whole marketing team — governance, audit, brand lock — are exactly the parts a product announcement has no incentive to dwell on.

Three uses worth trying first

Based strictly on what both sources describe, not on anything run here, three starting points look lowest-risk:

• Batch photo cleanup inside Gemini. Lighting and color correction on a batch of product shots is a narrow, low-stakes task to pilot the connector on before trusting it with anything brand-sensitive.
• Campaign brief review in Claude. The Document Review skill reading a PDF brief and returning notes is a genuinely useful first touch — as a second opinion, not a replacement for a human sign-off.
• Template reskinning in Express via either chat. Adapting an existing, already-approved template to a new campaign is a smaller ask than generating brand-new creative from scratch, and a reasonable place to learn the tool's limits.

What we would not do yet: route a client-facing or regulated-industry document through an AI-orchestrated redaction step without a human re-checking every page. "Redact sensitive information" is Adobe's phrase; whether it gets it right every time is exactly the kind of claim that needs independent testing before anyone trusts it with something that can't be unsent.

Who should wait

Teams with a formal DAM (digital asset management) system, a locked brand-guideline enforcement process, or regulated-industry document handling should treat this as a pilot, not a rollout. The orchestration Adobe describes sits on top of existing Creative Cloud and Acrobat permissions, but neither source states how enterprise admin controls map onto a Gemini- or Claude-initiated edit. If your team already runs a DAM workflow that enforces who can touch a brand asset, treat this as a parallel experiment, not a replacement, until that question has a direct answer from Adobe.

The obvious caveat

This piece is built from two sources: Adobe's own announcement and one independent outlet's same-day report. Both describe the same features consistently, which is reassuring, but a vendor's own blog post is marketing copy until someone outside the vendor runs it. We have not tested these connectors ourselves and are not claiming to. Treat every capability above as "Adobe says," and verify directly before building a process around it.

This post was researched and refined with AI tools.