Website Screenshot API
Pricing
from $5.00 / 1,000 screenshot captureds
Screenshot any URL in a real browser: full-page or viewport PNG/JPEG, desktop and mobile presets, dark mode, cookie banners hidden, optional PDF. Pay per page.
Pricing
from $5.00 / 1,000 screenshot captureds
Rating
0.0
(0)
Developer
Joshua Smith
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 hours ago
Last modified
Categories
Share
One URL per line. The scheme is optional (example.com works). Duplicates are removed.
Viewport, pixel density and user agent preset. Choose custom to set width, height and scale factor yourself.
Capture the whole scrollable page instead of just the first screen.
PNG is lossless; JPEG files are much smaller and support the quality setting.
Hide the most common cookie / consent pop-ups (OneTrust, Cookiebot, Didomi, Usercentrics, Quantcast and 60+ others) with CSS before capturing. Nothing is clicked or accepted.
Additionally save the page as a PDF (billed as a separate PDF event).
Paper size used when rendering PDFs.
Emulate prefers-color-scheme: dark so sites with a dark theme render it.
Only used with the custom device preset.
Only used with the custom device preset.
1 = standard, 2 = retina, 3 = high-density phone. Only used with the custom preset.
When the page is considered ready. networkidle additionally waits (up to 15 s) for background requests to settle after the load event, which gives the most complete render.
Additional wait after the page is ready, for animations or late scripts.
Scroll through the page first so lazy-loaded images render in full-page screenshots.
Un-stick fixed and sticky elements in full-page captures, so headers, navbars and floating bars appear once at their natural place instead of repeating or covering content. Only applies when Full page is on.
Wait until this element exists before capturing, e.g. .chart-rendered or #main img. Waits up to the page timeout; if it never appears the page is still captured and the record gets a warnings entry.
Extra CSS selectors to hide before capturing, e.g. .chat-widget, #newsletter-popup.
[]Screenshot a single element, e.g. #pricing-table, instead of the page.
How many pages to render in parallel. Each browser tab uses roughly 200 to 400 MB of memory.
Give up on a page after this long.
Retry a page that failed to load this many times before reporting it.
Headers sent with every request, e.g. {"Authorization": "Bearer ...", "Accept-Language": "de-DE"}. Treated as secrets: values are never logged or stored in the output.
{}Abort requests for these resource types to speed up captures of heavy pages. Blocking image, media or font is usually safe; blocking stylesheet, script or xhr (XHR and fetch) changes how the page renders.
[]