Thum.io Alternative: A Screenshot API Built for Automation

If you landed here, you probably already have a Thum.io integration running somewhere, an <img> tag pointing at image.thum.io, maybe a prefetch job queuing up thumbnails in the background. It works, until the project needs something Thum.io was never built to do: a real PDF, a scheduled capture, structured data alongside the image, or ad-free output without writing your own blocking rules.

This isn't a takedown of Thum.io. It's a genuinely fast way to drop a live thumbnail into a page, and for that one job it's hard to beat. But "screenshot as a thumbnail" and "screenshot as infrastructure" are different problems, and a lot of teams outgrow the first one fast.

Here's what Thum.io actually does well, where it stops, and what a more complete API like ScreenshotAPI.net adds when your use case grows past a simple <img> embed.

Why Look for a Thum.io Alternative?

Most teams start searching for a Thum.io alternative for one of a few reasons:

• They need a real PDF of a webpage, not just an image, for invoices, reports, or archiving.
• They need scheduled or bulk captures instead of one-off requests triggered by an <img> tag. Thum.io's model is built around streaming an animated initial render so users see content fast, rather than waiting for a fully loaded, final screenshot. That's a smart trade-off for embedded thumbnails on a page people are actively browsing. It's a poor fit when your code needs a finished PNG or PDF the moment the request returns, which is exactly the case in CI pipelines, scheduled jobs, and server-side automation.
• They've hit the plan wall. Full page capture, custom viewport width, device emulation, and even the wait parameter are all gated behind Thum.io's paid "Better" plan, so testing these features means committing to a paid tier first.
• They need ad and cookie-banner blocking without maintaining their own rule list, since Thum.io's documented options don't include a built-in ad or consent-banner blocker.
• They want one API for screenshots, PDFs, scrolling video, and data extraction instead of stitching several tools together.

None of this makes Thum.io a bad product. It makes it a specialized one. If your entire need is "show a live-updating thumbnail on a page," it's a reasonable, cheap choice. If your need is "automate visual capture as part of a product or workflow," you'll likely need more.

What Does Thum.io Actually Offer?

To keep the comparison honest, here's what Thum.io's documented API actually supports, based on its public API documentation.

Thum.io's URL API takes modifier options as path segments before the target URL, covering things like width, crop height, cache max age, JPG or PNG output, and disabling the streaming animation for batch jobs. Full page capture, a configurable wait delay for animations or async content, custom viewport width up to 2400px, and device emulation presets (iPhone, Galaxy S5) are all restricted to paid "Better" plan accounts.

Beyond website screenshots, Thum.io also offers a separate image-resizing endpoint and a PDF-to-image converter that turns an existing PDF file into an image of a given page, which is different from rendering a live webpage as a downloadable PDF. For high-volume use, Thum.io supports a prefetch queue: you request an image ahead of time, poll or wait for a callback, then fetch the final file once it's cached.

Pricing starts at 1,000 free screenshot hits, then $2 per 10,000 hits on the "Good" plan with a $1 monthly minimum, or $1 per 10,000 hits on the "Better" plan with a $20 monthly minimum that unlocks the features listed above. There's also an Enterprise plan available by contacting Thum.io's sales team directly.

What you won't find in the documented API: built-in ad or cookie-banner blocking, scheduled/cron captures, bulk CSV or JSON upload, scrolling video output, direct HTML or text extraction from the page, or delivery straight to your own cloud storage bucket. If your workflow needs any of those, you're either building it yourself or looking elsewhere.

What Makes ScreenshotAPI.net Different?

ScreenshotAPI.net takes a different approach: one endpoint, one authenticated request, and the finished output, whether that's an image, a PDF, a scrolling video, or extracted page text, returned in a single call.

A few of the pieces that matter most if you're coming from Thum.io:

Real Chromium rendering, every plan. Every screenshot runs in a full, isolated Chromium instance, the same rendering engine behind Google Chrome, so React, Vue, Angular, and Next.js apps render correctly without waiting for a streamed placeholder first.

Full page and viewport capture aren't locked behind a paid tier. You can capture a full page or viewport screenshot on the free plan by setting full_page=true, and the full-page capture documentation covers how it automatically scrolls through lazy-loaded and infinite-scroll content before capturing.

Built-in ad and cookie-banner blocking. Setting block_ads=true and no_cookie_banners=true strips ads, GDPR consent pop-ups, and tracking scripts using a rule set of over 20,000 entries.

A real webpage-to-PDF converter. The file_type=pdf parameter saves a live URL as a clean, ad-free PDF with layout and fonts preserved, useful for invoices, compliance archiving, and reports, not just converting an existing PDF file.

Scheduling, bulk, and cloud storage. Cron-based scheduled captures and a bulk screenshot endpoint for CSV or JSON URL lists both ship as built-in features, and results can be delivered directly to your own S3, Google Cloud, or Wasabi bucket.

Data extraction alongside the image. The extract_text=true and extract_html parameters return the page's readable content in the same request that captures the screenshot and scraped data together.

None of this makes ScreenshotAPI.net the right pick for every use case. If all you need is a lightweight, animated preview thumbnail embedded directly in an <img> tag with minimal setup, Thum.io's simplicity is genuinely appealing. The comparison below should make the trade-offs clear rather than push you toward one answer.

Thum.io vs ScreenshotAPI.net: Feature Comparison

How Do You Migrate from Thum.io to ScreenshotAPI.net?

If you're replacing an existing Thum.io integration, the shift is mostly a matter of swapping the endpoint and parameter names. Here's a side-by-side look.

