# Snapvisor

> Snapvisor is a visual regression testing platform. It screenshots your UI on every pull request, diffs each screenshot against your approved baseline with a perceptual engine, and posts the result as a status check on GitHub or GitLab so unreviewed visual changes never merge. It is built on the open-source @argos-ci engine and runs a remote MCP server so AI agents can review UI too.

## What it does

- Captures screenshots from your existing Playwright, Cypress, Puppeteer, or Storybook suite using the official `@argos-ci` SDKs — no test rewrite.
- Compares against the last approved baseline for the branch; the first build on a branch becomes its baseline.
- Cross-browser and responsive: Chromium, Firefox, and WebKit in a single run.
- Perceptual diffing that ignores anti-aliasing and sub-pixel rendering noise, with tunable per-project sensitivity.
- Review workflow: approve or reject changes; approved diffs become the new baseline.
- Integrations: GitHub and GitLab status checks, Slack and email notifications.

## Docs

- [Quickstart](https://snapvisor.io/docs): install an SDK, set your project token, upload your first build from CI.
- [Getting started](https://snapvisor.io/docs/getting-started): create a project, set `ARGOS_TOKEN`, capture and upload screenshots.
- [Access tokens](https://snapvisor.io/docs/tokens): project tokens for CI uploads vs personal access tokens for the API and MCP.
- [GitHub integration](https://snapvisor.io/docs/github): build status checks on pull requests.
- [GitLab integration](https://snapvisor.io/docs/gitlab): commit statuses on merge requests, including self-managed GitLab.
- [Parallel testing](https://snapvisor.io/docs/parallel-testing): shard a screenshot suite across machines and finalize as batches.
- [Baseline builds](https://snapvisor.io/docs/baseline-build): how the reference build and base branch are resolved.
- [Monitoring mode](https://snapvisor.io/docs/monitoring-mode): auto-approve branches so builds set a success check without review.
- [Summary checks](https://snapvisor.io/docs/summary-checks): roll every build on a commit into one required status.
- [Flaky test detection](https://snapvisor.io/docs/flaky-test-detection): ignore recurring visual changes so flaky screenshots stop demanding review.
- [Slack notifications](https://snapvisor.io/docs/slack-notifications): hear about visual changes when a build lands.
- [Team members and roles](https://snapvisor.io/docs/team-members-and-roles): team levels and per-project admin, reviewer, and viewer roles.
- [SAML SSO](https://snapvisor.io/docs/saml-sso): log in through your identity provider (Enterprise plan).
- [Spend management](https://snapvisor.io/docs/spend-management): cap usage costs with a per-period spend limit.
- [Open source](https://snapvisor.io/docs/open-source): the visual-diff engine is inspectable and self-hostable.
- [FAQ](https://snapvisor.io/docs/faq): common questions on baselines, flaky changes, and AI agents.
- [Review workflow](https://snapvisor.io/docs/review-workflow): how baselines, approvals, monitoring mode, flaky-change detection and summary checks work together.
- [CI integration](https://snapvisor.io/docs/ci-integration): connect GitHub or GitLab, authenticate uploads with project tokens or tokenless auth, and split suites across machines.
- [SDKs](https://snapvisor.io/docs/sdks): the @snapvisor JavaScript packages, plus the Python SDK and CLI.
- [API](https://snapvisor.io/docs/api): REST API base URL, authentication and the OpenAPI specification.
- [Pricing (docs)](https://snapvisor.io/docs/pricing): plans and what each includes.
- [Self-hosting](https://snapvisor.io/docs/self-hosting): run your own Snapvisor instance with Docker Compose, with the required services and environment variables.
- [Migrate from Lost Pixel](https://snapvisor.io/docs/migrate-from-lost-pixel): move a Lost Pixel suite to Snapvisor.
- [Migrate from Percy](https://snapvisor.io/docs/migrate-from-percy): move a Percy suite (percySnapshot, percy exec, PERCY_TOKEN, .percy.yml, Storybook) to Snapvisor.
- [Support](https://snapvisor.io/docs/support): reach the team at support@snapvisor.io.

## For AI agents

- [Add to Claude](https://claude.ai/directory/3368eb9b-7adf-4166-8acf-1b39ff88e028): the fastest setup for claude.ai, Claude Desktop and Claude Code signed in with a Claude account. Opens Snapvisor's listing in Claude's connector directory; click Connect, then sign in. MCP requires a paid plan.
- [Agent setup instructions](https://snapvisor.io/agent-setup/prompt.md): raw markdown an AI coding agent fetches and executes to set itself up for Snapvisor. It connects the MCP server for Claude Code, Codex, Cursor or OpenCode, installs the SDK for the project's test runner, and verifies the connection with the `getMe` tool.
- [Agent setup guides](https://snapvisor.io/agent-setup): the same steps for people, with one page per agent: [Claude Code](https://snapvisor.io/agent-setup/claude-code), [Codex](https://snapvisor.io/agent-setup/codex), [Cursor](https://snapvisor.io/agent-setup/cursor), [OpenCode](https://snapvisor.io/agent-setup/opencode).
- [MCP server guide](https://snapvisor.io/docs/agents/mcp-server): connect Claude Code, Cursor, or any MCP client to list builds, read screenshot diffs, create reviews, and comment. MCP access is included on the Pro plan.
- [REST API reference](https://snapvisor.io/docs/api-reference): base URL, bearer-token authentication, and the OpenAPI specification.

## Agent surfaces

Machine-readable surfaces, grouped by what they are for. Where a surface is on another host, the host is in the URL.

Docs as markdown
- [Docs index for agents](https://snapvisor.io/docs/llms.txt): docs-only index, one link per docs page to its markdown mirror.
- Per-page markdown mirrors: add `.md` to any docs page URL, e.g. https://snapvisor.io/docs/baseline-build.md, and https://snapvisor.io/docs/index.md for the docs index. Each starts with the page title and a `Canonical:` line naming the HTML page. The generated API-reference operation pages have no mirror; use the OpenAPI document below.
- Content negotiation on the docs: a request to a docs page whose `Accept` header prefers `text/markdown` is answered with that page's markdown mirror; a browser's default `Accept` still gets HTML. `curl -H 'Accept: text/markdown' https://snapvisor.io/docs/baseline-build`. This covers docs pages only; other snapvisor.io pages are HTML.

MCP server
- MCP endpoint (streamable HTTP, OAuth 2.1 or personal access token): https://mcp.snapvisor.io
- [MCP server card](https://snapvisor.io/.well-known/mcp/server-card.json): the endpoint, transport and OAuth metadata location. The same card is served from https://mcp.snapvisor.io/.well-known/mcp/server-card.json.
- OAuth protected resource metadata (RFC 9728): https://mcp.snapvisor.io/.well-known/oauth-protected-resource
- OAuth authorization server metadata: https://mcp.snapvisor.io/.well-known/oauth-authorization-server
- Agent registration recipe: https://app.snapvisor.io/auth.md
- [MCP server overview](https://snapvisor.io/mcp): how to connect, and the discovery documents above in one place.

REST API
- REST API base URL: https://api.snapvisor.io/v2
- OpenAPI specification: https://api.snapvisor.io/v2/openapi.yaml
- OAuth protected resource metadata for the REST API: https://api.snapvisor.io/.well-known/oauth-protected-resource
- API catalog (RFC 9727): https://app.snapvisor.io/.well-known/api-catalog

## Product

- [Home](https://snapvisor.io/): overview, how it works, and integrations.
- [Pricing](https://snapvisor.io/pricing): Free (7,000 screenshots/month), Pro (usage-based from $9/month, 15,000 screenshots included, MCP access, 14-day trial), Enterprise (custom). GitHub SSO is included on Free and Pro.
- [Visual regression testing guide](https://snapvisor.io/visual-regression-testing): what visual regression testing is, how to set it up in CI, how Percy approaches it (sourced from Percy's public docs, checked 2026-10-11) and how the same workflow runs in Snapvisor, including moving from Percy. For the side-by-side see [Snapvisor vs Percy](https://snapvisor.io/compare/percy).
- [Self-hosted visual regression testing](https://snapvisor.io/self-hosted-visual-regression-testing): an open-source, self-hostable option for Storybook teams looking beyond Chromatic. What you run (Docker Compose, plus your own Postgres and S3-compatible bucket), how Storybook stories are captured with @snapvisor/storybook, what self-hosting costs in ops and limits (the built-in screenshot cap without Stripe, SAML, MCP, analytics keys), and that the server repository is not public yet. Chromatic statements are sourced from its public pricing page and docs, checked 2026-10-12. For the side-by-side see [Snapvisor vs Chromatic](https://snapvisor.io/compare/chromatic).
- [Visual regression testing in GitHub pull requests](https://snapvisor.io/visual-regression-testing-github): the review workflow on a pull request, step by step. GitHub Actions uploads screenshots, Snapvisor compares them with the baseline from the base branch, a commit status and one comment appear on the pull request, a reviewer approves or rejects the diffs, and approval moves the status to success. Covers the status context names, the optional summary status, the pull request comment setting, Storybook capture with @snapvisor/storybook, and the limits (GitHub App required, a deleted comment is not reposted). Behaviour is taken from the backend code, the published SDK and the docs.
- [Playwright visual regression testing](https://snapvisor.io/playwright): set up @snapvisor/playwright — install, the reporter in playwright.config.ts, argosScreenshot in your tests, the CI step and the pull request gate. Commands and options come from the Snapvisor docs and the published package.
- [Storybook visual regression testing](https://snapvisor.io/storybook): set up @snapvisor/storybook — one screenshot per story through the Storybook Vitest addon (recommended) or the Storybook Test Runner, extra screenshots from a play function, and the CI step.
- [Cypress visual regression testing](https://snapvisor.io/cypress): set up @snapvisor/cypress — registerArgosTask in cypress.config.js, the support import, cy.argosScreenshot in your specs, and the CI step.
- [Get the app](https://snapvisor.io/apps): install Snapvisor as an app on macOS, Windows, iPhone, iPad and Android. It is a progressive web app — there is no App Store, Google Play, Mac App Store or Microsoft Store listing today. Installing gives it its own window with no browser chrome, an icon in the Dock, taskbar or home screen, and a bundle cached on the device; it does NOT add push notifications or a share sheet.
- [App](https://app.snapvisor.io): sign in, create projects, review builds.
- [Refer & Earn](https://snapvisor.io/partners): the referral program — 30% of what everyone you refer pays, for their first 12 months, $50 minimum payout, paid through Stripe. No application and no setup; every account already has a link.

## Compare (sourced, verified 2026-09-25)

- [Snapvisor vs Percy](https://snapvisor.io/compare/percy): vs Percy (BrowserStack) — free tiers, pricing model, cross-browser coverage, and MCP access. Migration guide: [Migrate from Percy](https://snapvisor.io/docs/migrate-from-percy).
- [Snapvisor vs Chromatic](https://snapvisor.io/compare/chromatic): vs Chromatic — pricing tiers, Storybook depth, cross-browser coverage, and MCP access.
- [Snapvisor vs Applitools](https://snapvisor.io/compare/applitools): vs Applitools Eyes — pricing transparency, Visual AI, testing scope, and MCP access.
- [Snapvisor vs Argos CI](https://snapvisor.io/compare/argos): Snapvisor is a fork of the open-source Argos CI engine — what is the same and what Snapvisor changes (hosting, free tier, plan pricing, MCP access, self-hosting).
- [Snapvisor vs Lost Pixel](https://snapvisor.io/compare/lost-pixel): vs Lost Pixel — project status (sunset announced 2026-04-22, GitHub repository archived), baseline storage, free tier and capture sources, checked 2026-10-05. Migration guide: [Migrate from Lost Pixel](https://snapvisor.io/docs/migrate-from-lost-pixel).
- [Snapvisor vs Playwright](https://snapvisor.io/compare/playwright): Playwright's built-in toHaveScreenshot (golden files stored with your tests) and Snapvisor (server-side baselines, review UI, pull request status checks), checked 2026-10-12. Snapvisor captures through Playwright; it does not replace it.

## Legal

- [Privacy Policy](https://snapvisor.io/privacy): what data Snapvisor collects, the processors it uses (Stripe, PostHog, Sentry, Backblaze B2), and how to request deletion. Operated by Devino Solutions.
- [Terms of Service](https://snapvisor.io/terms): the agreement governing use of Snapvisor.
- [Delete your account](https://snapvisor.io/account-deletion): how to permanently delete a Snapvisor account, exactly what is deleted, what is retained and why.

## Contact

- [Support](https://snapvisor.io/support): email support, the in-app support form, and what to include in a report.
- [Contact](https://snapvisor.io/contact): sales, security disclosure, privacy, and data-deletion routes. Snapvisor is operated by Devino Solutions.

Discovery: [Sitemap](https://snapvisor.io/sitemap.xml) · [IndexNow key](https://snapvisor.io/6d0b700049a69d5772e0278ff6ecd56c.txt).