Chromatic alternatives
Chromatic is excellent for Storybook and priced per snapshot. The alternatives — Loki, Argos, the Vitest addon route, Applitools and page-level tools — with costs and what each gives up.
Chromatic is the best-integrated visual testing tool for Storybook, and that is not in dispute. Teams look for alternatives for two reasons: the snapshot bill at scale, or the growing realisation that story-level coverage is not the same as knowing your pages render correctly.
Which of those applies to you determines the answer, so it is worth being honest about it first.
Chromatic's published pricing, for reference
| Tier | Price | Billed snapshots | With TurboSnap | Browsers |
|---|---|---|---|---|
| Free | $0 | 5,000 | 25,000 | Chrome only |
| Starter | $179/mo | 35,000 | 175,000 | Chrome, Safari, Firefox, Edge |
| Pro | $399/mo | 85,000 | 425,000 | All |
| Enterprise | Custom | Unlimited | — | All, plus SSO and SLA |
If the problem is cost
Best for: Storybook teams who want zero vendor spend and can approve from a CLI.
- License
- MIT, open source (1.9k stars)
- Pricing
- Free
The closest open-source equivalent to what Chromatic does at the capture-and-compare layer. What you give up is precisely the part non-engineers used, so weigh who actually reviews your visual changes before switching.
- No snapshot ceiling and no bill at any volume
- Purpose-built for Storybook with minimal configuration
- Docker rendering makes results reproducible across machines
- Also targets iOS simulators and Android emulators
- No hosted review UI — approval is a CLI operation
- Designers and product managers lose the ability to review changes
- Baselines live in your repository
- No TurboSnap equivalent, so every story is captured every run
Best for: Teams wanting a hosted review UI at a lower price point.
- License
- Open source, with a hosted commercial tier
- Pricing
- Free 5,000 screenshots/mo · Pro $100/mo for 35,000 · Storybook overage $0.0015 each
The strongest value argument among hosted alternatives, and the Storybook overage rate is notably cheap. Run the numbers on effective snapshots rather than billed ones though — with TurboSnap enabled, Chromatic's 35,000 becomes 175,000, which changes the comparison substantially.
- $100/mo for 35,000 versus Chromatic's $179 for the same volume
- Storybook screenshots are priced at $0.0015 versus $0.008 for Chromatic overage
- Full review and approval workflow
- Also covers page-level Playwright captures, so coverage is not limited to stories
- No TurboSnap equivalent, so the effective allowance comparison is closer than the headline
- Smaller ecosystem and fewer Storybook-specific niceties
- Less mature design-collaboration tooling
Best for: Teams already moving to Storybook's current recommended runner.
- License
- Free, varies by addon
- Pricing
- Free
The most forward-looking free option, and the one with the most churn. Check an addon's recent commit history before adopting it. Background in Storybook visual regression testing.
- Storybook now recommends the Vitest addon over the older test-runner
- Runs stories as real browser tests, so this aligns with where Storybook is going
- Several visual addons exist: storybook-addon-vrt, storybook-addon-vis, @storycap-testrun/browser
- No vendor and no snapshot limit
- The visual addons vary in maturity and are the most fast-moving part of this ecosystem
- No hosted review UI
- This space already lost Lost Pixel, archived April 2026 when its team joined Figma
If the problem is coverage
This is the more consequential reason to look elsewhere, and it is not really a Chromatic limitation — it is a limitation of story-level testing generally.
- A component with no story is invisible. Coverage is a function of story discipline, which decays.
- Isolation hides composition bugs. A button can pass in its story and still overlap a heading on the settings page.
- Stories use fixture data. Real pages get long strings, missing fields, and nulls — exactly what breaks layouts.
- Nobody writes a story for a route. The pages customers actually load are not what you are testing.
If that is your problem, no Storybook-based alternative solves it. You need page-level coverage, either alongside Chromatic or instead of it.
Best for: Adding real-route coverage that stories cannot provide.
- License
- Apache 2.0 / commercial
- Pricing
- Playwright free · Applitools Starter $667/mo billed annually
The honest framing is that this is a different job rather than a replacement. Many teams run both: Chromatic for the design system, and page-level checks on the routes that carry revenue.
- Tests the composed page with real data, not a component in isolation
- Playwright is free and its assertions retry until the image is stable
- Applitools adds perceptual comparison and cross-browser rendering at scale
- You author a spec per route, which is the maintenance Chromatic's story reuse avoided
- Playwright gives no hosted review workflow
- Applitools is materially more expensive than Chromatic at comparable volume
Best for: Page-level coverage without writing a spec per route.
- License
- Commercial
- Pricing
- First week free, then paid
This is our product, and we would not suggest dropping Chromatic for it if your design system is the thing you need tested. The case is for the gap Chromatic leaves: the composed pages nobody wrote a story for.
- Discovers routes from the running application, so coverage is not tied to story or spec discipline
- Waits for real data before capturing, so pages are tested in their real state
- Recaptures only the routes a change can affect
- Complements Storybook rather than replacing it
- Not a component-library tool — it will not replace Chromatic for design-system work
- Hosted only
- Newer, with a smaller integration surface
Choosing
- Bill too high, and TurboSnap is already on — Argos at $100/mo, or Loki for free if CLI approval is acceptable.
- Bill too high, TurboSnap not enabled — enable it first. It is usually a 70–80% reduction.
- You need Safari coverage and are on the free tier — that is the $179/mo Starter tier, and Argos is cheaper for equivalent volume.
- Regressions keep reaching production despite green Storybook runs — your gap is page-level coverage, not the vendor.
- You want to leave Storybook entirely — that is a much larger decision than a visual testing one.
Frequently asked questions
What is the best alternative to Chromatic?
For cost, Argos at $100/month for 35,000 screenshots, or Loki for free if approving baselines from a CLI is acceptable. For coverage gaps rather than cost, no Storybook-based alternative helps — you need page-level testing through Playwright, Applitools, or a route-discovering service.
Is there a free alternative to Chromatic?
Loki is the closest free equivalent — MIT-licensed, purpose-built for Storybook, with Docker rendering for reproducibility. It has no hosted review UI, so approval happens at the command line. Chromatic's own free tier of 5,000 billed snapshots also stretches to roughly 25,000 with TurboSnap.
Why is Chromatic expensive?
Pricing is per snapshot, and snapshots multiply as stories × viewports × browsers × runs. The most common cause of an unexpectedly large bill is TurboSnap not being enabled — it copies unchanged snapshots rather than recapturing them, typically cutting billed snapshots by 70–80%.
Sources
- Chromatic pricingchecked 2026-09-13
- Argos pricingchecked 2026-09-13
- Loki repositorychecked 2026-09-13
- Storybook Vitest addon documentationchecked 2026-09-13
- Applitools pricingchecked 2026-09-13