zeroheight Review (2026): Pricing, Features & Honest Verdict

TLDR

zeroheight is a design system documentation platform that syncs Figma components, Storybook code and design tokens into one living styleguide. It is the most polished option in this category, and the free tier is genuinely usable. Best for: product teams maintaining a shared design system. Price: Free plan yes, Starter from $49 per editor/mo. Rating: 8.3/10

What is zeroheight?

zeroheight is a hosted home for your design system. You connect Figma, Storybook and your token files, then write documentation around them in a straightforward editor. The output is a styleguide site, public or private, that designers, engineers and product managers can all read without opening a design file. Components pull from the source, so when a designer updates a Figma frame the documentation updates with it. No exports, no screenshots, no stale PNGs rotting in a Confluence page.

The company is a London based team that has been building this since before “design system” was a standard job title, and the head start shows in how finished the product feels. zeroheight says a fifth of the Fortune 100 uses it, with Uber and Dutch Railways among the named customers. The 2026 version has widened well past documentation into governance and measurement: adoption analytics, token management, an AI assistant that drafts component docs, and MCP support so AI coding agents can read your system. We dug into it and found the core still does the thing it always did best, which is make a design system legible to people who do not live in Figma all day.

What Are zeroheight’s Key Features?

Live Figma and Storybook sync

This is the feature that sells the product. Embed a Figma frame in a zeroheight page and it stays connected to the file, so a component update in Figma flows through to the docs without anyone re-exporting anything. The same applies to Storybook: you point zeroheight at a Storybook instance and it renders the real interactive component next to the design. Engineers get the code, designers get the visual, and both are reading the same page. Sketch and Adobe XD integrations exist too, and every integration is available on every tier including the free one, which is unusual. Most competitors gate the developer connections behind a paid plan. You also get versioning on the styleguide itself, so you can publish changes deliberately rather than having half-finished edits appear live the moment somebody saves.

Design token management

zeroheight stores token sets and publishes them as documentation, so your colour ramp, spacing scale and typography live in one place rather than in three half-synced spreadsheets. Tokens are capped by plan: one token set on Free, three on Starter, ten on Enterprise. That cap matters more than it sounds. A team running separate light and dark themes plus a marketing brand will burn through three sets faster than they expect, and the jump from Starter to Enterprise means a sales call. Tokens can be pushed out to code through the GitHub and GitLab integrations, so the documented values and the shipped values stay aligned rather than drifting apart over a few releases.

Adoption analytics

The measurement layer tracks how much of your system is actually being used, which is the number design system leads get asked about in every quarterly review. You can see which components are documented, which are being viewed, and where the gaps sit. It is the strongest argument for paying for zeroheight rather than assembling a free stack, because a Notion page and a Storybook instance will never tell you whether anyone is using the thing you built. In practice this is what turns a design system from a side project into a funded programme. When a director asks what the system is returning, screenshots do not answer the question and a usage chart does.

AI documentation and MCP support

The AI assistant drafts component descriptions, usage guidance and do/do-not examples from your existing components, which removes the worst part of design system work. Capability scales with tier, and the full assistant is Enterprise only. More interesting for engineering teams is the MCP server: it lets AI coding agents query your design system directly, so a generated component has a chance of matching your tokens instead of inventing its own.

How Much Does zeroheight Cost?

zeroheight starts free. The Free plan gives you one editor, one styleguide, one token set and unlimited viewers, with the Figma, Sketch, Storybook, GitHub and GitLab integrations included. That is a real product, not a demo. A solo designer documenting one system can run on it indefinitely, and the unlimited viewer count means the whole company can read it without adding a cent.

Starter is $49 per editor per month billed annually, or $59 per editor month to month, which is a 20 percent penalty for staying flexible. It is capped at five editors. It unlocks a second styleguide, three token sets, commenting and a custom domain, and comes with a 14 day trial. Enterprise is custom priced and covers five or more editors, five or more styleguides, ten token sets, SSO, IP range restrictions, API access and a dedicated customer success manager. The per-editor model is friendly if your system has two or three maintainers and hostile if you want a wide contributor base, since every person who edits a page needs a seat.

