Visual testing pricing in 2026: Percy vs Chromatic vs Argos
Visual testing pricing in 2026: what a snapshot costs on Argos, Chromatic, Percy, and Applitools, checked on each vendor's pricing page, with worked math.
Visual testing pricing in 2026 ranges from free to several hundred dollars a month for an entry plan, and the sticker price is the least interesting number. What actually determines your bill is how each vendor counts a "screenshot" or "snapshot", because viewports, browsers, and CI builds multiply that count fast. As of October 2026, Argos Pro costs $100/month flat with 35,000 screenshots included, Chromatic Starter is $179/month for 35,000 snapshots, Applitools Starter is $667/month billed annually, and Percy Desktop is $199/month billed annually for 10,000 screenshots.
Every vendor's pricing page shows a monthly price next to a snapshot allowance. None of them walk you through the multiplication that turns your test suite into that number. This article does, with verified pricing and a worked example you can adapt to your own suite.
What are you actually paying for?
Every platform bills on the same unit: a captured image (or snapshot) that gets stored and diffed. But each vendor defines that unit differently, and the definition changes your bill more than the list price does.
- Argos: one screenshot = one file uploaded and stored for a build, so each viewport or browser you capture is its own file. That includes images from Playwright, Cypress, or Storybook, and also non-image files like Markdown, JSON, or HTML, since Argos diffs any file, not just pixels. Capture happens locally in your own test browser, so you decide exactly how many screenshots exist. (argos-ci.com/pricing, as of October 2026)
- Chromatic: one snapshot = one test capture, per browser, per viewport. Chromatic's billing docs give the formula: tests × builds × browsers × modes, where a mode is a viewport, theme, or locale you test. So 2 tests × 10 builds × 2 browsers × 2 viewports = 80 snapshots. Accessibility tests add one snapshot per test and mode in each build.
- Percy: your test uploads DOM, CSS, and assets, and Percy re-renders them in its cloud at every width set in
.percy.ymland in every browser enabled in the project's settings. Each rendered combination is a screenshot, the unit Percy bills. The multiplication happens server-side, after your test finishes. - Applitools: bills in checkpoints. Its Starter plan includes 100,000 component checkpoints or 1,000 page checkpoints; higher tiers are sized in active pages and quoted by sales.
The pattern to internalize: cloud-rendering vendors multiply your count for you; local-capture tools like Argos only count what you explicitly capture.
What multiplies your screenshot volume?
Your monthly volume is roughly:
tests (or stories/pages) × viewports × browsers × builds per month
Each factor deserves a hard look:
- Tests, stories, or pages. A 200-story Storybook is 200 captures minimum. Component-level testing keeps this manageable; full-page E2E suites grow faster.
- Viewports. Testing mobile + desktop doubles everything. Three breakpoints triples it.
- Browsers. On Chromatic and Percy, each browser multiplies the count again. On Argos, you only pay for extra browsers if you actually run your tests in them (extra Playwright projects, for example).
- Builds per month. Every push to an open PR triggers a build. An active team easily runs 20–40 visual builds per month per project. Force-pushes and CI re-runs count too.
- Retries. Flaky tests that retry can re-capture screenshots. Argos shows Playwright retries separately so they don't pollute your review, and stabilizing your screenshots keeps retry volume down on any platform.
Caps and overage matter just as much. When you exceed a paid plan's allowance, Chromatic charges $0.008 per extra snapshot, Percy $0.036 per extra screenshot on its Desktop plan ($0.048 on Desktop & Mobile), and Argos $0.004 per extra screenshot ($0.0015 for Storybook screenshots). All three let you keep shipping; on the Argos and Chromatic free plans, testing pauses at the limit. Argos additionally lets you set a budget limit so a runaway CI loop can't surprise you at the end of the month.
Visual testing pricing compared (as of October 2026)
All numbers below were checked on each vendor's official pricing page or billing docs in October 2026.
| Vendor | Free tier | Cheapest paid plan | Included volume | Overage | Parallelization |
|---|---|---|---|---|---|
| Argos | 5,000 screenshots/mo | $100/mo flat | 35,000 screenshots | $0.004/screenshot ($0.0015 Storybook) | Unlimited, included |
| Chromatic | 5,000 snapshots/mo (Chrome only) | $179/mo (Starter) | 35,000 snapshots | $0.008/snapshot | Unlimited parallel runs |
| Percy (BrowserStack) | 5,000 screenshots/mo | $199/mo (Desktop, annual) | 10,000 screenshots | $0.036/screenshot | Parallel builds supported |
| Applitools | None listed | $667/mo (Starter) | 100,000 component checkpoints | Not published | Not published |
Three notes on this table:
- Percy's prices are on BrowserStack's main pricing page. The old
browserstack.com/percy/pricingURL returns a 404, but browserstack.com/pricing?product=percy lists Desktop at $199/month billed annually ($249 month to month) for 10,000 screenshots, or $449 for 25,000, and Desktop & Mobile, which adds real mobile browsers, at $599/month billed annually ($729) for 25,000. Extra screenshots cost $0.036 on Desktop and $0.048 on Desktop & Mobile, and an Enterprise add-on (SSO, a dedicated success manager) is quoted by sales. The Percy billing docs count every browser and width combination: two pages rendered in two browsers at three widths are twelve screenshots. - Applitools publishes one price. Its pricing page lists Starter at $667/month, paid annually ($8,004 a year), for 100,000 component or 1,000 page checkpoints; Professional and Enterprise are quoted by sales. The Visual AI diffing is good at ignoring anti-aliasing noise, but the pricing is built for annual procurement, not a dev team with a credit card.
- Chromatic's numbers are real and public, which deserves credit. Free covers 5,000 snapshots (Chrome only), Starter is $179/month for 35,000, Pro is $399/month for 85,000, and TurboSnap bills unchanged stories at 1/5th the snapshot cost. It's an excellent product for Storybook-centric teams. Just do the browser × viewport multiplication before you pick a tier.
Worked example: what does a real team pay per month?
Take a concrete, common setup: 200 Storybook stories × 2 viewports (mobile + desktop) × 30 PR builds per month, single browser.
The volume math is the same everywhere:
200 stories × 2 viewports = 400 captures per build
400 × 30 builds = 12,000 captures per month
Now the bill, using only the verified numbers above:
| Vendor | Plan needed for 12,000/mo | Monthly cost | The math |
|---|---|---|---|
| Argos | Pro ($100/mo, 35,000 included) | $100 | 12,000 < 35,000 included, zero overage |
| Chromatic | Starter ($179/mo, 35,000 included) | $179 | 12,000 < 35,000 included, zero overage |
| Percy | Desktop ($199/mo billed annually, 10,000 included) | $271 | $199 + (2,000 × $0.036) overage |
| Applitools | Starter ($667/mo, billed annually) | $667 | Fits if Starter's 100,000 component checkpoints are monthly; the page doesn't say |
Argos is the cheapest at $100/month: 56% of Chromatic's price, 37% of Percy's and 15% of Applitools Starter, before the multipliers bite.
Now add a second browser (say Firefox) because a customer hit a rendering bug:
12,000 × 2 browsers = 24,000/month → still within the Argos and Chromatic 35k allowances
Percy: $449 (24,000 fits Desktop's 25,000 tier, billed annually)
Add a third browser or a third viewport and you cross 35,000:
200 × 2 viewports × 3 browsers × 30 builds = 36,000/month
Chromatic: $179 + (1,000 × $0.008) = $187.00
Percy: $449 + (11,000 × $0.036) = $845.00 (Desktop's 25,000 tier, billed annually)
Argos: $100 + (1,000 × $0.0015) = $101.50 (Storybook screenshot rate)
The gap widens as volume grows, because Argos overage runs at half Chromatic's rate for regular screenshots, under a fifth for Storybook screenshots, and a ninth of Percy's Desktop rate. And under 5,000 captures a month, a solo developer pays $0 on Argos, Chromatic, or Percy. Teams are where the free tiers differ: Chromatic's free plan allows unlimited collaborators but is Chrome-only, Percy's has unlimited users and keeps builds for one month, while Argos's free Hobby plan is for individual developers (commercial work and private organization repositories included), so a team that reviews builds together needs Pro.
One more line item that's easy to miss: parallelization. Sharding Playwright across 4 CI machines is the standard way to keep pipelines fast. Argos and Chromatic include unlimited parallel runs, and Percy supports parallel builds as well. If you shard your suite, check that your plan doesn't limit it.
How to keep visual testing costs down
Whatever platform you choose:
- Pick viewports deliberately. Two well-chosen breakpoints catch most responsive regressions. Five viewports is usually paying 2.5× for marginal coverage.
- Don't multiply browsers by default. Rendering engines have converged for most CSS. Add Firefox or WebKit when you have a reason, not as a starting point.
- Kill flaky retries. Every retry can re-capture screenshots. Stabilize your screenshots and flake stops inflating both your bill and your review queue.
- Set a budget cap. Argos lets you configure a spend limit; a misconfigured CI loop pushing 50 builds a day becomes a capped incident, not an invoice.
- Verify pricing yourself before you commit. Pages change. If a vendor makes you talk to sales to learn the price, assume it's negotiable.
Verdict
As of October 2026, Argos is the cheapest of the four for serious visual testing: free up to 5,000 screenshots per month for individual developers, then $100/month flat with 35,000 included, the lowest published overage rates of the four, and unlimited parallelization at no extra charge. Chromatic is a fair, transparently priced second choice at $179/month, especially if your workflow is deeply Storybook-centric, as long as you do the viewport × browser math first. Applitools starts at $667/month billed annually, and Percy's Desktop plan at $199/month billed annually for 10,000 screenshots, with extra screenshots at nine times Argos's rate.
If you're currently on Percy and the renewal quote stung, the migration to Argos is mostly a find-and-replace: percySnapshot becomes argosScreenshot, and your .percy.yml widths become Playwright viewports. For a broader feature comparison beyond price, see Percy vs Chromatic vs Argos.
FAQ
How much does visual testing cost per month?
For a typical team (a few hundred components, two viewports, ~30 CI builds per month, roughly 12,000 captures), pricing checked in October 2026: Argos costs $100/month, Chromatic $179/month, Percy $271/month on Desktop (billed annually, 2,000 screenshots over its allowance), and Applitools $667/month on Starter (billed annually). A solo developer under 5,000 captures a month pays nothing on Argos or Chromatic.
What counts as a snapshot in visual testing pricing?
It depends on the vendor, and it's the most important fine print. On every tool, viewports and browsers multiply the count; what differs is who does the multiplying. Argos counts each file you upload (a video shared with media sharing counts as 25), so every viewport you capture is a file you can see. Chromatic and Percy multiply server-side: 200 tests at 2 viewports in 2 browsers is 800 billed captures per build (Chromatic calls them snapshots, Percy screenshots), not 200. Always compute tests × viewports × browsers × builds per month before comparing plans.
How much does Percy cost?
As of October 2026, Percy's plans are on BrowserStack's pricing page; the old browserstack.com/percy/pricing URL is a 404. Free includes 5,000 screenshots a month and unlimited users. Desktop is $199/month billed annually ($249 month to month) for 10,000 screenshots, then $0.036 per extra screenshot. Desktop & Mobile is $599/month billed annually ($729) for 25,000, then $0.048. Every browser and width a snapshot renders in is a separate screenshot, so one page in two browsers at two widths uses four.
Is free visual testing good enough?
Often, yes, to start. Argos's free Hobby plan gives an individual developer 5,000 screenshots per month, commercial use included, which covers a small project comfortably; teams that review builds together need Pro. Fully free options like Playwright's built-in toHaveScreenshot cost nothing but push the expense elsewhere: git-committed baselines, platform-dependent rendering, and no team review UI (see Playwright visual testing limits).
Do retries and re-runs count against my screenshot quota?
They can. A flaky test that retries may capture and upload screenshots again, and a full CI re-run always does. Argos supports GitHub Actions partial re-runs and displays Playwright retries separately; on any platform, fixing flaky visual tests is the cheapest cost optimization available.
