To get started with a web safe colors chart, browse its 216 swatches or enter a valid 3-digit or 6-digit HEX code to find the nearest channel-level match.
The chart is a working reference for the historical browser-safe palette, not a general guarantee that a color is readable, printable, brand-safe, or universally displayable.

Set the right goal for the color
Begin by deciding whether the task calls for a legacy color, a deliberately low-color design, or a way to study the old RGB cube. An ordinary current brand palette or data visualization rarely needs to be limited to these 216 entries unless the brief explicitly asks for that constraint.
The palette comes from an era when many displays could show only 256 indexed colors at once. A shared cube reduced the chance that a browser would dither a page color into a speckled approximation. The W3C's historical Introduction to CSS documents browser-safe colors and the six evenly spaced channel levels.
The W3C WAI 216-color picker example independently demonstrates a 216-choice picker, but neither reference turns palette membership into an accessibility or design-quality certification.
Modern computers, phones, and browsers normally support far more than 216 color combinations, so use the chart as a transparent reference, matcher, and copy aid rather than as a modern compatibility switch.
Browse the grid and copy a starting swatch
Use direct browsing when you want to see the historical palette or need a color that is already part of it.
- Open the Web Safe Colors Chart and let the complete interactive grid load.
- Scan the 216 tiles. They are generated in a deterministic red-major, green-middle, blue-minor order, so red changes slowest, followed by green and then blue.
- Select the tile you need. The compact grid may show only a shortened three-character hint, but the selected swatch exposes its complete six-digit HEX value in the larger result area; its accessible label and title also contain the full value and RGB triplet.
- Use the copy control to copy the full HEX code. If the browser denies clipboard access, select the visible code manually instead.
- Record the intended use of the color, such as a background, border, illustration, or historical mockup, before moving on to the foreground pair.
Browsing is the better starting route when the color itself is the goal; matching is more useful when you already have a HEX value that must be brought into the cube.
Match an existing HEX to the cube
The matching route converts one input into a predictable palette entry without changing the chart's simple channel-level method.
- Copy the source color as a valid three-digit or six-digit hexadecimal value.
- Paste it into the chart's HEX input field. A three-digit value expands under normal CSS shorthand rules before matching begins.
- Select Find match. The tool rounds each 8-bit RGB channel independently to the nearest allowed multiple of 51.
- Read the returned six-digit HEX value and use it as the palette reference for the next step.
For #3470d0, the red byte 34 is 52 decimal and snaps to 51, or 33 in hexadecimal; the green byte 70 is 112 and snaps to 102, or 66; and the blue byte D0 is 208 and snaps to 204, or CC. Reassembling those three levels produces #3366CC.
This is nearest matching in the ordinary, unweighted RGB cube, not a perceptual color-difference calculation. Another swatch may look closer to a person even when it is not numerically closest; a specialist workflow can compare in Lab or OKLCH, account for an ICC profile, or optimize a palette across an entire image. For a separate comparison, use the Color Difference Calculator.
Read the six-level channel structure
Each color in the palette combines one red, one green, and one blue value. Every channel is restricted to six levels, and the three channels vary independently, producing 6 × 6 × 6, or 216, unique entries.
| Decimal channel value | HEX pair |
|---|---|
| 0 | 00 |
| 51 | 33 |
| 102 | 66 |
| 153 | 99 |
| 204 | CC |
| 255 | FF |
That structure explains why every match remains inside the cube: the matcher rounds each 8-bit channel to one of these six values before recombining them. The chart does not assign subjective color names, and it does not imply equivalence to Pantone, CMYK inks, physical material samples, or calibrated device output.
Choose the route that fits the job
Start with the result you need rather than running every available action.
| Job | Chart route | Result |
|---|---|---|
| Inspect the historical palette | Browse and select a tile | The selected swatch and its complete six-digit HEX value |
| Bring an existing color into the cube | Enter a valid HEX and select Find match | The nearest palette entry by independent channel rounding |
| Build a deliberately retro set | Browse and copy selected tiles | A constrained set of chosen palette entries |
| Teach or audit the RGB cube | Inspect the grid and channel levels | A transparent view of the six allowed values in each RGB channel |
| Check text readability | Choose colors first, then use a contrast checker | A pair-specific assessment, not a web-safe guarantee |
For a multi-color project, keep a record of each selected code and the role it plays. That prevents a convenient cube match from quietly becoming the entire brand palette when the original brief did not require it.
Apply the selected HEX in a web project
- Confirm the color's role in the layout, including whether it serves as text, a background, a border, or a non-text graphic.
- Copy the complete six-digit HEX value from the chart's result area rather than relying on the compact three-character tile hint.
- Paste the value into the relevant CSS declaration, and use the full six-digit form consistently so the source is easy to audit.
- Preview the color in the actual page context and on the target devices, paying attention to adjacent colors, image content, and hover or active states.
- Pair the color with the other foreground and background colors in the design before moving to a final accessibility check.
The chart does not turn a CSS value into a production-ready palette or judge the page as a whole. If the project is not intentionally constrained, continue with modern colors outside the 216-color cube.
Check the final color pair for readability
Web safe does not mean accessible for text. Contrast depends on the foreground and background together, along with font size, font weight, and the accessibility criterion that applies.
After applying the colors, open the Color Contrast Checker, enter the actual foreground and background values, and review the result against the relevant WCAG AA or AAA rule. Repeat the check for every real pairing rather than assuming a famous historical palette is automatically legible.
If clipboard access was denied earlier, the manually selected code still gives you the value needed for CSS and the separate contrast check. The correct workflow is therefore chart for selection, followed by a real pair for contrast.
For a deeper look, see How to Check Results After Using an HTML Color Names Chart.
For a deeper look, see How to Use a Web Safe Colors Chart Correctly.