Product comparison
VisualRunner vs Chromatic: component testing or full-website monitoring?
Compare VisualRunner and Chromatic for visual regression testing: Storybook components in CI versus discovered production pages, languages and scheduled monitoring.
Chromatic, from the team that maintains Storybook, snapshots UI components and stories in CI and routes changes into a review workflow. VisualRunner snapshots whole production pages — every language, viewport and state — and keeps watching them after release.
At a glance
VisualRunner and Chromatic compared
| Capability | VisualRunner | Chromatic |
|---|---|---|
| Unit of testing | Complete rendered pages and page states | Storybook stories and components; test-framework snapshots |
| Trigger | Schedules, on-demand runs, browser extension and API | CI builds on commits and pull requests |
| Catches CMS and third-party changes | Yes — production is captured on a schedule | Only when a build runs against that content |
| Page discovery | Sitemap, crawler, URL list and spreadsheet import | Defined by stories and tests in the repository |
| Localization | Language variants of each page captured side by side | Locales covered by stories or tests you write |
| Best fit | Website, QA, localization and agency teams | Front-end and design-system teams using Storybook |
Third-party product information was checked against official documentation on October 1, 2026. Products change; review the current Chromatic documentation, Storybook visual testing docs before purchasing.
Choose Chromatic for design systems and component libraries
If your UI is built in Storybook and you want every pull request to show which components changed, Chromatic is designed exactly for that loop. It also supports end-to-end test frameworks for page-level snapshots.
Choose VisualRunner for what customers actually see
Components can pass review while the assembled page breaks: CMS content, translations, third-party scripts, campaign banners and real data only appear in production. VisualRunner captures the rendered pages and monitors them on a schedule, so those changes are caught even when no code was deployed.
Use both where the boundaries meet
Component tests protect the building blocks; production monitoring protects the finished site. Teams with a design system often keep Chromatic for components and add VisualRunner for marketing, localized and ecommerce pages that change outside the release process.
Questions
Frequently asked questions
Is VisualRunner a Chromatic alternative?
It solves a different part of the problem. Chromatic focuses on components in CI; VisualRunner focuses on complete production pages. Some teams replace one with the other, many use both.
Does VisualRunner need Storybook?
No. It works from URLs, so any website can be captured regardless of framework.
Can VisualRunner check pages behind a login?
Yes. Authenticated environments and interaction rules let captures reach signed-in states, and the Private Runner can capture internal or VPN-only environments.
Continue exploring
Related resources
Watch the pages your customers see, not only the components
Discover your pages, capture the important states and keep a visual history of every meaningful change.
Start free trial