Fitting a culling app next to Lightroom or Capture One

Adding a selection tool should shorten your workflow. Often it lengthens it, because the tool builds its own library and now two programs disagree about which frames you picked. This is how to avoid that: the three handoff patterns, the exact settings in Lightroom Classic and Capture One, where selection belongs in the pipeline, and a convention that stops your tools fighting.

The second library is the actual cost

Every serious photo program wants to be the place your photos live. It builds a database, points it at your folders, and starts recording what it knows about each frame. That is fine when you have one. It gets expensive when you have three.

The symptom is familiar. A shoot is marked up in the culling app. Lightroom shows the same folder with nothing flagged. You re-import, or worse, you re-do the pass, and the twenty minutes the tool saved you get spent finding out where your decisions went. The subscription was never the cost. The duplicate library was.

The good news is that this is a solved problem, and the solution is boring: pick one place where decisions are recorded, make sure everything else reads from it, and never let two programs write to it at once. Everything below is the detail of doing that in a real stack.

Three ways a selection tool can hand off

Whatever it says on the marketing page, a culling tool does one of three things when it finishes. Knowing which one you bought tells you most of what you need.

The first pattern is the one to want. XMP is not glamorous, but it is the shared bus that every editor already listens to, and the way it works is covered in more depth in our guide to photo metadata. Aftershoot's own support documentation is unusually clear about this: it tells users that with the right settings "your edits, Star Ratings, and Color Labels transfer seamlessly between the apps" via XMP files. Narrative Select takes a similar view, listing "Ship to Lightroom, Photoshop & Capture One" on every tier including its cheapest.

The third pattern is the one that quietly costs you. If a tool can only give you a folder of exported copies, your originals and your selections have gone their separate ways and nothing downstream can put them back together.

Sitting next to Lightroom Classic

Lightroom Classic keeps everything in a catalog, and by default it does not tell the outside world anything. Three settings change that.

• Catalog Settings, Metadata tab, Automatically write changes into XMP. Off out of the box. Switch it on and your ratings, labels and flags get written out as you work.
• Photo, then Save Metadata to File, or Command S. The manual push, for a folder you want to hand over right now.
• Metadata, then Read Metadata from File. The step almost everyone forgets. After the culling app has written its verdicts, Lightroom will keep showing you the catalog's stale version until you tell it to look.

Adobe's own documentation explains why sidecars exist at all: for proprietary raw formats, XMP is not written into the original file and goes into a separate .xmp file instead, while JPEG, TIFF, PSD and DNG get it embedded. From the October 2025 release, version 15.0 also writes an .acr sidecar for heavy edits and masks, keeping the .xmp light. If you move files by hand, that is now two companion files per raw.

Two rules keep the catalog single. Import a folder once and only once: a second import of the same path is the classic route to two rows for one frame. And when Lightroom shows the small metadata conflict badge on a thumbnail, read it rather than clicking through, because the wrong choice there overwrites the pass you just made elsewhere.

Worth factoring in before you buy anything: Adobe now ships Assisted Culling inside Lightroom Classic, labeled early access, switched on in Catalog Settings under Metadata. It scores subject focus, eye focus and eyes open and marks frames as Selects or Rejects. It is not a reason to skip a dedicated tool, but it does mean the honest comparison has moved. What Lightroom still cannot do is covered in where Lightroom runs out of road for selection.

Sitting next to Capture One

Capture One is stricter, and in a way that works in your favor. Its documentation states flatly that "Capture One will never write metadata to source files; all metadata changes are done via proxy file." Your adjustments are recorded in .cos files in a Session, or in the database in a Catalog, and never in XMP. So no culling tool can trample your edits by writing a sidecar. It can only ever change the labels.

The setting that matters is Auto Sync Sidecar XMP, in Preferences, with three options described in Capture One's own words:

• Full Sync "will update the XMP sidecar files with any metadata changes or will create the XMP sidecar file if it is not present. Any information in the XMP that is not present in Capture One will be loaded. It is a two-way synchronization." Capture One warns this can hinder performance on large collections.
• Load "will load the information from any XMP sidecar file into the .cos (session) or cocatalogdb (catalog). It will not update the XMP sidecar file with changes from Capture One." One way in, which is exactly what you want if the culling app is the author of record.
• None turns it off, leaving the manual Load Metadata and Sync Metadata commands.

One structural difference catches people out. Capture One has star ratings and color tags, and no pick and reject flag in the Lightroom sense. If your culling tool speaks in flags, decide up front what a flag becomes on the Capture One side, usually five stars or one specific color tag, and set it once. Our notes on flags versus stars and color labels are worth a read before you choose.

Photoshop is not a library, and Bridge is your referee

Photoshop belongs at the end of the chain, not in the middle of it. It opens one file, does something irreversible and expensive to it, and writes a new one. It has no opinion about your shoot. Anything that treats Photoshop as a stage in a selection workflow has misunderstood the tool, and the PSB files it can produce are on Adobe's list of things that do not sync.

Adobe Bridge is more useful than its reputation. It is a free download, it reads XMP directly, and crucially it holds no catalog of its own. That makes it the neutral referee for any handoff you are not sure about.

Where selection belongs in the running order

Most integration pain is really ordering pain. Two operations, ingest and renaming, must happen before anything makes a decision, because both of them break the filename link that sidecars depend on.

1. Ingest and rename, once. One tool owns this. Photo Mechanic is the traditional choice and it is very good at it, applying names and IPTC at copy time, as we set out in Photo Mechanic versus Lightroom for culling. Whatever you use, the names your files will carry forever are set here. See a naming system that survives.
2. Back up, twice, before any judgment. Two copies on separate media before a single frame is assessed.
3. Selection pass. Now, and not before, the culling tool runs, writing its verdicts as standard metadata.
4. Editor reads the metadata. Read Metadata from File in Lightroom Classic, or Load or Full Sync in Capture One.
5. Edit, export, deliver. From this point one program is in charge and nothing else touches the folder.

Get the order wrong and the failure is silent. Cull first and rename second, and every sidecar is orphaned with no error message. The post-shoot ingest checklist is the short version to tape to your desk, and the device-to-device version of the same trap is in syncing picks between devices.

Write down who owns which field

The last piece is a convention. Ratings, flags and color labels are a shared namespace, and if two tools both use stars for different meanings you will lose an evening working out which is which. Assign each field an owner and one meaning, then never change it. Here is a convention that works, offered as a starting point rather than gospel.

Two details make it hold. Color label names have to be spelled identically on every machine or they arrive as an unnamed color. And a machine pass should write to a different field than you do, so you can always sort your judgments from the software's, and undo one without touching the other. If you want the fuller version of getting selections into Lightroom cleanly, we wrote it up in exporting selections to Lightroom.

This is also the design constraint Kepla is being built around: a first pass that marks frames and writes nothing else, with every original left exactly where it is, never deleted, moved or renamed, so your editor stays the one library that matters. Those apps for iPhone, iPad and Mac are still in development and we will say so until they ship. The booking page is live and free today.

FAQ