Skip to main content
Known Participant
Nov 22, 2026 3:56 AM UTC
Answered

Bridge to Camera Raw to Photoshop workflow disrupted after updates

Since my update to Photoshop 2026 v 27.11.1,  and Bridge 2026 v 16.0.8.10 this week, Photoshop is reopening my .NEF (Nikon Raw) files strangely:  instead of showing the Camera Raw dialog, the images are opening just as they were opened the previous time in Photoshop.  I often open large number of images in Photoshop as part of my sorting workflow, doing minimal adjustments to exposure but little else the first time around; when I reopen to prepare a finished version of the file, I want to start over in Camera Raw.

And sometimes they are not opening even with the previous minimal adjustments, but are opening as if cropped (which they were not), and doing that repeatedly, even if I do a deliberate 'open with camera raw' from the Bridge menu and make sure any crop was cleared.  Several times they they opened up with the original exposure adjustment despite having redone the exposure settings when forcing open via Camera Raw.   

What might be going on here?

Photoshop and Bridge 2026 versions above
MacOS 26.7.3

    Exciting_Miracle2353Correct answer
    Participating Frequently
    Nov 22, 2026 5:53 AM UTC

    What's most likely happening here is that Camera Raw is remembering the settings it already saved for each file. When you adjust a raw file, Camera Raw writes those adjustments into a small sidecar .xmp file next to the .NEF, and every later open reapplies them — exposure, crop, everything. So reopening a file brings back your earlier edits instead of a fresh start, and the phantom crop keeps returning because the crop lives in that same sidecar file.

     

    To start over on a file, clear the stored settings first. In Bridge, select the files, right-click, choose Develop Settings and then Clear Settings. Or open the file in Camera Raw and reset it to its as-shot state before reopening it. If you want a fresh look at a file without wiping anything, copy the .NEF into a new folder first — the copy has no sidecar attached to it, so it opens untouched.

     

    If clearing the settings doesn't stick, the old values are probably being read from somewhere stale. Try purging Bridge's cache for that folder (Tools, then Cache, then Purge Cache for Folder), and check that the .xmp sidecars next to your images aren't locked or read-only, so Camera Raw can actually update them. It's also worth checking in Camera Raw Preferences where your settings are saved — sidecar .xmp files or the Camera Raw database — since that decides where the old values are hiding.

     

    Since this started right after the 27.11.1 and 16.0.8.10 updates, resetting Camera Raw preferences is worth trying too, and check whether a newer Camera Raw update has appeared since you installed those versions.

    2 replies

    debunixAuthor
    Known Participant
    Nov 22, 2026 6:26 AM UTC

    This was quite a weird sequence of events.  

    I updated Camera Raw, Photoshop, and Bridge all at the same time last week, to the latest versions.  

    Mac OS Preview.app opens the files as full sized images, so it’s something about the workflow sequence.  

    Clearing develop settings did cause the files to open in Camera Raw, and that undid the exposure adjustments, but not the weird cropping.  They were still opening as if cropped.  

    I’d cleared the cache for some other errors earlier today (couldn’t see files added to the folder being displayed in Bridge);, but the sequence of clearing develop settings; and again clearing the cache; and then reopening the same files finally fixed it. 

    For the moment, it’s fixed….will check back if it recurs.

    Thank you for the tip about ‘Develop settings’, I’ve never used that feature before.

     

     

    I

    Translate
    Exciting_Miracle2353Correct answer
    Participating Frequently
    Nov 22, 2026 5:53 AM UTC

    What's most likely happening here is that Camera Raw is remembering the settings it already saved for each file. When you adjust a raw file, Camera Raw writes those adjustments into a small sidecar .xmp file next to the .NEF, and every later open reapplies them — exposure, crop, everything. So reopening a file brings back your earlier edits instead of a fresh start, and the phantom crop keeps returning because the crop lives in that same sidecar file.

     

    To start over on a file, clear the stored settings first. In Bridge, select the files, right-click, choose Develop Settings and then Clear Settings. Or open the file in Camera Raw and reset it to its as-shot state before reopening it. If you want a fresh look at a file without wiping anything, copy the .NEF into a new folder first — the copy has no sidecar attached to it, so it opens untouched.

     

    If clearing the settings doesn't stick, the old values are probably being read from somewhere stale. Try purging Bridge's cache for that folder (Tools, then Cache, then Purge Cache for Folder), and check that the .xmp sidecars next to your images aren't locked or read-only, so Camera Raw can actually update them. It's also worth checking in Camera Raw Preferences where your settings are saved — sidecar .xmp files or the Camera Raw database — since that decides where the old values are hiding.

     

    Since this started right after the 27.11.1 and 16.0.8.10 updates, resetting Camera Raw preferences is worth trying too, and check whether a newer Camera Raw update has appeared since you installed those versions.

    Translate