Against the field, that positioning is fair rather than cheap. Supernova has its own free plan and starts around $20 per builder seat per month on annual billing, so it undercuts zeroheight at the entry level. Frontify does not publish prices at all and sells on enterprise contracts. Storybook is free and open source but only documents code, not design intent. The real cost question is the Enterprise cliff: API access and SSO are both locked behind it, so a mid-sized company that needs single sign-on has no published price to plan against.

Who is zeroheight Best For?

Use zeroheight if you have a design system with more than one maintainer and an audience that includes engineers. The Figma and Storybook sync is the whole point, and it only pays off when designers and developers are both consuming the same documentation. It is also the right pick if you need to prove adoption to leadership, because the analytics do that work for you rather than leaving you to build a spreadsheet nobody trusts.

• Design teams of 3 to 30 who maintain a shared component library
• Product organisations where engineers ignore Figma and designers ignore Storybook
• Agencies handing a documented system over to a client team
• Teams that already run Storybook and want a design-facing layer on top of it
• Design system leads who need adoption numbers for a budget conversation

Skip zeroheight if you are a solo freelancer with one small system, because the free tier will cover you and you will never touch the paid features. Skip it if your system lives entirely in code and nobody reads design documentation, in which case Storybook plus a README is enough. And skip it if you need rendered, production-connected components with governance workflows across many codebases, which is closer to what Knapsack is built for. Finally, be honest about the editor count: if you want twenty people contributing docs, per-editor pricing will get expensive fast.

Best zeroheight Alternatives

Supernova

Supernova has drifted toward AI prototyping and design-to-code generation, but it still does design system documentation and token pipelines well. It has a free plan and Pro starts at roughly $20 per builder seat per month on annual billing, which makes it the cheaper entry point. Pick Supernova if automated code output from tokens is the goal and your team is comfortable with a product that is actively changing direction. Pick zeroheight if documentation quality, editing experience and adoption measurement matter more than code generation.

Frontify

Frontify is the brand-first option: digital asset management, brand guidelines and design system documentation in one platform, priced on monthly active users with no published rates. It suits organisations where marketing owns the brand and product owns the components and both need one home. It is heavier than zeroheight and the sales process is longer. Choose it if brand assets are as important as UI components, not if you only need a product design system. For a pure product team, most of what you pay for in Frontify goes unused.

Storybook

Storybook is free, open source and the default place engineers document components. It renders every state of a real component and it costs nothing. What it does not do is design context: usage guidance, accessibility notes, tokens, or anything a non-engineer wants to read. Plenty of teams run Storybook alone for years. If your documentation audience is entirely engineers, start here and only move to zeroheight when designers and product managers start asking where the docs are. The two are not mutually exclusive either, since zeroheight embeds Storybook directly.

Final Verdict: Is zeroheight Worth It?

zeroheight earns an 8.3 because it is the rare tool that does one job properly. The Figma and Storybook sync removes the single biggest reason design systems go stale, the editor is approachable enough that a first-timer can publish a decent styleguide in an afternoon, and the free tier is not a crippled trial. Design system practitioners consistently rate it the most satisfying documentation tool in the category, and having dug through the platform we understand why. Nothing about it feels like a workaround. The pages look good by default, the integrations behave, and the maintenance burden after setup is close to zero, which is exactly the failure mode most design systems die from.

The marks come off for pricing structure rather than product quality. Per-editor billing punishes wide contribution, the token set caps arrive sooner than you expect, and putting API access and SSO behind an unpriced Enterprise tier makes budgeting awkward for mid-sized teams. If you have a real design system, two to five maintainers and an audience that includes engineers, zeroheight is worth the $49 per editor. If you are one person documenting one system, stay on the free plan and enjoy it, because it is the best free design system documentation you can get without hosting anything yourself.