Pick a color with the native control, type HEX, or edit RGB and HSL — all fields stay in sync. Use the EyeDropper (Chrome / Edge / Opera) to sample from the screen, copy CSS-ready strings, and see rough contrast hints vs white and black. Runs entirely in your browser.
HEX is a compact encoding of 8-bit red, green, and blue channels (#RRGGBB). RGB uses the same channels as separate numbers. HSL (hue,
saturation, lightness) is often easier for tweaking palettes: move hue for the “color wheel”, saturation for vividness, lightness for tints and shades.
The tool converts internally through sRGB (standard web RGB). Editing any field updates the others so you can work in whichever notation matches your design workflow. Short HEX
forms like #RGB expand to #RRGGBB on blur.
In supporting browsers, EyeDropper lets you pick a color from anywhere on screen (including outside the browser in many setups). If the button is disabled, your browser does not expose the API — use the native color input or type values manually.
The stats row shows WCAG-style contrast ratios against pure white and black for rough accessibility guidance. For WCAG compliance you still need to test real text sizes, fonts, and non-text UI; use dedicated a11y checkers for sign-off.
hsl).No. Everything runs locally in your page session. Refreshing resets to the default unless your browser restores form state.
Rounding, different gamuts, or non-sRGB profiles can shift numbers. This tool uses standard sRGB math suitable for web CSS.
No — only sRGB-style HEX/RGB/HSL for screens. Print workflows need ICC profiles and ink-specific conversions elsewhere.
The native color input may allow wide-gamut picking in some browsers, but fields here normalize to sRGB for interoperability.
This page uses opaque RGB. For alpha, add rgba() / hsla() or modern rgb(… / …) syntax in your own stylesheet.
Some environments restrict screen capture, or the user dismissed the picker. Permissions and OS policy vary.
It is a rough suggestion based on relative luminance: high lightness often pairs better with dark text, low lightness with light text — not a guarantee for every design.
No. Use it for quick exploration; production apps should use a centralized palette, tokens, and documentation for consistency.