Is DESIGN.md a Standard?
On this page
DESIGN.md is an open format published by Google under the Apache 2.0 license. It is a specification with a reference implementation, not a formal standard: it has not been ratified by a standards body such as the W3C, ISO, or ECMA. The related W3C Design Tokens Community Group (DTCG) format is the community standard for token interchange. DESIGN.md is inspired by it and can export to it, but the two are different things.
The short answer#
Is DESIGN.md an official standard? No, not in the formal sense. DESIGN.md is an open format published by Google as the @google/design.md package under the Apache 2.0 license. It is a convention with a reference implementation, and it is versioned like software (v0.3.0 at the time of writing). No standards organization has ratified it.
That is not a criticism. Plenty of widely used formats are open specifications maintained by a single publisher rather than ratified standards. The distinction matters mainly for how you reason about stability and governance, which the rest of this page covers.
What "standard" actually means here#
The word "standard" gets used loosely. It helps to separate two meanings.
A formal standard is a specification ratified by a recognized standards body: the W3C, ISO, ECMA, IETF, and similar. Ratification implies a formal process, multi-party governance, and a versioning and change procedure that is deliberately slow and consensus-driven.
A de facto standard is a format or convention that becomes widely adopted without formal ratification. It is usually defined by a reference implementation and its documentation. Many everyday developer formats live here.
DESIGN.md is in the second group. It is defined by its published spec and the @google/design.md reference implementation. Adoption, not a committee, determines its reach.
Who publishes it, and under what terms#
DESIGN.md is published by Google. The package is open source under the Apache 2.0 license, which permits use, modification, and redistribution, including in commercial projects. The current version is 0.3.0.
Two things follow from being pre-1.0 and single-publisher:
- It can change. A 0.x version signals that the format is still evolving. Keys, defaults, and linter rules can shift between releases. Pin the version you author against if you need stability.
- Governance is the publisher's. The direction of the format is set by its maintainers rather than a standards committee. That tends to mean faster iteration and less formal ceremony.
DESIGN.md is not DTCG, and that distinction is the crux#
The most common source of confusion is the relationship between DESIGN.md and the closest thing to a token standard: the W3C Design Tokens Community Group (DTCG) format.
- DTCG is a JSON-based token interchange format maintained by a W3C Community Group. It reached schema version
2025.10. Of the two, it is the one associated with a standards body. - DESIGN.md is a Markdown-plus-YAML format from Google. Its documentation notes it is inspired by the W3C token work, and its CLI can export a DESIGN.md to a valid DTCG JSON file.
So when someone asks whether DESIGN.md is a W3C standard, the precise answer is: no, but it interoperates with the W3C-community token format. DESIGN.md can be your human-and-agent-facing source of truth while still feeding DTCG-based pipelines through the export command. For a full comparison of the two formats, see DESIGN.md vs DTCG.
Should its status change whether you adopt it?#
Formal status is the wrong thing to optimize for here. A DESIGN.md is a plain-text file that an AI coding agent or a person can read, and its usefulness does not depend on ratification. What actually matters for adoption:
- The files are durable. Markdown and YAML stay readable regardless of what happens to the spec. Even if you stopped using the tooling entirely, your DESIGN.md is still a legible document.
- The files are checkable. The CLI lints a file against the current spec, so you can detect when a file has drifted from the version you target. See the design tokens guide for what the linter checks.
- The files are portable. Export to Tailwind for implementation or to DTCG for tool pipelines. You are not locked into one output.
Treat DESIGN.md as what it is: a useful, open, evolving convention with solid tooling. Adopt it because it solves the problem of giving agents durable design context, not because a committee blessed it.
Confirm your file against the current spec#
Because the format is pre-1.0, the practical safeguard is to check your file rather than assume it is compliant. Paste or drop your DESIGN.md into the viewer to see it rendered and confirm every token resolves. Parsing runs entirely in your browser, so nothing is uploaded.
Frequently asked questions
Is DESIGN.md a W3C standard?
No. DESIGN.md is an open format published by Google under the Apache 2.0 license. The W3C Design Tokens Community Group publishes a separate token interchange format (DTCG). DESIGN.md is inspired by that work and can export to it, but DESIGN.md itself is not a W3C standard.
Who created DESIGN.md?
DESIGN.md is published by Google as the open-source @google/design.md package, released under the Apache 2.0 license. The package is the reference implementation of the format, including the CLI that lints, diffs, and exports files.
Is DESIGN.md stable enough to use?
The spec is pre-1.0 (v0.3.0 at the time of writing), so expect it to change. The files are plain Markdown and YAML, so they stay readable even as the spec evolves, and the CLI can lint a file against the current spec to catch drift.