Html2Pdf.app vs PDFShift Pricing for Frequent Website PDF Captures

For frequent website PDF captures, compare the size of the PDFs you generate as well as the number of capture requests. Both Html2Pdf.app and PDFShift describe credit use in 5 MB chunks, so one large document can use several credits. Html2Pdf.app publishes monthly tiers of $9 for 1,000 credits, $25 for 5,000, and $39 for 10,000; its free tier includes 100 credits. PDFShift’s retrieved pricing details confirm 50 free credits, a 15 MB free file cap, and a 30-second free timeout. Its FAQ gives a $24/month Boost example with 2,500 credits and optional $0.03 overage per extra credit. That is not a complete current PDFShift price table, so confirm its live plan selector before choosing.

This comparison is for hosted APIs that convert a public URL or HTML into a PDF. It is not a desktop PDF editor comparison. Pricing and plan limits can change; the details below reflect the official pages checked on October 3, 2026.

Pricing at a glance

Service / plan	Price shown	Credits	Relevant limits and notes
Html2Pdf.app Free	$0/month	100/month	PDF output up to 1 MB; 1 parallel conversion
Html2Pdf.app Startup	$9/month	1,000/month	Unlimited PDF size; 3 parallel conversions
Html2Pdf.app Standard	$25/month	5,000/month	Unlimited PDF size; 10 parallel conversions
Html2Pdf.app Scale	$39/month	10,000/month	Unlimited PDF size; 20 parallel conversions
PDFShift Free	$0/month	50/month	15 MB maximum file size; 30-second timeout
PDFShift Boost example	$24/month	2,500/month	FAQ example; optional overage at $0.03 per extra credit

Html2Pdf.app says each 5 MB chunk of generated PDF costs one credit. PDFShift describes the same 5 MB accounting rule. For example, a 14 MB PDF uses three credits on either service under those published rules. The pricing pages describe monthly credit resets; Html2Pdf.app says its credits reset on the first day of each month.

Sources: Html2Pdf.app pricing, PDFShift pricing, and PDFShift FAQ.

How to estimate the monthly cost

1. Count successful output PDFs. Exclude retries and failures only if the vendor’s billing rules exclude them; verify that detail in current terms rather than assuming it.
2. Measure actual output size. Collect representative PDFs, including long pages, image-heavy pages, and pages with charts. Use the 5 MB chunk rule to estimate credits.
3. Calculate credits per month. A practical estimate is ceil(output_bytes / (5 * 1024 * 1024)) per document, multiplied by the expected monthly document count. Confirm how each vendor rounds at exact boundaries.
4. Add headroom. Account for seasonal peaks, larger-than-usual pages, and any retry behavior in your own application.
5. Compare the appropriate plan and limits. Check maximum output size, parallel conversion limits, timeout, asynchronous behavior, and overage settings as well as the monthly credit count.

Example: if 10,000 captures each produce a 2 MB PDF, the rough estimate is 10,000 credits if each file consumes one credit. If those same captures average 14 MB, the estimate becomes 30,000 credits. This illustration applies the vendors’ stated chunk rules; it is not a performance or billing test.

Html2Pdf.app: published tiers and practical fit

The visible monthly tiers are straightforward to compare by included credits: Free has 100, Startup has 1,000 for $9, Standard has 5,000 for $25, and Scale has 10,000 for $39. The free plan’s 1 MB maximum PDF size can rule it out for larger pages. Paid tiers shown on the pricing page state unlimited PDF size, with parallel conversion allowances of 3, 10, and 20 on Startup, Standard, and Scale respectively.

The documentation describes an authenticated POST API that accepts either a publicly reachable URL or raw HTML and returns PDF binary data. It says the rendering engine is headless Chromium. CSS media selection, available fonts and resources, and JavaScript load timing can affect the result. Those details matter when estimating both output size and whether the rendered document is usable. Read the Html2Pdf.app API documentation for the request format and current options.

The retrieved pricing material does not establish overage terms, timeout values, or annual prices. Check those on the current plan selector or in account terms before using them in a budget.

