Exporting XMP to Lightroom Classic, Bridge, or Camera Raw

If you plan to finish a gallery in Adobe’s tools after editing it in Imagen, the file format doing the actual handoff is XMP. It is easy to gloss over as a technical detail, but understanding what XMP carries, and what it deliberately leaves out, changes how you plan a shoot that is going to move between two systems. Here is exactly what happens when you export from Imagen toward Lightroom Classic, Bridge, or Camera Raw, step by step. Imagen can also export finished JPG, TIFF, or PNG files directly, but this guide follows the XMP route.

None of this requires any special setup on your end. It is worth knowing anyway, because it explains a few things that would otherwise look like missing features.

What XMP actually is

XMP is a metadata format Adobe’s own applications already read natively. Rather than baking edits permanently into a photo’s pixels, an XMP file, or XMP data embedded alongside a RAW file, describes the adjustments that should be applied: exposure, color, tone curve, and the rest of a typical edit. Lightroom Classic, Bridge, and Camera Raw all understand this format because Adobe built it, which is exactly why it is the format Imagen uses to hand off edits rather than inventing a proprietary one that Adobe’s tools would not recognize.

The practical upside is that nothing gets flattened or baked in during the handoff. The edit arrives as instructions Adobe’s tools can read, adjust further, or reprocess, the same way a native Lightroom edit would behave.

This also explains why the process feels invisible when it works correctly. There is no export dialog asking which edits to include or exclude, and no separate file to manage alongside the photo. The XMP data travels with the image as a single package, which is exactly the behavior Adobe designed it to have long before Imagen entered the picture.

What specifically gets written into the XMP data

Everything your Personal AI Profile touches gets written into that XMP data, and so does any additional AI tool pass layered on top, say a targeted retouch or a batch exposure fix. The moment the export lands in Adobe’s world, those adjustments are already sitting there, fully readable.

On the other side of the ledger: dragging a slider by hand, marking up a star rating, flagging a reject, tagging a color label, none of that is written into the XMP file, because none of it was ever meant to leave Imagen in the first place. Knowing that in advance changes the order you work in. Finish the AI pass, export, and only then start any manual retouching that is specifically bound for Photoshop or Lightroom Classic, rather than doing that hands-on work inside Imagen first and losing it at the door.

It is worth repeating this because it is the single most common point of confusion for anyone new to the handoff: an AI Profile pass and a manual slider adjustment can look identical on screen inside Imagen, but only one of them was ever going to survive the trip to Adobe. Knowing which is which before you start manual touch-ups saves a wasted pass.

Step by step: getting a gallery into Lightroom Classic

Once your AI Profile and any AI tools have finished processing a gallery inside Imagen, exporting sends the finished files, RAW or otherwise, out to your computer along with their XMP data attached. Point Lightroom Classic at that same folder, either by importing it fresh or by letting Lightroom Classic detect the XMP if the originals are already in your catalog, and the AI editing shows up as if it had been applied inside Lightroom itself. From there, you work exactly the way you always have: adjust further, apply a Lightroom preset on top, or export straight to a client.

There is no conversion step and nothing to reformat by hand. The XMP data is doing the translation for you in the background.

If you manage a large catalog and prefer to keep everything in one place rather than creating a separate import folder each time, pointing Lightroom Classic at the same watched folder Imagen exports into works just as well, picking up new XMP data automatically as fresh galleries land.

Opening the same export in Bridge or Camera Raw

Bridge and Camera Raw read the same XMP data the same way Lightroom Classic does, since all three are built by Adobe to share this format. If your process runs through Camera Raw directly, perhaps because you prefer working file by file rather than through a full catalog, opening an exported RAW shows the Imagen edit already applied in the develop panel, ready for further adjustment. Bridge behaves similarly for browsing and batch operations across a folder of exported images.

Refining an AI edit with manual sliders in the Imagen editor

This is particularly useful for photographers who use Bridge as a lightweight browser before deciding which files actually need Photoshop. The AI editing is already visible at that stage, so the decision about what needs more work is based on a real preview rather than an unedited RAW file.

