Catch UI regressions before they merge.
Visual regression testing for Playwright, Storybook, Vitest and mobile apps. Your coding agent sees every UI change it makes, so visual bugs never reach production.
Or, paste this into your agent of choice
Set up UI Verify in this repo: fetch https://uiverify.ai/install.md with curl and follow it.
See it in action
How it works
Your tests check that the code works.
We check that it looks right.
Unit and end-to-end tests catch broken logic. They don’t notice a button that lost its colour or a layout that breaks on mobile. UI Verify checks every UI change, from your agent’s first edit to the pull request.
01
Open a pull request
UI Verify screenshots every affected screen and posts a clear verdict on the PR.
02
See exactly what changed
Before and after, side by side, with every changed pixel highlighted.
03
Accept or flag it
Your team comments on the exact spot, then accepts intended changes in one click.
04
Your agent fixes the rest
Flagged changes go to Claude Code, Cursor or Codex over MCP. The agent fixes the code and runs the check again.
Compare
Same safety net. A much smaller bill.
Your agent checks its own work
One command renders the screens a change touches, before a pull request exists.
A free plan you can actually use
10,000 snapshots a month (50,000 for open source), no credit card.
The same pixels on every machine
Storybook, Playwright, Vitest and Bun captures render in our own pinned browser, so a diff is a real change.
Features
Everything you need.
Nothing that slows you down.
Works with your stack
Storybook, Playwright, Vitest and Bun. Native iOS, Android and desktop apps through the screenshots your tests already take.
Made for coding agents
An MCP server lets Claude Code, Codex, Cursor and others see what changed and fix it.
Flake-resistant capture
Animations, timers, fonts and async data are pinned, so a red build is a real change.
Re-render only what changed
Unchanged screens carry forward without a new render, and aren’t billed. On our own app, the median PR re-renders 13 of 154.
Every browser, every size
Chromium for every project, plus Firefox and Safari for Storybook, at desktop and phone widths.
A history you can trust
Every accepted baseline is versioned and kept, so you can step back through each change to a screen.
Setup
From zero to your first build
in about 5 minutes.
- 01
Paste one prompt
Give the line below to your coding agent. It reads the install guide and picks your framework.
- 02
Approve the sign-in
Your agent opens a sign-in link in your browser. No key to copy and no project to create first.
- 03
Accept your first build
It installs UI Verify and uploads your first build. Accept it, then add the check to your pull requests.
Paste this into your coding agent
Set up UI Verify in this repo: fetch https://uiverify.ai/install.md with curl and follow it.
Testimonials
Teams catching bugs before their users do.
FAQ
Questions teams ask
Flake is a capture problem, so we fix it at capture. Animations are held still, randomness is seeded and fonts are inlined before the screenshot is taken, and a change that does not reproduce on a re-render is labeled a flake and kept out of your review. A red build means a real change, not a rerun.
You always have the last word. Every verdict comes with the judge's reasoning, the check holds the merge until each change is accepted (a denied one fails it), and nothing becomes a baseline on the judge's say-so. It pre-reads every diff for you; it never merges for you.
One screen (a component or page) rendered in one browser at one viewport. You rarely pay for all of them: we render only what your change touches and carry the rest forward free, so a typical pull request bills a fraction of your full UI. On our own app, the median PR re-renders 13 screens out of 154.
Each plan includes a monthly bucket of snapshots (10,000 free and 50,000 for open source, 30,000 on Starter, 65,000 on Pro). Beyond the bucket, extra snapshots are $0.004 each. In-plan they work out to about $0.003.
An AI review is one vision verdict on a changed snapshot: intended change, real regression, or flake. Every plan includes a monthly bucket (100 free, 1,000 on Starter, 2,500 on Pro); beyond it, extra reviews are $0.03 each.
Extra snapshots are billed at $0.004 each, the same low rate. On the Free plan, snapshots pause until the next cycle or you upgrade.
Your first build has no baseline to compare against, so every screen arrives as new: accept it once (or upload with --auto-accept-changes) and it becomes the starting baseline. From the next pull request on, UI Verify diffs against it and shows only what changed.
No. UI Verify works with your Vitest browser-mode component tests, your Storybook build, your existing Playwright end-to-end suite, or visual tests on bun test. Add @uiverify/vitest or @uiverify/playwright to your tests, or write visual tests with @uiverify/bun, and every component or page they render is captured, or point it at a static Storybook and every story becomes a snapshot. More frameworks are on the roadmap.
UI Verify renders in Chromium for every project, and a Storybook project can add Firefox and Safari (WebKit), with every story captured in each. Edge runs on the same Chromium engine.
Yes. The CLI runs in any CI, including GitLab CI and Bitbucket Pipelines, and every build is diffed and reviewed in the dashboard the same way. On GitHub it also posts a check and a comment on the pull request.
On every pull request. UI Verify renders your components and pages, diffs them against the baseline, and posts a check with a comment, so you review only what changed.
Yes. UI Verify runs an MCP server, so your coding agent (Claude Code, Cursor, and others) can list builds, inspect diffs, and accept or deny changes, the same review actions you'd take in the dashboard. It's included free on every plan.
Snapshots are encrypted in transit and at rest, isolated per team, and never used to train models. See our Security page for the details.
On the self-serve plans, yes. They are monthly, so you can cancel or change tier whenever you like. An Enterprise plan follows its contract.
Ship faster. Break nothing.
Add UI Verify to your next pull request in about 5 minutes.






