How should I manage the returned variants when a Lightroom Classic photo is sent to an external editor?

Define the Review Case

This workflow applies to Lightroom Classic's external-editor process. The supplied documentation does not establish that the same choices or returned-file behavior apply to Lightroom, Lightroom on the web, or Lightroom on mobile, so do not transfer this procedure to those clients without separate documentation.

Before sending an approved product image, preserve the approved original and work from a test copy or a clearly identifiable working selection. Record the selected choice in the job notes: Edit A Copy, Edit A Copy With Lightroom Classic Adjustments, or Edit Original. That record makes the later review meaningful because the returned result can be judged against the intended source effect.

1. Identify the source photo and its current Lightroom Classic state.
2. Write down the external-editing choice before confirming the send.
3. Keep the source identifiable throughout the round trip.

Choose the Correct Route

Choose Edit A Copy With Lightroom Classic Adjustments when the external editor should receive a rendered copy that already reflects the current Lightroom Classic adjustments. The external work then begins from that rendered appearance, while the source remains identifiable.

Choose Edit A Copy when the external editor should receive a copy but the current Lightroom Classic adjustments should not be applied as part of that rendered handoff. This is a different starting point from the adjusted-copy route, so record the choice rather than describing both results simply as an edited photo.

Choose Edit Original only when working on the original is deliberate. Its source effect differs from both copy choices. Adobe's documentation notes format restrictions for Edit A Copy and Edit Original, but the supplied source details do not specify those restrictions or which formats are affected. Before using either route, consult the linked Adobe guidance for the applicable format restrictions; do not infer that a returned file replaced the source merely because the external editor opened successfully.

Inspect the Return

When the external editor returns control to Lightroom Classic, locate the returned file and inspect its name and format. Where visible in your catalog, also note its catalog location and stack relationship. A returned edited copy may have an -Edit name and may be stacked. Those signs can help identify a variant, but the name or stack alone does not prove that the source was replaced.

Compare the returned image with the source at the decision points that matter for the product asset: subject identity, intended external changes, and whether the rendered starting appearance matches the recorded route. The review should leave the returned variant independently identifiable from the source.

1. Locate both the source and returned file in Lightroom Classic.
2. Compare their names and catalog entries.
3. Inspect whether a stack is present, without treating stacking as proof of replacement.
4. Stop and investigate if the returned file cannot be distinguished from the source.

Illustrative Exercise

Illustrative exercise: use a fictional test product image named Mug-front and a second fictional input named Mug-shadow. Send Mug-front through the external editor using Edit A Copy With Lightroom Classic Adjustments, and send Mug-shadow using Edit Original. These are illustrative inputs, not results from a real software test.

For Mug-front, check whether the returned edited copy is distinguishable, for example by a name containing -Edit, and whether the source remains identifiable. Pass this branch only when the returned variant can be reviewed separately from the source. If the copy cannot be distinguished, stop before export and resolve the catalog or naming ambiguity.

For Mug-shadow, review the source/result relationship separately because Edit Original has different behavior from the copy choices; do not assume a separate returned file. Pass only when the team can establish what happened to the original and identify the result of the edit. If that relationship cannot be established, stop rather than treating the result as an approved replacement.

Approve and Export

Use the returned variant for review only after its identity and relationship to the source are clear. Keep the approved original available, and export the reviewed returned file only when its catalog identity matches the recorded external-editing choice and the acceptance condition is met.

Editorial diagnosis: if repeated reviews fail because filenames or stacks are ambiguous, the workflow problem is traceability rather than image quality. Improve the recording and identification step before sending more assets. Do not solve ambiguity by deleting the catalog, disabling security, or mass-replacing files.

Use this question’s review worksheet

The sample rows are fictional exercise data. Preserve the example, save a working copy and record your own inputs, observations and decisions. The example is not a test receipt.

Fictional/manual external-edit return worksheet (CSV)