There are six honest ways to get design tokens out of a live website in 2026, and the right one depends on whether you are doing this once, weekly, or inside a product. Here is the list, with the tradeoffs stated plainly. Yes, our own API is on it - ranked where I would rank it if it were not ours.
1. CSS Stats - fastest free look
cssstats.com has been the "paste a URL, see the CSS" tool for a decade. It reports every color, font size, and font family the stylesheet declares, plus specificity graphs nobody asks for but everyone screenshots.
- Good: free, no signup, instant.
- Bad: it reads declared CSS, not used CSS. A site shipping a big framework stylesheet reports hundreds of colors that never render. There is no export worth automating against.
- Use it when: you want a two-minute overview of a site's CSS health, not a token set.
2. Project Wallace - the analyzer that kept evolving
Project Wallace does what CSS Stats does but deeper: color counts, typography breakdowns, and change tracking over time if you create an account.
- Good: the most thorough free CSS analysis on the web, actively maintained.
- Bad: same fundamental limit - declared, not rendered. Still a report you read, not a token file you use.
- Use it when: auditing your own CSS over time, or studying how a site's stylesheet is put together.
3. Superposition - tokens on your desktop
Superposition is a desktop app that crawls a page and exports design tokens to CSS variables, Sass, JS, and even Adobe XD. It was ahead of its time.
- Good: genuine token export formats, one-click, offline app.
- Bad: desktop-only, so there is nothing to call from code or CI. Development has been quiet for a while - check that the export you need still works.
- Use it when: you are a designer who wants tokens from a reference site without touching a terminal.
4. A DIY Playwright script - full control
Load the page in a headless browser, read getComputedStyle off every element, count what repeats. We wrote the complete walkthrough in How to Extract Design Tokens from Any Website in Python.
- Good: free, sees exactly what renders (including runtime CSS-in-JS), infinitely customizable.
- Bad: you now run browser infrastructure. Cookie banners, lazy fonts, and viewport-dependent styles are your problem, and the script that worked in April breaks in July.
- Use it when: one-off extractions, research, or when you need something no tool exposes.
5. MiroMiro browser extension - point and click
Our extension shows a site's tokens live as you browse: colors, typography, spacing, assets. Click an element, see its resolved styles, export what you want.
- Good: zero setup, visual, great for picking tokens from a specific component rather than the whole page.
- Bad: it is a human tool. Nothing to automate, no JSON endpoint, and it extracts what you look at, not a thousand URLs.
- Use it when: hand-picking design decisions from reference sites during design or build.
6. MiroMiro extract API - tokens as an endpoint
One GET request returns the ranked token set as JSON, CSS variables, or a Tailwind theme block:
curl "https://miromiro.app/api/v1/extract?url=stripe.com&format=tailwind" \
-H "Authorization: Bearer $MIROMIRO_API_KEY"
- Good: deduped and ranked (not raw declared values), covers colors, type scale, spacing, radii, shadows, gradients, and motion, resolves
var()chains and every declared breakpoint. It is the only option on this list you can put inside a product. - Bad: it parses static HTML + CSS and does not execute JavaScript, so a fully client-rendered app can come back thin. Costs credits past the free 100 a month.
- Use it when: tokens need to arrive programmatically - agent pipelines, onboarding flows, bulk analysis.
The comparison in one table
| Tool | Output | Rendered or declared? | Automatable | Price |
|---|---|---|---|---|
| CSS Stats | Web report | Declared | No | Free |
| Project Wallace | Web report + tracking | Declared | Partially | Free tier |
| Superposition | Token files (CSS/Sass/JS) | Rendered | No | Free |
| DIY Playwright | Whatever you build | Rendered | Yes, you maintain it | Your time |
| MiroMiro extension | Visual + export | Rendered | No | Free tier |
| MiroMiro API | JSON / CSS vars / Tailwind | Parsed + resolved | Yes | 100 credits/mo free, then from €19/mo |
The verdict
For a quick look, Project Wallace. For hand-picking from a reference site, the extension. For anything that runs on a schedule or inside a product, the API - and I would say that even if it were someone else's, because it is the only entry here that returns a token file over HTTP. You can get a free API key (100 credits a month, no card) or poke it in the playground first.
Frequently asked questions
What is the fastest free way to extract design tokens from a website?
Paste the URL into CSS Stats or Project Wallace. Seconds, no signup. Expect raw declared values, not a cleaned token set.
Can I get tokens as CSS variables or a Tailwind config directly?
Yes - format=css returns custom properties, format=tailwind returns a theme block. Details in the design tokens docs.
Do these tools work on Tailwind sites?
The ones reading real CSS or computed styles do; bg-indigo-600 is just CSS once shipped. Tools that only look for CSS custom properties miss most of a Tailwind site's system.
What is the difference between a token set and a color palette?
A palette is one token group. A full token set adds the type scale, spacing, radii, shadows, motion, and z-index layers - see the design token types reference.
Skip the maintenance - one API call
Design tokens, brand data, fonts, SVGs, images, and section code from any URL. 100 free credits a month, no card.
Soraia · Founder, MiroMiro
Building MiroMiro: a browser extension and API that extract design tokens, assets, and production-ready code from any live website. The gotchas in these posts come from the extraction engine's own commit history.
Follow on X