Can Lightroom save virtual copy develop settings to XMP sidecar files?

Asked 9/20/2011

8 views

2 answers

0

I use Lightroom with “save metadata to XMP” because I prefer having develop settings stored alongside the image rather than relying only on the catalog. However, virtual copies seem to lose their edit settings if the catalog is deleted.

Can Lightroom write virtual copy settings to an XMP sidecar? Can one XMP file store multiple edit versions for the same image? If not, what are practical workarounds for preserving virtual copy edits outside the catalog?

Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0

Photography Stack Exchange contributor

14y ago

2 Answers

5

It is not currently possible to either save multiple .XMP files per image nor to save multiple versions of settings in a single .XMP file. Here are a couple workarounds:

  • Instead of creating a virtual copy, make one set of adjustments and save a snapshot in the Develop module, then go on and make the other set of adjustments. This is kind of clunky, but you can quickly get to that snsapshot.

  • Once you have one version of the file, save it out as a DNG. You now have two version of the file.

Originally by user89. Source · Licensed CC BY-SA 4.0

user89

14y ago

0

AI Answer

Generated from our catalog & community — verify before relying on it.

Lightroom does not normally support saving multiple sidecar XMP files for one image, and virtual copies are primarily catalog-based. A single image won’t get separate standard XMP sidecars for each virtual copy.

Workarounds mentioned:

  • Use snapshots instead of virtual copies. Make one edit, save a snapshot in Develop, then create another look and save that too. Snapshots can be written into the metadata.
  • One answer notes that if you save snapshots on the original and virtual copy, then use “Save Metadata to File,” the XMP may contain both snapshots/settings entries, which can preserve both versions.
  • Export virtual copies as original/DNG files so each version becomes its own real file with its own metadata. You can rename them and stack them with the original if needed.
  • Another simple option is to create a DNG copy after finishing one version, giving you two separate files to edit independently.

So: virtual copies themselves are not truly portable outside the catalog, but snapshots or exporting separate files are the main ways to preserve alternate edits.

UniqueBot

AI

14y ago

Your Answer