Design & UI/UX Tools
Twenty-five tools for choosing colour, styling CSS, setting type and building layouts. Colour work happens in OKLCH, contrast is judged at full precision, and nothing you make here — no colour, no image, no generated code — leaves your browser.
Colour
Generated perceptually, so the steps look even rather than merely measuring even.
Accessibility
Measured against the criterion that actually applies, and honest about what a ratio does not prove.
CSS and visual styling
Every value copyable, every slider paired with a number field.
Typography and units
With the derivation shown, because a value you cannot explain is one you will delete.
Layout
The parts that are hard to type, built from controls.
Surfaces and effects
Including the two styles whose whole aesthetic is in tension with a WCAG criterion, measured rather than shipped quietly.
SVG and icons
An SVG is a document, not a picture. Everything here sanitises on the way in, from an allowlist, and lists what it removed.
Motion
Every output carries a reduced-motion branch, and every loading indicator carries the role and the name that make it announce.
More accessibility
Held to the criterion that actually applies, and clear about which level each figure comes from.
Design systems and tokens
Primitives, semantic references, and formats that keep them — with the lossy conversions named at the point of export.
Why everything here works in OKLCH
HSL and sRGB are how a screen addresses its pixels. They say almost nothing about how a colour looks next to another one, and arithmetic on them produces the failures every designer recognises: the ramp with a muddy middle, the yellow that glares beside a blue that sinks, the gradient with a grey band through it.
OKLCH is built so that equal numbers look equal. A ramp with even lightness steps has even perceived steps. A hue rotated 180° comes back at the same perceived lightness. A straight line between two colours passes through the colours a person would name in between. That is the whole reason these tools produce different output from the generation of tools before them.
Colours that sRGB cannot show
OKLCH and Display P3 can name colours no standard screen reproduces. Where that happens the colour is brought into gamut by reducing its chroma at constant lightness and hue, and the amount lost is reported.
The obvious alternative — clipping each channel to its range — is faster and silently moves the hue. A vivid cyan clipped that way comes back a different cyan, and nothing downstream can tell that happened. No tool here does it.
What a contrast ratio proves
It satisfies one WCAG success criterion. It does not make an interface accessible, and it says nothing about focus order, labelling, motion, or whether the thing is usable at all. Automated checks find a minority of real barriers.
Within that limit these tools are careful: the ratio is computed at full precision and rounded only for display, alpha is composited against a stated backdrop rather than assumed white, and a role is judged against the criterion that actually applies to it — a surface sitting a shade off the canvas is not a component, and failing it against 3:1 would be inventing a requirement WCAG does not make.
Nothing you make here is uploaded
Colours, images, SVG and generated code are processed on your own device. There is no server to send them to. The image palette extractor decodes your file in the tab and releases the pixels when you clear it.
A palette made on one page is available on the next through a workspace kept in this browser's local storage. It is never synced, never uploaded, and clearing your site data deletes it.
Related tools already on the site
The grid splitter and image tools handle raster work; developer tools cover encoding and formatting. For applying colour to a document rather than an interface, the PDF tools are next door.