Tools / Website Screenshot Scraper – Screenshot API, JPEG, URL to PDF
Website Screenshot Scraper – Screenshot API, JPEG, URL to PDF
Capture any public URL as a JPEG, PNG or PDF screenshot with a real Chromium browser. Full-page or viewport-only, four device presets (desktop, iPhone 14, Pixel 7, iPad) or a custom viewport, a single CSS-selector element capture, a fixed 1200x630 Open Graph card render, and raw-HTML rendering when you already have the markup and just need an image. Visual diff mode pixel-compares every URL against a comparison URL — staging against production, or one page before and after a deploy — and returns the differing-pixel count, the change percentage and a highlighted diff image for one charge per comparison, not two. Emulate dark mode, a locale, a timezone, touch support or a GPS position for pages that render differently under any of them; wait for a specific selector instead of a fixed delay; route the browser through a proxy; and pass HTTP headers or cookies you already hold for pages that need them. A URL that fails to load (timeout, DNS error, 4xx/5xx) returns a clear error row and is never charged — you only pay for screenshots that actually come back. No API key, no start fee, JPEG output by default to keep file size (and your bill) small.
Run it
Pay-per-result on Apify, no FetchSmith account needed. Use your own Apify API token, or hit Run on the Store page with no token at all.
curl -X POST "https://api.apify.com/v2/acts/fetchsmith~website-screenshot-scraper/run-sync-get-dataset-items?clean=true" \
-H "Authorization: Bearer YOUR_APIFY_TOKEN" -H "Content-Type: application/json" \
-d '{"devicePreset": "desktop", "format": "jpeg", "fullPage": true, "urls": ["https://example.com"]}'
Returns the rows as JSON when the run finishes. A hosted FetchSmith API (one key, no Apify account, see API docs) is planned but not open yet.
Output fields
url format success error imageUrl screenshotKey contentType byteSize capturedAt compareUrl compareImageUrl compareScreenshotKey diffImageUrl diffScreenshotKey diffPixels comparedPixels diffPercent changed diffRegions diffRegionsLargestPixels diffSpecks diffRegionMinPixels baselineWidth baselineHeight compareWidth compareHeight sizeMismatch
Sample output
{
"byteSize": 169944,
"capturedAt": "2026-10-19T21:32:48.357Z",
"contentType": "image/jpeg",
"error": null,
"format": "jpeg",
"imageUrl": "https://api.apify.com/v2/key-value-stores/EhN1wpS9r9M5zZZ4t/records/screenshot-1792445568253-1.jpg",
"screenshotKey": "screenshot-1792445568253-1.jpg",
"success": true,
"url": "https://news.ycombinator.com"
}
Guides
- "Website Screenshot API, No Key: Three Free Endpoints Measured — and Where Each One Breaks" — "There is no single public 'screenshot API' standard, but three keyless HTTP endpoints exist and are widely linked. Measured live: one 403s outright from a datacenter IP, one silently serves a 24-hour-stale cached image unless you ask the right way, and one allows exactly 5 requests per rolling 24 hours."
- We swept a visual-diff threshold from 0.02 to 0.3 expecting a curve. We measured a cliff. — Pixel-diffing two unrelated pages at three diffThreshold settings — the strict end reads as 99.75% different, the default as 6.22%, and the loose end barely moves from there. The useful range is one order of magnitude wide, not the whole 0-1 scale.
- PNG to JPEG saved 15-63% on a full-page screenshot, depending on the page. Cropping beat both. — We priced a screenshot Actor by measuring it twice, on a text page and a photo page, and the format switch everyone recommends turned out to be real but wildly page-dependent — and still the weaker lever either way.
Only publicly accessible pages are read. Respect the source site's terms when using the data.