Export selections to Lightroom or Capture One, without losing anything

Your picks live in one program and your edits happen in another. Nothing physically crosses between them except a small block of text, and every failure in this handoff comes from that text being written in the wrong place, read in the wrong order, or never read at all. This is the mechanics, tool by tool, with the parts that quietly do not survive.

There are only three ways picks cross over

A culling tool cannot reach into your Lightroom catalog and set a star rating on a photo you already imported. The catalog is a database Lightroom writes to. So in the documented workflow of every tool below, a selection crosses in one of three ways.

• Metadata written next to the file. An XMP sidecar for raw files, or metadata inside the file for DNG and JPEG. This is how most of the work gets done.
• An import dialog. The tool asks Lightroom to open its import window with your picks already chosen, so the metadata arrives when the photos do.
• A folder of files. The tool copies or moves your picks into a separate folder and you import that.

Knowing which of the three you are using tells you where to look when something goes missing. Our post-production pipeline guide maps all the stages. This page is only about the join between two of them.

What an XMP sidecar is, and which files get one

XMP is a small text block holding everything the camera did not record: rating, color label, keywords, caption, copyright, raw adjustments. Where it lives depends on the file type.

For proprietary raw files, CR3, NEF, ARW and the rest, it sits in a separate file beside the photo with the same name and an .xmp extension. Adobe keeps it separate by design, rather than write into a format it does not own. For DNG, JPEG, TIFF and PSD there is no sidecar, because the metadata is written into the file itself. Imagen describes the same split: for raw, "a separate sidecar file created in the same folder as the original photo", and for DNG and JPEG it is embedded.

The practical consequence is dull and expensive. A sidecar is a second file. Hand off a folder of raw files and leave the .xmp files behind, and you have handed over photos with no ratings, no labels and no edits. There is now a second one to watch: since Lightroom Classic 15, heavy edits, masks and AI settings such as Denoise go into a companion .acr file alongside the .xmp so the sidecar stays light. Two companion files per raw file, both of which need to travel. If the fields themselves are new to you, our photo metadata guide covers what is worth filling in.

What survives the hop, and what does not

Everything in the top half of this table travels between programs. Everything in the bottom half is a Lightroom Classic feature that lives only in the catalog file, so there is nothing on disk to hand over.

The flag row is the one that catches people. Flags feel like the natural way to pick, they have the best shortcut, and they are the least portable thing in Lightroom. As photography writer Tim Grey puts it, "features that are specific to Lightroom Classic, such as collections, virtual copies, pick and reject flags, and more, will not be included" when metadata is saved out.

We go deeper on that tradeoff in star ratings versus flags, and on label systems that hold up in color labels for culling.

What each tool actually hands off

Every one of these is a good tool. They draw the line in different places, and the difference shows up at 11pm when a rating does not appear.

Aftershoot is explicit that it syncs "Star Ratings, Color Labels, and edits via XMP", in both directions. Its export step filters by folders or by stars and colors, then copies or moves the chosen files. That copy or move choice deserves a second of thought, because moving is the only irreversible option on this page.

Narrative Select splits the job in two, which is why its help center has separate articles for each half. Ratings and labels travel by XMP. The photos travel by Ship and Edit, which opens a window where you "choose to either create a new Lightroom catalog or select an existing one", then hands over to Lightroom's normal import dialog. Our Narrative Select review covers whether the culling suits your work.

Photo Mechanic has one mismatch worth knowing before you build a system on it. Camera Bits gives you "eight different color classes plus 'none'". Adobe gives you five color labels. Classes six, seven and eight have nowhere to land in Lightroom, which is part of why Photo Mechanic ships preference snapshots aimed at specific programs, Lightroom Classic included.

Lightroom's own Assisted Culling is the interesting case, because there is no handoff at all and that is the point. Adobe's help page describes an Organize Result step where you "apply batch actions to organize photos by flagging, rating, labeling, and adding the Selects and Rejects photos to the collection or folder." Read that list again: of the four ways it offers to record the result, only two will ever leave the catalog.

The three Lightroom Classic settings that decide whether this works

Lightroom will not read a sidecar it was not told to look at, and will not write one unless you ask. Three settings, set once.

