Why does an sRGB JPEG with an embedded ICC profile look faded in my browser?
Asked 1/7/2016
9 views
2 answers
0
After processing an image in Photoshop, I save it as a JPEG with the option “ICC profile: sRGB IEC61966-2.1” checked. I expected that embedding the sRGB profile would make the image display correctly on the web, since sRGB is the standard color space for browsers. However, the JPEG looks faded in my browser. Why can an image tagged as sRGB still appear wrong, and what is likely happening?
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
10y ago
2 Answers
1
Here's my guess. You note in a comment that "If the browser uses the profile, it gets sRGB, if not, then it defaults to sRGB." But, that's not necessarily the case. The browser may say "If there's a profile, I'll treat the photo as color managed" and "If there's no profile, show it in the monitor's native colors". That native space may be sRGB, and for a long time, that was a fine approximation of reality, but isn't necessarily true especially if you have a fancy new monitor.
There's a page here: http://www.gballard.net/psd/go_live_page_profile/embeddedJPEGprofiles.html which goes into detail. The top demo lets you mouse over to see the difference between Adobe RGB and sRGB in taggged and untagged versions; scroll down to see different color spaces compared to the same color space untagged. On my laptop (with a terrible yet color-profiled screen) and Firefox, Adobe RGB shows a more visible jump, but untagged sRGB is definitely also different from tagged. (While tagged Adobe RGB and sRGB both appear indistinguishable.)
I also notice that on my system, the untagged sRGB image shows up slightly darker and with more contrast. That sounds like it might be what you describe when you say the one with the embedded profile is "faded". So, I think bottom line is that the version with the ICC profile is probably actually correct; if you want it to be "punchier", adjust your processing accordingly.
Originally by user1943. Source · Licensed CC BY-SA 4.0
user1943
10y ago
0
Generated from our catalog & community — verify before relying on it.
Embedding the sRGB ICC profile is usually the right choice for web images, but correct display still depends on the browser and display pipeline actually handling color management properly.
What may be happening is:
- Some browsers/apps treat tagged images as color-managed but display untagged images in the monitor’s native color space.
- On a wide-gamut or non-sRGB monitor, “native” is not the same as sRGB, so tagged and untagged images can look noticeably different.
- Some software is inconsistent: a few apps ignore sRGB profiles, mishandle them, or strip/change profile-related metadata.
So even if your JPEG is correctly saved as sRGB, it can still look faded if the browser or another application is applying color management differently than you expect.
In short: saving as sRGB with the profile embedded is still best practice for the web, but browser/app behavior and your monitor’s native gamut can make the image appear faded or different.
Recommended products
UniqueBot
AI10y ago
Your Answer
Related Questions
Does embedding an ICC profile in a JPEG include the full profile data?
How do web browsers display a JPEG with no embedded color profile?
In GIMP, should I convert a TIFF tagged sRGB IEC61966-2.1 to GIMP built-in sRGB before exporting JPEGs for the web?
Should web images keep their ICC color profile, or is it safe to remove it?
Do all modern browsers and operating systems color-manage web images, including Adobe RGB?