I have a situation and I am interested to find your point of view. We have a calibrated monitor at D6500, tone curve as measured ~2.4, white level ~90cd/m2 and a tagged sRGB / untagged sRGB image founded on the web.
Using Firefox v46.01 browser + Color management 0.5.3.1 Extension as attached, the browser will use the default OS profile (which I think that is the new monitor .icm created/installed by the calibration software, DisplayCAL set as system default or sRGB(?)—please correct me if I'm wrong).
It's well known that not every browser have support for color management. Having said that, is that a bad approach to save and use for web sRGB untagged images in order to have the same viewing result covering also those browsers that doesn't support color management (e.g IE or even Chrome—the latest versions)?
Thanks,
Answer
While the saying that browsers are not color managed was true a few years ago, it's no longer the case.
Firefox supports color management by default for tagged images (source). The extension you're using is simply a front-end for changing the configuration more easily, it's not the actual color management engine.
Chrome is also color managed: https://photographylife.com/chrome-color-management The image in the test mentioned on the website displayed ok in IE11 as well.
So, as long as you're not using a higher gamut profile (e.g. AdobeRGB) and saving the image untagged, it should be displayed ok.
I'd be more worried however of the impact of calibrating your monitor to gamma 2.4. This makes you view the images differently than anyone else who has calibrated their monitor to 2.2 (the sRGB gamma curve is approximately 2.2)
No comments:
Post a Comment