Do screenshot APIs charge extra for PDF output or large images?

Short answer: sometimes, but there is no universal surcharge rule. In the provider pricing pages reviewed for this guide, PDF output is included in some screenshot allowances and limited to paid plans by another provider. Those pages do not list a general extra charge based only on image dimensions. That does not guarantee every provider treats full-page captures, high-DPI output, unusually large images, or enterprise workloads the same way.

Before you estimate cost, check two separate things: whether PDF is available on your plan, and what the provider counts as a billable unit. A format can be plan-gated without having a separate per-PDF fee.

1. What the reviewed pricing pages say

These are examples from provider-published pages reviewed in 2026, not a complete market survey. Prices, allowances, and features can change; verify the current pricing and terms before choosing a plan.

Provider	PDF and formats	Published billing details	What this tells you
ScreenshotNeo	PNG, JPEG, WebP, or PDF; all features are available on every plan.	Free: 1,000 shots/month. Paid plans start at $5 for 3,000 shots.	PDF is available across plans. Only clean shots are billed; bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing.
ScreenshotAPI.to	PNG, JPEG, WebP, and PDF are listed in the free allowance.	200/month free. Listed examples: Starter $19/month for 5,000 screenshots, with $0.006 per screenshot over allowance; Growth $49/month for 25,000, with $0.004 overage. One credit is defined as one screenshot.	The listed plan includes PDF among supported output formats. Its page says cached responses do not count against the monthly allowance.
ScreenshotCenter	PNG, JPEG, and WebP appear in the 500-capture free trial; PDF rendering is listed on Starter.	Starter is listed at $15/month for 2,000 screenshots.	PDF can be a plan-tier difference even when a separate per-PDF fee is not stated.
ScreenshotEngine	HTML-to-PDF export and PNG/JPEG/WebP are listed across plans.	Its comparison lists 50 screenshots on Free and 3,000 on Starter. Plans differ by volume, rate limit, and support.	Its pricing page says rendering capabilities are the same across plans; dimensions are capture parameters with documented bounds, not a listed per-dimension charge.
ScreenshotCore	PDF generation is included in its format comparison.	Plan overage rates are listed; no separate PDF surcharge is specified on the comparison page.	PDF is listed as a capture format, but confirm the current unit and overage terms.
ScreenshotAPI.com	Its pricing page lists PNG, JPG, and GIF; it does not establish PDF availability.	Metered billing is described per shot, and a successful image capture counts as a screenshot.	Do not infer PDF support or PDF pricing from that pricing page.

Sources: ScreenshotAPI.to pricing, ScreenshotCenter pricing, ScreenshotEngine pricing and its parameter reference, ScreenshotCore pricing, and ScreenshotAPI.com pricing. Provider terms and exact page URLs can change; check each provider’s current official pricing and documentation.

2. Why PDF may cost more without a per-PDF surcharge

Pricing pages often combine feature availability and usage billing, but they answer different questions:

Availability: Is PDF output enabled on your plan, or do you need to upgrade?
Usage unit: Does one PDF count as one render, one screenshot credit, multiple pages, or another unit?
Allowance: Is the output covered by the monthly quota or a separate credit pool?
Overage: What happens when the allowance runs out: per-unit billing, a hard limit, or a plan change?

A plan that includes PDF can still charge usage once you exceed its allowance. A plan that gates PDF may charge for the higher plan rather than add a fee to each PDF. Do not assume that a multi-page PDF counts as one unit—or that each page counts separately—unless the provider defines it.

3. Do large images or high resolution cost extra?

The reviewed pages and documentation do not establish a general surcharge based on width, height, or pixel count. Some expose image dimensions as capture parameters and state permitted bounds, but that is not the same as promising that every size is included at the same price.

Large captures can still matter operationally even where no dimension-based fee is listed. They can take longer to render and transfer, use more memory, produce larger files, or hit a provider’s parameter and timeout limits. Full-page and high-DPI captures may also be governed by separate plan limits or billing definitions that are not visible in a short pricing comparison.

For an exact cost, ask the provider whether a full-page or high-DPI image consumes the same unit as a viewport capture, whether dimensions have maximums, and whether output pages affect PDF billing.

4. A practical checklist for estimating your bill

