Document an HTML color names chart lookup by recording the exact search input, matched CSS keyword, swatch, standardized HEX and RGB values, intended CSS use, and any alias or accessibility decision.
The HTML Color Names Chart supports this workflow as a reference lookup: it lists all 148 opaque CSS named-color keywords, preserves standardized aliases as separate rows, and operates entirely in your browser. It does not generate documentation or insert a complete CSS declaration, so your saved note should be the durable record.

Separate the lookup procedure from the color result
A useful color record contains two connected parts: the procedure explains how the value was found, while the result records what the chart displayed. Keeping those parts distinct makes the lookup reproducible without implying that the chart made a design or accessibility decision.
| Record field | What to write | Why it belongs in the note |
|---|---|---|
| Lookup task | The CSS property or design decision being investigated. | Explains why the color is needed and what the result will affect. |
| Search mode and input | The exact name fragment, six-digit HEX string, or complete rgb(...) string entered. | Allows another developer to repeat the same search. |
| Matched keyword | The exact CSS identifier shown by the chart. | Preserves the spelling used by the specification, including aliases. |
| Swatch | Whether the rendered color matched the expected visual reference. | Provides a visual check without replacing the numeric mapping. |
| HEX mapping | The lowercase six-digit value, including its leading #. | Records the stable color token supplied by the chart. |
| RGB mapping | The decimal value in the form rgb(r, g, b). | Records the second standardized representation. |
| Outcome | The selected value, a no-match result, or a manual-copy fallback. | Shows how the lookup ended and whether another action is required. |
Also note whether the final CSS should use the named identifier, the copied HEX value, or another representation. The chart gives you the mapping, but the choice between those forms belongs to your stylesheet requirements and project conventions.
Document each lookup in a repeatable order
Use the following sequence whenever you need to verify a CSS color name or preserve its exact value in project documentation.
- Define the decision before searching. Write down the property or question you need to resolve, such as confirming a legacy border color or choosing a readable keyword for a prototype. This prevents a visually similar result from being mistaken for the intended value.
- Open the chart with the full table visible. The chart initially contains all 148 opaque named colors. Starting from the complete list makes it easier to confirm whether a filtered result is a genuine match or only one entry in a longer set.
- Enter one supported search value. Type part of a CSS color name, an exact six-digit HEX value beginning with #, or a complete rgb(...) string. Save the query exactly as entered so the note reproduces the same matching behavior.
- Review every matching row. Confirm the standardized keyword, rendered swatch, lowercase HEX value, and decimal RGB value. An exact HEX or RGB lookup can reveal more than one row when valid aliases share the same mapping, so check the keyword rather than assuming there is only one match.
- Record a no-match result without substituting a color. If the chart displays its no-match message, document that outcome instead of selecting a nearby swatch. The chart does not invent fuzzy synonyms or replace an invalid query with an unrelated color.
- Copy the HEX value only when it is needed. Clicking a HEX value requests a clipboard write, and the chart reports success only after the browser resolves that request. If clipboard permission is denied, select the visible keyword, HEX, or RGB text and copy it manually.
- Write the result into your project notes. Include the exact query, matched keyword, swatch observation, HEX, RGB, and the reason for your CSS choice. The chart itself does not save notes, so save them beside the stylesheet, design token, or task where the value will be used.
- Clear the filter when the lookup is complete. Clearing it restores all 148 opaque named-color rows. This resets the reference view without changing any recorded mapping.
Choose the search mode that matches your input
The chart has three distinct matching modes, and each mode should be documented because the same-looking query can produce a different kind of result.
- Name fragment: Keyword search is case-insensitive and matches fragments of CSS color names. A fragment may return several rows, so review the complete filtered set before selecting one.
- Exact HEX: A search beginning with # uses exact six-digit HEX matching rather than a partial or fuzzy match. Copy the full displayed value instead of shortening it.
- Complete rgb(...): A complete rgb(...) search also uses exact matching. This restriction prevents a short numeric fragment from accidentally matching an unrelated channel value.
Filtered results remain in the specification table order, which is ASCII alphabetical by keyword in this implementation. Filtering never alters a mapping, merges aliases, creates synonyms, or converts the color into another color space. If your documentation depends on a precise comparison, record both the input mode and the resulting keyword rather than only writing “found in chart.”
Record aliases and excluded keywords correctly
Several CSS names share an exact mapping because they are distinct valid identifiers. The chart deliberately preserves those spellings, and your notes should do the same.
| Name or keyword | Chart treatment | Documentation note |
|---|---|---|
| Aqua and cyan | Separate rows that both map to #00ffff and rgb(0, 255, 255). | Choose the spelling required by the stylesheet; do not treat the shared value as an error. |
| Fuchsia and magenta | Separate rows that both map to #ff00ff and rgb(255, 0, 255). | Preserve the identifier used by existing code when documenting or maintaining it. |
| American and British gray spellings | Several valid gray names coexist as separate rows. | Retain the original spelling when explaining or editing an existing rule. |
| transparent | Excluded from the 148 opaque rows. | It is a special alpha-bearing keyword representing transparent black rather than an opaque named swatch. |
| currentColor | Excluded from the 148 opaque rows. | It depends on an element's computed color property and has no fixed standalone HEX mapping. |
For formal background, compare the entries with the W3C CSS Color 4 named-colors specification and the MDN named-color reference. The chart is a focused lookup aid; the standards references provide the wider CSS context.
Create a reusable documentation note
A repeatable note format reduces ambiguity when another designer, developer, or maintainer revisits the color. Copy this structure into your project documentation and fill in every relevant field:
- Purpose: State the property or decision being documented.
- Search mode: Label the query as a name fragment, exact HEX, or complete RGB string.
- Exact query: Preserve capitalization and punctuation as entered.
- Matched keyword: Record the CSS identifier displayed by the chart.
- Visual result: State whether the swatch matched the intended reference.
- HEX: Record the complete lowercase value, including #.
- RGB: Record the decimal rgb(r, g, b) value.
- Decision: Explain why the keyword or HEX token will be used.
- Status: Record a completed copy, manual copy, or no-match result.
For example, a compact note could say: task, document a link color; query, aqua; matched keyword, aqua; swatch, reviewed; HEX, #00ffff; RGB, rgb(0, 255, 255); decision, retain the named identifier because the target CSS property accepts it; clipboard, not needed.
When you need CSS syntax, write the declaration yourself around the copied token—for example, color: #00ffff; in an appropriate rule. The chart copies the HEX value itself; it does not change capitalization or add a selector, property, semicolon, or declaration around it. A CSS named-color identifier can be used anywhere a CSS color value accepts that identifier, subject to the property grammar and browser support.
Know what the chart cannot establish
Documenting a lookup accurately also means recording its boundaries. The reference provides exact sRGB mappings for the opaque named-color set, but it does not make broader design judgments.
- Accessibility: A color name alone cannot establish text readability. Contrast depends on the foreground-background pair, text size, weight, and applicable guidance. Use the Color Contrast Checker for that separate evaluation.
- Perceptual or physical meaning: CSS names are historical identifiers, not a perceptually even palette, scientific taxonomy, or guarantee that a display reproduces a physical pigment. Nearby names can look unexpectedly similar.
- Color conversion: The chart does not convert its entries into CMYK, gradients, palettes, sampled image colors, or a historical web-safe palette. Use a focused tool when one of those outputs is the actual task.
- Opacity: The 148-row dataset contains opaque named colors. Do not use it as a source for a fixed transparent or currentColor mapping.
- Privacy: Searches and copied values remain in the browser and are not sent to a server.
- Clipboard access: Permission denial does not remove the result. The visible keyword, HEX, and RGB text remain available for manual copying.
A complete note therefore records the method, exact result, CSS decision, and relevant limits. That combination lets another person repeat the lookup and understand why the selected color was used without mistaking a standardized name reference for a generator or accessibility evaluator.
If you're weighing options, How to Troubleshoot a Web Safe Colors Chart covers this in detail.
If you're weighing options, Do You Need a CSS Color Gradient? Decision Guide covers this in detail.