PagePixels vs Thum.io: Which Screenshot API Is Better in 2026?

Short answer: ScreenshotNeo is the first service to evaluate when you want clean website screenshots, predictable billing, and an API that also works with AI agents. Between the two products in this comparison, PagePixels is the better fit to investigate for recurring monitoring and multi-step browser workflows. Thum.io is the simpler candidate for URL-to-image requests, resizing, cropping, and its documented streamed initial-render behavior. No source in the reviewed material establishes a winner for speed, uptime, accuracy, or reliability.

That distinction matters because “better” depends on the job. A scheduled visual regression workflow has different requirements from a thumbnail endpoint. This guide compares the published capabilities and pricing models, shows how to choose without relying on unverified benchmarks, and explains where ScreenshotNeo fits.

Comparison at a glance

Need	First service to evaluate	Why
Clean screenshots with consent banners and widgets removed	ScreenshotNeo	It accepts consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture. Only clean shots are billed.
Scheduled monitoring, alerts, and multi-step browser actions	PagePixels	Its published product and API pages describe schedules, login steps, clicks, form filling, selector waits, change notifications, integrations, location capture, and AI analysis.
Simple URL screenshot or embed image	Thum.io	Its public pages focus on a URL API, streamed initial rendering, resizing, cropping, cache age, and image formats.
AI agents using MCP	ScreenshotNeo	An MCP server exposes `take_screenshot`, `get_page_info`, and `capture_pdf` for Claude, Cursor, and other MCP clients.
Lowest paid entry among the services with stated plans here	ScreenshotNeo	Starter is $5 for 3,000 shots. Its free plan includes 1,000 shots per month without a card.

What PagePixels documents

PagePixels presents itself as a capture and monitoring workflow available through a web app, Screenshot API, or AI assistant. Its product page lists instant and scheduled captures. The documented browser actions include logging in, clicking, filling forms, and waiting for elements. It also lists location capture through a proxy network, change notifications, integrations, and AI analysis. The Screenshot API documentation describes quick snaps, scheduled screenshots, multi-step browser interactions, location capture, custom HTML, AI analysis, and NPM, Python, and Ruby packages. These are vendor-documented capabilities; they are not independent confirmation that every workflow succeeds on every site.

PagePixels is therefore a candidate when the screenshot is one step in a larger process. For example, a monitoring job might open a page, authenticate, click a tab, wait for a chart, capture from a selected location, compare the result, and send a notification. Before committing, test the exact login flow, selectors, redirects, and geographic requirements on a representative site.

PagePixels pricing model

The PagePixels pricing page lists 25 free screenshots per month. The displayed paid plans include 3,000 screenshots for $16.99 per month, 10,000 for $24.99, 15,000 for $49.99, 30,000 for $59.99, 50,000 for $99.99, 70,000 for $139.99, 100,000 for $199.99, and 200,000 for $399.99. It also lists separately metered AI analysis credits at $9.99 per 1,000, real-location bandwidth at $20 per 2 GB, and domain-research credits at $25 per 125 credits. The vendor says every feature is on every plan.

These are live-page terms accessed on September 29, 2026. Recheck the pricing page before purchase. Calculate the total using your screenshot count plus any AI, location-bandwidth, or research usage rather than comparing only the headline screenshot allowance.

What Thum.io documents

Thum.io’s homepage describes real-time website screenshots. It says the service streams an initial render as an animated GIF followed by ongoing render updates. The same page describes resizing and cropping, full-page capture, mobile emulation, PDF-to-image conversion, and image processing. The URL API documentation lists modifiers for width, crop height, maximum cache age, JPG, PNG, and device emulation.

That makes Thum.io worth evaluating for a straightforward URL-to-image integration, especially when an application needs a particular width, crop, format, or cache policy. The published material does not establish feature parity with PagePixels’ schedules, login actions, alerts, integrations, or AI analysis. It also does not provide a matched benchmark proving that streamed rendering is faster for your pages.

Thum.io pricing model

Thum.io’s homepage lists up to 1,000 impressions per month free without signup. The displayed “Good” tier is $2 per 10,000 website screenshot hits with a $1 monthly minimum. The “Better” tier is $1 per 10,000 hits with a $20 monthly minimum and lists unbranded loader options, queue priority, adjustable viewport width, and full-page screenshots. An enterprise plan is also mentioned.

