Why do my RAW product edits disappear when I send the photo to another editor?

Identify where the edit instructions live

A proprietary camera RAW file usually retains the original sensor-derived image data. Lightroom Classic's Develop adjustments are instructions interpreted by its processing engine, not permanent changes to those original pixels.

Adobe documents that Lightroom Classic stores adjustments in the catalog by default. Saving metadata externally allows supported applications to access relevant settings without opening the original catalog.

For proprietary RAW files, XMP metadata is commonly stored in a sidecar file beside the original. DNG and certain rendered formats can store metadata internally.

Importantly, Lightroom Classic 15.0 introduced additional ACR sidecars for some heavier edits, including masks and certain AI operations. Do not assume that copying only an XMP file preserves every adjustment in a current Lightroom workflow.

Determine what the recipient actually received

Ask for the exact file list rather than relying on a statement that the RAW was sent.

1. Identify the original camera file and its filename.
2. Check whether the sender saved current metadata to the file or sidecars.
3. Inspect whether matching XMP and, where applicable, ACR sidecars accompany the source.
4. Confirm that the recipient kept the related files together.
5. Open the files in the intended receiving application and compare the result with an approved rendered reference.

A missing sidecar can explain why the recipient sees the unedited RAW. However, a present sidecar does not guarantee identical rendering. The receiving application must support the relevant adjustment definitions and processing behavior.

Do not rename files independently during the handoff. Preserve the source and associated metadata relationships.

Separate editable settings from approved appearance

There are two different handoff goals. The recipient may need editable RAW adjustments, or may need a finished product image that looks like the approved version.

For editable adjustments, use the documented metadata-saving route and check application compatibility. For an exact visual reference, also provide a rendered TIFF or other appropriate output with recorded color management.

A rendered derivative preserves a particular interpretation of the edits, but it does not retain the same RAW-stage editing flexibility. Conversely, a RAW with sidecars may be editable but render differently in unsupported software.

If the recipient sees the exposure correction but not a mask, inspect sidecar completeness and feature compatibility before assuming that the entire handoff failed.

Illustrative diagnosis: a retouched perfume photograph

Hypothetical editorial scenario; no Lightroom or receiving-editor operation was performed. A perfume photograph is adjusted in Lightroom Classic 15.0. The edit includes exposure correction, white balance and a local mask around the bottle label.

The sender initially transfers only the proprietary RAW. The recipient opens it and sees the original exposure without the approved corrections.

The sender then saves metadata and identifies both an XMP and an ACR sidecar associated with the file. The receiving application supports the relevant Adobe adjustments in this hypothetical example.

After the complete handoff, the recipient sees the intended exposure and label treatment. A separately rendered TIFF is retained for visual comparison.

The completed diagnosis is incomplete transfer of adjustment metadata, not damage to the original RAW. This example does not imply that every non-Adobe editor will reproduce the same masks.

Verify the handoff before closing the task

Reopen the transferred files in the recipient's actual application. Compare the overall tone, product color and one local edit with the approved reference.

If only part of the treatment appears, identify the unsupported or missing adjustment. If nothing appears, inspect file association and metadata-saving status first.

Keep the original catalog and RAW source independently protected. A sidecar is an exchange mechanism, not a complete catalog backup.

CartVisual does not synchronize Lightroom catalogs or sidecars. Use the verified rendered reference when creating downstream visuals, and keep the editable source package for future revisions.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• Adobe — Save metadata to external sidecar files: Official documentation updated October 27, 2025, explaining XMP and ACR sidecars. Lightroom Classic 15.0 and later can create additional ACR sidecars for heavy edits.
• Adobe — Metadata basics and actions: Explains catalog-stored adjustments, external metadata writing, and differences between proprietary RAW and DNG metadata storage.
• Adobe — Advanced metadata actions in Lightroom Classic: Documents synchronization with Camera Raw and Adobe Bridge and metadata-conflict behavior. Does not guarantee compatibility with unrelated RAW editors.