Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
15

P: Color Distortion When Opening Images saved from Facebook in Photoshop 26.5

Community Beginner ,
Mar 28, 2025 Mar 28, 2025

After updating to the latest version of Photoshop, we encountered an issue where images saved from Facebook from the previous year display color distortions when opened in the program. However, images saved recently from Facebook open without any issues and display correctly.

 

x 1.jpg

 

x 2.jpg42164006-9e1f-43ac-9db4-d4e548a8f222.jpg

pin-icon
Bug Investigating
TOPICS
macOS , Windows
11.2K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Apr 29, 2025 Apr 29, 2025

Hi all! Special thanks to our expert @Andrew Yoole and all others who provided sample images. The team is investigating this. In the meantime, you can use Camera Raw to render the images while opening them in Photoshop. 


Go to Photoshop(macOS)/Edit (Win) > Settings/Preferences > Camera Raw > File Handling > Set JPEG to 'Automatically Open all Support JPEGs' 

 


Thanks!

Sameer K

Translate
replies 154 Replies 154
154 Comments
Community Beginner ,
Apr 17, 2025 Apr 17, 2025

I’m experiencing a persistent issue with image rendering in Photoshop 26.5 on macOS Sequoia 15.4.1, using an M1 Max MacBook Pro (top spec, 2021). Whenever I import images—whether JPEG or PNG—they appear distorted in Photoshop: washed out colors, horizontal banding, and a noticeable shift in tones. The original files are totally fine and display perfectly in Preview and other apps.

Here’s what I’ve tried so far:

  • Fully uninstalled and reinstalled Photoshop (including removing preferences)

  • Disabled "Use Graphics Processor" in Preferences

  • Disabled OpenCL and any Metal rendering (when available)

  • Ran Photoshop in Rosetta mode (issue still persists)

  • Updated to the latest macOS (15.4.1 Sequoia)

  • Tested with multiple image formats and brand-new documents

  • Verified it's not template- or file-specific

  • Reset color settings to sRGB IEC61966-2.1

The issue has been ongoing for a few weeks and affects all images regardless of source. It also existed in the previous Photoshop version I had installed before updating to 26.5.

I’m currently installing Photoshop Beta to see if the issue is resolved there, but this feels like a deeper rendering bug specific to M1/M2 systems or the Sequoia update.

Would love any input or a timeline on a fix—this is seriously impacting my workflow.

Thanks!

Translate
Report
Adobe Employee ,
Apr 17, 2025 Apr 17, 2025

Hi @nwra! Welcome to the community!

I'm sorry to hear about the issues you're having with Photoshop. If the problem persists even after disabling "use graphics processor," it likely isn't related to your graphics card. Do you have any third-party plug-ins or fonts installed? Sometimes, outdated or incompatible ones can cause various issues.

Could you also share your System Info with us? You can find it in Photoshop under Help > System Info. Just copy the info to a text file and attach it to your response, or share it through Google Drive, WeTransfer, or another file-sharing platform.

Thanks a lot! 😊

Alek

*(If you mention me with an @, like @Aleke, I’ll get a notification and can respond faster.)*
Translate
Report
Explorer ,
Apr 17, 2025 Apr 17, 2025

On the left, you see Photoshop, which was exported from Lightroom in AdobeRGB. On the right, you see Lightroom in the Develop Module with GPU enabled. I will also attach the screenshots from the programs, including Luminar, which I have also exported directly from Lightroom in the AdobeRGB color space. Luminar renders the image correctly, unlike Photoshop. The effect is also noticeable in the histogram, as the values are different in Photoshop and Lightroom.

Translate
Report
Explorer ,
Apr 17, 2025 Apr 17, 2025

Side By Side.jpg

Translate
Report
Explorer ,
Apr 17, 2025 Apr 17, 2025

Upon further inspection, I discovered that my Photoshop image had not been zoomed in to 100%. To rectify this error, I have re-processed the image and presented both versions at 100% zoom. This will ensure that you can accurately assess the differences and avoid dismissing my findings.Side by Side 2.jpg

Translate
Report
Community Beginner ,
Apr 17, 2025 Apr 17, 2025

HI @Aleke

Thank you for the reply. I was able to fix this issue by installing and using Photoshop Beta and disabling use Graphics Processor, but it did not work in regular Photoshop. 

 

No third-party plug-ins or fonts installed. 

Here is my system info, attached. 

Translate
Report
Explorer ,
Apr 17, 2025 Apr 17, 2025