“Impressions” and “hits” are not automatically equivalent to PagePixels’ “screenshots.” Confirm the current definitions, minimums, cache treatment, and eligibility on Thum.io’s live page. A low unit price can still produce a different monthly bill if your traffic, cache behavior, or minimum charge differs from the assumptions in a spreadsheet.

Feature-by-feature decision guide

One-off capture versus recurring monitoring

For an occasional URL screenshot, begin with the smallest API that meets your output needs. Thum.io’s documented URL modifiers are relevant when width, crop height, format, cache age, or device emulation are the main variables. PagePixels becomes more relevant when captures must run on a schedule, perform browser actions, or generate alerts and integrations.

Choose a URL endpoint or a workflow platform according to the steps your capture requires.

Authentication, clicks, and dynamic pages

A static marketing page is easy to describe as URL in, image out. Authenticated dashboards and applications are different: you may need a login sequence, a click, a selector wait, or a delay for client-side rendering. PagePixels explicitly documents multi-step actions and selector waits. Test redirects, two-factor authentication, cross-origin frames, and elements that appear only after a user action. Do not assume a listed capability handles your site’s security controls without a trial.

Location and device requirements

PagePixels documents location capture through a proxy network. Thum.io documents device emulation, while ScreenshotNeo supports 12 device presets and arbitrary viewports, timezone, and geolocation. For any location-sensitive page, specify the country or region, timezone, language headers, and viewport you need, then compare the rendered result with a browser session from the same conditions.

Output control

Thum.io documents JPG and PNG output, width, crop height, and full-page capture. PagePixels describes screenshot workflows and custom HTML, but the reviewed dossier does not enumerate a complete output-parameter list. ScreenshotNeo supports PNG, JPEG, WebP, PDF, full-page capture with lazy images loaded, one-element capture by CSS selector, retina scale, image resizing, transparent backgrounds, custom CSS, and JavaScript.

Alerts and integrations

PagePixels explicitly lists change notifications and integrations. If you need a visual-change pipeline, define the comparison policy first: which pages, how often, what viewport, what dynamic regions to mask, and what constitutes a meaningful change. Thum.io’s reviewed pages focus on capture and image processing rather than a documented monitoring workflow.

How to compare them fairly

Define the workload. Record URL count, captures per day, required viewport and location, authentication steps, output format, and retention period.
Separate listed features from measured behavior. A vendor page can establish that a feature is offered. It cannot establish your page’s latency, success rate, or visual accuracy.
Use the same pages and conditions. Keep URLs, viewport, device emulation, cache state, location, and wait rules constant.
Measure the outcomes you actually need. Track time to usable image, failed loads, blank pages, incorrect login state, missing lazy images, and unwanted overlays.
Model the complete bill. Include free quotas, minimum monthly charges, cache rules, screenshot or hit definitions, location bandwidth, AI credits, and research credits.
Retest difficult pages. Include consent banners, cookie-dependent content, heavy JavaScript, bot checks, authenticated routes, and pages with animations.

The reviewed research contains no independent head-to-head benchmark. A claim that one service is faster, more reliable, or more accurate would require a transparent matched test with repeated captures and published failure criteria.

Or skip the browser setup

ScreenshotNeo provides a one-request website screenshot API and an MCP server. Before capture, it accepts the cookie or consent banner like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets. Each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing; response headers identify the page verdict and whether the request was billed.

Here is a complete cURL request. See the ScreenshotNeo documentation for the full option list.

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

Python

import requests

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

Node.js

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://stripe.com'
});

const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
const data = Buffer.from(await res.arrayBuffer());
require('fs').writeFileSync('shot.webp', data);

Options to plan for

Capture the full page, including lazy-loaded images, or capture one element with a CSS selector.
Choose dark mode, a device preset, any viewport, and retina scale.
Return PNG, JPEG, WebP, or PDF. PDF supports paper size, margins, landscape mode, and page ranges.
Render supplied HTML/CSS, inject custom CSS or JavaScript, click an element, hide selectors, or wait for a selector, delay, or network idle.
Block ads, trackers, requests, or resource types. Supply custom headers, cookies, a user agent, or an Authorization header.
Set timezone and geolocation, use a transparent background, resize the image, or cache with a TTL you choose.
Use signed links for public <img> tags, asynchronous jobs with signed webhooks, bulk capture for up to 100 URLs per call, the usage API, and the OpenAPI specification.

