Token bridge
M3 → DTCG Bridge
Material 3's DSP export was archived October 2024 and doesn't emit W3C DTCG format. Paste your M3 token CSS or JSON — get W3C DTCG 2025.10 output, validated and ready to download.
The neutral bridge between Google's two non-interoperating design-data initiatives: M3 (DSP archived) and DESIGN.md (ships DTCG). Whether your tokens come from M3, DESIGN.md, Tokens Studio, or hand-written JSON — Designesy validates them against the W3C standard.
Input — Material 3 tokens (CSS custom properties)
Why this exists
Material Design 3 is the most influential design system on Earth. Its native token export format — DSP (Design System Package) — was archived October 17, 2024. No replacement has been announced. M3 participates in the W3C DTCG community group but has not shipped DTCG export.
Meanwhile, Google's DESIGN.md initiative (different org, same umbrella) does ship DTCG export via npx @google/design.md export --format dtcg. These two Google projects don't interoperate at the token format level.
Designesy bridges the gap. Paste M3 tokens → get DTCG output → validate with the Designesy token validator. This is the technical moat: Designesy is the only tool that converts M3's archived format to the W3C standard and then verifies the result.