PDFCrowd Pricing: How Much Does the HTML to PDF API Cost?

Direct answer: PDFCrowd’s pricing page displayed monthly plans from $1 for 10 credits on Nano to $2,630 for 3,000,000 credits on Enterprise 3000 when checked on October 3, 2026. It also listed a one-month trial with 100 test API credits. These are prices displayed on that date, not guaranteed current prices; check PDFCrowd’s live pricing page before choosing a plan.

The credit count is not the same as the number of documents. PDFCrowd says one credit covers up to 0.5 MB of generated output, so output size, request rate, concurrency, and JavaScript wait needs all affect which tier fits. The API converts URLs, HTML, or uploaded HTML into PDF bytes.

Displayed monthly plans

The following prices and allowances were displayed on October 3, 2026. The source page did not give them an effective date, so treat them as a dated snapshot and verify the current table before subscribing.

Plan	Monthly price	Credits per month
Nano	$1	10
Micro	$11	200
Small	$23	1,000
Medium	$35	5,000
Large	$61	10,000
Ultimate	$106	20,000
Enterprise 50	$221	50,000
Enterprise 100	$331	100,000
Enterprise 175	$455	175,000
Enterprise 250	$559	250,000
Enterprise 500	$838	500,000
Enterprise 1000	$1,258	1,000,000
Enterprise 1500	$1,645	1,500,000
Enterprise 2000	$1,970	2,000,000
Enterprise 2500	$2,304	2,500,000
Enterprise 3000	$2,630	3,000,000

PDFCrowd’s pricing page also showed a one-month trial with 100 test API credits. Trial credits are for testing and are listed as valid for one month.

How PDFCrowd credits translate into documents

PDFCrowd’s published rule is one credit per 0.5 MB of generated output. Output up to 0.5 MB uses one credit; output over 0.5 MB through 1 MB uses two, and the same stepwise pattern continues. A useful estimate for a document is therefore:

credits per PDF = ceiling(output size in MB / 0.5)
monthly credits = PDFs per month × credits per PDF

For planning, round output size up to the next 0.5 MB band. Under that estimate, a 0.4 MB PDF uses one credit, a 0.8 MB PDF uses two, and a 1.2 MB PDF uses three. Measure representative generated files rather than assuming every conversion has the same size.

Typical output size	Estimated credits per PDF	Approximate PDFs from 1,000 credits
Up to 0.5 MB	1	1,000
Over 0.5 MB through 1 MB	2	500
Over 1 MB through 1.5 MB	3	About 333
Over 2 MB through 2.5 MB	5	200

These are arithmetic estimates based on the published credit rule, not guaranteed document counts. Images, fonts, page count, and layout can affect output size. The pricing page’s volume selector assumed typical output below 500 KB, which may understate usage for larger files.

Choose a plan using volume and peak load

Estimate monthly volume. Count expected conversions, including retries and seasonal peaks.
Measure output size. Convert a representative mix of small, typical, and large documents. Apply the 0.5 MB credit bands to each group.
Include dynamic rendering. Pages that depend on JavaScript may need a wait period, so compare the plan’s allowed asynchronous JavaScript wait with the page’s actual readiness needs.
Check peak request rate. The displayed limits ranged from 15 requests per minute on entry tiers to as high as 480 per minute on the highest tier.
Check concurrency. The displayed concurrency limits ranged from one active conversion on entry tiers to 16 on the highest tiers. A sufficient credit balance does not itself mean all requests can run at once.
Leave room for variation. If document sizes or traffic vary, size the plan against a busy month and observe actual credit usage before committing to a long-term estimate.

Request-rate, concurrency, and JavaScript wait limits vary by license. Confirm the current plan table for exact limits; the displayed figures can change.

What the API converts and what you pay for

PDFCrowd describes a backend API that converts a reachable URL, raw HTML, or uploaded HTML into a PDF. Documented use cases include reports and dashboard exports, invoices and statements, proposals, letters, certificates, tickets, and archived pages. Page controls include paper size, orientation, margins, page breaks, headers, footers, and print CSS; dynamic content controls cover JavaScript and readiness settings.