Upon opening files in ProPhoto or sRGB in Photoshop, the image renders correctly (although this does not occur in AdobeRGB). However, during soft proofing, I observe discrepancies between Photoshop and Lightroom, even when the same ICC profile is selected. Consequently, this workaround becomes ineffective, as I am unable to post online or print images using ProPhoto and cannot soft proof for my respective media output. I believe there should be no variation in image rendering between software modules referencing the same ICC profile, particularly for generic profiles such as sRGB, which is commonly used for internet proofing. Although I have tried other profiles such as the one from Nevada Art Printers where I have my images printed, I have been using these profiles for years with no problems until I acquired a MAC M1/M2.

To illustrate this, I have attached screenshots of an image opened in ProPhoto using “Edit In” to open in Photoshop. In both programs, I have selected sRGB for soft proofing, and I have captured screenshots of each.

 

LIGHTROOM  

Screenshot 2025-04-17 at 1.56.07 PM.png

 

PHOTOSHOP

Screenshot 2025-04-17 at 1.56.15 PM.png

Translate
Report
Explorer ,
Apr 17, 2025 Apr 17, 2025

 

I am currently encountering a similar issue when attempting to open images in Photoshop. The degradation I am experiencing is particularly evident in the shadow areas of the images, where the tones appear lighter and washed out, resulting in a significant loss of detail. Additionally, I have observed discrepancies in the rendering of my images between Lightroom and Photoshop during the soft proofing process.

In my experience, the Develop module in Lightroom displays the images accurately when the GPU is enabled, as does the Library module when HDR is activated. However, this accurate rendering does not translate to Photoshop when exporting from Lightroom using the AdobeRGB color profile. The images render correctly in Photoshop when exported in either the sRGB or ProPhoto color spaces. While I appreciate this outcome, I prefer not to utilize either of these profiles for printing purposes.

To address this issue, I could consider opening the images in ProPhoto prior to conducting soft proofing for my selected output profile, although I have noted variable results when soft proofing in sRGB, AdobeRGB, or my print lab’s specific .ICC profile. This inconsistency has led to considerable complications, which appear to resemble your situation.

Have you contemplated exporting images to Photoshop utilizing the “Edit In” function while varying your color profile among Adobe98, sRGB, and ProPhoto? If you have not yet pursued this option, I recommend doing so and sharing whether you encounter similar results. Furthermore, I suspect there may be an underlying issue concerning how Adobe is leveraging the GPU on M1 and M2 Mac systems.

For your reference, here is a link to the thread I initiated regarding my issue: https://community.adobe.com/t5/photoshop-ecosystem-discussions/shadows-washed-out-when-opening-in-ph....

Translate
Report
Community Expert ,
Apr 17, 2025 Apr 17, 2025

What monitor profile are you using here? That last screenshot shows a ProPhoto file displayed without any color management. That's how it looks when the numbers in the file are just sent straight to screen uncorrected.

 

And that happens when you proof to the monitor profile. So that's why the monitor profile used could give a clue about what's happening.

 

If you're seeing this without proofing, then something is very wrong. Then your monitor profile isn't used at all.

 

I think you should keep proof out of it for now. That just introduces yet another variable. No one has ever dismissed what you're seeing, I don't doubt it's real. But for troubleshooting you need to reduce the number of variables as much as possible. You also need to go back to the most basic premise possible and work from there.

 

In this case, the basic zero point is that if things display differently, it's because different/wrong numbers are sent to screen.

 

There are three fundamental links in the color management chain:

the document profile

the monitor profile

the conversion from the former to the latter, performed in the GPU.

 

If all these three steps are in correct working order, the image has to display correctly, by definition. The document profile is rarely the problem, as long as it's there. So that leaves the GPU and/or the monitor profile. Which one can be hard to determine, but simple tests are to replace the monitor profile (and relaunch the application), and to disable the GPU in preferences, returning color management to the CPU in the traditional way. If either of those gives a result, then you know where to look further.

 

A more remote possibility is that Lightroom isn't encoding the image it sends to Photoshop (via ACR) correctly. We have seen that happen when the versions have been out of sync, and default camera profiles have changed. In that case ACR may not have the correct camera profile available, and substitutes another. I'm just mentioning this as a possibility, but it's moot if all versions are on the same level.

 

These are just the general principles. I'm travelling with only a laptop now, so I can't get into specifics.

Translate
Report
Explorer ,
Apr 17, 2025 Apr 17, 2025

thank you for your response.

I have uploaded images without softproofing as well as one with soft proofing enabled. Please reference the first set of images as they were created using your chosen method explained to me in an alternate forum. The blacks in those images are clearly different, although it is more difficult to see on my iPod than on my monitor so you may have difficulty on you laptop. I think its pretty clear though.

