ScreenshotNeo

BlogHTML to image & PDF

PDFCrowd Free Plan Limits: How Many Web Pages Can You Convert?

PDFCrowd does not publish a numeric page limit for its free online converter. Its separate API trial uses output-size credits, not webpage counts.

By the ScreenshotNeo team4 October 20266 min read

Short answer: PDFCrowd does not publish a numeric page-count allowance for its free online HTML-to-PDF converter. Its credit FAQ says credits do not apply to Online Tools, but that does not establish that use is unlimited or rule out technical, anti-abuse, or per-conversion caps. The online converter is described as free to use; the reviewed official pages do not state a number of pages, conversions, or URLs allowed per day, month, or account.

There are two different offerings people may mean by “PDFCrowd free plan”: the browser-based online converter and the free API trial. The trial currently includes 100 API credits for one month. Credits measure generated output size, not the number of source webpages, so there is no reliable way to translate that allowance into a fixed page count.

1. What the free online converter allows

PDFCrowd’s online tool converts web pages, HTML files, or HTML code. It is identified as free to use, and the vendor says the credit system does not apply to Online Tools. However, the reviewed pages do not specify a numeric usage limit or promise unlimited use. The careful answer to “How many pages can I convert for free?” is therefore: PDFCrowd does not publish a number for the free online converter.

The free online output includes PDFCrowd branding and has reduced settings. PDFCrowd says a license removes the branding and enables customized conversion settings. If you need a specific number of conversions or a particular setting, check the current tool terms or ask PDFCrowd support rather than assuming a limit or entitlement.

2. The API trial is measured in output-size credits

The separate PDFCrowd API trial includes 100 test API credits valid for one month, according to its pricing page. This is an API trial allowance, not a count of webpages you may convert in the online tool.

PDFCrowd defines one credit as 0.5 MB of output. A generated file under 0.5 MB uses one credit; output between 0.5 MB and 1 MB uses two. The amount of output varies with the page and conversion, so 100 credits cannot be converted into a dependable page count. See the vendor’s credit FAQ for the credit rules.

3. Credits, rate limits, concurrency, and delay are different limits

For API and integration plans, a credit allowance answers how much output is covered. It does not tell you how many requests can run at once or how quickly you can send them.

Term What it measures What it does not tell you
Credits Output size; one credit covers 0.5 MB Number of source URLs
Rate limit Conversions allowed per minute Total credits included
Concurrency Conversions allowed at once Monthly page allowance
Max delay How long to wait for asynchronous JavaScript The overall conversion time limit
Overall conversion time limit The total conversion time, described as 60 seconds in the plan-parameter FAQ The amount of output credits consumed

PDFCrowd explains these terms in its plan parameter FAQ. When estimating whether a plan will work, check output credits and request throughput separately.

4. Choosing the right PDFCrowd path

  1. For an occasional manual conversion: use the online converter and verify that its branding and available settings meet your needs.
  2. For repeated or automated conversions: compare the API and integration options with your expected output size, rate, and concurrency. PDFCrowd’s site also points to WebSave, WordPress, Zapier, and Make paths.
  3. For a workflow that depends on a specific free quota: do not build around an assumed page count. The online converter’s reviewed pages do not publish one. Ask PDFCrowd about your intended volume and confirm current terms.
  4. For custom settings or unbranded output: PDFCrowd says a license provides branding removal and customized conversion settings; consult its current pricing for plan details.

For more on the distinction, see the current PDFCrowd pricing and the credit FAQ.

5. Avoid turning credits into a page estimate

If you are evaluating the API trial, use the credit unit directly. Record the generated file sizes for representative pages, then estimate the output credits those conversions consume. Treat that as a planning estimate, not as an official page allowance: output size can vary between pages and runs.

  • Keep the online converter and API trial in separate comparisons; they are different products with different terms.
  • Do not interpret “credits do not apply” as “unlimited pages.” It only establishes that credits do not meter Online Tools.
  • Do not divide 100 credits by an assumed average file size and present the result as a guaranteed number of webpages.
  • For production automation, account separately for output credits, rate limits, concurrency, JavaScript delay, and the overall conversion time limit.

6. Troubleshooting quota and conversion questions

“Where does PDFCrowd show my free online page allowance?”

The official pages reviewed do not publish a numeric allowance for the online converter. The credits FAQ says Online Tools are not limited by credits, which is not the same as a stated page quota. Check the live terms or contact PDFCrowd for a limit that applies to your account or workflow.

“I have 100 credits. Does that mean 100 pages?”

No. The API trial’s 100 credits are based on output size, and one credit covers 0.5 MB. A page’s output can use more than one credit, depending on the generated file size.

“Why did an API conversion use more credits than expected?”

Credits are charged by output size in 0.5 MB units. Check the generated file size and the current credit FAQ; do not estimate credits from the number of input URLs alone.

“Why can’t my integration send more conversions?”

Rate limit and concurrency are plan parameters separate from credits. Check the plan’s conversions-per-minute and simultaneous-conversion limits, and schedule requests within those values.

“Why did a page with JavaScript not finish as expected?”

The plan-parameter FAQ distinguishes the maximum wait for asynchronous JavaScript from the 60-second overall conversion time limit. Review the configured delay and overall limit for the plan, and simplify or retry the source page if it does not render in time.

“Why does my online PDF have branding or fewer settings?”

The online converter page says free output includes PDFCrowd branding and reduced settings. PDFCrowd says a license removes branding and enables customized settings; check its current plan details if those are required.

7. Screenshot alternative for a visual record of a webpage

If your actual goal is to save a visual snapshot rather than create a document for printing or text distribution, try ScreenshotNeo first. It is a website screenshot API and MCP server. A single GET request can return a PNG, JPEG, WebP, or PDF; the PDF output can be useful when you need a capture rather than PDFCrowd’s HTML-to-PDF conversion workflow.

ScreenshotNeo removes known cookie and consent banners, newsletter popups, and chat widgets before capture, and only clean shots are billed. Bot checks, blank pages, failed loads, timeouts, and cache hits cost nothing; response headers identify the page verdict and billing status. Its MCP server offers screenshot, page-info, and PDF-capture tools for AI agents. It has 1,000 screenshots a month free with no card, and paid plans start at $5 for 3,000 screenshots. All features are on every plan.

Or skip the browser setup

Make one GET request. Replace YOUR_API_KEY with your key and change the target URL. See the ScreenshotNeo API documentation for options.

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}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));
  • Cookie banners, popups, and chat widgets are removed before the screenshot.
  • Bot checks, blank pages, and failed loads are never billed.
  • An MCP server lets AI agents take screenshots.
  • 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000.

Sign up free for 1,000 screenshots a month, with no card required.

8. FAQ

Does PDFCrowd say the free online converter is unlimited?

No. The sources reviewed say the online tool is free and not governed by credits, but do not promise unlimited usage.

Are PDFCrowd API credits the same as webpages?

No. Credits correspond to generated output size, at one credit per 0.5 MB.

Can I use the free online converter without an account?

The reviewed sources do not establish account requirements for every use case. Check the current converter page for its active workflow and terms.

Where can I confirm current API trial terms?

Review PDFCrowd’s live pricing page and its credit FAQ, since trial and plan terms may change.

Sources