1. Catalog Settings, Metadata tab, Automatically write changes into XMP. Turn this on. It pushes your Lightroom work out to disk so a culling tool can see it. Aftershoot says to enable exactly this before importing into Aftershoot.
2. Metadata, Read Metadata from File. Nothing arrives on its own. After rating in the other program, select the photos in Lightroom and run this to pull the sidecars in. Aftershoot and Narrative both name this step.
3. Apply During Import, set to None. The sneaky one. Narrative's troubleshooting page tells you to set both Develop Settings and Metadata to None at import, because a preset applied on the way in writes over what the culling tool just put there.

Order matters more than any one of them. Save out of Lightroom first, then cull, then read back. Narrative's warning is blunt: get the sequence wrong and "any edits or rating you previously did in Lightroom will be overwritten." There is no merge step. The last program to write wins. Our Lightroom culling workflow covers the rest of the setup.

Capture One plays by different rules

Capture One reads a rating written by any of these tools. It handles "Embedded EXIF, Embedded IPTC-IIM, Embedded XMP, and .XMP sidecar file". But its default posture surprises Lightroom users: "Capture One will never write metadata to source files; all metadata changes are done via proxy file." Your ratings and color tags live in .cos files in a session, or the database in a catalog.

So two preferences, both on the Image tab, do all the work. Auto Sync Sidecar XMP has three positions: Full Sync writes your Capture One changes out to sidecars and reads external ones in, Load reads only, None leaves you to run Load Metadata or Sync Metadata by hand. Prefer Sidecar XMP over Embedded Metadata decides who wins when a file has both. Aftershoot tells Capture One users to set Full Sync before, then toggle that preference on after.

If you round trip between Lightroom and Capture One, accept that only stars, labels, keywords and IPTC fields make the journey. Adjustments do not. Neither program can interpret the other's edits, and no setting changes that.

Five ways this quietly fails

None of these throw an error, which is what makes them expensive. You open the catalog and find eight hundred photos with no ratings.

The color label set does not match. A label is stored as a word, so if the receiving program looks for a different word, the swatch is blank. Narrative documents the version that catches people out: if Lightroom Classic is set to a language other than English, it "will prevent it from recognizing the colors". The fix is to build a matching Color Label Set under Metadata and save it as a preset. Imagen's docs flag the same class of mismatch.

Case sensitive drives. Documented by Narrative: "Lightroom writes the XMP files in lower case (.xmp), whereas Narrative writes them in upper case (.XMP)." On a normal drive nothing happens. On a case sensitive volume you get two sidecars per photo and each program reads its own.

Read only volumes. If your archive sits on an NTFS drive mounted read only on a Mac, the culling tool cannot write anything at all, ratings included. It will look like the software failed. The drive did.

Sidecars left behind. Copy raw files between drives by file type rather than by folder and you can strand the .xmp files, and now the .acr files, where they were.

The wrong write order. Two programs writing to the same sidecar without a save and read cycle between them means one silently wins. Do the pass in one program, read it into the other, then stop touching the first.

The routine, in the order that works

Once a job is on disk, this sequence holds up whichever tools you use. It follows on from the first hour after you get home, where the file structure gets set.

1. Back the card up twice before anything else touches the files.
2. If the shoot is already in Lightroom, run Save Metadata to File first so nothing you have done gets written over.
3. Do the selection pass in your culling tool, recording the result as stars or color labels if it has to travel, never as flags.
4. Bring it back: Read Metadata from File in Lightroom, or Load Metadata in Capture One with Prefer Sidecar XMP on.
5. Spot check ten photos against what you picked before editing. A one minute check beats finding out at photo four hundred.
6. Build the collection or album in the editing program. That is the one thing that was never going to cross over.

Every step above happens after you get home, which is the part nobody questions. It is worth questioning. The first pass is judgment work, and judgment does not need a desk. That is what we are building Kepla around: the first pass on your iPhone or iPad on the drive home, then the same shoot open on your Mac when two frames need comparing at full size. Kepla never deletes, moves or renames a file. It only marks which ones it picked, so every frame it set aside is one tap away. Lightroom integration is on the roadmap, designed against the rules on this page. The picking app is still being built. The booking page is live and free today.

FAQ