Skip to main content
johnrellis
Legend
April 1, 2026

P: Save Metadata To File sometimes writes huge .acr sidecars for JPEGs unnecessarily

  • April 1, 2026
  • 11 replies
  • 148 views

Save Metadata To File will unnecessarily write a huge .acr sidecar for a JPEG that’s been exported from LR and reimported. This affects users who regularly export with the Add To Catalog option. See here for a motivating use case:

https://www.lightroomqueen.com/community/threads/exported-jpgs-with-an-acr-file.54565/

 

To reproduce  on LR 15.2.1 / Mac OS 26.2:

 

1. Download and open the attached catalog, which contains a single raw, DSC08981.ARW, with Denoise applied.

 

2. Ensure the option Catalog Settings > Metadata > Include Develop Settings In Metadata is enabled (the default).

 

3. Select the raw and export it as a JPEG to the desktop, with Quality = 70 and the option Metadata > Include: All Metadata.

 

4. Import the exported JPEG with the Add Option.

 

5. Select the JPEG and do Metadata > Save Metadata To File. Observe that DSC08981.acr is created, about 10.3 MB (three times the size of the .jpg) (incorrect).

 

6. Delete DSC08981.acr from the desktop.

 

7. Edit DSC0891.jpg in Develop and change Exposure = -2.

 

8. Do Metadata > Save Metadata To File.  Observe that no .acr sidecar is created (correct).

 

9. Delete DSC08981.jpg from the desktop.

 

10. Select the raw and export it with Export With Previous.

 

11. Create a new catalog and import DSC08981.jpg from the desktop with the Add option.

 

12. Select the imported .jpg and do Metadata > Save Metadata To File.  Observe that no .acr sidecar is created (correct).

 

* * * 

 

In step 5, Save Metadata To File is incorrectly ignoring the develop setting xmp:AlreadyApplied = True and writing the .acr sidecar even though the contained Denoise result can never be used with the JPEG.  

 

