Finishing in Adobe, If That's How You Work

Not every photographer wants a gallery to leave Imagen already finished, and that preference does not need a justification attached to it. Some photographers run a project from cull to export entirely inside Imagen. Others treat Imagen as the first half of the process on purpose, every time, and hand the second half to Lightroom Classic, Bridge, Photoshop, or Camera Raw. Both are normal, complete ways to use the same tool, not a compromise version of one or the other.

The confusion that occasionally comes up is not about whether this is allowed. It clearly is. It is about exactly what survives the trip to Adobe, why a photographer would choose this path deliberately, and how to keep the sequence clean when only part of a gallery is headed that way. That is what the rest of this covers.

Here is the mechanics of the handoff, the three reasons it comes up most often, and a worked example showing one gallery split cleanly between two finishing paths.

The simplest path, in one sentence

The version of this workflow that shows up most often is short: cull the gallery, let your Personal AI Profile and any AI tools finish their pass, review the results without making manual tweaks you would lose at the door, and export straight into whichever Adobe tool you already use. Nothing about that sequence is a workaround or a lesser way to use Imagen. It is one of two fully supported paths, and plenty of photographers land on it as a permanent default rather than a temporary phase while they learn a new tool.

The reason it works cleanly is that it respects the one rule the whole handoff depends on: finish the AI editing first, then decide what happens next. Reviewing and rating before the AI pass is complete, or trying to make manual adjustments you plan to export anyway, is where most of the confusion around this workflow actually starts.

What actually gets handed off

Handing a gallery to Adobe after Imagen is straightforward, but only one category of work makes the trip. Whatever your Personal AI Profile decided, along with any AI tool pass layered on top such as a targeted retouch or an exposure correction, exports as XMP data that Lightroom Classic, Bridge, Photoshop, and Camera Raw all read natively the moment you point them at the exported files. Whatever you decided by hand inside Imagen instead, a dragged slider, an assigned star rating, a reject flag, a color tag, stays exactly where you left it, because none of that was ever written into the XMP data in the first place.

Knowing that split before you start reviewing changes how you spend the time between export and delivery. If a set of images is headed to Photoshop regardless of what happens inside Imagen, there is little point second-guessing a slider by hand first, since that specific adjustment will not be the one that arrives on the other side. Put the manual attention where it will actually count, which for this workflow means after the export, not before it.

This is also why sequencing matters more than it looks like it should. A photographer who reviews and rates carefully but then keeps nudging sliders after already deciding what is headed to Adobe ends up doing some of that work twice, once inside Imagen and again once the files land in Photoshop.

Reason one: a Photoshop routine that already works

The most common reason photographers keep a Photoshop step is that they already have one, built over years, tuned to a specific look, and not worth rebuilding just because a new tool arrived. Imagen’s role in that setup narrows on purpose: cull the shoot, apply a consistent AI-edited baseline across the whole gallery, and export. The compositing, dodge and burn, or detailed retouching work continues in Photoshop exactly as it always has, untouched by anything upstream.

This is also the honest answer for anyone wondering whether Imagen’s built-in editor, still in beta, is meant to replace that kind of routine right away. It is not, at least not yet, for every specialized technique a seasoned Photoshop workflow depends on. There is no reason to wait on the editor catching up when Photoshop already does the job well. Nothing here is urging a switch before a photographer’s own routine is ready for one.

Reason two: a retoucher or lab with specific requirements

A second common case involves a third party rather than the photographer’s own preference. Wedding and portrait photographers who outsource retouching often work with someone who expects files in a particular state, opened through a particular Adobe tool, with presets already tuned to their process. A print lab can be the same story, with an export preset built around its own paper stock and color profile that took real effort to get right in the first place. In both cases, the practical answer is to let Imagen produce a clean, AI-edited baseline gallery, export it, and let the retoucher or lab pick it up through Lightroom Classic, Bridge, or Camera Raw exactly the way they already work.

Culling a shoot inside the Imagen project view