The HTTP guide describes versioned endpoints, HTTP Basic authentication using a PDFCrowd username and API key, form-encoded request fields, and PDF bytes on success. The guide states a maximum upload size of 300 MB and a 60-second processing limit. Rate and concurrency limits depend on the license.

These are operating constraints, not just documentation details: a large HTML upload may hit the upload cap, a slow page may exceed the processing window, and a sudden burst may exceed the plan’s rate or concurrency allowance.

Trial, renewal, and unused credits

Credits reset on the billing date.
Unused credits do not roll over.
The listed trial provides 100 test API credits valid for one month.
Monthly plan amounts and limits should be verified against the live pricing page before purchase because the checked page did not provide an effective date.

Since unused credits expire at the reset, a plan with a large allowance can be poor value when volume is irregular. Estimate from actual output sizes and month-to-month demand, then compare the resulting credit need with the current tiers.

PDFCrowd or a screenshot API?

PDFCrowd is positioned for application-controlled conversion of a URL or HTML into a PDF. ScreenshotNeo is a separate option when the output you need is a screenshot of a web page, or a PDF capture of a page. ScreenshotNeo supports PNG, JPEG, WebP, and PDF captures, with options such as full-page capture, selector capture, paper size, margins, landscape mode, and page ranges. See ScreenshotNeo and its API documentation for the available request parameters.

ScreenshotNeo’s pricing is request-based: 1,000 screenshots per month are free with no card; paid plans start at $5 for 3,000 shots. It is worth considering when you need visual page capture, cookie-banner and popup cleanup, or an MCP server for AI agents. It does not replace a workflow that specifically needs PDFCrowd’s HTML-to-PDF conversion behavior; choose based on the input and output your application requires.

Or skip the browser setup

For a webpage screenshot or PDF capture, ScreenshotNeo returns the result from one GET request. This runnable cURL example saves a WebP screenshot; replace the URL and API key with your own values.

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()
with open("shot.webp", "wb") as f:
    f.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(`ScreenshotNeo returned ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

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. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up free for ScreenshotNeo.

Troubleshooting and cost-control checklist

Symptom	Likely cause	What to check
More credits used than expected	Generated files cross additional 0.5 MB output bands.	Inspect output sizes across a representative sample and recompute credits per file.
HTTP 429	Request rate exceeds the license limit.	Reduce request frequency or check whether a plan with a higher rate limit fits.
HTTP 430	Too many conversions are active concurrently.	Limit parallel workers or check the license concurrency limit.
Conversion times out	Processing exceeded the stated 60-second limit or the page did not become ready in time.	Check page readiness and JavaScript behavior; simplify the input where possible and verify current service limits.
Upload rejected	Uploaded HTML exceeds the documented 300 MB maximum.	Reduce the upload size or use a reachable URL or smaller HTML input if appropriate.
Dynamic content missing	The page was converted before its JavaScript content was ready.	Review readiness settings and JavaScript wait allowance for the license.

Record output size and credits for a representative set of documents.
Include retries and peak traffic in volume forecasts.
Match concurrency and rate limits to peak load, not only average load.
Verify current prices, limits, trial terms, and credit rules before subscribing.

Frequently asked questions

Does one PDF always use one credit?

No. One credit covers up to 0.5 MB of output; larger files use more credits in 0.5 MB increments.

Do unused credits carry into the next month?

No. PDFCrowd says credits reset on the billing date and unused credits do not roll over.

Is the trial free?

The checked pricing page listed a one-month trial with 100 test API credits. Confirm the live offer and terms before starting.

Is PDFCrowd intended for manual conversions?

The HTML-to-PDF API is described for backend application use. PDFCrowd also distinguishes it from a manual online converter and other products such as its visitor-triggered page-saving service and invoice API.

What should I use for webpage screenshots?

For image or PDF capture of web pages, consider ScreenshotNeo; for converting arbitrary HTML or uploaded HTML into PDFs, compare the conversion requirements with PDFCrowd’s API.

Sources

Pricing, plan allowances, and displayed limits: PDFCrowd pricing. Credit mechanics: PDFCrowd FAQ. Product capabilities and positioning: PDFCrowd HTML-to-PDF API product page. Authentication, input formats, upload and processing limits, and HTTP status codes: PDFCrowd HTTP guide. Pricing snapshot checked October 3, 2026.