That would depend on what your monitor is capable of and also your own particular editing/viewing goals and also on what software you want to use with whatever monitor profile you might make. I’m still experimenting to figure out what works best with my own monitor/goals/software. I’m putting together an article with some test images and procedures/considerations for profiling monitors, but I’m not quite ready to load the article up to my live website.
Speaking of software that you might want to use when viewing images, here are two screenshots illustrating some peculiarities of Firefox/Palemoon (they both seem to handle monitor profiles the same way), vs Google Chrome:
As shown below, when the system monitor profile is a LAB LUT profile, Firefox/Palemoon and Google Chrome both use sRGB (presumably their own built-in version of sRGB) as the monitor profile. I confirmed this by opening the image in GIMP-2.9 and telling GIMP to use sRGB as the monitor profile. The sky is not supposed to be saturated turquoise blue, but rather “normal” blue sky blue:
As shown below, when the system monitor profile is an XYZ LUT profile, Firefox/Palemoon show correct colors, though deep shadow texture is flattened compared to what GIMP-2.9 shows. But Google Chrome shows, um, something else:
The two sets of screenshots above use:
- Google Chrome Version 63.0.3239.84 (Official Build) (64-bit), with no changes to whatever chrome does by default to color-manage images.
- Pale Moon 27.4.1 and Firefox 52.5.0 with settings as per Viewing photographs on the web
Obviously Chrome really is picking up on the system monitor profile, else the image in Chrome would look the same in both screenshots. And just as obviously, it’s not doing the right thing for LUT profiles.
Is there a way to tell Chrome to use particular color management settings, such as what Firefox allows using about:config?