Nothing about this requires explaining the handoff to that third party in any detail. From where they sit, the files simply arrive already looking like a finished first pass, ready for whatever comes next in a process that has nothing to do with how those files got there.

Reason three: you simply prefer it, and that is enough

Sometimes there is no workflow requirement behind the choice at all. A photographer might just prefer thinking through final adjustments inside an interface they have used for a decade, and that preference does not need a stronger reason than familiarity. Comfort with a tool is a legitimate factor in how someone runs a business, not a gap that needs closing or a habit to be talked out of.

This is worth saying plainly because it is easy to assume a new tool expects to be used for everything, all the time, or not at all. That was never the design intent here. A photographer can use Imagen for culling and a consistent AI-edited baseline on every gallery, and still finish every one of them by hand in Adobe, indefinitely, without that being a half-adopted workflow or a phase they are expected to grow out of.

A practical example: one wedding, two finishing paths

Say a wedding produces eighteen hundred frames across the day. The photographer culls the full set inside Imagen and runs the Personal AI Profile across everything, since a consistent baseline matters even for the frames nobody will scrutinize closely later. Roughly seventeen hundred of those, the candid coverage, the reception, the dancing, export as finished JPG files straight from Imagen and go into the client gallery within a day or two of the wedding.

The remaining frames, family formals, the first look, a handful of portrait sets the couple specifically asked to be printed large, get pulled aside during review and flagged for a different path. That smaller set exports the same way as everything else, as AI-edited files carrying their XMP data, but lands in Photoshop instead of the delivery folder. The photographer finishes those manually, the same way they always have for print-bound images, while the rest of the wedding is already sitting in the couple’s online gallery.

Nothing about running two paths on one event slows down the larger batch waiting on the smaller one. The split happens once, during review, and each set moves at its own pace afterward.

Keeping the sequence simple on a deadline

The order that avoids trouble is the same one every time: finish AI editing first, do all culling and rating inside Imagen, decide which files are headed to Adobe using Imagen’s own review tools, and only then export. Exporting before the review is finished, or trying to route different subsets out at different stages of the process, is where photographers end up chasing which version of a file actually has the current edit applied to it. Because edited photos arrive in batches, you can start reviewing early frames while the rest finish, but hold the export until the last batch has landed.

For a closer look at how culling, rating, and export decisions fit together across a full shoot, the valuable tips library covers the sequencing in more depth than fits here.

On an actual deadline, boring and predictable is the goal, not clever. A gallery that follows this order start to finish rarely produces a surprise once it lands in Adobe, and a gallery that does not follow it is exactly where photographers lose the most time re-checking work that should already have been settled.

What’s new in Imagen: The latest Imagen is an intelligent, agentic Studio for professional photographers: a single project where you cull, edit, review, and export in any order. Whether you finish inside Imagen with the built-in editor (Beta) or hand your AI edits to Lightroom Classic, Bridge, or Camera Raw as XMP, both paths stay open. Availability is expanding gradually while the Studio is in beta.

Frequently asked questions

Do I have to send anything to Adobe if I do not want to?

No. Finishing entirely inside Imagen is fully supported, using the built-in editor (Beta) for manual touches and exporting finished JPG, TIFF, or PNG files. Exporting to Lightroom, Bridge, Photoshop, or Camera Raw is available whenever it is useful, not a required step.

What if I only want to finish some of a gallery in Photoshop?

That is exactly what splitting a gallery supports. Flag or rate the subset you want to finish separately during review inside Imagen, then export that group along with the rest.

Will my ratings and flags still be there if I check Lightroom Classic?

No. Ratings, flags, and color labels are part of Imagen’s own review process and stay there. Only your Personal AI Profile and AI tool edits travel to Adobe as XMP.

Does choosing to finish in Adobe cost anything extra inside Imagen?

No. Pricing follows what you export from Imagen itself. What you do with those files afterward in Adobe’s tools does not change that.

Ready to see how a gallery splits between Imagen and Adobe on your own work? Start a project in Imagen’s new Studio, where you cull, edit, and export together, and choose exactly what you export at imagen-ai.com.