Stagewright and visual regression testing (Chromatic, Percy)

What visual regression testing is, in the vendors’ words

Chromatic: “Ship flawless UIs with less work. Our pipeline catches visual, interaction, and accessibility issues before they ship.” It’s made by the Storybook team, tests components in real browsers, and asks for “Explicit sign-off” on changes, with baselines tracked in Git. Percy is BrowserStack’s visual testing product, billed by screenshots per month on its published plans.

Neither makes content for your customers. That’s the line between them and Stagewright.

The same workflow, a different job

	Visual regression testing	Stagewright
Asks	Did the UI change, and was it meant to?	Does the flow we teach customers still work, and does what we teach still match it?
Unit of work	A component story or page snapshot	A walkthrough: a narrated, multi-step flow with checks
Who reads the result	Engineers and designers	Engineers on the PR; then customers, support and training, through the published video and article
When something changed on purpose	Accept the new baseline	Approve the new recording; the player, help article and course update
When something broke	A failed check	A failed check, and an issue filed with the clip and repro steps; the fix PR is replayed

Side by side

Stagewright and Chromatic

Stagewright and Chromatic: Stagewright and Chromatic
Capability	Stagewright	Chromatic	Source
Check on the pull request	Yes	Yes. Integrates with GitHub checks and PR workflows	source
Before and after frames, explicit sign-off	Approve in the PR check or in Stagewright	"Explicit sign-off enforces UI standards"	source
Re-run only what a change affects	Affected-only walkthroughs from changed files and the feature map	TurboSnap	source
Where baselines live	Walkthroughs in Git; approved recordings in Stagewright	"tracks baselines using Git"	source
What it checks	End-to-end flows customers are taught, against a preview or staging	Components and stories (Storybook), plus interaction and accessibility checks	source
Accessibility checks	No	Yes	source
Browsers	Chromium	Free tier is Chrome only	source
Narrated video, help article, training from the result	Yes	No	source
Failures filed as issues with video	Linear, Jira Cloud, GitHub Issues	No. Not documented, per their public docs as of October 2026	source
Pricing shape	Not priced yet (private beta)	Billed snapshots, unlimited users; Free 5,000 snapshots, Starter $179/mo, Pro $399/mo	source

Last verified 2026-10-11 against Chromatic's public pages, linked in each row.

Where visual testing tools are better

Coverage of the UI itself. Every component state, every story, in several browsers, with accessibility checks. A walkthrough only sees the screens its flow passes through.
Speed and scale. Snapshot tests run in parallel and finish fast. A walkthrough is a paced recording of a real flow with narration.
Maturity. These are established tools. Stagewright is in private beta.

Use both

Run your visual tests on every PR to catch UI bugs early. Run Stagewright on the same PRs for the handful of flows that customers are taught: sign-up, inviting a teammate, the core job of your product. When Chromatic shows a button moved, Stagewright tells you which walkthroughs, videos and articles that affects, and updates them when you approve.

FAQ

Isn’t a walkthrough just an end-to-end test? It is one, on purpose; we credit the idea to the Docs as Tests movement on our Method page. It also carries narration and is published, so the test result and the customer-facing content can’t disagree.

Should I move my Playwright tests into Stagewright? No. Keep them. stagewright import playwright converts a test into a walkthrough when you want a narrated version of the same flow, without moving or changing the test.