In short
- Design tokens are named design decisions, such as a brand color or a spacing value, stored once and used everywhere the brand appears.
- In October 2025 the Design Tokens Community Group published the first stable version of a shared format for them, which makes tokens easier to move between tools and platforms.
- They pay off when a brand lives across several websites, apps or teams. A single small website can get most of the benefit from well organized CSS variables.
Every growing company eventually discovers that its brand has quietly drifted. The website uses one shade of blue, the app another, the sales deck a third. Buttons have four slightly different corner styles. Nobody decided this. It happened one reasonable shortcut at a time.
Design tokens are the most practical fix we know for that drift, and in late 2025 they became considerably easier to adopt.
What design tokens are
A design token is a design decision with a name. Instead of writing a hex code into a stylesheet, a design file and an app separately, you define it once:
color.brand.gold = #F5A50C
Every place that needs the brand gold then refers to the name rather than the value. When the value changes, it changes everywhere. Tokens can hold colors, type sizes, font weights, spacing, corner radius, shadows and motion timings, which together make up most of what a brand looks like on screen.
Good token systems usually have layers. Base tokens hold raw values. Semantic tokens give them a purpose, such as color.action.primary or color.text.muted. Component tokens apply them to specific elements, such as the background of a primary button. The layers are what make the system flexible: you can redesign a button without touching the palette, or adjust the palette without redesigning every button.
What the stable specification changed
For years every tool stored tokens in its own way, which made sharing them between design software, code and documentation awkward. On 28 October 2025 the W3C Design Tokens Community Group announced that its specification had reached its first stable version, numbered 2025.10. It describes a vendor neutral file format for exchanging design decisions between tools.
The announcement highlights four areas:
- Theming. Light and dark modes, accessibility variants and brand themes can be managed without duplicating entire files.
- Modern color. Support for Display P3, Oklch and the other color spaces in CSS Color Module 4, which matters as more screens show wider color ranges.
- Relationships. Aliases, inheritance and references between tokens, so a semantic token can point to a base token rather than copying its value.
- Cross platform output. One token file can generate code for the web, iOS, Android and Flutter.
One caveat is worth knowing. As the group’s own FAQ explains, this is a Community Group specification, not a formal W3C standard, and it will keep evolving. The core format is described as stable enough for production use, which is what most teams were waiting for.
Why tokens matter for brand consistency
The obvious benefit is speed. Changing a color across a website, two apps and a component library becomes a single edit rather than a hunt through dozens of files.
The less obvious benefit is that tokens make brand rules explicit. A brand guideline PDF can say the gold is for accents only. A token system can enforce it, because the gold simply is not available as a text color.
This site is a small example. Our brand gold, #F5A50C, looks excellent on dark backgrounds and as a thin accent line, but it is far too light to pass contrast requirements as small text on white. So the system has a second, deeper gold, #8A5A00, reserved for text on light backgrounds. Designers and developers never have to remember the rule, because each token is only offered where it works. That is accessibility and brand consistency handled by the same decision.
When should a business adopt them?
Tokens are not free. They need someone to set them up, name them sensibly and maintain them. In our experience they are clearly worth it when:
- Your brand appears on more than one website or app, or on a website and a product.
- Several teams or agencies build things for you and need to stay consistent without constant checking.
- You run sub brands or regional variations that share most of their design.
- You need dark mode, high contrast themes or white label versions.
- A rebrand is planned, and you would rather change values once than redo everything.
If you have a single marketing website, a full token pipeline is probably more than you need. Well named CSS custom properties give you most of the benefit, and they can be turned into formal tokens later without starting again.
Getting started without a big project
- Audit what you have. Collect every color, type size and spacing value actually in use across your site and apps. The list is usually longer and messier than anyone expects.
- Agree the real palette. Merge the near duplicates and decide which values are genuinely part of the brand.
- Name by purpose, not appearance.
color.text.mutedsurvives a rebrand.color.grey.lightdoes not. - Store them in one place. A single source file in the shared format, under version control, from which other formats are generated.
- Connect design and code. The same names in your design tool and your codebase, so designers and developers are speaking the same language.
Our brand and design team builds identity systems with tokens from the start, so the brand you approve is the brand that ships, on every screen.
Sources
- Design Tokens specification reaches first stable version, W3C Design Tokens Community Group, 28 October 2025
- Design Tokens Community Group, designtokens.org
- Design Tokens FAQ, designtokens.org