HTML and eligible asset bytes are SHA-256 fingerprinted server-side. Bodies are discarded immediately and never stored inside the snapshot artifact.
Freeze the site.
Compare the truth.
Capture a portable bounded baseline before a deploy. SNAP fingerprints page HTML and eligible public assets with SHA-256, discards the bodies, then lets you compare a later state entirely in the browser.
Create snapshot →Know what changed,
not just that something changed.
Save a portable baseline before a deploy. Later, capture again or load another snapshot and compare routes, status, metadata and content fingerprints entirely in your browser.
A snapshot is a normal JSON file with a versioned 2XBR schema. Keep it with a release, ticket or deployment artifact.
Once two snapshots exist, comparison happens locally in the browser. Removed routes and changed bytes remain visible even if the old deploy is gone.
SNAP records caps and incomplete fingerprints. It never turns an unscanned resource into a claim of equality.