Send two snapshot sources, let Snapshot Site normalize the renders, and get back a third image that highlights what changed. The MVP ships with a single endpoint, a clean diff image, and mismatch metrics teams can plug into QA, launch checks, or monitoring.
The endpoint is intentionally simple: capture or load two states, normalize them into the same canvas, and return a diff image plus stats. That is enough to unlock QA triage, visual approval, and customer-facing release checks.
Use live URLs when you want Snapshot Site to render both pages, or provide existing PNG screenshots when you already have captures in storage.
The engine aligns both images on the same canvas, then highlights changed pixels in a dedicated diff image with a configurable sensitivity threshold.
Store the three image URLs, surface mismatch percentage in CI, or send the diff link to product, QA, or growth teams for approval.
{
"before": {
"url": "https://snapshot-site.com/pricing",
"width": 1440,
"fullSize": true,
"hideCookie": true
},
"after": {
"url": "https://staging.snapshot-site.com/pricing",
"width": 1440,
"fullSize": true,
"hideCookie": true
},
"threshold": 0.1
}
{
"status": "success",
"message": "Visual diff successfully created!",
"fetchTime": "2026-03-29T09:30:00.000Z",
"before": {
"link": "https://api.prod.ss.snapshot-site.com/screenshots/snapshot-site.com/uuid-1/1.png",
"width": 1440,
"height": 3980,
"source": "https://snapshot-site.com/pricing"
},
"after": {
"link": "https://api.prod.ss.snapshot-site.com/screenshots/staging.snapshot-site.com/uuid-2/2.png",
"width": 1440,
"height": 3980,
"source": "https://staging.snapshot-site.com/pricing"
},
"diff": {
"link": "https://api.prod.ss.snapshot-site.com/screenshots/comparisons/uuid-3/3.png",
"width": 1440,
"height": 3980
},
"summary": {
"mismatchPixels": 14382,
"mismatchPercentage": 1.27,
"totalPixels": 5731200,
"sameDimensions": true
}
}
The first release is already useful because it solves one painful question clearly: what changed between version A and version B?
A SaaS team compares key pages before every deploy to catch layout shifts, missing components, or regression bugs before customer traffic sees them.
A performance marketing team validates hero copy swaps, pricing card edits, and CTA changes before turning paid campaigns back on.
A compliance or archive workflow snapshots the same page regularly and uses the diff output to highlight exactly what changed since the previous capture.