Chromatic vs Percy
Feature checklists rarely decide anything. What decides it is the pricing metric, who has to write the tests, and which limitation you can live with.
Entry price
From $179 per month (Starter, 35k snapshots)
Free tierFree tier available
Free tierWhat drives the bill
The metric that actually scales your invoice.
Snapshot-based billing: Starter $179 for 35k snapshots, Pro $399 for 85k, then Enterprise. Overage runs about $0.008 a snapshot. TurboSnap, which only re-tests stories affected by a change, is the main cost control. Cross-browser coverage beyond Chrome starts at Starter.
BrowserStack no longer publishes standalone Percy prices — its own /percy/pricing page is gone and Percy now appears bundled into wider BrowserStack packages (it is one of the products in Team Ultimate at $375/month billed annually) or priced by sales. Paid plans still include a fixed screenshot allowance with overage on top, so multiply pages x widths x browsers x commits before committing — this is where budgets are misjudged.
Free tier
Free tier with 5,000 billed snapshots a month (25k TurboSnaps), unlimited projects and users.
5,000 screenshots a month, unlimited users and projects.
Open source
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Widely used
Chromatic · since 2017
Widely used
BrowserStack · since 2015
Strengths
- Zero-effort setup if you already have Storybook — stories are the tests.
- The hosted review UI is genuinely usable by designers and product managers.
- TurboSnap dramatically reduces snapshot cost on large libraries.
- Plugs into an existing suite with a few lines rather than requiring new tests.
- Server-side rendering removes machine-to-machine screenshot inconsistency.
- Good PR-based approval workflow that developers actually use.
Limitations
- Strongly tied to Storybook; without it much of the value disappears.
- Component-level, not full-page — it will not catch a broken page layout.
- Snapshot pricing still adds up on a big design system.
- Screenshot-based billing escalates faster than teams expect.
- Dynamic content requires careful masking or you drown in false diffs.
- Responsive widths are rendered, not truly executed in each browser, which occasionally hides real issues.
Best for
Design-system and component-library teams already invested in Storybook.
Teams with an existing E2E or Storybook suite who want visual coverage without new tests.
All of these integrate with: Storybook, GitHub, GitLab, Playwright.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.