This is the official DTCG repository for the design tokens specification (W3C community group page).
Design tokens are indivisible pieces of a design system such as colors, spacing, typography scale.
Design tokens were created by the Salesforce design system team, and the name comes from them (Jon & Jina).
Sharing design properties such as a color palette across many tools and platforms should be simple.
The DTCG's goal is to provide standards upon which products and design tools can rely for sharing stylistic pieces of a design system at scale.
We believe that a common way to share design tokens will unlock efficiency opportunities for plugins, design system teams, product teams, and end-users of design tools.
- Full charter
- Technical reports (Instructions for editing technical reports)
- Format Module meeting notes
Allow anyone to become familiar with design tokens. Empower people, no matter what their skills and tool choices are, as they develop new mental models, acquire skills, and implement tools to scale design in their projects.
Everyone is welcome to join the conversation and share use-cases with the community.
Stay focused on the smallest surface area necessary to cover the most commonly referenced use-cases. Be a platform that opens the door to a wide range of possibilities. This small footprint helps maintain simplicity with zero dependencies.
Extensibility allows the community to incubate new ideas that will define the future of design tokens.
Provide a stable foundation that users and tool makers can put in place and depend on in the long term. For example, by using existing and trusted standards (unless conflicting with the two first principles).
The community group is composed of UX professionals, developers, and representatives of design tooling vendors.
To achieve a v1 of the specification rapidly, its structure is restricted to a small, focused amount of people, organized in task forces.
As vendors adopt the specification and new requirements appear, the community group will consist of additional task forces.
- Abstract
- Adobe
- Alaska Airlines
- Amazon
- Atlassian
- Chroma
- Divriots
- Dynatrace
- Figma
- Framer
- Herman + Accoutrement
- Interplay
- InVision
- Kaspersky
- Knapsack
- Liferay
- Lona
- Marvel
- Microsoft
- Open edX
- Penpot
- Philips Design
- Salesforce
- Sass
- Shopify
- Sketch
- Specify
- Sprout Social
- Style Dictionary
- Superposition
- Supernova
- Synology
- system-ui
- Toolabs
- Tokens Studio
- Universal Design Tokens
- Webstudio
- Zendesk
- Zeplin
- zeroheight
- ex-contributors to Theo (by Salesforce)
Here's an overview of all of the published versions of this specification:
| name | url | date | status |
|---|---|---|---|
| 2025.10 | www.designtokens.org/TR/2025.10/ | 2025-10-28 | Stable |
| third-editors-draft | www.designtokens.org/TR/third-editors-draft/ | 2025-07-21 | Draft |
| second-editors-draft | www.designtokens.org/TR/second-editors-draft/ | 2022-06-14 | Draft |
| first-editors-draft | www.designtokens.org/TR/first-editors-draft/ | 2021-09-23 | Draft |
| preview | www.designtokens.org/TR/drafts/ | — | Experimental |
Note: tools can use the date as a version number to signify compliance. For example:
2025.10.
See CONTRIBUTING.md.
Join the official DTCG Discord server for real-time community discussion.
We acknowledge that the format specification is only part of an ecosystem, supporting methods and practices that relate to scaling design tokens:
Design Tokens are a methodology. IMHO, saying "design tokens are just variables" is like saying "responsive design is just media queries". It's a technology-agnostic architecture and process for scaling design across multiple platforms and devices, including native, and more. — @jina on X