Why do sRGB and ProPhoto versions look different in Photoshop but the same in a browser?
Asked 4/3/2021
7 views
2 answers
0
I'm trying to understand color management in Photoshop. If I have one image in sRGB and another converted to ProPhoto RGB, a color-managed browser can make them appear the same. But in Photoshop they may look different, especially on a wide-gamut display.
What's the difference between Assign Profile and Convert to Profile here, and is there any true "round-trip" workflow between sRGB and ProPhoto RGB that will preserve appearance both in Photoshop and in a browser?
I'm also confused about how an untagged image is handled versus one with an embedded profile on a display that covers more than sRGB.
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
5y ago
2 Answers
2
I think there's a broad misconception here, but I'm not sure where to start to 'fix' that, so here are some rambling thoughts so far…
Bullet points in the question have been edited since I answered this, so my numbers no longer match the question. The broad scope is still the same.
- I tested the images from the linked website in four browsers, Left to right in the screenshot below, Safari & Chrome on Mac, Edge & Chrome on Windows. They all look pretty close. Both computers are colour profiled, though my Windows computer is never used for anything mission-critical so it's likely to have drifted over time. The Windows half of the screenshot is also over RDC, so that's another potential pitfall. Allowing for that, I think they're 'close enough'.
Also, both images taken from the site & opened in Photoshop look identical. The sRGB picture is actually an untagged RGB, so will be assumed to be sRGB. The ProPhoto seems to contain the correct profile.
That they appear identical is to be expected on a calibrated machine using an image originally from an sRGB source which I can only guess that was. My displays can display Adobe RGB but not full ProPhoto, so I wouldn't be able to see what may have been lost outside that gamut.
This all depends on how you "change" the profile…
Convert to profile will attempt to preserve a "visual match", even though ProPhoto can encompass a larger gamut [actually larger than any monitor can display or any eye can see].
Assign profile never works visually, because it doesn't attempt any compensation. It would be more useful to re-attach a known profile lost from an image.
Example of assigning sRGB to a ProPhoto image - colour is completely borked.

This may indeed be similar to the description from the linked site - "[If it] appears to have a dark blue/magenta sky with yellowish sand, then your browser is not color-managed."Once you have done your first conversion down from ProPhoto to sRGB, you ought then to be able to cycle round from one to the other seeing no change [you might get drift over time, this is not something I've ever needed to test].
So as this all ought to work in theory… we have to try figure out where you went wrong.
That you see different colours in Photoshop tells me Ps is set up wrongly.
The most common mistake is that people assign their screen icc profile as their working space.
Secondly, that on import, automatic profile conversion is done… to that wrong working space.
This leads to multiple erroneous compensations, one in Ps, the other as the image is displayed to your screen
You first need to make sure you don't have this set up in your workflow.
Aside from that, all this is going to be far more accurate if your screen is first accurately profiled - otherwise everything is just guesswork. Just dialling in the manufacturer's profile is not accurate enough for colour work.
However, no matter whether your profiling is correct or not, having it correctly assigned in your workflow should prevent this apparent drift between images.
Originally by user57929. Source · Licensed CC BY-SA 4.0
user57929
5y ago
0
Generated from our catalog & community — verify before relying on it.
A color-managed app should make an sRGB-tagged file and a properly converted ProPhoto-tagged file look essentially the same on screen, because both are converted from their embedded profile to your display profile for viewing.
Key point:
- Convert to Profile changes the RGB numbers to preserve appearance.
- Assign Profile does not convert color; it only changes the meaning of the existing numbers, so the image usually changes appearance.
An untagged file is ambiguous. Browsers often assume sRGB, but Photoshop can display it differently depending on color settings, which is why untagged files are a common source of confusion.
Your monitor being wider than sRGB does not mean Photoshop is "working in monitor space." Photoshop still uses the document profile and then converts for display. Also, your screen cannot display full ProPhoto RGB.
There is no special cyclical trick needed. The correct workflow is:
- Make sure the source file has the correct embedded profile.
- Use Convert to Profile when changing between sRGB and ProPhoto.
- Embed the profile when exporting.
- Avoid repeated conversions, because gamut clipping/rounding can make round-trips imperfect.
So yes, appearance can be preserved in managed software—but only when profiles are correct and embedded.
Recommended products
UniqueBot
AI5y ago
Your Answer
Related Questions
In Photoshop, is Adobe ACE more accurate than Microsoft ICM for color profile conversions?
Should I edit RAW photos in ProPhoto RGB or stick with sRGB for web use?
Why do colors look oversaturated in Chrome on a wide-gamut monitor?
Why do sRGB JPEGs look oversaturated in non-color-managed programs on a wide-gamut monitor?
How should color management be set up on Windows for an Adobe RGB monitor?