The same parameter names used by other screenshot APIs work with ScreenshotNeo, which can reduce migration effort. Its MCP server exposes take_screenshot, get_page_info, and capture_pdf to Claude, Cursor, and other MCP clients.

Plans: Free includes 1,000 shots per month with no card. Starter is $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan. Create a free ScreenshotNeo account.

Troubleshooting checklist

The image is blank

Likely causes: the page timed out, JavaScript failed, a bot check blocked the browser, or the capture happened before content rendered. Increase the wait rule, wait for a stable selector or network idle, and inspect the response verdict headers. With ScreenshotNeo, blank pages, failed loads, timeouts, and bot checks are not billed.

A screenshot service can clean overlays before returning the captured page.

Check whether the service supports consent handling and selector hiding. Add a hide selector or custom script when the overlay is site-specific. ScreenshotNeo accepts consent banners and removes known consent platforms, newsletter popups, and chat widgets before the shot; individual steps can be disabled when they are not wanted.

Lazy images are missing

Use full-page capture with lazy-image loading where available. Otherwise scroll or trigger the page’s loading behavior with a browser action, then wait for the image selector. Compare a cold capture with a warm cached capture.

Verify cookies, Authorization headers, user-agent requirements, redirects, and the exact login sequence. A selector wait should target an element that exists only after authentication. Avoid putting long-lived credentials in URLs; use the service’s header or cookie options and rotate secrets.

The bill is higher than expected

Check whether the provider bills screenshots, hits, impressions, cache misses, or workflow steps. Recalculate with monthly minimums and metered add-ons. PagePixels lists separate AI, real-location bandwidth, and domain-research charges. Thum.io lists minimum charges on its displayed paid tiers. ScreenshotNeo identifies billing in response headers and does not bill failed loads, blank pages, bot checks, or cache hits.

Results differ by region or device

Fix viewport, device emulation, timezone, geolocation, language, and user-agent settings. Record these values with each capture. Dynamic ads, experiments, consent state, and geo-targeted content can still produce legitimate differences.

Performance, reliability, and cost notes

Do not choose from marketing speed language alone. Thum.io promotes streamed initial rendering, but the dossier contains no controlled timing comparison. Run repeated captures against the same URLs and report median and tail times, failure rate, and the percentage of images that contain the expected content. Include cache state and location in the test record.

For reliability, treat a screenshot as a pipeline: DNS, connection, browser startup, page scripts, authentication, waits, resource loading, and image encoding can each fail. Add retries with backoff for transient network errors, enforce a client timeout, store the provider’s verdict headers, and keep the source URL and capture settings alongside the image.

For cost, multiply expected requests by the provider’s billable unit, then add minimums and extras. A cached response may be free for one service and billable for another. ScreenshotNeo’s cache hits and failed captures are free, and its usage API helps reconcile consumption. PagePixels and Thum.io use different terms, so their displayed unit prices cannot be compared directly without your workload.

FAQ

Is PagePixels or Thum.io better for every project?

No. PagePixels’ published workflow is broader for schedules, interactions, alerts, integrations, and location capture. Thum.io is oriented toward URL screenshots and image processing. Test the pages and billing conditions that matter to you.

Which one has the better free allowance?

The published figures are different units: PagePixels lists 25 free screenshots per month, while Thum.io lists up to 1,000 free impressions monthly without signup. Confirm current definitions before comparing them. ScreenshotNeo offers 1,000 free shots per month with no card.

Can I use these APIs for authenticated dashboards?

Investigate the documented login and interaction support, then test your exact flow. PagePixels explicitly documents login and multi-step actions. Any provider may encounter redirects, two-factor authentication, bot checks, or application-specific scripts.

Is there a proven speed winner?

No. The reviewed sources do not contain a matched benchmark. Claims about speed or reliability should be based on your own repeated test with identical conditions.

When should I try ScreenshotNeo?

Try it first when clean captures, transparent billing for failed pages, PDF output, extensive capture controls, or MCP access for AI agents are requirements. The free plan lets you evaluate 1,000 shots per month without a card.