Skip to main content
Inspiring
July 15, 2026

Washed colours when opening any image in Photoshop after updating to 27.9.0 (Beta) Mac release.

  • July 15, 2026
  • 9 replies
  • 143 views

 

PROBLEM :  Images have Washed colours when opening any image in Photoshop after updating to 27.9.0 (Beta) Mac release.

SEVERITY : URGENT.

  1. Ps Preferences > Performance > Use Graphics Processor is Checked.
  2. Ps Preferences > Technology Previews > Precise colour management for HDR display is Unchecked.
  3. View > Proof colours Unchecked.

DETAILS :

Opening any image or duplicating any image with an embedded icc profile (jpg, psd png etc.), it appears the embedded icc profile is not read.

Updating seemed to have reset all Custom Color settings.

After update I found Color Management Policies off, Profile Mismatches Ask When Opening UNchecked, and Missing Profiles Ask When Opening Unchecked.

My custom Color Settings were not preserved through the update.

My Saved Custom Color Settings are not found under the pop-up Settings.

Reseting Working space to RGB: Adobe RGB(1998) and Color management Policies to Preserve Embedded Profiles and checking all “Ask When Opening” does not seem to have an affect and colours continue to be washed when opening files.

(Note: desaturate monitor colours by 20 % was and remains unchecked).

 

EXPECTED RESULT :

icc profile is read and applied, or default Monitor is applied in respect to Custom Colour Profile Choices.

 

SOLUTION 1 : (Temporary ) Menu select,  View > Proof Setup > Monitor. Profile Colours are restored and the  image is as expected. But Proof Setup must be selected each and every time for each image opened or duplicated.

SOLUTION 2 : (Temporary ) Menu select,  View > Proof Colours. Profile Colours are restored and the image colour is as expected. But Proof Colours must be selected each and every time for each image opened or duplicated.

SOLUTION 3 : (Semi-Permanant) Photoshop Preferences > Performance > Uncheck Use Graphics Processor. Restarting the Photoshop app does not appear to be necessary. All color profile choices appear to be respected. Opening or image duplication respects the Custom Colour Profile Choices. But Photoshop is crippled with this choice and should not be considered a permanent solution.

Why is Photoshop not applying my Custom Colour Profile Choices?  

 

… Attached image has proof colors checked because Monitor (default ) is not respected. Duplicating the image colours get washed out again, the icc profile (adobe RGB) is not respected at all. My monitor profile, an EIZO CG2700x with self calibration and Adobe RGB 1998 are practically indistinguishable.

Thanks in kind for your help in this ===urgent matter. 

    9 replies

    CShubert
    Community Manager
    Community Manager
    July 20, 2026

    Hi all, please reference this thread: 

    The team has an update to fix this and should be out soon. Thank you for your patience.

     

    Thanks,

    Cory - Photoshop Product Manager

    ralph hasenohr
    Inspiring
    July 19, 2026

    same here.

    Participant
    July 17, 2026

    Same problem here.  Went back to 27.8 (Creative Cloud=> Apps=>Photoshop Beta=>  . .  .=> Other Versions => Install27.8. Color has been restored. BTW had the same problem when loaded 27.9.

    Participant
    July 16, 2026

    Go to settings → performance  and disable Use Graphic processor than restart. 

    Participant
    July 16, 2026

    Same happening for me even with the latest beta (27.20.0) —looks like files are being displayed with linear gamma, instead of normal 2.2 for sRGB & AdobeRGB

    dianer_macperson
    Inspiring
    July 16, 2026

    I went back to 27.8 till it’s fixed. No time for trouble.  Had the same problem. 

    Participant
    July 16, 2026

    Same issue! Still no permanent solution?

    Participant
    July 16, 2026

    Same issue, same dramas. Reverted back to Photoshop 2025 to be able to work.

    Also used Marcus’s CMD + Y  except have to do it everytime I open an image.

    Inspiring
    July 16, 2026

    Thank you for your comment. It’s nice to know it’s not “It’s just me” thing. I guess I’ll be downgrading too.

    Participant
    July 15, 2026

    Same issue here.
    Quick solution for me was to hit CMD + Y.