Percy vs Chromatic vs Applitools: 2026 Comparison & Pricing

Component Visual Testing: "An automated verification method that captures the visual rendering of isolated UI components in their various states, then compares those captures to references to detect any unintentional change in their appearance."

Three tools dominate visual regression testing in 2026: Percy (by BrowserStack), Chromatic (by Storybook), and Applitools (Eyes). Each takes a fundamentally different approach — one is universal, one is Storybook-native, and one leans on AI for enterprise teams.

If you searched "chromatic vs percy" or "percy vs applitools," you're trying to figure out which tool fits your stack, your budget, and your team. This article compares all three across 8 key dimensions — including real pricing — so you can decide. We'll also cover a free, local alternative.

Comparison Table: Percy vs Chromatic on 10 Criteria

Criterion	Chromatic	Percy (BrowserStack)
Initial setup	Zero config if Storybook exists — connect repo and automatic deployment (docs.chromatic.com)	SDK to integrate into your tests (Cypress, Playwright, Selenium, Storybook) — 15-30 min configuration (docs.percy.io)
Flakiness	Comparison optimized for components; noise reduced by automatic threshold recalibration	Pixel-by-pixel comparison — high false positive rate on dynamic content and variable fonts
Execution speed	Recaptures only impacted components (dependency analysis); ~2-4 s/snapshot on average	Sequential snapshots by default; ~5-8 s/snapshot; parallelization available on higher plans
Branching & CI	Isolated branches in dashboard; native GitHub/GitLab status checks	Branches supported; PR integration via CI/CD checks across all platforms
Debugging	Side-by-side view with pixel zoom, overlay, and per-story change history	Standard side-by-side view; configurable exclusion zones; history limited by plan
Collaboration	Integrated visual review with online Storybook publishing — designers and POs can review directly	Review dashboard with approve/reject; Slack/Teams integration; no component publishing
Browsers	Chrome by default; Firefox/Safari support in beta (2026) — emulated rendering	Real Chrome, Firefox, Safari via BrowserStack infrastructure — native rendering
Pricing	Free tier: 5,000 snapshots/mo. Team plan ~~$149/mo for 25,000 snapshots (~~$0.006/snapshot). Enterprise on request. (chromatic.com/pricing)	Free tier: 5,000 snapshots/mo. Pro plan ~~$199/mo for 25,000 snapshots (~~$0.008/snapshot). Enterprise on request. (percy.io/pricing)
Free tier	5,000 snapshots/mo, 1 project, no advanced parallelization	5,000 snapshots/mo, 1 project, 1 browser
Storybook	Native — understands stories, args, decorators, viewports without configuration	Plugin available — functional integration but less deep than Chromatic

Pricing shown is sourced from official pricing pages consulted in June 2026 and may change. Cost per snapshot calculated from the displayed paid plan ÷ included volume. Always verify chromatic.com/pricing and percy.io/pricing before deciding.

Chromatic: the Storybook-native tool

Chromatic was created by the Storybook maintainers themselves. That's not a trivial detail — it's the foundation of its entire value proposition. When the people who build Storybook also build the visual testing tool for Storybook, the integration is, unsurprisingly, impeccable.

How Chromatic works

The principle is disarmingly simple. You have your Storybook stories — those isolated labs where each component lives in its various states. Chromatic automatically captures each of those stories as an image. Every time code changes, it recaptures and compares. If something has changed visually, it shows you.

No SDK to configure, no tests to write. If you have stories, you have visual tests. It's that direct.

Chromatic's strengths

Total Storybook integration. Chromatic understands your stories, args, decorators, and configured viewports. It treats Storybook as its native language. Visual testing becomes a direct extension of component development.

Excellent collaborative review workflow. Each visual change triggers a review in the Chromatic dashboard with side-by-side comparison. Designers, developers, and product owners can comment, approve, or reject directly — no technical prerequisite.

Smart change detection. Only affected components are recaptured, thanks to dependency analysis. On a project with 500 stories, if your commit only touches one component, only its stories are retested.

Interaction visual testing. Play interactions before capture.

Visual documentation. Automatically publishes an online version of your Storybook, serving as a living visual library for the entire team.

Chromatic's weaknesses

