0

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,

  • 1
    IIRC, most browsers will interpret images as sRGB, regardless of an embedded profile (save for the few that support colour management); thus, converting to sRGB and saving as an untagged image is probably as good as you'll get on the web, while still supporting all browsers. – Tristan Seifert May 28 '16 at 19:23
  • This is my opinion too based on the research that I've made analysing the picture content shown on different well designed/known websites (e.g. here, here, or here and so on) but I just want to hear other thoughts maybe some cons? – user124853 May 28 '16 at 20:41
  • @TristanSeifert Please see meta.photo.stackexchange.com/questions/4655/… – Michael C May 29 '16 at 4:25
1

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)

  • Thank you for your feedback.Indeed,Firefox supports color management and I've used that extension to change the configuration in about:config section more easily.Regarding the latest versions of Chrome browsers, I suppose that there are still some limitations source here and here. IE11 should not be used for color critical work.Although it understands both ICCv2 and ICCv4 profiles, it does not use the monitor profile, which means you cannot rely on what you're seeing. Source mentioned above. – user124853 May 29 '16 at 9:32
  • Regarding the native gamma value (2.4 in my case), creating 1D LUT for video card, forcing the display to use 2.2 instead of native gamma value, will only cut the colour depth. More details here; – user124853 May 29 '16 at 9:36
  • Please note that Photographylife dot com article reffers to v22 of Chrome (2012) it's a little bit outdated. More than that Phil Newberry's comment (april 28, 2016) also I think that it's not so accurate simply because the same tagged sRGB picture will look different using latest version of Chrome vs. Using Photoshop in Proof color mode (monitor profile) please have a look. – user124853 May 29 '16 at 9:51
  • 2
    Normally viewing an image in PS takes the monitor's profile into account when doing CM. Choosing proof color mode (monitor profile) is something totally different. It's the same as Proof Setup -> Custom, selecting your monitor profile and leaving Preserve RGB Numbers checked, showing how it would look on that monitor if viewed with an application that doesn't do CM. Try it with an AdobeRGB image and you'll see much less saturated colors just like when you use an app without CM. I've exported the sRGB tagged image as a jpeg and opened it in Chrome. It looked the same as in PS. – D. Jurcau May 29 '16 at 11:59
  • Well, I've made a comparation, opening the file in Pshop and leaving it as is (tagged sRGB) without proof colors applied; As we can see, there is still a slightly color shift between what we are able to see in Chrome (top)/ Firefox (bottom) assuming that Firefox will apply the system default profile made by DisplayCAL and Photoshop. – user124853 May 29 '16 at 12:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.