SEOLivly
Menu
Home Tools Blog Services Contact Run the free scan

CSS Color Picker - grab the value, then check the contrast

Pick a colour and copy the hex, RGB or HSL value. Then check the contrast: a colour that looks fine on your monitor can vanish on a phone in daylight.

This is a utility tool for quick color reference. It does not analyze your site's color scheme or accessibility.
CSS Color

A colour picker gives you a value. It does not know your brand, and it cannot tell you whether the text will be readable on the background. That is the part that matters. Use it to grab a hex, RGB or HSL value, then run the pair through a contrast check. WCAG AA wants 4.5:1 for normal text and 3:1 for large text, a rule that catches more real accessibility problems than any palette trend.

I built this page because the old version was a joke meta tag and a wall of AtoZ filler. The picker underneath is fine. The copy around it was not. So here is what the tool actually does, what it cannot do, and the two-minute check that stops you shipping grey text on a grey button.

What it picks

Click the swatch, move the cursor, and the tool reads the colour under it. You get the value back in three formats at once: hex, RGB and HSL. Copy whichever one your CSS or design file needs.

That is the whole job. It is a converter and a sampler, not a design assistant. If you need a palette generated for you, this is not that tool, and I am not going to pretend it is.

Conversion matters more than people think. A brand guide gives you a hex. Your stylesheet wants RGB. Your designer is working in HSL because it is easier to nudge lightness. Same colour, three dialects, and one typo in the middle of a hex string gives you a completely different shade.

The formats explained

Hex is the default for a reason: it is short, it pastes anywhere, and every tool on earth accepts it. #1a1a1a is six characters and no ambiguity. Use it for brand colours and anything you are handing to someone else.

RGB is what the browser actually renders. You will see it in older codebases, in canvas work, and anywhere someone needed to add an alpha channel. rgb(26, 26, 26) is the same colour as that hex above, just spelled out.

HSL is the one I reach for when I am adjusting rather than specifying. Hue, saturation, lightness. Want the hover state 10% darker? Change one number. Try doing that with hex and you will be guessing at the relationship between three hex pairs.

Format Example When to use it
Hex #1a1a1a Brand colours, handoffs, anything pasted between tools
RGB rgb(26, 26, 26) Legacy code, canvas, anything needing an alpha channel
HSL hsl(0, 0%, 10%) Building hover and active states by adjusting one value

If you want the formal definitions, MDN's page on CSS colour formats and values is the reference I actually trust. It is dry, it is correct, and it does not sell you a palette subscription.

Contrast is the real check

Here is the thing the picker cannot do: it cannot see the other colour. Contrast is a property of a pair, text on background, not of a single swatch. A beautiful deep purple is perfectly readable on white and completely invisible on near-black.

WCAG AA sets the bar at 4.5:1 for normal text and 3:1 for large text, which usually means 18pt regular or 14pt bold. Those numbers are not arbitrary. They come from how human vision actually degrades, and they catch more real accessibility failures than any trend in colour theory.

So the workflow is: pick the colour here, then take the pair to a contrast checker. If you skip that step, you have picked a colour, not solved a problem. The dark background this page sits on is itself the lesson: light text on near-black is easy, mid-grey on near-black is where sites fall apart.

Honest limits: this tool picks and converts colour values. It does not check contrast, does not know your brand, and cannot guarantee readability. Contrast depends on the pair, text plus background, so check it separately. If a colour looks fine to you and fails 4.5:1, it fails for a chunk of your visitors too.

Colour and mobile daylight

A colour that works on your monitor can vanish on a phone. Two reasons. First, screens differ: cheaper panels wash out subtle greys and push saturated colours harder. Second, people use phones outdoors, where glare eats contrast alive.

I have watched a client's "elegant" light grey body text disappear entirely on an iPhone in direct sun. On a calibrated desktop it looked refined. On the pavement it looked like an empty page. The hex value was identical in both cases.

That is why the last step of any palette check is physical: open the page on your phone, walk outside, and look. No tool on this site can do that for you. It takes thirty seconds and it has saved more designs than any plugin.

A palette that does not fight

Most sites I audit have too many colours. Not slightly too many. Six shades of blue, three greys that are almost the same, an accent that only appears on one button nobody clicks. Every extra colour is another decision someone has to make and another chance to break contrast.

The rule I use: one accent, two neutrals, and a text colour. That is it. The accent is for actions and links. The neutrals carry backgrounds and borders. The text colour is the one you check against every background it lands on.

  • One accent colour, used only for things you want clicked
  • Two neutrals: a light surface and a dark surface
  • One text colour, contrast-checked against both surfaces
  • Hover and active states derived from the accent by adjusting lightness, not inventing new colours

If you cannot name what a colour is for, it is decoration. Decoration is fine, but it should not be load-bearing for readability. When in doubt, delete the colour and see if the page still works.

What this tool cannot do

It cannot know your brand. It has no idea whether your logo is warm or cool, whether your industry expects restraint, or whether that green means "go" or "money" to your customers. That is your call, and no picker replaces it.

It cannot check contrast, as covered above. It cannot tell you if a palette is accessible, because accessibility lives in the pairs and the sizes and the states, not in a single value. It cannot guarantee readability on every device, in every light, for every pair of eyes.

What it can do is give you an accurate value, fast, in the format you need, with a copy button. That is a small job done properly. A utility page earns trust by being correct and quick, not by being 4,000 words long. The old version of this page was the latter. This is the former.

The two-minute palette check

Pick your text colour here. Pick your background colour here. Write both values down, then take them to a contrast checker and confirm you clear 4.5:1 for body text and 3:1 for anything large.

Then do the part no tool handles: open the page on your phone, step outside, and look at it. If the text holds up in daylight, you are done. If it does not, darken the text or lighten the background and run the check again.

Once the colour is settled, check the layout at real widths next, because a readable colour on a broken layout is still a broken page. Then look at what the page weighs, since heavy pages and slow loads undo a lot of good design work. And if you want the rest of the set, they are all on all the tools on this site.

What contrast is required?

WCAG AA asks for 4.5:1 for normal text and 3:1 for large text, which is roughly 18pt regular or 14pt bold. AAA is stricter at 7:1, and worth aiming for on body copy if you can. Check the actual pair, not the single colour.

Which format should I use?

Hex for brand colours and handoffs, because it is short and universal. HSL when you are building hover and active states, because you can adjust one value instead of guessing. RGB when your code or canvas needs it. They are the same colour in different spelling.

Why does my colour look different?

Different screens, different calibration, different ambient light. A colour that looks right on your monitor can wash out on a cheap phone panel or vanish in direct sun. Check the pair on a real phone outdoors before you call it done.

If you want to know how many other things on the page are quietly costing you clicks, run the free 40-point scan at /website-auditor. If you would rather I just fix it, the service and pricing are on /page/seoservices. Start with the scan. If it is a five-minute fix, do it yourself.

More free tools that return a result

All the tools, sorted by what works · Have the fixes done for you