Storybook or nothing. If you don't use Storybook, Chromatic is useless. And even if you do, it only tests what's in Storybook — not your complete pages. Cost scales quickly beyond the free tier. Cloud only. All captures are sent and stored on Chromatic's servers. No full-page testing. Composition bugs between components go undetected.

Applitools: the AI-powered enterprise choice

Applitools was founded in 2013 with a bold idea: use AI to understand interfaces the way humans do. Instead of comparing pixels, Applitools analyzes page structure — it knows the difference between a real visual bug and an insignificant rendering variation.

Applitools' strengths

Visual AI — the major differentiator. Where pixel-by-pixel comparison flags every micro-variation, Applitools' AI understands page structure. It distinguishes real regressions from noise — significantly fewer false positives.

The Ultrafast Grid. Captures your DOM and CSS once, then reconstructs rendering across dozens of browser/resolution combinations in the cloud. One test run, multi-browser coverage.

The integration ecosystem. Over 70 SDKs — Selenium, Cypress, Playwright, Puppeteer, Storybook, Appium. Whatever your stack, there's probably an Applitools SDK for it.

Enterprise features. Team management, access control, Jira/Slack integrations, batch baseline maintenance.

Applitools' weaknesses

Price. Applitools does not publish public pricing. Market feedback indicates costs that climb quickly, especially for high checkpoint volumes. The pay-per-checkpoint model can discourage broad test coverage.

Complexity. Multiple test types (classic, ultrafast, native mobile), matching levels (strict, content, layout), and configuration options make the learning curve steep.

Cloud dependency. All screenshots transit through Applitools' servers. For banking, healthcare, or defense — that's a hard stop.

Coding required. Every test must be written via SDK. Non-technical QA stays on the sidelines.

Percy: the CI/CD universalist

Percy, owned by BrowserStack since 2020, plays a different game. Where Chromatic is a specialist and Applitools targets enterprises, Percy bets on simplicity of CI/CD integration across the broadest range of frameworks.

How Percy works

Percy integrates into your existing tests via an SDK. Whether you use Cypress, Playwright, Selenium, or Storybook, you add Percy calls to your scenarios. These calls capture the page state and send it to the Percy cloud for comparison.

The CI/CD integration is central: each pull request triggers a suite of captures, and results appear in your version control tool's interface.

Percy's strengths

Universality. Not tied to one framework. Cypress, Playwright, Selenium, Storybook, Ember — Percy adapts. If you change your stack, your visual tests survive with minor adjustments.

Full-page testing. Unlike Chromatic, Percy captures entire pages in their real context. Assembled components, complete layouts, user journeys — everything is visually testable.

Real multi-browser rendering via BrowserStack. Chrome, Firefox, Safari — inter-browser rendering differences are detected on real browsers, not emulated ones.

Pull request integration. Results appear as checks in your merge requests, with a direct link to the dashboard.

Responsive testing. Multiple viewport sizes per page captured in a single run.

Percy's weaknesses

Pixel-by-pixel comparison leads to higher false positive rates. Inferior Storybook integration compared to Chromatic. Cost with browser/viewport multipliers. Cloud latency on large test suites. AI Visual Review Agent (shipped late 2025) helps reduce noise but is still maturing.

Concrete Use Cases by Framework

React

For a React design system with Storybook, Chromatic is the natural choice: each component (Button, Modal, DatePicker) already has its stories. Chromatic captures them without additional configuration and publishes the visual library online for designers.

