Visual regression testing in CI/CD
Capture screenshots of key pages on every deploy across Mobile, Tablet, and Desktop viewports, then diff them against a baseline to catch unintended layout changes before they reach production.
URL
Try a Screenshot
This matches the settings you just tried above. Swap in your API key and drop it straight into your project.
curl "https://shot.screenshotapi.net/v3/screenshot?token=YOUR_API_KEY&url=https%3A%2F%2Fwww.google.com%2F&file_type=png&output=image" --output screenshot.pngA quick reference for every option in the Playground above, so you know exactly which parameter to change in your own API calls.
A quick guide to picking a file format and response type based on what you're building.
Choose based on what the screenshot will be used for.
PNG
Best for: UI screenshots, text-heavy pages, anything needing transparency
Trade-off: Larger file size than JPG or WebP for photo-heavy pages
JPG
Best for: Photo-heavy pages where file size matters more than sharp edges
Trade-off: Lossy compression can blur small text and UI edges
WebP
Best for: A balance of quality and file size for most general use cases
Trade-off: Slightly less universal support in older tooling than PNG/JPG
Best for: Archiving, reports, and pages you want to treat as a document
Trade-off: Not ideal for embedding as a web image
Choose based on how the result fits into your workflow.
IMAGE
Best for: Direct display, downloads, or embedding the file itself
Trade-off: No metadata — you only get the raw file back
JSON
Best for: Automated pipelines that need a hosted URL plus status metadata
Trade-off: Requires an extra step to fetch the image from the returned URL
A single API call runs a full render pipeline behind the scenes. Here's what happens between your request and the screenshot you get back.
Call the API with a target URL and the parameters you want. Viewport, file type, output mode, and any advanced options like full page or ad blocking.
The target page is loaded in a real browser environment at the requested viewport size, so the capture reflects what a visitor would actually see, including JavaScript-rendered content.
If enabled, cookie banners and ad placements are removed and the page is scrolled through before capture, so scroll-triggered content and lazy-loaded images render correctly.
The response is returned as either the image/PDF file directly, or as JSON containing a hosted URL and metadata. Ready to store, display, or pass into another step of your pipeline.
The same parameters you just tried above power these common use cases.
Capture screenshots of key pages on every deploy across Mobile, Tablet, and Desktop viewports, then diff them against a baseline to catch unintended layout changes before they reach production.
Take scheduled screenshots of competitor pricing pages or landing pages to track changes over time without manually checking each site.
Generate Open Graph images or blog thumbnails automatically from a live URL instead of maintaining static preview images by hand.
Attach full-page screenshots to SEO audits or client reports so stakeholders can see exactly what was reviewed, alongside the data.
Capture a dated, full-page record of a page's state, useful for legal, compliance, or documentation purposes where you need proof of what a page looked like on a given date.
Check how a page renders at Mobile, Tablet, Desktop, and 4K viewports in one pass instead of manually resizing a browser window for each breakpoint.
Answers to common questions about using the screenshot API, straight from the parameters you just tried above.