Watch your website
Name the public pages of your website and Snapvisor photographs them, compares them with the last version you approved and shows what moved. No code, no install, no pipeline.
Your website changes without you: an AI agent ships a fix, a teammate edits a style, a plugin updates. Snapvisor takes a picture of each page you care about, compares it with the last picture you approved, and tells you what moved. You decide whether the change stays.
This page is for people who do not write code. If you already use automated tests, start at Getting started instead; the engine and the approval step are the same.
What you need
- A free Snapvisor account. Sign up and create a project with just a name (no repository).
- The public addresses of the pages you want watched, such as
https://example.com/andhttps://example.com/pricing.
Add your pages
- Open your project, then Settings → Pages to watch.
- Give each page a short name (
home,pricing) and paste its address. Names are how Snapvisor matches the same page from one check to the next, so keep them stable. - Pick a screen size: desktop, tablet or phone.
- Press Check now.
Snapvisor opens each page in its own browser, photographs it, and creates a build. The first build is your reference: open it, look at the pictures, and approve it.
Check again
Press Check now whenever you want a fresh look, or ask an assistant to do it: in Claude, connect Snapvisor from the directory listing and say "Capture the pages of my Snapvisor project site in the account acme." Each check is compared with the last capture you approved.
Read what changed
A build with differences shows Changes detected. Open it and each page shows the approved picture, the new picture and the parts that moved, highlighted. Pages that look the same are listed as unchanged.
If a page could not be photographed (the address does not answer, or it needs a login), the build ends in Error and names the page and the reason. Fix the address and check again.
Approve or flag
- Approve when the change is wanted. That capture becomes the new reference.
- Reject (flag) when it is not. The previous reference stays, and the build stays marked until a later capture is approved.
Reviewers of the project get an email when a capture finds a change. Turn it off under your account's Notifications settings, in Builds to review.
Limits
- Public pages only. Addresses on your own machine, a private network or behind a login are refused when you press Check now.
- Up to 10 pages per check. Create a second project for more.
- Each check counts one screenshot per page toward your plan's monthly screenshots (7,000 on Free).
- Checks run when you ask for them. Scheduled checks are not available yet.
For developers
The form calls the same capture as the captureScreenshotsForProject API operation and MCP tool, documented in Visual testing without CI. To make sure only a person can approve a project's builds, switch on Settings → Approvals → Require a person to approve; see Review workflow.
Getting started
Create a Snapvisor project, set your project token, capture screenshots from your existing test suite, and upload your first build.
Migrate from Lost Pixel
Move a lostpixel.config.js suite to Snapvisor - how shots, masks, breakpoints, and thresholds translate, and why baselines stop living in your git repository.