Screenshot API for full pages, viewports, and page elements
Turn a public webpage into PNG, JPEG, or WebP with explicit controls for the capture area, viewport, page readiness, and color scheme.
Endpoint
Turn a public webpage into an image with explicit controls for output format, viewport, page state, and capture area.
Capture the document from top to bottom.
Capture one visible element with a CSS selector.
Set viewport, device scale, waits, and color scheme.
Useful for
Website previews / Visual test inputs / Agent vision
Capture the page state your workflow needs
The Screenshot endpoint accepts one public HTTP or HTTPS URL and returns the image body directly. Choose full-page or element capture, set viewport dimensions and device scale, and wait for page load or a visible selector before capture.
Full page or one element
Capture the entire document or one visible element with a CSS selector.
Responsive rendering
Set viewport dimensions and a 1β2Γ device scale factor.
Page readiness controls
Wait for load, network idle, a visible selector, or an additional delay.
Image output controls
Choose PNG, JPEG, or WebP, quality, light or dark color scheme, background, and animation behavior.
What is a screenshot API?
A screenshot API opens a webpage in a managed browser and returns a rendered image. It lets applications capture dynamic pages without operating their own Chromium fleet. Search1API supports PNG, JPEG, and WebP output, full-page or CSS selector capture, viewport and device scale controls, page readiness waits, timeouts, color scheme emulation, background handling, and animation control.
Typical workflow
Turn a public webpage into PNG, JPEG, or WebP with explicit controls for the capture area, viewport, page readiness, and color scheme.
Send one public URL with the output format and capture options.
The service renders the page in a managed browser and waits for the requested page state.
Receive the binary image, then compare, store, or analyze it in your own application.
Best for
Turn public webpages into PNG, JPEG, or WebP images
Generating website thumbnails and link previews from URLs.
Creating baseline and candidate images for a separate visual comparison system.
Preparing webpage images for downstream vision models or agents.
FAQ
Which image formats does Screenshot API support?
Screenshot API supports PNG, JPEG, and WebP. JPEG and WebP accept an optional quality value from 1 to 100.
Can Screenshot API capture one page element?
Yes. Pass a CSS selector to capture one visible element. Element capture and full-page capture cannot be enabled together.
How does Screenshot API wait for a page?
You can wait for DOM content, the load event, or network idle; optionally wait for a visible CSS selector or add a delay of up to five seconds. The request timeout can be set from 1 to 30 seconds.
How many credits does Screenshot API use?
A successful Screenshot API request costs 2 credits. Failed requests are not charged.