Confirm the needed format. Find PDF in the plan’s feature list and documentation. If it is absent, treat availability as unconfirmed.
Identify the billable event. Look for wording such as successful render, screenshot, page, file, or API request.
Check image limits. Verify maximum viewport width and height, full-page constraints, pixel or file-size caps, and retina/high-DPI behavior.
Read failure and cache rules. Check whether failed loads, bot checks, timeouts, retries, and cached results consume quota.
Calculate expected use. Estimate successful captures per month, include retries if they are billable, then compare allowance and overage rates.
Check batch semantics. For bulk or multi-page output, confirm whether billing is per request, URL, image, or page.
Recheck before production. Pricing pages can change, and enterprise or negotiated terms may differ from public plans.

5. Cost examples and how to compare them

Suppose a service defines one successful image capture as one screenshot and includes 5,000 per month. Your initial estimate is successful captures minus the included allowance, multiplied by the stated overage price. This arithmetic is only valid if the provider confirms that your PDF or large image consumes the same unit.

estimated_overage = max(0, billable_units - included_units) * overage_price

For the ScreenshotAPI.to figures listed above, 1,000 units beyond the 5,000 Starter allowance at the stated $0.006 rate would be $6 in overage, if those units qualify under the provider’s current definition. That example does not establish how another provider bills PDFs, large images, or failed requests.

Compare total expected monthly cost, not just the headline plan price. Include the included quota, overage rate, format availability, failure billing, cache behavior, rate limits, and any required higher-tier plan.

6. Troubleshooting billing surprises

PDF requests are rejected on a free plan

Likely cause: PDF is a plan-gated feature. Fix: check the provider’s format matrix and upgrade only if PDF is required and the plan terms fit your workload.

The invoice is higher than the plan price

Likely cause: usage exceeded the allowance, retries counted as separate requests, or your billing unit differs from your assumption. Fix: compare usage records to the provider’s definition of a billable unit and overage rate.

A large capture fails or times out

Likely cause: dimensions exceed documented bounds, the page is unusually long, or rendering exceeds the timeout. Fix: reduce viewport or scale, capture a specific element, split work where appropriate, and use the documented timeout and size limits. Confirm whether a failed attempt is billable.

PDF page count changes between runs

Likely cause: print layout, page size, margins, fonts, or dynamic content changed. Fix: set paper size, margins, orientation, and a deterministic wait condition; compare the rendered output before treating page count as a stable billing estimate.

Cached requests appear differently in usage

Likely cause: providers define cache billing differently. ScreenshotAPI.to says cached responses do not count against its monthly allowance, but that rule should not be generalized. Fix: check the specific provider’s cache and billing terms.

7. Performance, reliability, and cost controls

Use the smallest sufficient output. Avoid unnecessarily large viewports and retina scale when the downstream use does not need them.
Choose a stable wait condition. Waiting for a relevant selector can be more predictable than a long fixed delay; dynamic pages may still require a timeout policy.
Cache repeat work when appropriate. A configurable cache can reduce duplicate rendering, but verify how cache hits affect both freshness and billing.
Make retries bounded. Retry transient network failures with a limit and backoff; otherwise retries can increase latency and possibly billable usage.
Track response status and usage metadata. Distinguish successful output from blocked pages, timeouts, and other failures where the API exposes that information.
Budget for the production shape. Test representative long pages, image-heavy pages, and PDF layouts; a simple viewport capture may not predict their time or size.

8. Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. One GET request can return a PNG, JPEG, WebP, or PDF. Its PDF and capture features are available on every plan, and only clean shots are billed: bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. Cookie/consent banners, newsletter popups, and chat widgets are handled before capture. AI agents can use its MCP server with tools including take_screenshot, get_page_info, and capture_pdf. See the API documentation for parameters and setup.

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}`);

Those examples use the documented endpoint and request shape; set the desired output and other capture parameters according to the docs. ScreenshotNeo includes 1,000 shots per month free with no card. Paid plans start at $5 for 3,000 shots, and every feature is on every plan. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed; an MCP server lets AI agents take screenshots. Sign up for 1,000 free screenshots a month, with no card required.

9. Frequently asked questions

Does a PDF always count as one screenshot?

No universal rule is established by the reviewed pages. Check whether the provider bills per request, output file, screenshot, or page.

Are larger screenshots always more expensive?

The reviewed sources do not list a general dimension surcharge. They also do not establish that every provider accepts every size at the same cost or within the same limits.

Can an API charge more for PDF without listing a PDF fee?

Yes. PDF may require a higher plan, which raises the plan cost without a separate per-file surcharge.

Are failed captures usually free?

Billing rules vary. Read the provider’s definitions for failed loads, timeouts, bot checks, retries, and cached results.

Should I choose a provider based on the lowest monthly price?

Compare the plan’s included units, PDF availability, overage, failure billing, limits, and the size and frequency of your real workload.