What are design tokens?
Design tokens are the smallest, reusable pieces of a design system—named values that represent design decisions like:
Colors: e.g.,
brand-orangeinstead of#FFA500Typography: font sizes, line heights
Spacing: padding, margins
Shadows & animation durations
They’re used in both design tools and code. When a token is updated, that change can cascade across the entire product—keeping styles consistent and easy to maintain.
Teams often store tokens in a central file or sync them with development environments, making them essential for theming, scaling, and aligning design and development.
Similar questions
When should designers use the Liquid Glass Regular vs. Clear variants?
What should a design system include?
What's the difference between a design system / style guide and pattern library?
How do I maintain a design system as it grows?
Should I use an existing design system or build my own?
How can designers and developers collaborate through a design system?
How can I get my team to adopt a design system?
What tools can I use to build a design system?
What is atomic design and how does it relate to design systems?
How do I document a design system effectively?
What are common mistakes to avoid when creating a design system?
Do small teams need a design system?
How do I incorporate accessibility into my design system?
What’s the difference between style tokens and design tokens?
How do you document interaction patterns in a design system?
What is the role of a design token framework?
How do you handle dark mode in a design system?
Why are spacing tokens important in design systems?
What’s the difference between atomic design and design systems?
How do you evaluate a design system’s effectiveness?