I’m Dudley Storey, the author of Pro CSS3 Animation. This is my blog, where I talk about web design and development with , and . To receive more information, including news, updates, and tips, you should follow me on Twitter or add me on Google+.

web developer guide

my books

Book cover of Pro CSS3 AnimationPro CSS3 Animation, Apress, 2013

my other blogs

Massive Head Canon: Intelligent discussion of movies, books, games, and technology.

my projects

A Sass color keyword system for designers. Replaces CSS defaults with improved hues and more memorable, relevant color names.

CSSslidy: an auto-generated #RWD image slider. 3.8K of JS, no JQuery. Drop in images, add a line of CSS. Done.

tipster.ioAutomatically provides local tipping customs and percentages for services anywhere.

Seaside city on a cliff

Color for Web Designers: Understanding sRGB

design / color

Estimated reading time: 2 minutes

The desire for the color of elements to appear consistently on the web across different devices and screens has long been a quest for web designers. However, with the vast majority of people unaware of how to properly color calibrate their monitors beyond crude and often ignorant manipulation of brightness and contrast controls, the quest always seemed a pipe dream.

This is beginning to change. The first hurdle – a broad agreement on a standardized color space and gamma – was reached in 1996, in the form of a standard called sRGB. Device and application support for the sRGB color profile – including digital cameras, scanners, printers, HD televisions, monitors, and design tools like PhotoShop – is now widespread.

Color management is also supported in modern browsers, including Firefox 3.6 and higher, Safari 5+ (include Mobile Safari) and Internet Explorer 9 (although IE’s support comes with one important caveat). Chrome and Opera both lack support for color management as of this writing.

The browser color management process could be simply described as this:

  1. The browser reads the monitor settings, to understand how the user’s system displays color. (This is the part that IE currently skips).

  2. The browser reads the image file, and attempts to determine its color profile (i.e. how it was displayed on the original creator’s system). “Untagged” images (those without an embedded color profile) are assumed to be sRGB.

  3. By understanding the color profile of both the image and the monitor, the browser can map one to the other to preserve the best image quality.

If any of these steps is skipped, the color in the final image is likely to be compromised: it will usually appear over saturated or washed-out. To avoid this issue, the suggested workflow for color management on the web is:

  1. Work in whatever RGB color space you prefer (Adobe RGB is a general recommendation), but always convert to sRGB for export. (Adobe PhotoShop 5.5 does this by default in the Save For Web option).

  2. You may wish to tag your JPEG image (“Embed Color Profile”) for greater color profile support across browsers. The downside of this is that doing so will usually increase the file size by a few kilobytes. GIF and PNG files will be tagged during export from PhotoShop by default.

comments powered by Disqus

This site helps millions of visitors while remaining ad-free. For less than the price of a cup of coffee, you can help pay for bandwidth and server costs while encouraging further articles.