zeroheight / Tokens

Sync tokens across design, docs and code

Bring tokens into zeroheight for live documentation across your styleguides, then deliver them straight to your codebase. Modes, brands and token changes stay perfectly synced from design to implementation.

Manage

Make big design changes with confidence. Implementing dark mode or a new sub-brand is easier when you can see every brand, mode and alias in one place.

Document

Your design systems team stops becoming a helpdesk. Document tokens alongside your components, so product teams can find and use the right ones without asking.

Deliver

Ship design changes automatically. Update a variable in Figma and engineers get a pull request, instead of a backlog ticket asking them to copy values by hand.

Tokens / Manage

Spot gaps across brands and modes

Sync collections and modes directly from multiple Figma files. Your token structure is preserved and aliases continue to resolve correctly across brands and modes. Bring core and brand libraries together in zeroheight, and switch between brands in the token manager to compare every mode side-by-side.

Tokens / Document

Your tokens docs are always current

Stop spending time updating token documentation. Add live token tables to styleguide pages, choosing the mode combinations readers need to compare. Show resolved values and swatches, reference tokens inline with @mentions, and link documented components to the tokens they use.

Tokens / Deliver

Retire your hardcoded values

Get tokens into every codebase so engineers don't fall back on hardcoded values. Export in 13 formats, including CSS, Swift, Flutter and DTCG JSON. Choose the collections and modes to include, matching modes across collections to get only valid Light and Dark permutations. Deliver via exports, hosted URLs, the API or pull requests.

Tokens / Design-to-code

Automate token delivery from token change to pull request

zeroheight automates your token pipeline. When Figma variables change, it pulls them into the token manager, converts them to the format your codebase uses, then opens a pull request in your repo. Designers never have to leave Figma, and engineers can review the updates in Git like any other PR.

If we want to change something about the design tokens, we don’t need to ask all of the squads to make the change. We have control over the whole application.

Christophe de Canteloube

Staff Frontend Engineer

Tokens / Measurement

Find remaining hardcoded colours

Scan your repos to see which raw colour values are still in your code, in which files, and how often they appear. Plus, with the zeroheight MCP server, you can ask your coding agent to check a file against your tokens and even replace hardcoded values with the closest matching token.

Little details that make token work easier

From token search to inline references, zeroheight includes the practical features that remove friction from everyday token work.

Figma styles work too

Sync colour, text, effect and stroke styles as tokens, even if you don't use variables.

Git in both directions

Sync JSON from GitHub, GitLab, Bitbucket or Azure DevOps. Send edits back as pull requests.

Built-in guardrails

Catch duplicate paths, wrong types and broken aliases when editing tokens in zeroheight.

Independent token sets

Use the same sets across styleguides, or combine several sets on one page.

See changes before you sync

The Figma plugin shows which collections changed or were removed since your last sync.

Broken alias warnings

Get warned when an alias points to an unsynced library, with a prompt to import it.

Find tokens through search

Find tokens by name and jump directly to them in your styleguide.

API access

List sets and exports, or fetch any format for your own tooling (Enterprise plans only).