🎨
← Back to Guides

Web Safe Colors: Are They Still Relevant in Modern Web Design?

· Tags: web-safe-colors, color-palette, web-design, css, color-history

Web Safe Colors: Are They Still Relevant in Modern Web Design?

If you have been designing for the web long enough, you remember the days of the "web safe" color palette. The 216 colors that promised consistent display across every monitor and browser. But in an era of HDR displays, wide gamut screens, and millions of colors, do web safe colors still matter?

The short answer is: mostly no, but with important exceptions. This guide covers the history, the math, and the modern relevance of web safe colors.

What Are Web Safe Colors?

Web safe colors are a set of 216 colors developed in the mid-1990s that were guaranteed to display consistently across different computer systems, browsers, and monitors. At the time, most computers could only display 256 colors simultaneously (8-bit color), and the web safe palette ensured that colors would not dither — a process where the browser approximates unavailable colors by scattering pixels of available colors in a pattern.

The name "web safe" came from the guarantee that these colors would appear the same on a Windows PC with a VGA monitor, a Macintosh with a built-in CRT, and a Unix workstation with an X11 display.

The 216-Color Palette: How It Works

The web safe palette consists of colors where each RGB component can only take one of six values: 0, 51, 102, 153, 204, or 255. In hex, these are: 00, 33, 66, 99, CC, FF.

Since each of the three RGB channels has 6 possible values, the total palette is 6 x 6 x 6 = 216 colors.

A web safe hex color always looks like this: #336699, #FFCC00, #996633.

The pattern is easy to spot: each two-digit hex pair must be one of the six values (00, 33, 66, 99, CC, FF). The color #33AACC is web safe only if every pair is in that set — so #33AACC is not web safe because AA is not one of the six values.

The 216 colors exclude 40 of the 256 total system colors because different operating systems reserved different ranges for system UI elements. The web safe palette was designed to work on Windows, Mac, and Unix systems simultaneously.

The Problem Web Safe Colors Solved

In the 1990s, most consumers had monitors set to 8-bit color depth (256 colors). When a website specified a color outside the browser's palette, the browser would either:

  1. Dither the color — Mix pixels of available colors to approximate the intended color. The result was a speckled, noisy appearance.
  2. Map to the nearest color — The browser would snap to the closest available color, often producing unexpected results.

Web safe colors eliminated this uncertainty. If you stuck to the 216, what you designed is what users saw — on any system, any browser, any monitor.

Are Web Safe Colors Still Relevant in 2026?

When They Absolutely Do Not Matter

For general web development today, web safe colors are essentially obsolete:

Display technology has moved far beyond 8-bit color:

  • Every smartphone made in the past 15 years supports 24-bit color (16.7 million colors) or higher
  • Modern displays support 30-bit (1 billion colors) or even HDR with 10-bit panels
  • Even budget displays comfortably cover the sRGB color space

All modern browsers dither correctly:

  • Modern rendering engines handle color approximation smoothly
  • Anti-aliasing and subpixel rendering eliminate the dithering artifacts of the 90s

The color management ecosystem is mature:

  • ICC color profiles ensure accurate color reproduction across devices
  • CSS and HTML support the full sRGB gamut natively
  • Modern design tools (Figma, Sketch, Adobe XD) default to full sRGB color

User expectations have shifted:

  • Users expect rich, vibrant, nuanced colors
  • Flat, limited palettes look dated and low-quality to modern eyes
  • Design trends favor depth, gradients, and subtle color variation

When They Still Matter (Rarely)

There are niche scenarios where web safe colors are still relevant:

1. Legacy Systems and Embedded Displays

  • Point-of-sale terminals, ATMs, ticketing kiosks
  • Industrial control panels and embedded Linux displays
  • E-ink readers and specialized display hardware
  • Some public information displays in transportation and government

2. Projection Displays

  • Some projectors have limited color gamuts
  • Conference room projectors often display at lower color depths
  • High ambient light in projection environments reduces perceived color variation

3. Retro and Pixel Art Design

  • Purposeful retro aesthetics that mimic 90s web design
  • Pixel art games with intentional color limitations
  • Nostalgic or "brutalist" web designs that evoke early internet style

4. Telecommunications and Low-Bandwidth Applications

  • Some specialized terminals in logistics and field service
  • Applications written for extremely constrained environments

For the vast majority of web developers, none of these scenarios apply.

Modern Alternatives to Web Safe Colors

Rather than limiting yourself to 216 colors, use these strategies for cross-platform color consistency:

1. Work in the sRGB Color Space

sRGB is the standard color space for the web. All browsers and most displays (excluding professional wide-gamut monitors) are calibrated to sRGB. By working in sRGB, you ensure your designs appear as intended on the widest range of devices.

2. Use Design Tokens with Sensible Boundaries

Modern design systems define color scales with 10-12 stops rather than the full spectrum. This provides the consistency that web safe colors promised, but with better visual results:

--blue-50: #EFF6FF;    /* Lightest */
--blue-100: #DBEAFE;
--blue-200: #BFDBFE;
--blue-400: #60A5FA;
--blue-600: #2563EB;
--blue-800: #1E40AF;
--blue-900: #1E3A8A;   /* Darkest */

3. Use Perceptually Uniform Color Spaces

OKLCH and LAB provide consistent perceptual spacing that the web safe palette could not. Two colors with the same lightness value in OKLCH will appear equally bright — something the web safe palette never guaranteed.

4. Test on Real Devices

Instead of relying on a theoretical palette, test your colors on actual devices:

  • A MacBook Pro or iMac with a high-quality display
  • A mid-range Windows laptop
  • A recent Android phone and iPhone
  • An external monitor or projector if your audience uses them

The Legacy of Web Safe Colors

While the web safe palette is technically obsolete, its legacy lives on in important ways:

  • Constrained palettes are still good practice — Limiting yourself to a curated set of colors (like 10-12 in a design system) produces more cohesive designs than using arbitrary colors everywhere, even if those colors are not web safe.
  • The math is still elegant — The 6 x 6 x 6 = 216 formula is a beautiful example of working within technical constraints, a skill that remains valuable in web development.
  • Cross-platform testing matters — The core concern that drove web safe colors (consistent display across platforms) is still critical. We just solve it differently now.

Conclusion

Web safe colors are a fascinating piece of web development history, but they are no longer relevant for modern web design. Today's displays, browsers, and color management tools give you the full sRGB spectrum to work with — and beyond, with wide gamut and HDR support.

Instead of limiting yourself to 216 colors, focus on building thoughtful, accessible, and brand-consistent color systems. Use perceptually uniform color spaces like OKLCH, test on real devices, and ensure accessibility through contrast verification. The web safe palette is history — learn from it, but do not design by it.

Use our free online color converter to check whether any hex color is web safe and convert between all modern color formats.