Website Screenshots: Full Page, Mobile, PDF & Change Alerts
Pricing
from $3.00 / 1,000 screenshots
Screenshot any list of URLs (full page or viewport, desktop or mobile, PNG, JPEG or PDF, one element, no cookie banners), or schedule it to compare each page with the last run and get how much it changed, with the changed area and a Slack-ready summary.
One page per line, for example https://apify.com/pricing. Add a name for alerts with "Name | URL", for example "Competitor pricing | https://example.com/pricing". Only public pages: pages that ask for a password are never captured. At most 5,000 per run; split longer lists across runs or tasks.
Capture the whole page from top to bottom (up to the max page height). Turn off to capture only what fits in the window (the viewport).
Desktop is a 1280 x 800 window. Mobile is a 412 x 915 phone screen and tablet an 800 x 1280 one, both at 2x pixel density with touch, so sites show their mobile layout.
Optional. Overrides the device's window width, for example 1440 or 1920. Leave empty to use the device preset.
Optional. Overrides the device's window height. With Full page off, this is the height of the screenshot, for example 600 for just the top of the page.
PNG is pixel-exact (best for monitoring and text). JPEG files are several times smaller (good for archives and thumbnails). For a PDF, turn on "Also save a PDF".
JPEG only: 1 (smallest file) to 100 (best quality).
Also save each page as an A4 PDF with backgrounds, linked in pdfUrl. Included in the screenshot price.
Optional. Capture only the first element matching this CSS selector instead of the page, for example #pricing or .plans. When monitoring, changes are measured on that element only, which makes small changes (a price) show up clearly.
Hide consent banners (OneTrust, Cookiebot, Didomi, Usercentrics and about 20 more consent tools, plus unknown banners found by their wording) and chat launchers (Intercom, Drift, HubSpot, Zendesk and more). Nothing is clicked or accepted: they are only hidden.
CSS selectors of elements to hide, one per line, for example .ad-slot or #rotating-banner. Their space is kept, so the layout does not move. Use it to keep rotating content out of change monitoring.
Optional. Wait until this element is visible before capturing, for example .price-table. If it never appears within the page timeout, you get a free row explaining that and no charge.
Wait this long after the page has loaded (and lazy content was scrolled in) before capturing, for animations or late widgets. 0 for none, at most 10 seconds; it counts inside the page timeout.
Scroll down the page (for at most 6 seconds, up to the max page height) and back up before a full-page capture, so lazy-loaded images and scroll animations appear.
Ask the page for its dark theme (prefers-color-scheme: dark). Pages without a dark theme look the same.
Full-page captures stop at this height, so endless pages cannot run up time and memory, and the row says so (truncated). Captures are also kept under 16,000 image pixels tall and 16 megapixels in all, so mobile stops at 8,000 px, tablet at 5,000 px and a 3,840 px wide window at about 4,100 px.
How long a page may take to load, including waiting for your element and the extra delay. A page that is still not ready gets a free error row and is not charged. At most 60 seconds, so one page never takes more than about 90 seconds.
Turn on, save as a task and schedule it: each page is compared with its last screenshot, and you get the share of pixels that changed, the changed area, a link to the previous screenshot and an image with the changes in red. The first run saves each page as its baseline. Normal runs never touch this memory.
A page counts as changed when at least this share of its pixels changed (a pixel counts when a colour moved by more than 24 of 255, so font smoothing does not). The default 0.1% catches a changed paragraph or banner on a full page; for a price, capture the price element (then the share is of that element) or pick 'Any visible change'. Raise it, or use "Hide these elements", for pages with carousels, dates or ads.
Monitoring only: pages that did not change get no row and no screenshot charge (only the comparison), so your dataset, sheet or Zapier flow holds changes only.
Monitoring only: the first run saves each page's baseline without returning rows (each baseline is charged as one comparison instead of a screenshot), so alerts start with the first real change.
Key-value store that keeps each page's last screenshot between runs (lowercase letters, digits and hyphens). Each saved task and each set of capture options keeps its own memory inside it, so the default works for most people.
