Design tokens are named values, such as colours, font sizes and spacing, stored in one place so design tools and code use exactly the same settings.
Design · Reviewed by Ray Rasouli
Ask about design tokens
Plain answers, with your setup in mind.
Ask anything about design tokens. For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
Instead of writing a hex colour like #0B5FFF in hundreds of places, a team defines a token such as "color-primary" and uses that name everywhere. Change the token once and every button, link and chart that uses it updates.
For a retailer with a website, a mobile app and a staff tablet app, tokens keep the brand blue, the spacing and the type scale identical across all three, even if they are built with different technologies.
Tokens are also how teams support themes like dark mode: the same token name points to a different value in each theme.
In practice
Raw values sneak back into code.
Developers paste exact colours or pixel sizes directly, bypassing the tokens and breaking future updates.
Names describe looks, not purpose.
A token called "blue-500" is hard to change; one called "color-action" can change colour without confusion.
Design and code tokens are kept separately.
Two lists that are updated by hand drift apart over time.
Contrast is not checked per theme.
A token pair that passes in light mode may fail accessibility contrast in dark mode.
Not strictly, but even a small set of tokens for colours, fonts and spacing makes future changes and rebrands much easier.
Often JSON or CSS custom properties, which tools can then convert for web, iOS, Android and design software.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.