Visual testing is an automated verification method that compares screenshots of an interface (or of an isolated component) with reference images in order to detect any unintended graphical regression.
If you use Storybook, you probably know Chromatic. It is the visual testing tool developed by the Storybook team itself, integrated so deeply into the ecosystem that you might think it is the only option available. It is not. And believing otherwise is a trap too many teams fall into.
This article explores why depending on a single vendor for the visual testing of your Storybook components is a risky strategy, which alternatives really exist, and how to choose the approach that fits your context.
The essentials on one page: definition, no-code automation, tool selection grid: Automated regression testing, no-code.
Testing your Storybook components should not lock you into a single vendor. Delta-QA compares your stories without code, with a free account and no credit card. Try Delta-QA for free →
Why Storybook and Visual Testing Go Together
Storybook has transformed how front-end teams develop and document their components. Each component lives in isolation, with its variants, its states, its edge cases. It is a living catalog of your design system.
But a catalog without automated verification is a museum nobody remembers to watch over. One developer changes a color token in the global theme. Another adjusts a padding to fix a bug on a page. A third updates a CSS dependency. None of these changes breaks a unit test. None fails an integration test. But visually, three components are now disfigured.
Visual testing fills this gap. It captures the real appearance of each component in Storybook and detects deviations from an approved reference. It is the safety net your functional tests do not provide.
A word of caution, though: testing your components in isolation in Storybook remains insufficient as soon as those components are assembled by several teams. If you work with a distributed architecture, read why visual testing micro-frontends on the assembled page is the only way to detect CSS conflicts and layout breaks that only appear at integration.
Chromatic: What It Does Well, and the Problem
Let us say it upfront: Chromatic is a good product. The integration with Storybook is smooth: logical, since it is the same team. The review workflow is well designed. Change detection is polished, and TurboSnap only recaptures the stories affected by a file change. As of 10/2026, Chromatic is no longer limited to Storybook: it also captures Playwright, Cypress, or Vitest test pages, adds interaction and accessibility tests, and renders captures in Chrome, Firefox, Safari, and Edge.
So what is the problem?
Vendor Lock-In Is Real
When your entire visual testing pipeline relies on a single cloud service, you give it considerable power over your delivery workflow. If Chromatic changes its pricing (which happens regularly in SaaS), you have no plan B ready to deploy. If the service has an outage, your merge requests wait. If the API changes and breaks your integration, your CI stops.
This is not paranoia. It is basic risk management.
Per-Snapshot Pricing Is a Time Bomb
Chromatic bills by the number of snapshots. As of 10/2026, the free plan includes 5,000 snapshots per month on Chrome only; Starter goes to $179/month for 35,000 snapshots and opens Firefox, Safari, and Edge; Pro is $399/month for 85,000; each extra snapshot costs $0.008. At first, with 50 components and 3 variants each, the bill is reasonable. But a design system grows. Variants multiply. Themes are added. A year later, you have 400 stories and the bill has been multiplied by eight. At that point, reducing the number of snapshots means reducing test coverage: exactly the opposite of what you want. TurboSnap cushions this increase by recapturing only what changed, provided you enable and tune it.
Your Test Data Leaves Your Infrastructure
For teams under compliance constraints (healthcare, finance, public sector), sending interface screenshots to a third-party cloud service is not trivial. Even if the screenshots theoretically contain no sensitive data, security policies do not always make that distinction.
Alternatives to Chromatic for Storybook Visual Testing
Percy (BrowserStack)
Percy is the most established direct competitor. Its approach: you capture snapshots of your Storybook stories, Percy renders them in real browsers in the cloud, and you review the differences in a dashboard.
What works. Percy handles cross-browser natively. You test your components in Chrome, Firefox, and Safari without configuring anything locally. The review dashboard is mature and the approval workflow is solid.
What is problematic. You leave one cloud vendor for another. Pricing is also snapshot-based. And the integration with Storybook, although functional, is not as native as Chromatic's: logically, Percy was not designed specifically for Storybook.
Percy is relevant if your main need is visual cross-browser testing and you are comfortable with a paid cloud model. But it does not solve the fundamental vendor dependency problem.
Playwright With toHaveScreenshot()
Playwright natively integrates screenshot comparison. With a bit of configuration, you can use it to capture and visually compare your Storybook stories.
What works. Everything runs locally or in your own CI. No third-party cloud service. No per-snapshot billing. Baselines live in your repo, under your full control. And Playwright is maintained by Microsoft: longevity is not a concern.
What is problematic. Setup takes work. You have to write the logic that opens each story in a headless browser, takes a screenshot, and compares it. The initial configuration of a Playwright/Storybook script is documented, but you will be maintaining that code. False positives from pixel-by-pixel comparison will require tuning. And you have no review dashboard: when a test fails, you open PNG files locally to understand what changed.
Playwright is the solid technical choice for teams with in-house skills who want zero external dependency. But it is a maintenance investment.
BackstopJS
BackstopJS is an open source tool dedicated to visual regression. It can target URLs: so your locally served Storybook stories.
What works. It is free, open source, and the generated HTML report is more readable than a folder of diff files. The JSON scenario configuration is clear. It is also one of the best-known free visual testing tools in the ecosystem.
What is problematic. The project has gone through phases of intermittent maintenance. Integration with Storybook is not direct: you have to point BackstopJS at the individual URLs of each story. The JSON scenario configuration is documented, but at the scale of a substantial design system, scenario management becomes verbose.
Delta-QA: The No-Code Approach
Delta-QA takes the problem differently. No scripts to write. You open your served Storybook stories (on a deployed Storybook or a staging environment) and record the journey without code; Delta-QA replays the pages in a real browser, compares them the way a human eye would, and presents the differences in a dedicated review interface: the report says which element changed. For teams who prefer to verify from their Playwright tests, Delta-QA now has an SDK, the Vision SDK.
What changes. Visual testing of your Storybook components no longer depends on your test stack. Your QA team can configure and maintain visual coverage without touching test code. Designers can take part in the review workflow: they see visual differences without having to understand a test report.
What is different compared with Chromatic. The free account is created with no credit card, and the On-Premise offer (free one-month POC) keeps your captures inside your infrastructure if you need it. In return, Delta-QA compares on Chromium today; Firefox and WebKit are planned.
Visual testing without vendor dependency is possible. Delta-QA compares your Storybook stories with no-code, with a free account: no Chromatic subscription required. Try Delta-QA for free →
How to Choose: The Decision Grid
Rather than pretending one solution suits everyone (that would be false), here are the questions to ask yourself.
Do you have data sovereignty constraints? If yes, rule out Chromatic and Percy. That leaves Playwright, BackstopJS, and Delta-QA.
Does your team have the skills to maintain visual test scripts? If not, rule out Playwright and BackstopJS. Delta-QA's no-code or Chromatic/Percy's managed approach are better suited.
Is your design system actively growing? If yes, beware of per-snapshot pricing. What costs 50 € per month today can cost 500 € in a year.
How many browsers do you need to cover? If cross-browser is critical, Percy and Chromatic (from its Starter plan) cover several browsers; Delta-QA compares on Chromium today. For the others, a single Chromium browser is often enough to detect visual regressions.
Do you want to involve non-developers in the review? If your designers or QA team must validate visual changes, a tool with an accessible review interface (Delta-QA, Chromatic, Percy) will be preferable to a folder of PNG files in Git.
The Hidden Risk: Tooling Monoculture
Beyond the choice of tool, there is a more fundamental principle that many teams overlook: do not put all your tests in the same vendor basket.
If your CI, your functional tests, your visual tests, and your monitoring all depend on a single ecosystem, one business decision by that vendor can paralyze your entire pipeline. This is true for Chromatic, it is true for any tool.
Resilience, in software engineering, comes through diversification. You do not host your database and your application on the same physical machine. Apply the same logic to your testing tooling.
Migrating From Chromatic: Where to Start
If you are currently on Chromatic and considering an alternative, do not do a big bang. Proceed in stages.
Step 1: Identify your critical stories. Not all your stories. The 20% that cover 80% of the components your users see.
Step 2: Set up the alternative in parallel. Run Delta-QA (or Playwright, or the tool of your choice) on those critical stories at the same time as Chromatic. Compare the results over two to three sprints.
Step 3: Expand gradually. Once confidence is established, extend coverage and reduce your use of Chromatic proportionally.
Step 4: Cut the cord. When alternative coverage reaches a satisfactory level, turn off Chromatic.
This approach takes time. But it avoids the disaster scenario where you discover the limits of your new tool in production.
FAQ
Is Storybook visual testing really necessary if we have unit tests?
Yes. Unit tests verify that your component works: that it accepts the right props, renders the right content, reacts to events. Visual testing verifies that it looks the way it should. A component can pass all its unit tests and have a completely broken layout. They are two complementary dimensions.
Can you use Playwright to visually test Storybook without Chromatic?
Absolutely. Playwright can navigate to each story individually and compare screenshots. The effort is in setup and maintenance: you have to write the code that iterates over your stories, manage the baselines, and handle false positives. It is doable but it is an investment of engineering time.
Does Delta-QA work with Storybook directly?
Yes. Delta-QA can open any served URL, including individual Storybook stories. You do not need to modify your Storybook configuration or install a plugin. All that is needed is for your Storybook to be reachable from Delta-QA (deployed, or on your network with the On-Premise offer) to record a scenario and compare your components.
Is pixel-by-pixel comparison reliable for Storybook components?
It is reliable if your rendering environment is perfectly stable: same OS, same browser, same resolution, same fonts. In practice, achieving that stability between a developer's machine and a CI runner takes work. Perceptual approaches (which tolerate minor rendering differences) or tools that handle that stability for you considerably reduce false positives.
How much does Storybook visual testing cost if we leave Chromatic?
It depends on the alternative. Playwright and BackstopJS are free (open source) but cost engineering time. Percy bills per snapshot like Chromatic (as of 10/2026, Chromatic: free up to 5,000 snapshots per month, then $179 or $399 per month depending on volume). Delta-QA starts with a free account, no credit card. Do the math with your actual number of stories and variants.
Is it possible to combine several visual testing tools on the same project?
Not only is it possible, it is sometimes recommended. You could use Playwright for critical visual tests in your CI pipeline and Delta-QA for collaborative review with your design team. Diversification reduces your dependency risk and lets you exploit the strengths of each tool.
Conclusion
Storybook visual testing is indispensable for any team that maintains a serious design system. But the tool you choose to do it has implications well beyond the technical. It affects your budget, your autonomy, and the resilience of your delivery pipeline.
Chromatic is a good tool. It is not the only one. And in a context where flexibility and independence are strategic advantages, exploring alternatives is not a luxury: it is prudence.
If you are looking for a no-code approach, as SaaS or On-Premise, that works with Storybook as with any web application, Delta-QA deserves your attention.
Ready to take back control of your visual testing? Launch your first story comparison with Delta-QA, with a free account and no credit card. Try Delta-QA for free →