DTCG JSON: W3C Design Tokens Format (2025.10)
Official W3C 2025.10 JSON schema ($type: 'color', structured $value colorSpace/components/hex objects) uniting Figma Variables and CSS codebases.
| Extension / Token | .tokens.json |
|---|---|
| MIME / Media type | application/design-tokens+json |
| Gamut scope | Wide Gamut (P3 / Unbounded) |
| Human readability | High |
| Perceptual uniformity | Yes |
| Alpha channel support | Yes |
| Best for | Vendor-neutral Figma <-> Git <-> Style Dictionary <-> CSS/iOS/Android pipelines |
DTCG JSON
TOKENS.JSON{"brand":{"primary":{"$type":"color","$value":{"colorSpace":"oklch","components":[0.55,0.21,262],"alpha":1}}}}Strengths
- Official open interchange format backed by Figma, Tokens Studio, Style Dictionary, and Penpot.
- First-class support for wide-gamut spaces (oklch, display-p3, srgb) with structured numeric arrays.
- Supports semantic token alias references ({color.brand.500}) and Git code review diffs.
Trade-offs
- More verbose than flat Hex JSON files and requires tooling to compile into CSS or Swift/Kotlin.
Convert & inspect DTCG JSON locally
Related color engineering guides
- W3C Design Tokens (DTCG 2025.10): Figma Variables to CSSStructure vendor-neutral color tokens with W3C DTCG 2025.10 JSON ($type, $value colorSpace & components), aliases, and export to CSS & Tailwind v4.
- Zero-Server Browser Color Processing: Privacy & ArchitectureHow Colr executes Canvas quantization, CSS rewriting, and binary .ase/.aco/.cube parsing 100% inside local browser RAM with zero file transfers.
DTCG JSON frequently asked questions
What changed in W3C DTCG 2025.10 color values?
2025.10 replaces plain hex-only strings with structured { colorSpace, components, alpha, hex } objects so OKLCH and Display P3 survive intact across tools.
Can Colr convert legacy hex JSON tokens into DTCG 2025.10?
Yes — use /design-tokens-converter/ or /css-color-extractor/ locally in your browser.