The inconsistency in results between steps 5, 8, and 12 further reinforce there is no coherent design rationale or use cases for writing a .acr sidecar when xmp:AlreadyApplied = True. 

 

 

    11 replies

    johnrellis
    Legend
    April 2, 2026

    [View this post in your web browser. It contains formatting and images that don't appear in email.]

     

    @drtonyb If I Save Metadata to File [on the raw], I get this error: … I also tried Importing your test photo into one of my own test catalogs

     

    I tried the recipe with a fresh downloaded copy of the .zip on a different Windows 11 machine (real, not virtual) and it went as expected.  So I’ve tried it on a Macbook, Windows 11 Intel-on-Mac ARM virtual machine, and Windows 11 Intel.

     

    My only thought is that there’s an incompatibility between the Mac default compression of .zips and the utility getting invoked on your Windows for uncompressing .zips.  I’ve got the Windows 11 default uncompression.

    Legend
    April 3, 2026

    @johnrellis 

    I am using 7zip, so I tried the Windows unzip; that worked as expected.

     

    Started over again using 7zip again and it worked today. I hate it when that happens.

     

    johnrellis
    Legend
    April 3, 2026

    It’s the phase of the moon...

    Legend
    April 2, 2026

    @johnrellis 

    This is what I see when I open your test catalog:

     

     

    If I Save Metadata to File, I get this error:

     

     

    If I remove your test photo, then try to Import it again, the Import dialog cannot display a preview and this is what I get when I do try to Import it:

     

     

    I also tried Importing your test photo into one of my own test catalogs and got the same result.

    It’s all very weird because your test catalog doesn’t have any Previews, so LrC must be reading the RAW file and generating a preview when I open your test catalog as provided.

     

    My testing also shows that an Export as a TIFF doesn’t get any Sidecar Files, nor does it get a .acr file when Save Metadata to File is executed.

    johnrellis
    Legend
    April 2, 2026

    [View this post in your web browser. It contains formatting and images that don't appear in email.]

     

    @drtonyb My testing also shows that an Export as a TIFF doesn’t get … a .acr file when Save Metadata to File is executed.

     

    I observed that too. I didn’t include the details in the original bug recipe (need to keep them as simple as possible to increase the likelihood Adobe will successfully reproduce them).  


    But with files exported as TIFF or JXL, the Save To Metadata in step 5 doesn’t create a .acr but rather increases the size of the exported file by about 10 MB,  indicating that the computed AI results are being stored directly in the file rather than the .acr sidecar.  

    johnrellis
    Legend
    April 2, 2026

    @drtonyb, I’ve attached a screen recording showing steps 1-5 of the bug recipe on a near-virgin installation of LR 15.2.1 on Windows 11 (a virtual machine I use for testing).  I inserted some steps: After opening the catalog, I removed the raw and re-imported it, to show that it’s not corrupted and to get rid of the spurious “acr” shown in the Sidecars field of the Metadata panel (that was a holdover from how I created the catalog).

     

    I’m not sure what’s happening on your computer.

    Legend
    April 2, 2026

    @johnrellis 

     

    I’m having a problem with your test catalog and the whole premise of this bug.

     

    I can open your catalog on my Windows PC and see your test photo in LrC. I note that the Sidecar Files is xmp, acr, but your test catalog doesn’t contain the .acr file.

     

    I removed your test photo and tried to Import it. LrC can’t generate a preview in Import and if I Import it, LrC reports that it cannot read the file because it is corrupted.

     

    So, I did your test with my own file. Applied Denoise to a photo, Saved Metadata to File for the RAW so that it created .xmp and .acr files. After Exporting to a JPEG with Include: All Metadata, I note that the JPEG has Sidecar Files acr when Imported. I think this is wrong. A JPEG can’t use .acr data for Denoise; LrC can’t denoise JPEG files.

     

    I start over after removing my test photo and Importing it again. I Denoise, but don’t Save Metadata to File. Export to JPEG and Import; the Sidecar Files field is blank as expected.

     

    I start over again. Save Metadata to File for my RAW, close LrC, delete the .acr file and relaunch. Export to JPEG and Import it. The Sidecar Files field is blank. Save Metadata to File for the JPEG; the Sidecar Files field is now acr. Again, this is wrong, but worse is what you observe, a .acr file is created and attached to the JPEG. So the .acr file is associated with the RAW file and the JPEG file. Deleting the JPEG fro the drive with LrC deletes the .acr file too. That’s also bad.

     

    johnrellis
    Legend
    April 1, 2026

    [View this post in your web browser. It contains formatting and images that don't appear in email.]

     

    A workaround is to export non-raws with the setting Metadata > Include: All Except Camera Raw Info.  This ensures that develop settings are not included in the exported files.

     

    Note that the option Catalog Settings > Metadata > Include Develop Settings In Metadata Inside JPEG, TFF, PNG, and PSD files doesn’t affect the bug. This setting controls the behavior of Save Metadata To File and Automatically Write Changes Into Sidecar Files for files that are cataloged, not files that are exported.

    johnrellis
    Legend
    April 1, 2026

    Moderators, ​@Sameer K, please merge with this bug:

     

    johnrellis
    Legend
    April 1, 2026

    A bug causes Save Metadata To File (and Automatically Write Changes Into Sidecar Files) to write .acr sidecars for a non-raw that was exported/re-imported from a raw to which an AI command has been applied (AI masking, Denoise, Super Resolution, AI Remove). 

     

    In your situation, removing a color label from the exported/re-imported JPEG changes the Metadata Status to Has Been Changed. Automatically Write Changes then writes the changed metadata to disk, and the bug causes the .acr sidecar to also be written;

    Legend
    April 1, 2026

    This sounds like the same bug I reported, where removing a label on a JPEG or PSD will create an acr file. My report got ignored. :(

    johnrellis
    Legend
    April 1, 2026

    [View this post in your web browser. It contains formatting and images that don't appear in email.]

     

    @ExUSA My report got ignored. :(

    As a practical matter, bug reports posted here are much more likely to be acknowledged by Adobe and filed internally if you provide a precise, step-by-step recipe with sample files for reproducing the bad behavior. Only if many people complain about symptoms will developers investigate without bug recipes.

     

    Adobe’s policy is to keep the Bug Reports section of the forum reserved for acknowledged bugs (which I appreciate).  When they move a bug report to the Questions section, it’s not because they don’t believe the bug report is plausible, but rather they haven’t investigated and reproduced the behavior.

     

    Unfortunately, Adobe’s management policy of strictly limiting engineering resources means that developers have to prioritize their time investigating bug reports.  So they’ll prioritize reports of serious misbehavior coming from many people and bug reports that only take a few minutes to reproduce.

    Legend
    April 1, 2026

    The precise recipe was simple, remove a label from a JPEG or PSD file. We are already doing considerable unpaid labor for a multi-billion dollar company, if they don’t want to acknowledge problem reports then I’m not sure what use it is even posting them. :sigh:

    Legend
    February 27, 2026

    I wrote a Photoshop script to remove the label (since that ability is not available in the GUI) so I can bypass the whole problem and just deal with it before I save a file. I still think this is a bug but hopefully this is a viable workaround.

    try{
    if(ExternalObject.AdobeXMPScript == undefined) ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript');
    var docRef = app.activeDocument;
    var xmp = new XMPMeta(docRef.xmpMetadata.rawData);
    if(xmp.doesPropertyExist(XMPConst.NS_XMP,'Label')){
    xmp.deleteProperty(XMPConst.NS_XMP,'Label');
    docRef.xmpMetadata.rawData = xmp.serialize();
    }
    }
    catch(e){
    Window.alert(e + e.line);
    }

     

    Legend
    February 25, 2026

    Ok, I’ll rephrase. How do I limit writing XMP/ACR sidecars to RAW files (which I want) and not to JPEG and PSD files (which I don’t want)?

    C.Cella
    Legend
    February 25, 2026

    Disable these two option in Catalog Settings... > Metadata 
     



    In your workflow you still apply rating those the JPEG and PSD and that is enough to create the .xmp if you save them.

    So set up Smart Collection for RAW files only and save only those.

    You can apply rating to JPEG and PSD, this would though set them as “Has been changed”...don’t save them.





     

    Legend
    February 25, 2026

    I have the develop settings toggle set to off, but I do want sidecars written for my CR2 files. Just not JPEG and PSD.

    I label RAW files so I know which ones I want to retouch, and the label is assigned when I save the RAW file to a PSD and then JPEG. So I can’t avoid having finished files labeled unless maybe I write a Photoshop script to remove the labels (which I shouldn’t have to.)

    Bottom line, Lightroom shouldn’t write an 8MB acr file (I do NOT get an XMP) just because I changed the label on a 300k JPEG.