I have opened photoshop and lightroom with several different monitor profiles. The reason you are seeing these images in Prophoto is because for this specific test I was match I g te monitor profile to the workspace. I have done it many ways including the way you have described in an alternate forum:

  • take a screenshot from an Adobe RGB file that has dark values but no clipping
  • assign the monitor profile, then convert it back to Adobe RGB
  • the two histograms should now be identical”
  • They are not identical          

     

Translate
Report
Adobe Employee ,
Apr 17, 2025 Apr 17, 2025

Hey @avalent

 

Totally hear you—this kind of thing is frustrating, especially when you're just trying to get work done and an update throws a wrench in it. A bug has already been filed with the team. I've also added more context to the bug based on your experience with artifacting and color. Please follow this thread for updates. In the meantime, if the issue wasn’t present in the previous version of Photoshop, I recommend rolling back to that version for now: https://adobe.ly/3YCdiGW

 

Please also remember that it's okay to express your frustrations and that we appreciate constructive feedback; however, we will enforce the Community Guidelines.

^CM

Translate
Report
Explorer ,
Apr 17, 2025 Apr 17, 2025

Here is a raw file in Lightroom Classic, opened directly into Photoshop with "Edit In".

 

As you can see, they DO NOT display Identically

Screenshot 2025-04-17 at 4.12.27 PM.pngScreenshot 2025-04-17 at 4.13.16 PM.png

Translate
Report
Community Expert ,
Apr 17, 2025 Apr 17, 2025
quote

The reason you are seeing these images in Prophoto is because for this specific test I was match I g te monitor profile to the workspace.      

    

By @TheBeatnikHimself

 

That disables all color management, and of course it will be wrong. If source and destination profiles are the same, nothing happens, the document numbers are just sent directly to screen uncorrected. That's the definition of no color management. If doesn't even matter what that profile is; as long as they're the same, no color management occurs.

 

There is never any need to match profiles. That defeats the whole purpose, they're not supposed to match. Document profile and monitor profile are two different things, serving different purposes. The monitor profile describes the monitor's native color space. That's why you use a calibrator to measure the monitor's response, so that the profile can be an accurate description of the monitor in its current state.

 

I'm sure you know all this, so apologies for stating the obvious. But this needs to be very clear.

 

I think you need to simplify things considerably if you want to get to the bottom of this. You're introducing lots of variables that only confuse the issue. 

 

Stick to a standard color space that is not the same as your monitor profile. And make sure your monitor profile is built on the monitor's actual and current behavior, based on actual measurement. Don't "experiment" with monitor profiles - except for testing the integrity and validity of the profile, which you can do by temporarily replacing it with a standard profile that is reasonably close to the monitor's native color space (sRGB, Adobe RGB or Display P3, depending).

 

You say you have been using a Spyder - is the profile made by the Spyder software?

 

You keep stressing that Lightroom/Photoshop display differently. Yes, I understand that. I never doubted that. But there is a reason for it, and that reason is either a bad monitor profile, or a problem in the GPU driver. Or both. There is nothing inherent in Photoshop that does this. I can not reproduce this.

Translate
Report
Explorer ,
Apr 17, 2025 Apr 17, 2025

You keep focusing on the differences in a single example, but I’d like to clarify why I presented it that way. It was part of a test requested by Adobe Support, and I shared the results here for reference. I've also included other examples using my calibrated monitor profile and asked you to reference them, which you still haven't done.

 

I sent you the exact same information you've already received. In your previous response, all you stated was: 

 

"Here is a raw file in Lightroom Classic, opened directly into Photoshop with 'Edit In.' As you can see, they display absolutely identically."

 

I made the same post, yet you won't address it as you continue to dissect my issue based on just one example from the Adobe Support test. This approach is simply unhelpful. You haven't provided any new insights and continue to dismiss the clearly articulated situation I've laid out.

 

If you truly understand what’s happening, I expect you to share that knowledge. Please refrain from reiterating the same example without contributing anything of value to this conversation. If you can’t add to the discussion, I would appreciate it if you would stop posting in this forum.

Translate
Report
Explorer ,
Apr 17, 2025 Apr 17, 2025

Have you tried reproducing the issue on a Mac M2?

Translate
Report
Explorer ,
Apr 17, 2025 Apr 17, 2025

The last post I made was example of images that I opened in a color space that was not the same as my monitor profile. This profile was created less than two weeks ago using hardware calibration methods. As I have been doing for years! What else do I have to do to get you to listen? This is ridiculous!

 

Translate
Report
Explorer ,
Apr 17, 2025 Apr 17, 2025

