How to Capture a Full-Page Screenshot with Thumbalizr

To capture a full-page screenshot with Thumbalizr, set the capture size to page. Thumbalizr’s demo lists full-page capture for Silver and higher memberships; its free membership is screen-size only. For API use, the documented parameter table names the option size, with page and screen as values. Check Thumbalizr’s current documentation and plan page before using the service, since plan details can change.

What “full page” means

A screen-size capture covers the browser’s visible viewport. A page-size capture extends beyond that viewport to include the page below it. Thumbalizr documents size=page for the latter. The capture is still rendered at a browser viewport width: setting a wider or narrower viewport can change responsive layout and therefore the resulting image.

Capture a full page in Thumbalizr

1. Open Thumbalizr’s demo or interface and provide the URL of the page to capture.
2. Choose page-size or full-page capture if the interface offers the setting. The documented demo says this requires Silver membership or higher; free membership is screen-size only.
3. For API use, set size=page. Set the browser width and height if you need a particular viewport; these dimensions control the browser viewport, not the total height of the captured page.
4. If the page needs time to render after load, use the documented delay setting where your plan allows it. Check the current API documentation for the parameter syntax and limits for your account.
5. Inspect the result and, for API requests, check the response status and error headers if the capture is queued or fails.

The official materials describe the workflow and settings but do not enumerate a stable sequence of current interface button names, so follow the labels shown in the live demo.

Use Thumbalizr’s API

The API documentation’s parameter table specifies size with page or screen. It also describes browser width and height controls and a delay after page load. Encode the target URL as a query parameter; nested URLs contain characters that must be percent-encoded.

curl -G "THUMBALIZR_API_ENDPOINT" \\
  --data-urlencode "url=https://example.com/article?ref=docs&view=full" \\
  --data-urlencode "size=page" \\
  --data-urlencode "width=1365" \\
  --data-urlencode "height=900"

Replace the endpoint and any authentication parameters with the values specified in Thumbalizr’s current API documentation. The dossier does not provide a verified endpoint, authentication scheme, or complete request syntax, so those details should not be guessed. The API documentation’s example uses mode=page, while its parameter table identifies size; use the current parameter table and avoid mixing legacy API syntax with the newer Embed API.

Choose the right capture settings

Need	Setting or consideration
Only the visible browser area	size=screen
The page beyond the viewport	size=page; the demo lists Silver tier and above
Match a desktop or mobile layout	Set browser width and height to the viewport dimensions you want. Responsive pages may render different layouts at different widths.
Wait for delayed content	Use the documented post-load delay if available on your tier. Confirm the current defaults and limits in the API documentation.
Integrate into an application	Use the documented API or recommended Embed API. Keep their parameter conventions separate.

Full-page capture and viewport size solve different problems: the viewport determines how the page is laid out, while page size determines whether content beyond the visible screen is included.

Common problems and fixes

Symptom	Likely cause	What to do
The image stops at the visible screen	The request used screen-size capture, omitted the size setting, or used syntax from a different API version.	Use the current API parameter table and set size=page. Confirm that the selected membership supports full-page capture.
The full-page option is unavailable	The demo lists free membership as screen-only.	Check Thumbalizr’s current plan details; Silver and higher are documented as supporting page-size capture.
The capture has the wrong layout	The browser viewport dimensions differ from the intended device width.	Set the documented width and height controls to the target viewport and capture again.
Images or content appear before they are ready	The page renders content asynchronously or after initial load.	Use the documented delay option where available and tune it to the page. Verify current tier limits rather than assuming an unlimited wait.
The API reports a queued job	The capture has not completed yet.	Check the documented status header. Thumbalizr lists QUEUED, OK, and FAILED; handle queued work according to the API instructions.
The API reports failure	The capture did not complete; the response may include an error header.	Inspect the documented error header, verify the URL and request parameters, then retry only after correcting the reported issue.

Reliability, performance, and cost

Large or long pages naturally require more rendering and produce larger image files than a viewport-only capture. Choose the smallest viewport width that faithfully represents the page, and use a delay only when the target needs extra rendering time. These choices can reduce unnecessary capture work, though Thumbalizr’s cited documentation does not provide benchmark figures.

For integrations, treat the API status as part of the workflow: distinguish queued, successful, and failed captures, and use the documented error header to diagnose failures. Avoid assuming that a request is complete merely because it was accepted.

Thumbalizr’s free demo membership is documented as screen-size only, while Silver and higher support full-page capture. Plan quotas and prices can change; check the live Thumbalizr features and pricing page before choosing a tier. No price is repeated here because the research materials flag those figures as volatile.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Make one GET request with the target URL to receive an image or PDF; its API documentation covers the request options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, and failed loads are never billed; responses identify outcomes in headers. Its MCP server gives AI agents tools to take screenshots, inspect page information, and capture PDFs. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for 1,000 free screenshots a month, with no card.

FAQ

Can Thumbalizr’s free membership capture a full page?

The documented demo describes free membership as screen-size only. Full-page capture is listed for Silver and higher.

Should I use size=page or mode=page?

The API parameter table names size and gives page as a value. The docs’ example also shows mode=page; use the current parameter table for the API version you are integrating and do not combine legacy and Embed API syntax.

Does browser height set the final screenshot height?

The documentation describes browser width and height as viewport dimensions. The capture extent is controlled separately by the screen or page size setting.

Sources

• Thumbalizr demo and membership information
• Thumbalizr API documentation
• Thumbalizr features and plans