Convert CSS custom properties into SCSS, Less, a Tailwind theme, JSON, a JS module or W3C draft tokens, keeping every scope instead of flattening them.
Waiting for a stylesheet
Paste CSS containing custom properties. Everything declared with a leading -- is picked up, with the selector it was declared in.
The converted tokens appear here
Every custom property rewritten in the format you choose, with the scopes kept rather than flattened.
Design Token Converter runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Converting CSS custom properties to SCSS variables is not a change of notation, it is a change of behaviour, and this is the thing a token converter can quietly destroy. Custom properties resolve at runtime: they cascade, they respond to media queries, and JavaScript can change them. SCSS and Less variables resolve at compile time and do not exist in the output at all. A dark theme built by redeclaring tokens in a second selector stops working the moment those tokens become compile-time constants.
So the conversion warns rather than reporting success. When the stylesheet declares tokens in more than one scope and the target format can only hold one value per name, the surface names the scopes being lost and offers to convert one at a time instead of silently letting the last declaration win.
`var()` references are written through unchanged rather than resolved. Resolving them would discard indirection you put there deliberately — `--color-link: var(--color-brand-500)` exists precisely so that changing the brand changes the link. In a format that does not evaluate `var()` at runtime those references will not work, which the page says plainly instead of producing output that looks resolved.
The W3C design token format is included and labelled as the draft it is. The Design Tokens Community Group spelling has changed before and may again, and the types written into it are inferred from each value, so they are worth reading before anything depends on them.
No, and this is the important caveat. Custom properties resolve at runtime and can cascade, respond to media queries and be changed by JavaScript. SCSS variables resolve at compile time and are gone from the output. The names and values survive the conversion; the behaviour does not.
In a runtime format, nothing — it converts cleanly. In a compile-time format it cannot survive, because the same name cannot hold two values. The tool tells you which scopes would be lost and lets you convert one scope at a time rather than letting the last declaration win silently.
Because resolving them would throw away indirection that is usually deliberate. A link colour pointing at a brand colour exists so that changing one changes the other. The references are passed through unchanged, and the page says where they will not work.
Not yet. It is a Community Group draft whose spelling has changed before. It is offered because tools are adopting it, and it is labelled as a draft because depending on it means accepting that it may move.
Yes. Turning on nesting splits hyphenated names into an object path, so --color-brand-500 becomes color.brand.500. A name that is both a leaf and a branch is placed under a DEFAULT key, which is the convention Tailwind uses for that case.