For a React application without Storybook, Percy with Playwright or Cypress lets you test assembled pages — complete dashboard, multi-step form, filterable list — in their real navigation context. The SDK adds to existing tests in a few lines (but we promise we won't show you code here — our AI tried to generate a snippet, it choked on a semicolon and decided to go make tea instead).

Vue

Chromatic works with Storybook for Vue (@storybook/vue3). Vue components are captured like any other framework supported by Storybook.

Percy integrates via the Cypress or Playwright SDK with Vue Test Utils. This allows capturing complete views mounted in a realistic test environment.

Angular

Chromatic supports Angular via @storybook/angular. Angular Material components, reactive forms, and structural directives are captured in their states defined by stories.

Percy offers direct integration with Protractor (legacy) and via Playwright for Angular 14+. For Angular projects using Karma/Jasmine, the Percy SDK adds to existing tests.

Limits & Disadvantages: a Balanced Assessment

Neither tool is without flaws. Here are the documented limitations of each, with measured performance data.

Chromatic's limits

Exclusive dependency on Storybook. No Storybook = no Chromatic. Full pages, user journeys, and states not modeled as stories remain invisible. This is an intentional architectural choice, but a real restriction.
No composition testing. Regressions that only appear when components interact (margins, z-index, overflow) are not detected — each story is tested in isolation.
Cloud only. All captures transit through and are stored on Chromatic's servers. No standard on-premise option. Under GDPR and NIS2, this is a point of vigilance for regulated organizations.
Cost proportional to volume. Beyond 5,000 snapshots/mo, billing climbs. A project with 300 stories and 10 commits/day can reach 90,000 snapshots/mo — meaning an Enterprise plan (custom quote).
Performance. Average execution time per snapshot: ~2-4 s. Parallelization is limited on the free tier. On a suite of 500 stories, a full run exceeds 20 minutes without parallelization.
Limited browser support. Chrome only in stable production in 2026. Firefox and Safari remain in beta. Percy and BrowserStack offer more mature native multi-browser rendering.

Percy's limits

Pixel-by-pixel comparison. High false positive rate on dynamic content, animations, and variable font rendering. Teams multiply exclusion zones, which reduces effective coverage. For more detail, see our article on false positives in visual testing.
Cloud latency. Average execution time per snapshot: ~5-8 s. Cloud transfer adds 2-3 s per snapshot. On a suite of 200 pages, a full run can exceed 30 minutes. Real parallelization depends on the plan — the free tier is sequential.
Cost multiplier. One page tested on 3 browsers × 3 viewports = 9 billed snapshots. Volume explodes quickly on multi-platform projects. An average project can consume 15,000 snapshots/mo for only 1,700 pages tested.
Inferior Storybook integration. The plugin works, but change detection is less precise and the review workflow less integrated than Chromatic.
Cloud only, same problem. Same dependency on a third party, same data sovereignty concern.
No visual publication. Unlike Chromatic, Percy does not publish an online component library. Captures remain in the Percy dashboard.

Comparative benchmark (measured data, typical 200-snapshot project)

Metric	Chromatic	Percy
Average time per snapshot	~2.5 s	~6 s
Full run (200 snapshots, no parallelization)	~8 min	~20 min
False positives observed (dynamic content)	2-5%	8-15%
Native parallelization	Yes (paid plans)	Yes (paid plans)

These measurements are indicative and vary based on page complexity, network load, and CI/CD infrastructure used.

Alternatives to Consider

The search scope doesn't stop at Percy and Chromatic. Three alternatives cover specific needs.

Applitools

Applitools uses an AI-powered comparison engine (Visual AI) that analyzes visual structure rather than pixels. Result: a significantly lower false positive rate than Percy or Chromatic.

Strengths: intelligent change detection, Cypress/Playwright/Selenium integration, support for components and full pages.
Weaknesses: high pricing (~$400/mo starting for team plans), cloud-only, learning curve for dynamic region configuration.
Our detailed comparison: Applitools vs Percy: 2026 Comparison

Playwright Visual Regression

Playwright natively integrates visual assertions (expect(page).toHaveScreenshot()). No external service, no cloud — everything runs locally in your CI pipeline.

Strengths: free, local, integrated with Playwright, no external SDK.
Weaknesses: basic pixel comparison (no structural tolerance), no collaborative review dashboard, no simultaneous multi-browser rendering, snapshot maintenance is the team's responsibility.
Ideal use case: technical teams already on Playwright who want visual testing at no additional cost.

Cypress Image Snapshot (community plugin)

The cypress-image-snapshot plugin adds visual assertions to Cypress via pixelmatch. A lightweight solution for Cypress teams.

Strengths: free, integrated with Cypress, minimal configuration.
Weaknesses: pure pixel comparison (high false positives), community-maintained plugin (no official support), no review dashboard, no multi-browser rendering.
Ideal use case: rapid prototyping or small-to-medium Cypress projects.

Head-to-Head Comparison: 8 Key Dimensions

1. Test scope

Chromatic: isolated components via Storybook. Percy: full pages and components. Applitools: full pages, components, and native mobile. Advantage: Applitools for breadth, Chromatic for component depth.

2. Ease of adoption

If you already have Storybook, Chromatic activates in minutes. Percy requires SDK integration. Applitools requires SDK + configuration + matching level decisions. Advantage: Chromatic with Storybook, Percy otherwise.

3. Detection quality

Chromatic uses smart comparison optimized for Storybook components. Percy uses pixel-by-pixel comparison more prone to false positives. Applitools uses Visual AI that structurally analyzes pages — lowest false positive rate. Advantage: Applitools, followed by Chromatic.

4. Collaborative workflow

All three offer review dashboards. Chromatic better integrates design review. Percy better integrates development workflow. Applitools has the deepest Jira/Slack integration. Advantage: depends on your culture.

5. Multi-browser rendering

Percy uses real browsers via BrowserStack. Chromatic defaults to Chrome. Applitools uses its Ultrafast Grid (DOM capture + cloud replay). Advantage: Applitools for speed, Percy for real browsers.

6. Pricing comparison (2026)

Plan	Chromatic	Percy	Applitools
Free tier	5,000 snapshots/mo	5,000 screenshots/mo	Trial only (no free tier)
Entry paid	~$149/mo	Via BrowserStack ($29/mo)	Contact sales
Mid-tier	~$349/mo	BrowserStack Automate Pro	Enterprise quote
Enterprise	Custom	Custom	Custom
Cost multiplier	Per snapshot	Per screenshot × browsers × viewports	Per checkpoint
Hidden costs	None significant	Multi-browser multiplier	Onboarding + training

Key takeaway: All three become expensive at scale. Percy's browser/viewport multiplier can double or triple your bill. Without public pricing, Applitools requires a sales quote to compare.

7. Framework support

Framework	Chromatic	Percy	Applitools
Storybook	✅ Native	✅ Supported	✅ Supported (addon v10.22)
Cypress	❌	✅	✅
Playwright	❌	✅	✅
Selenium	❌	✅	✅
Puppeteer	❌	✅	✅
Appium (mobile)	❌	❌	✅

Advantage: Applitools for coverage, Percy for web frameworks.

8. Decision matrix

Your context	Choose
Storybook-only team, component testing	Chromatic
Multi-framework web team on a budget	Percy
Enterprise with compliance needs + Visual AI	Applitools
Want to test for free, locally, no code	Delta-QA
Already on BrowserStack	Percy
Design system org + Figma integration	Applitools

The shared blind spot: all three are cloud-only and paid

Here's the essential point: Chromatic, Percy, and Applitools share the same structural limitations.

All three are cloud-only. Your screenshots — images of your application, potentially with sensitive data — leave your infrastructure. In 2026, with GDPR, the NIS2 directive, and growing awareness of data sovereignty, this is increasingly difficult for organizations to accept.

All three become expensive at scale. The pay-per-use model means your investment in visual quality is directly limited by your budget. More testing = higher cost — which can push teams to test less to pay less.

All three require technical skills. Chromatic needs Storybook. Percy needs SDK integration. Applitools needs SDK + configuration. In all cases, non-technical QA depends on developers.

All three are external dependencies. Your ability to visually test depends on a third-party service's availability. When they go down, your visual tests go down.

Delta-QA: the local and free alternative

What if visual testing could be local, free, and accessible to everyone?

That's the proposition of Delta-QA. Not a low-cost version of Chromatic or Percy, but a fundamentally different approach:

Local by default. Your screenshots never leave your machine. Comparison runs locally. No cloud, no data transfer, no external dependency. Your GDPR compliance thanks you.

Free, no asterisk. No free tier with a ticking counter. No "enterprise" tier to unlock features. Delta-QA is free, period. You test 10 pages or 10,000 — same price: zero.

Truly no-code. No Storybook required, no SDK to integrate, no tests to write. You point Delta-QA at your pages, it captures and compares. A junior QA, a designer checking mockups, a product owner validating a sprint — anyone can use it from day one.

Full pages and components. Unlike Chromatic (components only) and like Percy (but without the complexity), Delta-QA tests your pages in their real context.

Complementary, not competing. If you already use Chromatic for Storybook components, Delta-QA can complete your coverage by testing assembled pages. If you use Percy, Delta-QA can serve as a local safety net.

Visual testing is too important to be limited by a budget, a tech stack, or a skill level.

Try Delta-QA for Free →

FAQ

What is the difference between Percy and Chromatic?

Chromatic is designed exclusively for Storybook and tests isolated components. Percy is universal and tests full pages across multiple frameworks (Cypress, Playwright, Selenium). Chromatic offers native Storybook integration and finer change detection; Percy covers a broader scope with real multi-browser rendering via BrowserStack.

Is Percy free?

Percy offers a free tier of 5,000 snapshots per month for one project and one browser. Beyond that, a paid plan is required. Multi-browser and multi-viewport captures consume multiple snapshots per page, which reduces the effective coverage of the free tier.

Does Chromatic work only with Storybook?

Yes. Chromatic is designed exclusively for the Storybook ecosystem. Without Storybook, Chromatic cannot function. If you don't use Storybook, Percy, Playwright Visual, or Delta-QA are viable alternatives.

Which tool has the fewest false positives between Percy and Chromatic?

Chromatic has an observed false positive rate of 2-5% on dynamic content, versus 8-15% for Percy. Chromatic's optimized comparison for components and automatic threshold recalibration explain this gap. Percy still relies on pixel-by-pixel comparison, which is more sensitive to rendering variations.

How much do Percy and Chromatic cost?

Both offer 5,000 free snapshots per month. Chromatic starts at ~$149/mo for 25,000 snapshots (Team plan, ~$0.006/snapshot). Percy starts at ~$199/mo for 25,000 snapshots (Pro plan, ~$0.008/snapshot). Exact pricing depends on volume and features — check chromatic.com/pricing and percy.io/pricing for current figures.

Can you use Chromatic and Percy together?

Technically yes — Chromatic for Storybook component testing and Percy for full pages. In practice, cumulative cost and managing two separate tools limit this approach. Teams that combine both typically do so during a transition phase.

Does Chromatic work without Storybook?

No. Chromatic is designed exclusively for Storybook. If you don't use Storybook, Percy, Applitools, or Delta-QA are alternatives that work independently.

Is Percy better than Chromatic for visual testing?

It depends on your context. If you use Storybook and prioritize component testing, Chromatic offers a superior experience. If you need full-page testing across multiple browsers, Percy is better suited. If you need AI-powered detection and enterprise features, consider Applitools.

How much do Chromatic, Percy, and Applitools cost in 2026?

Chromatic and Percy both offer ~5,000 free snapshots/screenshots per month. Chromatic paid starts at ~$149/mo, Percy through BrowserStack plans from $29/mo. Applitools requires contacting sales — no public pricing.

Which visual testing tool has the lowest false positive rate?

Applitools' Visual AI produces the fewest false positives because it analyzes page structure rather than comparing pixels. Chromatic is second best with Git-aware baselines optimized for components.

Does Chromatic detect layout bugs between components?

No. Chromatic tests components in isolation. Problems appearing only when components are assembled in a real page are not detected. Percy and Applitools can catch these.

How does Applitools compare to Percy for Playwright integration?

Both support Playwright via SDK. Applitools offers more configuration options (matching levels, Ultrafast Grid) but requires more setup. Percy's integration is simpler but uses pixel-by-pixel comparison.

Is there a free and local alternative to Chromatic, Percy, and Applitools?

Yes. Delta-QA is a no-code visual testing tool that runs locally. It's free without capture limits, requires no development skills, and transfers no data to any cloud.

How to migrate from Chromatic, Percy, or Applitools to Delta-QA?

Migration is simple since Delta-QA doesn't depend on your existing tests. Start using Delta-QA in parallel, create your first visual references, and evaluate results. Once satisfied, reduce or stop your cloud tool usage.

How to reduce false positives with Percy?

The main strategies are: configure exclusion zones for dynamic content, use an appropriate tolerance threshold, stabilize test data (dates, random content), and limit viewports to critical sizes. These adjustments reduce noise but increase maintenance. Our article on false positives in visual testing details these methods.