How to Capture a Full Page Website Screenshot Online or via API

To capture a full page website screenshot, you can either use a browser-based tool (paste the URL, pick a viewport, choose a format, and let it scroll the whole page into one image) or send a single request to a screenshot API when you need automation. Site-Shot offers both paths from the same Chromium engine: the online tool needs no signup or API key, while the API requires an account and email confirmation to get a key. The main constraints to plan around are height limits — full-page captures go up to 20,000 px, except WebP, which stops at 16,383 px.

Option 1: Capture a full page in the browser (no signup)

This is the fastest route for one-off screenshots. Everything runs in your browser, and per the site's own description there is no signup, no API key, and no credit card required.

1. Enter the target URL in the online tool.
2. Choose the capture mode — select the full-size / full-page option so the tool scrolls the entire page rather than grabbing only the visible viewport.
3. Set the viewport to match how you want the page to render (see the device table below).
4. Pick an output format: PNG, JPEG, or WebP.
5. Apply cleanup options if the page is cluttered — the tool can remove ads and cookie banners so they don't cover your capture.
6. Generate the screenshot and download the resulting image.

Expected result: one tall image containing the whole page, not just the top screen.

Viewport and device presets

The tool exposes both custom dimensions and named device emulation. Matching the viewport to the real audience matters, because responsive layouts change what a "full page" even looks like.

You can also set width, height, and zoom manually if none of the presets fit.

Format and height limits: the part that causes truncation

The most common "my screenshot is cut off" problem comes from format limits, not from the tool failing.

Practical rule: if the page is very long and you need WebP, expect the bottom to be dropped past 16,383 px. Switch to PNG or JPEG if you need the full height, or capture the page in sections.

Option 2: Automate with the screenshot API

Use the API when you need repeatable, batch, or scheduled captures rather than a one-off image.

1. Create an account on the site.
2. Confirm your email — the API key is issued after confirmation.
3. Send a single request with the target URL to capture a full-page screenshot.
4. Add parameters as needed: viewport size, device emulation, output format, proxy/geolocation, and ad or cookie-banner removal.

The API runs on the same Chromium engine as the online tool, so results should be consistent between the two. Code samples and API documentation are available on the site.

When the API is worth it over the browser tool

• You're capturing many URLs on a schedule.
• You need consistent viewports and formats across a set of pages.
• You need localized captures via proxy rotation and geolocation.
• You want clean images without ads or cookie popups at scale.

Getting clean, localized captures

Two features change the quality of the result more than most people expect:

• Ad and cookie-banner removal — without it, a consent dialog can sit on top of the page content in your screenshot, making the capture useless for documentation or comparison.
• Proxy rotation and geolocation — the tool lists a long set of country options (United States, Germany, Japan, Brazil, and many more). A page can serve different content, currency, or language by region, so a capture taken from the wrong location may not match what your users actually see. Note that a subset of countries is available on the free/direct connection, while additional countries require a paid plan.

Troubleshooting common failures

Choosing between the two paths

Use the online tool for one-off screenshots, quick checks, or when you don't want to create an account. Use the API when the capture needs to be automated, repeated, or run at scale with consistent settings. Both share the same engine and the same height and format limits, so the decision is about workflow, not image quality.