PDFShift: confirmed details and what to verify

The pricing page confirms a Free allowance of 50 credits, a 15 MB maximum file size, and a 30-second timeout. Its page says generated data is counted in 5 MB chunks. The FAQ describes paid plans with a 100-second default timeout and a standard parallel-conversion limit of 50 at once, subject to custom arrangements. It also gives the Boost example of $24/month for 2,500 credits, with overage disabled by default and optionally enabled at $0.03 per extra credit.

Treat the Boost figures as an FAQ example, not a complete current paid plan table. The retrieved pricing display did not establish the full mapping of paid prices, credit quantities, and file-size limits. Use the live PDFShift pricing page and FAQ to confirm the plan currently available to your account and whether its limits fit your workload.

PDFShift’s developer material describes conversion from HTML or URLs and advertises CSS/JavaScript injection, headers and footers, and asynchronous or parallel processing. These are vendor-described capabilities, not independently measured speed or reliability results. See the PDFShift developer site for current API details.

Which service fits frequent captures?

If your main constraint is…	What to compare
A predictable published monthly tier	Html2Pdf.app lists $9/1,000, $25/5,000, and $39/10,000 credits. Confirm current pricing before purchase.
A larger free file allowance	The retrieved limits show 15 MB for PDFShift Free versus 1 MB for Html2Pdf.app Free. Compare timeout and available credits too.
Many simultaneous conversions	Html2Pdf.app lists plan-specific limits of 1, 3, 10, and 20. PDFShift’s FAQ says 50 concurrent conversions as a standard default; confirm account-specific terms and queue behavior.
Overage control	PDFShift’s FAQ says overage is off by default and gives a $0.03-per-credit Boost example. Html2Pdf.app overage terms were not established in the retrieved material.
Reliable output for a particular site	Render representative pages through each candidate and inspect fonts, CSS media, dynamic content, page breaks, and file size.

There is no supported basis in the retrieved information for declaring PDFShift cheaper overall at a given high volume: its complete current paid tier table is missing. Nor do the listed credit totals alone prove which API will cost less, because the PDF size distribution determines credit use. Make the decision from your measured output sizes and the vendor’s current terms.

Run a fair comparison before committing

1. Choose a representative URL set: short and long pages, image-heavy content, dynamic pages, and pages with the fonts or charts important to your users.
2. Generate PDFs with equivalent page settings and wait behavior. Keep the source content and capture time as similar as possible.
3. Record output size, success or failure, conversion time, and any missing or mispositioned content. This is your own workload data, not a vendor benchmark.
4. Calculate credits from each output PDF using the vendor’s current rounding rule, then multiply by projected volume.
5. Exercise the expected concurrency and retry policy. Observe queueing and timeout behavior without assuming the published maximum guarantees a particular throughput.
6. Check the account’s current price, overage setting, file-size cap, timeout, and monthly reset date before production rollout.

API integration considerations

For either hosted converter, keep API credentials on a server, send URL or HTML using the vendor’s documented request format, and treat the result as binary PDF data. Do not expose a secret key in browser code. Set a client timeout consistent with the service’s server-side timeout, and handle non-success HTTP responses before writing the response body as a PDF.

For frequent jobs, use a queue with bounded concurrency rather than launching an unbounded burst. Make retries selective: retry transient connection failures or server errors with backoff, but do not repeatedly retry a permanent invalid-input response. Store enough metadata to reconcile each requested URL, response status, output size, and resulting credit estimate. Confirm each service’s current authentication, asynchronous job, webhook, and error-response details in its official developer documentation.

Troubleshooting frequent website PDF captures

