Convert W3C DTCG 2025.10 Tokens
Read and generate official W3C Design Tokens Format (2025.10) JSON files ($value colorSpace/components) and compile straight to CSS, Tailwind v4, or JSON.
DTCG 2025.10
- 100% browser-local
- Zero server transfers
- CSS Color 4 precision
or drop a color string, CSS/JSON snippet, or file here · Ctrl V to paste · or drop CSS/JSON config · Ctrl+V to paste directly
Instant Before & After Specimen
W3C DTCG 2025.10 + Figma JSON <-> CSS/TW4{
"$schema": "https://tr.designtokens.org/format/",
"brand": {
"primary": {
"$type": "color",
"$value": {
"colorSpace": "srgb",
"components": [0.1451, 0.3882, 0.9216],
"hex": "#2563eb"
},
"$description": "Primary Cobalt Studio CTA"
},
"emerald": {
"$type": "color",
"$value": {
"colorSpace": "oklch",
"components": [0.696, 0.17, 162.48]
}
}
}
}:root {
--brand-primary: oklch(0.5461 0.2152 262.88);
--brand-emerald: oklch(0.696 0.17 162.48);
}| Property | Source: DTCG JSON | Target: OKLCH |
|---|---|---|
| Gamut scope | Wide Gamut (P3 / Unbounded) | Wide Gamut (P3 / Unbounded) |
| Perceptual uniformity | Yes | Yes |
| Alpha channel support | Yes | Yes |
| Human readability | High | High |
| Extension / Token | .tokens.json | .css / .json |
| Best for | Vendor-neutral Figma <-> Git <-> Style Dictionary <-> CSS/iOS/Android pipelines | Perceptually uniform UI palettes, Tailwind v4 design tokens, and wide-gamut CSS |
How to use DTCG Design Tokens
DTCG Design Tokens — cleanly inside your local browser with zero server transfers.
- Paste code or drop configPaste CSS variables, Tailwind configs, DTCG JSON, or multi-line Hex lists — or drop a local file.
- Adjust conversion formatSelect target syntax (Tailwind v4 @theme, CSS vars, JSON, or ASE) and source-comment options.
- Copy, chain, or exportCopy ready CSS/JSON snippets, download binary swatch files, or pipe directly to related Colr tools.
Frequently asked questions
Does it support structured 2025.10 { colorSpace, components } values?
Yes — both modern 2025.10 color objects (oklch, display-p3, srgb) and legacy flat Hex strings parse seamlessly.
How are semantic alias tokens resolved?
Curly-brace references like {color.brand.500} resolve cleanly across nested groups.