Skip to main content
defaultmo40spq2ztwr
Participant
June 14, 2026
Question

Copy edit settings

  • June 14, 2026
  • 2 replies
  • 17 views

There seems to be a bug in Lightroom when using the "Copy Edit Settings" feature. Even when I uncheck all settings and select only the Denoise tool to copy, Lightroom still pastes every single adjustment (like exposure, color, and contrast) onto the new image. It is completely ignoring my specific selection in the "Copy Settings" checkbox menu and overwriting all the original settings on the target image.

    2 replies

    Srishti Bali
    Community Manager
    Community Manager
    June 15, 2026

    Hi ​@defaultmo40spq2ztwr 

     

    Thanks for reaching out, and I'm sorry to hear you're experiencing this issue. To help us investigate further, could you please share a few additional details?

    • Has this issue started happening recently, or has it been occurring for some time?
    • Please share your System Info from Lightroom (Help > System Info) by copying and pasting the report here.
    • Does the issue occur with a specific image or catalog, or does it happen across multiple images/catalogs?

    As a troubleshooting step, please try closing Lightroom and relaunching it while holding down the Shift + Option (macOS) or Shift + Alt (Windows) keys. Let us know if that helps.

    If the issue persists, please share a short screen recording showing the behavior. This will help us better understand and investigate the problem.

     

    @JohanElzenga are you having the same issue at your end too?

    Thanks, Srishti Bali | Community & Engagement Strategist, Digital Imaging | Adobe
    JohanElzenga
    Community Expert
    Community Expert
    June 15, 2026

    @Srishti Bali I can’t check it right now, but I do not think I have the issue. I was (and still am) typing this on my iPad and I thought I remembered have seen a report like this. Maybe I remember that incorrectly.

    -- Johan W. Elzenga
    JohanElzenga
    Community Expert
    Community Expert
    June 15, 2026

    I believe this is a known bug.

    -- Johan W. Elzenga