Thum.io: basic embedded thumbnail

<img src="//image.thum.io/get/width/100/crop/600/http://www.google.com/" />

ScreenshotAPI.net: equivalent capture via REST call

curl "https://shot.screenshotapi.net/screenshot?token=YOUR_API_KEY&url=https://www.google.com&width=100&height=600&output=image&file_type=png"

For a production workflow that needs a full page screenshot with ads and cookie banners stripped, here's a working Node.js example against ScreenshotAPI.net's documented endpoint and parameters:

const fs = require("fs");
const fetch = require("node-fetch");

const token = "YOUR_API_KEY";
const url = encodeURIComponent("https://example.com");

const query =
  `https://shot.screenshotapi.net/v3/screenshot?token=${token}` +
  `&url=${url}` +
  `&output=image` +
  `&file_type=png` +
  `&full_page=true` +
  `&block_ads=true` +
  `&no_cookie_banners=true` +
  `&lazy_load=true`;

const response = await fetch(query);
const buffer = await response.arrayBuffer();
fs.writeFileSync("screenshot.png", Buffer.from(buffer));

And the same request in Python, using file_type=pdf to save the page as a clean PDF instead:

import urllib.request

token = "YOUR_API_KEY"
url = "https://example.com"

query = (
    "https://shot.screenshotapi.net/v3/screenshot"
    f"?token={token}&url={url}&file_type=pdf&full_page=true"
    "&block_ads=true&no_cookie_banners=true"
)

urllib.request.urlretrieve(query, "page.pdf")

If you were relying on Thum.io's maxAge parameter to control caching, the equivalent on ScreenshotAPI.net is the fresh=true flag, which bypasses the cache to force a current screenshot instead of returning a previously stored one.

Which Features Matter Most for Production Use?

Not every project needs every feature. Here's how to think about which ones actually matter for your workflow.

If you're generating link previews or Open Graph images, lazy loading and full page capture matter more than raw speed, since images that load asynchronously or via infinite scroll need to fully render before the capture happens.

If you're archiving pages for compliance or legal purposes, PDF output and delivery to your own storage bucket matter more than animation. A timestamped, ad-free PDF saved directly to a private S3 bucket is a meaningfully different deliverable than a cached thumbnail image.

If you're monitoring competitor pages, scheduled captures and bulk processing save the most engineering time, since you're not writing your own cron jobs or queueing logic on top of a screenshot endpoint. ScreenshotAPI.net's blog covers this pattern in more depth in its guide to analyzing competitors the modern way and its piece on screenshots for SEO and SERP tracking.

If you're running visual regression tests in CI, consistent rendering across environments matters more than anything else. Every capture running in the same Chromium version removes a whole category of "works on my machine" bugs from your test suite.

How Does Pricing Compare?

Thum.io's free tier gives you 1,000 screenshot hits per month without even requiring a signup, which is genuinely convenient for quick prototypes. Paid usage starts at $2 per 10,000 hits on the Good plan, or $1 per 10,000 hits on the Better plan, which carries a $20 monthly minimum and is required for full page capture, custom viewports, and device emulation.

ScreenshotAPI.net's free plan includes 100 screenshots with no credit card required, then scales to $9/month for 1,000 screenshots on the Essential plan or $29/month for 10,000 screenshots with scheduled and bulk capture on the Startup plan. Full page capture, PDF output, and ad blocking are available starting on the free tier rather than gated behind a higher-priced plan.

Which is cheaper depends entirely on volume and which features you actually need turned on. For a simple, high-volume thumbnail with no full page or PDF requirement, Thum.io's per-hit pricing is hard to beat. For a workflow that needs full page capture, PDF export, or scheduling from day one, comparing the effective cost per feature rather than per screenshot gives a more honest picture.

Which One Should You Choose?

If your only requirement is a fast, animated, embeddable thumbnail for a page people are actively browsing, and you don't need PDFs, scheduling, or bulk processing, Thum.io does that one job efficiently and its free tier requires no signup at all.

If you need full page screenshots without a plan upgrade, a real webpage-to-PDF converter, built-in ad and cookie-banner blocking, scheduled or bulk captures, or structured data extracted alongside the image, ScreenshotAPI.net's feature set is built for that broader range of automation work out of the box.

It's also worth comparing more than two options before committing. ScreenshotAPI.net has published honest, feature-by-feature comparisons against other screenshot APIs, including ScreenshotOne and Urlbox, ApiFlash, and a dedicated Urlbox alternative breakdown, which are worth reading alongside this one if you're weighing several providers.

Frequently Asked Questions

Does Thum.io support full page screenshots?

Yes, but only on Thum.io's paid "Better" plan, using the fullpage/ parameter. On the free "Good" tier, full page capture isn't available.

Can Thum.io convert a webpage into a PDF?

Not directly. Thum.io's PDF feature converts an existing PDF file into an image of a specific page, rather than rendering a live URL as a new PDF document. If you need a webpage saved as a PDF, that's a gap Thum.io's documented API doesn't cover.

Is there a free way to test ScreenshotAPI.net before switching from Thum.io?

Yes. The free plan includes 100 screenshots with no credit card required, covering full page capture, ad blocking, and PDF output, so you can test the exact features Thum.io restricts to a paid plan before committing to anything.

How do I block ads and cookie banners automatically in a screenshot?

On ScreenshotAPI.net, add block_ads=true and no_cookie_banners=true to your request, which applies a built-in rule set of more than 20,000 entries. See the block resources documentation for the full list of related parameters, including blocking chat widgets and tracking scripts.