I have also run these test on a completely separate machine with a different monitor and calibration hardware/software. I am getting the EXCACT same results of that machine. How could it be a corrupted .ICC profile if this is the case.

 

I'm sure you're just going to gaslight me again. My perception of the problem is the problem right?

 

Translate
Report
Explorer ,
Apr 18, 2025 Apr 18, 2025

That's okay, feel free to moderate however you find fit, just as I'll air my grievances as an All Apps Suite paying customer and being forced to make almost monthly visits to the Adobe Community whenever I update an app and something breaks.

Translate
Report
Community Expert ,
Apr 18, 2025 Apr 18, 2025

It seems that whatever I say here you take it the wrong way, so I'll just stop. 

 

I never doubted what you see is real, and I never intended to offend you, which I apparently have. I've only been trying to narrow down what is the actual root cause.

 

Someone else needs to take over here.

Translate
Report
Explorer ,
Apr 18, 2025 Apr 18, 2025

You have done nothing but deny my findings and offer your own confirmation bias. You did that here as well as the other threads you have been a part of.

You never even referenced the MANY examples I posted that were created I the way you have suggested, just denied the single example you didn't accept. 

Translate
Report
Adobe Employee ,
Apr 18, 2025 Apr 18, 2025

Hey @nwra! Thanks for sharing your system info. It looks like your scratch disks are running low on space, which can cause issues, especially with large files. Could you try freeing up some space on your scratch disks and see if that helps? You can follow this guide: https://adobe.ly/42uRpvX

Thanks a bunch! Let me know if you need any more help!

Alek

*(If you mention me with an @, like @Aleke, I’ll get a notification and can respond faster.)*
Translate
Report
Explorer ,
Apr 18, 2025 Apr 18, 2025

I need help.
And the so called support representative just abandon my case without even looking at thenseveral examples of the issue I uploaded to this forum. My case has not been resolved yet no help is offered by the Adobe Community. 

This is wrong!
https://community.adobe.com/t5/photoshop-ecosystem-discussions/shadows-washed-out-when-opening-in-ph...

Translate
Report
Explorer ,
Apr 18, 2025 Apr 18, 2025

Hello,

 

I am experiencing an issue when opening images in Photoshop when using the AdobeRGB color space. When opening the image into Photoshop via “Edit In,” the darker areas of the image lose detail. However, when opening the same image in Luminar Neo via “Edit In,” the image appears as expected.

 

Below is a raw file in Lightroom Classic, and that same file opened directly into Photoshop with “Edit In.”

 

As you can see, they display differently....

Lightroom:

lightroom develop-Monitor Profile.png

Photoshop:

photoshop-Monitor profile.png

Side by Side

Side by Side Monitor profile.jpg

 

Currently, I am utilizing a Mac M2 Studio to create these images. These images were generated using Screenshot, which assigns the current calibrated monitor profile to them. Additionally, I have uploaded screen captures using the AdobeRGB(1998) monitor profile to eliminate the possibility of a corrupted ICC profile causing the issue.

 

I have also included a video demonstrating my steps to recreate the issue. The video also shows me opening AdobeRGB images into Luminar Neo from Lightroom via “Edit In” without any loss of detail in the shadows. Please watch the video, as it contains additional information.

 

To verify the issue, I conducted a separate test using a different monitor and calibration equipment. I utilized a completely different computer, still a Mac M2. The results were the same in all conditions tested.

 

Over the past two decades, I have honed my skills as a working photographer and photo editor. I currently manage a successful education and photography business, while simultaneously consulting and editing images for various external clients. The technical issues we have been experiencing with Adobe software have resulted in a significant financial burden, with our combined businesses experiencing daily losses ranging from $2,000 to $5,000. Should Mac M2 computers fail to interoperate with our systems, the cost of replacing these devices alone would exceed $15,000. This figure is compounded exponentially across all the accounts I represent. Consequently, time management, effective communication, and professionalism are paramount in addressing this urgent matter.

 

I thank you for your persistence in this matter.

 

Link to Screenshots, Video, and System Info Below:

https://drive.google.com/drive/folders/1ydFT8MM2p_ECdiXPfA-JMY5gwSGJxmQT?usp=share_link

 

Translate
Report
Community Expert ,
Apr 18, 2025 Apr 18, 2025

Post merged with your existing thread on the same issue. Please do not start multiple threads on the same issue.
Dave

Translate
Report
Explorer ,
Apr 18, 2025 Apr 18, 2025

This thread was , moved without my permission. The previous advisor was dismissive of my findings and I had hoped to resolve this issue with a different representative. 

Translate
Report