[01] Visual Diff Detection
Catch UI changes before they reach docs.
When your product UI shifts, Reshot detects it in the same CI run that changed the code. Layout shifts, new elements, responsive regressions — every change surfaces in the review queue before it reaches a single embed.
[01] How visual diff works
Compare every capture against the baseline.
Each CI run produces a new capture. Reshot compares it pixel-by-pixel against the stored baseline. If the difference crosses the threshold, the capture is flagged and enters the review queue.
CI captures the current state
On every push, Reshot captures every screen defined in your reshot.config.json configuration. Each capture is compared against the stored baseline.
Pixel comparison finds the changes
The new capture is compared pixel-by-pixel with the baseline. If the difference exceeds the configured threshold, the capture is flagged as changed.
Changes enter the review queue
Flagged captures appear in the review queue with the before/after comparison and the specific regions that changed. Nothing publishes until reviewed.
Approve to update the baseline
When you approve a diff, the new capture becomes the baseline. The CDN URL updates. All embeds now show the approved version.
[02] The review queue
Before and after, side by side.
When a capture changes, you see the baseline on the left, the new capture on the right, and the detected difference highlighted. Status lanes show what needs attention.
[03] Where diffs surface
Changes show up where your team already works.
Reshot integrates into the review workflow you already have. Diffs appear in three places.
PR comments
When a capture changes, Reshot posts a comment on the pull request showing the before/after and the detected difference.
Review queue
All pending diffs appear in a kanban-style review queue inside the dashboard. Detected, Reviewing, Approved.
Approval workflow
Approve or reject changes from the review queue. Approved captures become the new baseline and publish to the CDN.
What Reshot doesn't do
Reshot detects UI changes. That's it.
It does not run visual regression tests against expected snapshots. It does not compare captures to Figma designs. It does not enforce pixel-perfect matching. It captures the real UI, compares it to the last approved version, and surfaces the difference for human review.
Get started
Start with one docs visual workflow.
Free tier. No credit card. Connect your repo, capture one real docs scenario in CI/CD, and keep the same URL current after every ship.