Photographers who split their attention across a laptop and a desktop often rely on this consistency without thinking about it directly: whichever Adobe application happens to be open reads the same underlying data the same way, so switching machines mid-project never means switching what an edit looks like.

What you will and will not see once the files land in Adobe

You will see your Personal AI Profile’s work and any AI tools you ran, looking the same as they did inside Imagen, because the XMP data describes the exact same adjustments. You will not see manual slider tweaks you made in Imagen’s own editor, and you will not see star ratings, flags, or color labels you applied while culling or reviewing there. Those exist only inside Imagen.

That is not a bug to troubleshoot. It reflects a clear line between what is meant to travel with the photo as portable edit data and what is meant to support your review process inside Imagen specifically. Knowing the line in advance means you never waste time looking for a rating that was never going to appear.

This same boundary explains why a photographer who reviews a gallery carefully inside Imagen, rating and flagging as they go, should not expect any of that organizational work to reappear once the files are sitting in a Lightroom Classic catalog. That work already did its job during the export decision, and it was never meant to be duplicated on the other side.

Where this workflow earns its place

This handoff matters most for photographers who have a specific reason to finish outside Imagen: a retoucher who only works in Photoshop, a print lab with a Lightroom Classic export preset already tuned exactly right, or simply a personal preference built over years that is not worth abandoning. It also suits mixed galleries well, where the bulk of the set ships straight from Imagen and a handful of hero images continue on to Adobe for extra attention. If nothing needs Adobe’s tools, the built-in editor (Beta) handles manual touch-ups inside Imagen.

None of this requires choosing one system permanently. A photographer can run this exact export process on one gallery and skip it entirely on the next, depending on what that specific set of photos actually needs. For a broader look at how editing, culling, and export decisions fit together, the valuable tips library covers each piece in more depth.

It is also a reasonable default for anyone still deciding how much of their process belongs in which tool. There is no requirement to commit to one pattern permanently. A photographer can run this exact export on a Tuesday wedding and skip it entirely on Wednesday’s product shoot, based on nothing more than what each specific job actually needs.

A quick troubleshooting note

If an exported file opens in Lightroom Classic, Bridge, or Camera Raw and the AI edit does not appear to be there, the most common cause is pointing Adobe at the wrong copy of the file rather than the one Imagen actually exported. Because XMP data travels with the specific exported file, opening an older version of the same photo, one exported before editing finished, will understandably look unedited. Re-exporting the current version after processing completes resolves this in nearly every case.

It is also worth remembering that this XMP handoff only carries AI Profile and AI tool work. If you were expecting a manual crop or a flag to show up in Lightroom Classic, that is expected behavior, not a failed export, since that category of edit was never designed to leave Imagen.

What’s new in Imagen: Imagen is now an intelligent, agentic Studio for professional photographers, so culling, editing, review, and export happen in one project in whatever order you like. Your AI edits still travel to Lightroom Classic, Bridge, and Camera Raw as XMP, and an assistant that finds photos when you ask in plain language can help you pick the frames to send onward. The rollout is gradual while the Studio is in beta.

Frequently asked questions

Do I need to convert anything before opening an Imagen export in Lightroom Classic?

No. The exported file already carries its XMP data. Import the folder or point Lightroom Classic at the files, and the AI editing appears already applied.

Will my manual edits from Imagen show up in Photoshop or Camera Raw?

No. Manual slider adjustments, ratings, flags, and color labels made inside Imagen stay in Imagen. Only your Personal AI Profile and AI tool edits travel as XMP.

Does Bridge support this the same way Lightroom Classic does?

Yes. Bridge and Camera Raw read the same XMP data as Lightroom Classic, since Adobe built all three to share it.

What should I do if I plan to finish a gallery in Photoshop after Imagen?

Let the AI editing finish processing first, review it without making manual tweaks you would lose in the handoff, then export. The finished files will carry the AI editing into Photoshop by way of Camera Raw or Bridge.

Ready to see your own edits land cleanly in Adobe? Start a project in Imagen’s new Studio, where you cull, edit, and export in one place, then send your edits to Lightroom Classic, Bridge, or Camera Raw at imagen-ai.com.