Avoid mistakes with an HTML color names chart by checking the 148 standardized CSS keywords against their exact HEX and RGB mappings rather than guessing from a swatch. The reference covers opaque sRGB values and keeps valid aliases as separate entries, so identical color values do not look like accidental duplicates.
The main risk is treating a color name as more than an identifier. A keyword can be valid CSS while still being unsuitable for a particular contrast pair, an inaccurate description of brightness, or a poor substitute for a brand token. A chart can verify what a keyword means; it cannot choose the right design or infer an unknown color from appearance alone.

What the chart actually contains
Use the HTML Color Names Chart as a code-value reference for the 148 opaque named-color keywords standardized by CSS Color. These are commonly called HTML color names because they can be used in CSS styles for HTML pages, but the names themselves are CSS keywords.
Each row contains one standardized keyword, one lowercase six-digit HEX value, one decimal RGB value, and a rendered swatch. The count refers to unique keyword entries, not 148 visually distinct colors, because standardized aliases remain separate rows. Filtering the chart never changes a mapping or converts a value into another color space.
The dataset follows the named-color definitions in the W3C CSS Color 4 named colors. The MDN named-color reference provides a useful cross-check for CSS syntax and browser-facing documentation.
Rows remain in the specification table order, which the implementation presents in ASCII alphabetical order by keyword. That order is useful for finding a specific entry, but it is not a hue scale, lightness ranking, or palette recommendation. Never assume that nearby rows are perceptually distant or that a later name is lighter.
Check a color name before using it in CSS
- Open the HTML Color Names Chart and locate the filter control.
- Enter one of the three supported lookup forms: part of a CSS color name, an exact six-digit value such as #00ffff, or a complete RGB string such as rgb(0, 255, 255). Keyword fragments are case-insensitive, while a search beginning with # uses exact HEX matching.
- Review the matching row. Confirm the standardized keyword, swatch, lowercase HEX value, and decimal RGB value before copying anything.
- Click the HEX value to request a clipboard copy. The chart reports success only after the browser resolves that request; if clipboard permission is denied, the visible keyword, HEX, and RGB text remain available for manual selection.
- Use the copied value where your CSS property accepts a color. The clipboard contains only the visible HEX token: no hidden format, capitalization change, CSS declaration, or surrounding syntax is added.
- Clear the filter to restore all 148 opaque rows. This is useful when switching from one verification task to another or checking the complete list again.
The chart runs entirely in the browser and does not send searches or copied values to a server. Its filters are lookup tools, not nearest-color matching features: if the supplied text does not match, the chart shows a no-match message rather than substituting a similar-looking name.
Match each search mode correctly
Most lookup errors come from expecting one filter mode to behave like another. Use a name fragment when you know part of a keyword, and use the exact numeric formats when you already have a color value to verify.
| What you enter | How the filter behaves | Best use | Mistake to avoid |
|---|---|---|---|
| Part of a CSS color name | Matches name fragments case-insensitively | Find a keyword when you know only part of its name | Assuming the result is a fuzzy synonym or nearest visual match |
| Exact #RRGGBB | A search beginning with # uses exact six-digit HEX matching | Verify a known HEX value against its standardized keyword | Expecting an abbreviated HEX such as #fff to match this filter |
| Complete rgb(...) string | Uses exact matching for the complete value | Confirm a known decimal RGB color | Entering only a channel number and expecting an unrelated color to appear |
| Text that does not match | Displays a no-match message | Detect a typo or unsupported input format | Assuming the chart will silently replace the value with a nearby color |
A complete RGB search is intentionally stricter than a keyword search. Entering a short numeric fragment cannot accidentally match a channel value elsewhere in the table. The chart also does not merge alias rows, invent synonyms, or convert colors between sRGB, HSL, CMYK, or another space.
Treat aliases as valid identifiers
Aliases are one of the easiest chart features to misread as errors. Two standardized keywords can be distinct valid CSS identifiers while pointing to the same numeric color. Preserving both is useful when reading or maintaining an existing stylesheet because the original spelling remains identifiable.
| Keyword type | Examples | What the chart shows | Correct interpretation |
|---|---|---|---|
| Color aliases | aqua and cyan | Both map to #00ffff | Two valid names with the same sRGB value, not an accidental duplicate |
| Color aliases | fuchsia and magenta | Both map to #ff00ff | Both identifiers are standardized and usable where CSS accepts a named color |
| Spelling variants | American and British gray spellings | Each standardized spelling has its own row | Use the exact spelling required by the stylesheet or specification |
| Special non-opaque keyword | transparent | It is excluded from the 148 opaque rows | It represents transparent black rather than an opaque named swatch |
| Context-dependent keyword | currentColor | It is excluded from the fixed opaque mappings | Its value depends on the element’s computed color, so it has no standalone HEX value |
Do not “correct” an alias automatically. First decide whether the goal is to preserve an existing identifier or intentionally rewrite it for consistency. Then use the chart to verify that the selected keyword has the intended mapping. The absence of transparent and currentColor is also intentional: neither fits the table’s promise of one fixed opaque color value.
Separate exact values from design expectations
All 148 listed colors resolve in the sRGB color space. That makes the HEX and RGB mappings useful for digital CSS work, but it does not guarantee that a display will reproduce a physical pigment or show exactly what appeared in a screenshot. A rendered swatch is a visual preview of the mapped value, not proof that two devices look identical.
CSS color names are historical identifiers. Some neighboring names look surprisingly similar, and some names do not describe relative lightness consistently. The chart is therefore not a perceptually even palette, a scientific color taxonomy, or an accessibility rating. Avoid choosing a keyword because its name seems intuitively brighter, warmer, or more serious than the alternatives.
A named-color identifier can be used anywhere a CSS color value accepts one, subject to the property grammar and browser support. The chart can help translate a legacy stylesheet, choose a readable keyword for a prototype, check the exact value behind a name, identify aliases, or copy a stable color token into CSS. For an arbitrary brand or design color, do not force a nearest-looking name into use; verify the intended value instead.
The reference also does not generate color relationships. For harmony-based palettes, use the Color Palette Generator; for CSS gradients, use the Color Gradient Generator. Image sampling and historical web-safe palettes require their own focused workflows as well.
Verify accessibility and production use
A color name alone cannot establish accessibility. Contrast depends on the foreground-background pair, text size, weight, and applicable guidance. The chart explicitly avoids labeling colors as accessible or inaccessible. Before using a name or HEX value for text, check the actual pair with the Color Contrast Checker, then assess the text size and weight in context.
Before placing a value in production, confirm that the exact mapping is correct, that the target CSS property accepts the form you are using, and that your browser requirements are met. A named color may be valid CSS without being the clearest choice for a large design system, where consistent HEX or RGB tokens can be easier to maintain across files.
A practical final review covers four points:
- Confirm the keyword and numeric mapping through the chart rather than by visual resemblance.
- Decide deliberately whether aliases and spelling variants should remain unchanged.
- Check contrast for the real foreground and background instead of inferring it from the name.
- Use dedicated tools for gradients, generated palettes, image sampling, and historical web-safe colors rather than treating this reference as a generator.
Following that process keeps the chart’s role clear: it verifies standardized code values, preserves valid distinctions, and prevents accidental substitutions while leaving broader design decisions to the appropriate tools and tests.
For a deeper look, see How Do I Get Started Using a Web Safe Colors Chart?.
For a deeper look, see How to Check Results After Using an HTML Color Names Chart.