Chromatic vs Argos
Argos is $100/month against Chromatic's $179 and captures locally in your own test browser. Where that architecture wins, where TurboSnap closes the gap, and which one fits your coverage.
The headline is price — $100 a month against $179 for the same 35,000 captures. The more interesting difference is architectural: Argos diffs screenshots taken locally in the browser your tests already run, while Chromatic renders your built Storybook in its own cloud. That decides more than the invoice does.
- Your coverage is Storybook stories and you want the deepest integration available
- TurboSnap materially cuts your volume — model it against your real git habits
- Baseline handling across many parallel branches matters
- Designers and PMs need a polished review and design-collaboration surface
- You want the cheapest hosted review UI — $100/mo for 35,000
- You capture with Playwright and want rendering to match your CI exactly
- Your coverage includes real routes, not only stories
- You want an open-source core and the option to self-host
At a glance
| Chromatic | Argos | |
|---|---|---|
| Free tier | 5,000 billed snapshots (≈25,000 with TurboSnap), Chrome only | 5,000 screenshots, framed for personal projects |
| Entry paid | $179/mo for 35,000 | $100/mo for 35,000 |
| Next tier | Pro $399/mo for 85,000 | Enterprise, custom |
| Overage | $0.008 per snapshot | $0.004, or $0.0015 for Storybook |
| Capture | Built Storybook rendered in Chromatic's cloud | Local, in your own test browser |
| Change targeting | TurboSnap — dependency-graph aware | None equivalent |
| Coverage | Storybook stories | Playwright, Storybook, and other capture sources |
| Licence | Commercial | Open-source core, hosted commercial tier |
| Parallelisation | Unlimited on all tiers | Included |
The price comparison is closer than it looks
At list price Argos is 44% cheaper for the same headline volume, and the Storybook overage rate of $0.0015 against Chromatic's $0.008 is a more than fivefold difference. On raw rates Argos wins clearly.
TurboSnap complicates it. Chromatic's 35,000 billed snapshots stretch to roughly 175,000 captures because unchanged stories are copied rather than recaptured. Argos has no equivalent, so 35,000 means 35,000. On that basis Chromatic can be the cheaper tool per unit of coverage.
The practical advice: run Chromatic free for a fortnight and read the actual billed-snapshot count against your capture count. That ratio is your real multiplier, and it is the only number worth putting in a spreadsheet.
Local capture vs cloud rendering
The architectural difference, and the one that matters beyond price.
Argos captures in your own test browser. The pixels you approve are the pixels your CI produced. If your application renders differently under your specific browser version, fonts or container, Argos sees that — and so do you. The cost is that determinism is entirely yours: fonts, animation, clocks and data all behave exactly as they do in your suite, including badly.
Chromatic renders in a standardised cloud environment that watches for loading, painting and reflow to choose the capture moment. That is a real determinism feature and removes a class of flake you would otherwise engineer around yourself. It also archives the DOM and styling at capture time, so you can inspect a change in your own browser rather than re-running the suite to reproduce. The trade is that the rendering environment is theirs, not yours.
Neither is simply better. If your flake problem is environmental drift, Chromatic's standardisation helps. If your bug is environment-specific, Chromatic's standardisation hides it. More on the underlying causes in how to fix flaky visual tests.
Coverage scope
Chromatic is Storybook-first by design; that tight coupling is its greatest strength and its firmest boundary. Coverage equals story coverage, so a component with no story is invisible and a composed page is never tested as a page.
Argos is capture-source agnostic — Playwright, Storybook, or anything that produces images — so it can cover real routes alongside components. If your regressions keep appearing on composed pages rather than in components, that flexibility matters more than the $79 difference.
Both still require you to write the thing that produces the capture. Neither discovers a route you did not test, which is covered in Storybook visual regression testing — and if that is the constraint you care about, a whole category of tools now generates its own coverage.
Baselines
Chromatic's baseline engineering is the deepest in the category: baselines live alongside git history, persist through branch and merge, and squash or rebase merges are detected via git provider APIs. With one documented catch — approving on main does not update other branches' baselines, producing "changes that look new but were already approved". The preferMergedBaselines flag fixes it but is account-level only.
Argos is simpler and keeps baselines outside your repository, which avoids the binary-bloat problem entirely. For most teams simpler is fine; for a busy monorepo with many parallel branches touching shared components, Chromatic's model is worth the money on its own. See managing visual test baselines.
Which one
- Pure Storybook design system, heavy volume, stable git workflow — Chromatic. TurboSnap likely makes it cheaper per capture, and the review UI is the best in the category.
- Playwright-driven route coverage — Argos. Cheaper, captures where your tests run, and not limited to stories.
- Cost is the whole motivation — Argos, but measure your real TurboSnap ratio first.
- You need Safari coverage on a free tier — neither; Chromatic's free plan is Chrome only.
- You want no vendor at all — neither; see open source visual regression testing tools.
Frequently asked questions
Is Argos cheaper than Chromatic?
On list price yes — $100 per month for 35,000 screenshots against Chromatic's $179 for 35,000 snapshots, with Storybook overage at $0.0015 versus $0.008. But Chromatic's TurboSnap can stretch 35,000 billed snapshots to roughly 175,000 captures, so cost per unit of coverage depends heavily on how much TurboSnap actually saves on your repository.
What is the difference between Argos and Chromatic's capture models?
Argos captures screenshots locally in the browser your tests already run, so the approved pixels match what your CI produced. Chromatic renders your built Storybook in its own standardised cloud environment that detects loading and reflow to pick the capture moment, removing some flake but using its rendering environment rather than yours.
Can Argos replace Chromatic for Storybook testing?
Yes — Argos integrates with Storybook directly and prices Storybook screenshots at $0.0015 each. What you give up is TurboSnap's dependency-graph change targeting, Chromatic's deeper baseline handling across branches, and its design-collaboration features.
Sources
- Chromatic pricingchecked 2026-09-13
- Argos pricingchecked 2026-09-13
- Chromatic TurboSnap documentationchecked 2026-09-13
- Chromatic branching and baselines documentationchecked 2026-09-13
- Argos' own Chromatic comparisonchecked 2026-09-13