A tool for inspecting a website's color palette

Contents

• [A practical way to inspect the palette](#a-practical-way-to-inspect-the-palette)
• [Turn raw colors into usable roles](#turn-raw-colors-into-usable-roles)
• [Check whether the palette works](#check-whether-the-palette-works)
• [Save a palette you can use](#save-a-palette-you-can-use)
• [Use this in your AI agent](#use-this-in-your-ai-agent)

The best tool for inspecting a website color palette should do more than list hex codes: it should show which colors repeat, where they appear, and whether they belong to text, backgrounds, borders, buttons, or accents. Use a page capture or browser inspection tool, then reduce the result to a small palette with clear roles instead of copying every color it detects.

A practical way to inspect the palette

Start with the page you want to study and record these five things:

1. The main background colors: page background, card surfaces, navigation areas, and footer.
2. The main text colors: separate strong heading text from muted body text or metadata.
3. The action color: buttons, links, selected states, and other controls may share one accent.
4. The supporting colors: borders, dividers, badges, icons, and subtle highlights.
5. The frequency and placement: a color used across a large surface has a different role from one used only in a small icon.

Open the example below and compare the first screen before borrowing a pattern. The Pangram AI Detector reference is paired with a muted green set that includes #496c10, #15502e, #14532d, #233f2a, and #799c92. Treat that list as an observed starting point, not as a finished design system. The useful question is where each green appears and whether the lighter values are reserved for supporting UI.

Turn raw colors into usable roles

A palette becomes easier to use when every color has a job. A simple role table works well:

Do not assume that the most saturated color is the primary brand color. A strong color may be used only for calls to action, while a darker related color handles headings or navigation. Compare repeated values and their location before naming a role. Mark inferred roles as unverified until the page gives you enough evidence.

Check whether the palette works

After collecting the colors, test the combinations people will actually see. Check heading text against the page background, body text against cards, button labels against button fills, and links against the surrounding surface. Also check hover, focus, disabled, and selected states. A palette can look cohesive while still making small text difficult to read.

Look for near-duplicates too. If several colors differ by only a few RGB values, they may come from anti-aliasing, image content, or layered transparency. Keep them separate only when they serve visibly different purposes. Otherwise, consolidate them into one token and document the exception.

Save a palette you can use

Before reusing the result, confirm that you have:

• One clear canvas color.
• One or two surface colors.
• A readable primary text color.
• A readable secondary text color.
• One main action color and, if needed, a darker state color.
• Border and divider values that do not overpower the content.
• Light and dark combinations checked at their actual text sizes.
• Notes about where each color was observed.

For a repeatable workflow, capture the page, inspect its colors and usage, compare it with another reference, then save only the roles that survive that comparison. A Fudge color inspection is useful when you need observed colors tied to page usage rather than a loose color-picker list. The final palette should explain how to build the interface, not merely how to reproduce one screenshot.

Use this in your AI agent

> Inspect the captured website's color palette. Return the most repeated colors, their observed roles, where they appear, approximate frequency, and any useful contrast pairings. Group near-duplicate colors, separate surface, text, accent, border, and state colors, and finish with a compact CSS variable palette plus notes about what should be verified before reuse.

Install Fudge for your AI agent

Treat each color as a combination of value and job. For every repeated color, record the element type, surface behind it, text size if applicable, state, and how often it appears. That lets you distinguish a primary action color from a decorative accent or an image-derived color.

A useful worksheet has these columns: hex, role, element, surface, state, frequency, and contrast check. Start with large regions, then buttons and links, then borders, icons, and status elements. If the same green appears in a logo, button, and heading, do not automatically give it one token. It may need separate roles or shades.

For the captured example, use the muted green colors as a comparison set and ask where the darker greens do structural work while lighter values support secondary details. That is more useful than treating all twelve colors as equally important. Keep an explicit unverified note for any role inferred from appearance rather than confirmed through repeated usage.

Use this compact template:

Add a screenshot or page reference beside each role when you can. If you later export the values to CSS, keep these human-readable notes beside the variables so another designer can tell why each color exists.

Related questions

• A tool for inspecting website color roles
• Inspect Text and Background Contrast on a Website
• Inspect a Website's Gradient Palette and Color Use
• Inspect a website's dark mode color palette