Symptom	Likely cause	What to do
Request times out	The page takes longer to load or render than the configured/server timeout.	Check whether the page depends on slow scripts or third-party resources; use the service’s documented wait controls and current timeout limits. Avoid assuming a client timeout can extend the provider’s server limit.
PDF is blank or missing dynamic content	Capture happened before JavaScript finished, or required resources were inaccessible.	Verify the URL is publicly reachable from the service, inspect script and network dependencies, and configure a supported wait strategy.
Fonts or layout differ from the browser	Fonts/resources did not load, or print CSS/media rules changed the page.	Check external resource access and CSS media behavior. Html2Pdf.app specifically notes media selection and resource availability can affect rendering.
File exceeds a plan limit	Long or image-heavy pages produce larger PDFs than expected.	Measure output size, reduce unnecessary page content or image weight where possible, and verify the chosen plan’s file-size cap. Remember that size can also increase credits.
Credits run out sooner than request count suggests	Large files consume multiple 5 MB credits.	Recalculate from the size distribution, including long-tail large documents, and confirm boundary rounding and any retry billing rules with the provider.
Jobs queue or are rejected under load	Concurrency exceeds the plan or account limit.	Bound parallel work to the account allowance, queue excess jobs, and verify the current limit with the provider.
Unexpected overage charge	Overage may be enabled, or estimated credits were too low.	Review account overage settings and compare actual output sizes and usage logs with the estimate. PDFShift’s FAQ says its overage is disabled by default, but check the account setting directly.

Reliability, performance, and cost controls

• Reliability: Keep a record of each capture attempt and its outcome. Use bounded retries with exponential backoff for transient failures, and route persistently failing pages for review rather than retrying indefinitely.
• Performance: Parallel limits are ceilings or account settings, not proof of end-to-end throughput. Measure your page mix and tune concurrency to avoid timeouts and queue buildup.
• Cost: Monitor output bytes as well as job count. Alert before credit exhaustion, and separately watch larger PDFs that cross additional 5 MB boundaries.
• Budget predictability: Check whether overage is available and how it is configured; do not rely on an example price as a promise for another plan.
• Rendering fidelity: Recheck pages after major site changes, especially changes to print CSS, fonts, client-side rendering, and third-party assets.

ScreenshotNeo as an alternative to try first

If your requirement is a website screenshot as an image rather than a full PDF conversion, try ScreenshotNeo first. It is a website screenshot API and MCP server from Yorker Media. Its API returns PNG, JPEG, WebP, or PDF, and it offers full-page capture with lazy images loaded. For website captures, cookie and consent banners are accepted and 60+ known consent platforms, newsletter popups, and chat widgets are removed before the shot; each step can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, with the page verdict and billing status indicated in response headers. Its MCP tools let Claude, Cursor, or another MCP client take screenshots, get page information, and capture PDFs.

It is not a like-for-like substitute if your workflow depends on an HTML-to-PDF API feature such as a particular document conversion option; check the ScreenshotNeo documentation against your requirements. ScreenshotNeo pricing is Free for 1,000 shots/month with no card, Starter $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.

Or skip the browser 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}`);

See the API documentation for capture options and response handling. 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; and 1,000 screenshots a month are free with no card, while paid plans start at $5 for 3,000. Sign up for the free plan.

FAQ

Does one API request always cost one credit?

No. Under the published rules summarized here, credit use depends on generated data size in 5 MB chunks. Check each provider’s exact rounding and retry billing terms.

Which service has the cheaper paid plan?

The captured Html2Pdf.app monthly tiers are clear, but the retrieved PDFShift material does not show a complete current paid tier table. Compare current account pricing at your expected credit usage before deciding.

Can I use these APIs to create a PDF from private HTML?

Html2Pdf.app documentation describes public URLs or raw HTML. For either provider, follow its current documentation for request security and avoid sending sensitive document content unless the service terms and your data requirements permit it.

Should I choose based on the maximum parallel conversion count?

Use concurrency as one planning input. Confirm account limits and run a workload-specific trial, because a stated parallel limit does not tell you how fast your particular pages render.

When is ScreenshotNeo a better fit?

Consider it when the output you need is a clean website screenshot or a supported PDF capture and you want consent overlays removed, failure-aware billing, or an MCP workflow. Compare its documented options with your required PDF conversion behavior.