UI Verify vs Chromatic

Chromatic pricing compared: UI Verify costs half as much per snapshot

Chromatic pioneered visual testing for Storybook. UI Verify gives you the same snapshot-and-diff on every pull request, adds an AI judge that tells a real regression from an intended change, and bills about half the price per snapshot.

2x
the free tier

10,000 snapshots a month, free, versus Chromatic's 5,000.

1/2
the price per snapshot

$0.004 over your plan versus Chromatic's $0.008.

1/2
the entry price

Starter is $89 a month versus Chromatic's $179.

Pricing, side by side

Both tools bill per snapshot. UI Verify includes more on every tier and charges half as much once you go over.

UI VerifyChromatic
Free10,000 snapshots5,000 snapshots
Starter$89/mo · 30,000$179/mo · 35,000
Pro$199/mo · 65,000$399/mo · 85,000
Over your plan$0.004 / snapshot$0.008 / snapshot

What you’d actually pay

Monthly bill at a given number of billed snapshots, on the cheapest plan that covers it.

The same 50,000 snapshots, two bills

UI Verify

Plan · 30,000 snapshots included
$89
20,000 over × $0.004
$80

Total / month

$169

Chromatic

Plan · 35,000 snapshots included
$179
15,000 over × $0.008
$120

Total / month

$299

That is $130 a month that stays with you, at list price, before the overage rates double the gap. Plug in your own numbers.

Snapshots / monthUI VerifyChromaticYou save
10,000Free$179$179/mo
25,000$89$179$90/mo
50,000$169$299$130/mo
100,000$339$519$180/mo

Chromatic list pricing from chromatic.com/pricing, November 2026. UI Verify pricing from our own plans. Both tools skip unchanged screens, so your billed snapshot count is typically far below your full UI on either.

How Chromatic pricing works, and how to cut the bill

Chromatic pricing is per snapshot: chromatic.com/pricing, November 2026 lists a free plan of 5,000 snapshots a month on Chrome only, Starter at $179 a month for 35,000, Pro at $399 for 85,000, and custom Enterprise pricing. Your bill is the states you render times how often CI renders them, so you cut it by rendering fewer states and skipping the unchanged ones. Competitor pricing moves, so treat the plan names and numbers here as the shape of the model and check Chromatic's own pricing page for current figures.

What counts as a Chromatic snapshot?

  • One story, one browser, one viewport, one snapshot. More stories, more browsers, or more viewports multiply the count directly.
  • Every build that runs a story re-bills it, unless the tool skips it as unchanged, and even a skipped story bills at a fraction of a snapshot. Running visual tests on every commit rather than every PR multiplies the run count.
  • Modes multiply too. A story rendered in light and dark, or at three breakpoints, is that many snapshots.
One Button with five stories, rendered in two browsers, is ten snapshots on every build that runs them.

Why does a Chromatic bill jump when you adopt coding agents?

The pattern is the same across teams: the bill roughly doubles or triples in a quarter on the same tests. Nothing about the UI got more valuable to screenshot. The machine opened many more pull requests, each one re-rendering your stories, and per-snapshot billing tracks render count times run frequency, so agent-scale PR volume hits both terms at once. When PR volume climbs, nobody spends proportionally longer reviewing each check, so you end up paying peak prices for a check people have stopped reading. Why your Chromatic bill exploded covers it in more detail.

How do you lower a Chromatic bill without dropping coverage?

  1. Render fewer states. Collapse near-duplicate stories and drive variants through args instead of separate exports. Two story patterns can cut a component's snapshot count up to 10x with the same coverage, walked through in how I cut my Chromatic bill 10x.
  2. Skip unchanged work. TurboSnap skips stories whose code did not change, which cuts the run term, though a skipped story is not free: Chromatic's pricing page counts Starter's 35,000 snapshots as 175,000 TurboSnaps, so each one bills a fifth of a snapshot. Check your actual skip rate rather than assuming it is working.
  3. Run on pull requests, not every commit, unless instant per-commit feedback is worth the multiple to you.
  4. Trim browsers and modes to the ones that catch distinct regressions for your product.
Once you stop re-billing unchanged stories on every commit and cut the exploding near-duplicates, the bill can come down by more than half on the same coverage. The levers are the same on any per-snapshot tool, so pull them before you decide the price is the problem.

How does UI Verify price the same job?

UI Verify does the same core job, cloud screenshots on every pull request diffed against baselines, with an AI judge on top. The free tier is 10,000 snapshots a month with no credit card (50,000 for open-source projects), then plans from $89 a month for 30,000 snapshots, with $0.004 per snapshot beyond your plan against Chromatic's $0.008. The same cost levers apply, so economical visual tests and skip-unchanged work here too. The pricing calculator shows your monthly cost across Chromatic, Percy, Applitools, and UI Verify at your volume.

Beyond price

The bigger difference is what happens to a changed snapshot. Chromatic shows you the pixel diff to triage by hand. UI Verify can add an AI judge’s verdict to each change, and lets your coding agent act on it over MCP.

UI VerifyChromatic
AI judge labels each change (intended or regression)YesNo
Coding agent reviews and fixes over MCPYesNo
Works without Storybook (Playwright, Vitest)YesYes
Snapshot only what changedYesYes
Every browser and viewportYesYes

Chromatic facts checked 2026-11-11 against chromatic.com/pricing, November 2026.

When Chromatic is the better choice

Chromatic is made by the Storybook team, so if you want first-party Storybook tooling, a built-in designer sign-off and publishing workflow, or the maturity of a tool that has been around for years, it is a strong, well-supported choice. UI Verify is the better fit when your priority is a lower bill, an AI judge that cuts review noise, and a review loop your coding agent can drive.

Chromatic and UI Verify: common questions

Chromatic is billed per snapshot, so there is no single number: your cost is the states you render times how often CI runs them, with higher plans buying a larger monthly allowance. Starter is $179 a month for 35,000 snapshots, then $0.008 each. A small project on the free tier of 5,000 snapshots a month pays nothing, while a team rendering hundreds of thousands of snapshots on agent-scale PR volume can reach four or five figures a month.

Chromatic has a free tier of 5,000 snapshots a month on Chrome, which is enough for a small library or a side project. Past that you move onto per-snapshot paid plans. UI Verify's free tier is 10,000 snapshots a month and 50,000 for open-source projects, and Playwright's toHaveScreenshot is free to run locally in your own CI with no service at all.

Switch in an afternoon

Your first build sets fresh baselines, and you can run UI Verify alongside Chromatic while you compare. Start free with 10,000 snapshots a month (50,000 for open source), no credit card.