Design tokens explained
Design tokens are named values for colour, type and spacing that connect design and code.

A design token is a named value — a colour, font size, spacing unit, radius or shadow — stored once and used everywhere. Instead of hard-coding “#25222A” in hundreds of places, designers and developers both use a name like “color-text-primary”.
When the brand changes, you change the token, not every screen.
Types of tokens
- Primitive (or global) tokens: raw values, e.g. blue-500 = #3B5BDB
- Semantic tokens: meaning-based names, e.g. color-action-primary = blue-500
- Component tokens: specific uses, e.g. button-primary-background = color-action-primary
Why tokens help
- Hard-coded
- Tokens
Our view, scored out of 5.
How tokens flow
Tokens are usually defined in a design tool such as Figma variables, exported to a shared format like JSON, and transformed into code for each platform — CSS variables for web, and equivalents for iOS and Android. Tools such as Style Dictionary or Tokens Studio automate the transformation.
Naming that scales
- Use semantic names for most decisions: what it’s for, not what it looks like
- Keep a consistent structure, e.g. category-property-variant-state
- Avoid names tied to a colour, such as “blue-button”
- Document each token’s purpose
Getting started checklist
Foundations
Semantics
Delivery
Spam check by Cloudflare
How this looks in your industry
Illustrative examples
Closest to you
B2B
A white-label software company
The problem: Each client theme took weeks.
What changed: Introduced semantic tokens for colour and type.
Result: New themes took days.
Closest to you
E-commerce
A retail group with three brands
The problem: Shared code but different colours everywhere.
What changed: One token structure with a theme per brand.
Result: Consistent components across brands.
Closest to you
Health
A health app adding dark mode
The problem: Colours were hard-coded across the app.
What changed: Replaced them with tokens mapped to light and dark themes.
Result: Dark mode shipped without a redesign.
Common mistakes
- Naming tokens after their value
- Only creating primitive tokens
- Tokens in design but not in code
- Too many near-identical values
Key takeaways
- Tokens are shared named values
- Use primitive, semantic and component layers
- Name by purpose, not appearance
- Automate the flow from design to code
Frequently asked questions
Do small teams need tokens?
If you have more than one product, theme or platform, tokens save time quickly. Even a small set helps.
Are Figma variables the same as tokens?
Figma variables are a way to define and use tokens in design. You still need to export them to code.
Do tokens help with accessibility?
Yes. Semantic colour tokens can be checked for contrast once and reused safely.
Your next step
Connect design and code properly
We set up token systems that keep products consistent and make theming simple.
Explore design systems