Screenshot API for Developers
A screenshot API accepts a URL and returns an image of the rendered page, so your application can capture sites on demand while the browser runs on the provider's side.
This guide explains what the capture workflow involves, which controls change the result, how credits are consumed, and how to make a first request.
What a screenshot API does
You send a request containing the target URL and a screenshot flag. The service loads the page in a real browser, renders it, and returns the image. Because rendering happens server-side, your code does not need to install or maintain a browser engine.
The same request can also return the page HTML, so a single call can give you both a visual record and the underlying markup for parsing.
Capture controls that change the result
These options determine what the returned image actually contains. Choose them deliberately, because a default capture and a configured capture can look very different.
- Full-page rendering captures the entire scrollable page rather than only the visible viewport.
- Custom viewport sets the width and height the page is rendered at, which affects responsive layouts.
- Custom JavaScript runs script before the capture, useful for dismissing banners or triggering lazy content.
- Custom cookies and headers let you capture authenticated or personalized states.
- Residential proxies route the request through residential IPs when a site restricts datacenter traffic.
- Chrome rendering provides the browser engine used to produce the image.
How credits are consumed
Each screenshot costs 5 credits because JavaScript rendering is required. Credits are valid for one month, and unused credits do not roll over to the next month. Plan sizes are expressed in both screenshots and API credits, so check the screenshot allowance rather than only the credit total when sizing a plan.
A first request
The public cURL example below requests a full-page screenshot of a blog URL. Replace the API key and target URL with your own values. The response is the rendered image; add the HTML option if you also need the markup from the same call.
Choosing a plan
Plans differ in screenshot allowance, API credits, concurrent requests, and support level. Standard plans cover Hobby through Business +; Enterprise plans add higher concurrency and dedicated account management. The figures shown in the plan table are a dated captured reference, so confirm current pricing and allowances before committing.
Telling failures apart
When a capture looks wrong, the cause usually falls into one of four categories:
- Blocked page: the site refused the request, often visible as a challenge or error page in the image. Try residential proxies or adjusted headers.
- JavaScript not executed: dynamic content is missing because the script did not run or finished after the capture. Add or adjust custom JavaScript and allow time for it.
- Wrong viewport: the layout looks like a different device because the viewport was not set as intended.
- Truncated full page: the image stops early because full-page rendering was not enabled or the page grew after capture.
Checking which category applies first saves time before changing unrelated settings.
| Control | What it changes | When to use it |
|---|---|---|
| Full page rendering | Captures the entire scrollable page | Archiving or reviewing long pages |
| Custom viewport | Sets render width and height | Testing responsive layouts |
| Custom JavaScript | Runs script before capture | Dismissing banners, loading lazy content |
| Custom cookies and headers | Sends session or personalization data | Authenticated or localized captures |
| Residential proxies | Routes through residential IPs | Sites that restrict datacenter traffic |
| HTML + screenshot | Returns markup and image together | When you need both visual and parsed output |
Capability descriptions reflect the captured product overview; confirm current option names and behavior in the documentation.
Frequently asked questions
How much does a screenshot cost in credits?
Each screenshot costs 5 credits because JavaScript rendering is required. Credits are valid for one month and do not roll over.
Can I get the HTML and the screenshot in one call?
Yes. The same API call can return both the page HTML and the screenshot image.
Can I capture pages that require login?
Custom cookies and headers let you send session data so authenticated or personalized pages can be captured.
What if a site blocks the capture?
Residential proxies route the request through residential IPs, which can help with sites that restrict datacenter traffic. Adjusting headers may also help.
curl "{{APP_BASE_URL}}/api/v1?\
api_key=API_KEY&url=https://finescrape.com/blog&\
screenshot_full_page=True"