Frequently asked questions

Short answers to the questions we hear most. Can't find yours? Reach us from the Support page. Seeing changes you did not make? See Troubleshooting flaky builds and false diffs.

How to invite someone to my Snapvisor team

Team owners send invites from the team's settings. Open your team, go to its members, and invite the person by email; they receive an invitation and join the team once they accept. New members pick up your team's default role — see members and roles for what that grants.

If you're not on a team yet, ask a team owner to send you an invite, or create your own team from the app.

More questions

How is this different from raw Playwright snapshot tests?

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.

Will it flag anti-aliasing and font rendering noise?

No. The diff engine uses perceptual thresholds, so the changes that surface are ones a person would actually notice. You can tune sensitivity per screenshot with the SDK threshold option, or for a whole upload with the ARGOS_THRESHOLD environment variable.

Do I have to rewrite my tests?

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.

How does baseline approval work?

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.

Can AI agents use Snapvisor?

Yes. Snapvisor runs a remote MCP server at mcp.snapvisor.io. Any MCP client — Claude Code, Cursor, and others — can create builds, upload screenshots, run visual diffs, and approve or reject changes — no CI pipeline required. The build loop (create a project, push screenshots, read the diff) is included on the Free plan; reviewing and approving changes, comments and team tools need a paid plan.

Is Snapvisor open source?

Snapvisor is built on a proven open-source visual-diff engine, so the core is inspectable and self-hostable. A self-hosted instance runs the same dashboard, worker and MCP server; the hosted service adds that we operate it, with billing, email, Git-provider apps and upgrades.