Color tools for developers
A color API without the ceremony
Every well-known color has a stable URL and a JSON representation: conversions between HEX, RGB, HSL, OKLCH and the Display P3 coordinates, the nearest named color, and contrast data against black and white. If your code needs to answer “what is this color, what does it convert to, and can text sit on it”, the API answers in one request, computed with the same engine as the tools on this site.
Tokens: CSS, Tailwind and DTCG
Design tokens are the contract between design and code. The tools here export the formats teams actually commit: CSS custom properties with oklch() values and sRGB fallbacks, Tailwind theme extensions, and W3C DTCG JSON for Style Dictionary pipelines. Generate a palette in Studio or pick one from the library and the export keeps color names, ramp steps and semantic roles intact.
Accessibility checks in the pipeline
Contrast failures are cheapest before they ship. The same WCAG ratio and APCA calculations behind the contrast checker are available per color, so a CI step can assert that your token pairs stay above your chosen threshold when the palette changes. The WCAG vs APCA guide explains which metric to gate on today (WCAG 2.2 for compliance, APCA as an additional readability check).