Tools · 26 of them, 14 new

CSS tools that write the CSS of now.

Most generators still hand you 2014: prefixes, rgba, a cubic-bezier. These write what browsers ship today, with the fallback line when one is needed, and tell you whether it is safe yet. Everything runs in your browser, nothing is uploaded, and every setup is a link you can send.

Colour

Perceptual colour spaces, derived palettes, and contrast you can prove.

Layout, type and sizing

Components that size themselves, fluid scales, text that wraps well, and things tethered to other things.

Motion

Easing with real physics, and animation driven by scroll and state, each with a reduced-motion exit.

Shape and surface

Corners, shadows, glass, masks and filters.

Selectors and the cascade

Which rule wins, and how to write fewer of them.

How these are built

The browser does the maths

Previews are painted by the declaration you copy, not by a JavaScript imitation of it. Where a fallback hex is given, it is read back out of the browser.

Fallback first

When a feature is not everywhere, the output starts with what works everywhere and upgrades inside @supports. Motion always leaves with a reduced-motion block.

Your setup is a link

Settings live in the address bar. Copy the link and someone else opens the tool exactly as you left it. No account exists to make.

Status is read, not typed

Every badge comes from the open web-features dataset when the site is built. Nobody here decides what counts as safe.