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

  • Claude Code
  • Codex
  • Cursor

Set up UI Verify in this repo: fetch https://uiverify.ai/install.md with curl and follow it.

See it in action

Used by engineering and product teams at

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.

  1. 01

    Open a pull request

    UI Verify screenshots every affected screen and posts a clear verdict on the PR.

  2. 02

    See exactly what changed

    Before and after, side by side, with every changed pixel highlighted.

  3. 03

    Accept or flag it

    Your team comments on the exact spot, then accepts intended changes in one click.

  4. 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.

Compared at list priceUI VerifyChromaticPercy
Price at 50,000 snapshots a month$169/mo$299/mo$1,639/mobilled yearly
Free plan10,000 snapshots a month5,000 snapshots, Chrome only5,000 screenshots a month
Free for open source projectsYes: 50,000 snapshots a month, no applicationPartly: 35,000 a month, UI libraries only, by applicationPartly: By application
Each snapshot over your plan$0.004$0.008$0.036 to $0.048
Your coding agent checks its UI change before the pull requestYes: One command, on every planPartly: A full Chromatic build each roundPartly: A full Percy build each round
Your coding agent reviews and accepts changes over MCPYes: Free on every planNo: In betaYes: Reviews and approves builds
Storybook, Playwright and Vitest, captured from the tests you haveYes: Plus BunYes: Plus CypressPartly: Snapshot calls added to your tests
Skips the screens a change can’t affectYes: Storybook and Vitest, and skipped screens aren’t billedPartly: TurboSnap, Storybook onlyPartly: IntelliStory, Storybook only
  • 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.

Setup

From zero to your first build in about 5 minutes.

  1. 01

    Paste one prompt

    Give the line below to your coding agent. It reads the install guide and picks your framework.

  2. 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.

  3. 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

  • Claude Code
  • Codex
  • Cursor

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.

  • “A Tailwind refactor broke a bunch of our buttons. Now UI Verify catches those bugs before we ship, and otherwise stays out of the way. Awesome stuff.”
    Adam TowersAdam TowersCTO
  • “I can see what agents changed without running the app.”
    Francisco MorettiFrancisco MorettiCreator
  • “Our customers make money decisions from our dashboards. UI Verify makes sure they're looking at the right thing.”
    Puli LiyanagamaPuli LiyanagamaCTO
  • “It's awesome! Super useful tool. My team uses it all the time.”
    Valeriia TorgoninaValeriia TorgoninaFrontend Developer
  • “Really top. I build a mobile app and see every screen my agent changed on each PR.”
    Kirill IlichevKirill IlichevFounder, Jutri

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.