Catch every pixel
before it ships.
Snapvisor screenshots your UI on every pull request, diffs it against your baseline, and surfaces the visual changes your unit tests will never catch.
14-day Pro trial · Connect your repo in minutes
The visual layer your test suite is missing
No third-party runtime requests
The blind spot
Your tests pass. Your UI still broke.
Unit tests check logic. They never see a button slide off-screen, a font swap, or a layout collapse on mobile. Those bugs only show up in production — in front of your users.
Silent layout shifts
A CSS tweak two components away nudges your checkout button below the fold. No unit test fails.
Broken typography
A font fails to load, fallback metrics differ, and your headline wraps into the navbar.
Responsive regressions
It looks perfect at 1440px and falls apart at 375px — exactly where half your users are.
Live regressions
What a regression actually looks like.
Three failure modes Snapvisor catches every day — the kind no assertion is watching for.
Layout shift
A CTA drifts out of place after an unrelated CSS change. Pixels move; tests stay green.
Color regression
A token update repaints a primary button off-brand. No assertion ever checks the hue.
Text overflow
A longer string clips inside a fixed button. Logic is fine — the label is unreadable.
How it works
Three steps. Zero flaky screenshots.
Drop Snapvisor into your pipeline and it does the watching for you.
Capture
Your CI uploads screenshots from the Storybook stories, Playwright, or Cypress specs you already run.
Diff
Each screenshot is compared against your approved baseline with a perceptual engine that ignores rendering noise.
Review
Changes land as a status check on your pull request. Approve the intended ones, reject the regressions.
Built for confidence
Everything you need to ship UI without fear.
From pixel-precise diffing to a review flow your whole team will actually use.
Pixel-perfect diffing
Perceptual comparison that flags real visual changes and ignores anti-aliasing noise.
Cross-browser & responsive
Capture every breakpoint across Chromium, Firefox, and WebKit in a single run.
Review workflow
Approve or reject changes inline. Approved diffs become the new baseline for the branch.
PR status checks
Every build posts back to the pull request, so nothing merges with an unreviewed change.
Parallel & fast
Thousands of screenshots diffed in parallel, so your pipeline stays quick.
Notifications
Slack and email alerts the moment a visual regression lands on a branch you watch.
MCP for AI agents
A remote MCP server lets Claude Code, Cursor, and other agents read diffs and approve changes.
In your CI
One step in the pipeline you already run.
Snapvisor plugs into GitHub Actions, GitLab CI, CircleCI, and anything that runs your tests.
- Install one @snapvisor SDK — no infrastructure to run.
- Screenshots upload from the CI job you already have.
- A status check posts straight to the pull request.
- Baseline updates automatically when you merge to main.
# .github/workflows/visual.yml
- name: Upload screenshots to Snapvisor
run: npx @snapvisor/cli upload ./screenshots
env:
ARGOS_TOKEN: ${{ secrets.ARGOS_TOKEN }}
# ✓ 412 screenshots uploaded
# ✓ 409 unchanged
# ! 3 changes need review →AI agents
Let AI agents review your UI.
Snapvisor runs a remote MCP server. Claude Code, Cursor, and any MCP client can list builds, read screenshot diffs, and approve visual changes — right inside the agent.
$ claude mcp add --transport http snapvisor https://mcp.snapvisor.ioBuilds & projects
List and inspect builds, projects, and their status across your organization.
Screenshot diffs
Read the visual changes in any build — baseline, current, and the computed diff.
Reviews & approvals
Create reviews to approve or reject visual changes without leaving the agent.
Comments
Read and post build comments so humans and agents stay on the same thread.
OAuth or a personal access token, tools derived from the same public API. Read the connect guide
Smart thresholds
Tuned to notice what humans notice.
Raw screenshot tests fail on a single anti-aliased pixel. Snapvisor's perceptual engine ignores sub-pixel rendering noise and only surfaces changes a person would actually see. Drag the threshold and watch the noise fall away.
Full coverage
Every browser. Every breakpoint.
Capture the whole matrix in a single run, so a regression can't hide on the viewport you forgot.
Why Snapvisor
Coverage the alternatives can't match.
Integrations
Works with the tools you already have.
Official SDKs for the frameworks and CI you run today — no rewrites required.
Enterprise-grade, open at the core.
The engine is open source and self-hostable; the hosted service layers on access control and single sign-on.
Pricing
Start free. Scale when you do.
Every paid plan starts with a 14-day Pro trial. Pro is usage-based — you only pay for what you render beyond the included screenshots.
Free
For open source and side projects.
- 7,000 screenshots / month
- Unlimited projects
- GitHub & GitLab status checks
- Fine-grained access control
- Community support
Pro
Usage-based, with a 14-day free trial.
- 15,000 screenshots included, then usage-based
- Review workflow & approvals
- MCP access for AI agents
- Slack & email notifications
- GitHub SSO available (+$50/mo)
Enterprise
For org-wide scale and control.
- Volume screenshot pricing
- SSO / SAML
- Self-hosted runners
- Role-based access & audit
- Dedicated support
FAQ
Questions, answered.
Playwright stores PNGs in your repo and fails on any pixel difference — including anti-aliasing noise. Snapvisor compares against an approved baseline with a perceptual engine, groups changes for review, and gives you an approve/reject UI instead of a red X.
No. The diff engine uses perceptual thresholds, so the changes that surface are ones a person would actually notice. You can tune sensitivity per project.
No. Point Snapvisor at your existing Storybook, Playwright, Cypress, or Puppeteer suite using the @snapvisor SDKs — open-source, drop-in forks of the official @argos-ci SDKs — and it captures screenshots from the stories and pages you already have.
When a change is detected, the pull request gets a status check linking to a side-by-side review. Approving a change promotes it to the new baseline for that branch — so intended changes never nag you twice.
Yes. Snapvisor runs a remote MCP server at mcp.snapvisor.io. Any MCP client — Claude Code, Cursor, and others — can list builds, read screenshot diffs, and create reviews. MCP access is included on the Pro plan.
Snapvisor is built on a proven open-source visual-diff engine, so the core is inspectable and self-hostable. The hosted service adds the review dashboard, integrations, and the MCP server.
Ship UI with total confidence.
Connect your repo, capture your first build, and never merge a silent visual regression again.
14-day Pro trial · Cancel anytime