Vitalii Holben
When we first set up screenshot monitoring, we left everything on the default viewport mode. It captures the visible portion of the page, roughly what fits on one screen without scrolling. Worked fine for checking headers, hero sections, and navigation. Then we started monitoring a competitor's pricing page, and for three weeks visual diff reported "no changes." The competitor had moved their pricing table below the fold, added a new comparison section, and restructured their entire plan layout. Our viewport screenshot never scrolled down far enough to see any of it.
That's the problem with viewport captures: they assume the important content is above the fold. For homepages and landing pages, that's usually true. For pricing pages, legal docs, and terms of service, the critical content usually lives further down. Think about a disclaimer buried at the bottom of a product page. Or a cancellation clause in paragraph twelve of the terms. Viewport mode misses all of it.
What full-page mode actually gives you
Full-page mode captures everything from top to bottom. The browser scrolls through the entire page and stitches the result into one tall image. The files are bigger (200-800 KB vs 30-100 KB for viewport), and processing takes a few seconds longer. The trade-off is worth it for any page where changes below the first screen matter. We switched our terms-of-service monitors to full-page after a client's cancellation policy changed in the last third of the page and we didn't catch it for a week. One thing to keep in mind: switching modes mid-stream on an existing monitor breaks the visual diff chain, because the image dimensions change drastically and every pixel comparison triggers as a difference. Pick one mode per URL when you set up the monitor and stick with it.
After running both modes for a few months, the pattern was pretty clear. viewport for quick post-deploy checks and header monitoring where speed matters more than completeness. Full page for pricing pages, legal documents, competitor audits, and anything compliance-related where missing a change below the fold could cost you. The full-page screenshots feature page goes into the technical side: viewport sizing in full-page mode, API configuration, that sort of thing.
Start archiving websites today
Free plan includes 3 websites with daily captures. No credit card required.
Create free account
7% of Amazon Pages Returned Errors With HTTP 200. Here's the Proof.
We added a handful of Amazon pages to track product prices. Instead of price changes, we started getting alerts about error pages. Turns out scheduled screenshots double as availability monitoring, and they catch things Pingdom never will.
False Positives in Screenshot Monitoring: What Causes Them and What to Do
We got 14 alerts in one day from a single website. The problem was a live counter and a logo carousel triggering visual diff on every capture. Here is how we fixed it with threshold tuning and hide selectors.
What Competitor Pages to Monitor and How Often to Take Screenshots
Most companies know they should monitor competitors, but few do it consistently. This guide covers the exact pages worth tracking — from pricing and homepage to careers and changelogs — with recommended screenshot frequencies for each, and how to turn 150+ monthly snapshots into actionable competitive intelligence.