ScreenshotNeo

BlogComparisons

Html2Pdf.app Pricing: API Plans, Usage Limits, and Overage Costs

Compare Html2Pdf.app’s monthly plans, credit rules, file limits, and concurrency. See what the official information does—and does not—say about overages.

By the ScreenshotNeo team4 October 20267 min read

Html2Pdf.app lists four monthly plans: Free at $0 for 100 credits, Startup at $9 for 1,000, Standard at $25 for 5,000, and Scale at $39 for 10,000. Credits are based on generated PDF size: the service says each 5 MB chunk costs one credit. The official material reviewed does not publish an overage price or clearly say what happens when credits run out, so confirm that behavior with the vendor before relying on continued conversions.

This guide summarizes the published monthly limits, explains how to estimate credit use, and shows what to check before choosing a plan. For exact terms, consult the official pricing page and API documentation.

1. Html2Pdf.app monthly plans at a glance

Plan Monthly price Credits per month Parallel conversions PDF size limit
Free $0 100 1 Up to 1 MB
Startup $9 1,000 3 Unlimited
Standard $25 5,000 10 Unlimited
Scale $39 10,000 20 Unlimited

The pricing page says its plans include customization options and access to the WordPress PDF plugin. Paid plans list unlimited PDF size, but that per-file allowance is separate from the monthly credit budget: a large PDF can consume multiple credits.

The page exposes monthly and yearly billing controls, but the yearly amounts and terms were not established in the official content reviewed for this guide. Check the pricing page or account checkout for current annual terms rather than estimating a discount.

2. How credits are calculated

Html2Pdf.app describes one credit for each 5 MB chunk of generated PDF output and gives a 15 MB PDF as a three-credit example. Credits reset on the first day of each month. The pricing material does not explain how it rounds documents whose size is not an exact multiple of 5 MB, and it does not describe credit rollover.

For planning, use the vendor’s stated examples and measure representative output from your own documents. Do not assume every API call costs one credit: a single large document may use several. Likewise, do not infer a precise rounding rule for, say, a 6 MB PDF without confirmation.

Estimate a monthly requirement

  1. Collect representative generated PDFs, including the largest and most complex cases.
  2. Record each output file’s size and the number of conversions expected in a typical month.
  3. Estimate credits using the documented 5 MB chunks, while treating non-multiple sizes as uncertain until the vendor confirms rounding.
  4. Add headroom for peak periods and parallel work; the plan’s concurrency cap can matter even when the monthly credit total is sufficient.
  5. Verify the account’s usage display and what happens at the limit before production rollout.

3. What happens when credits run out?

The official pricing and documentation reviewed do not state an overage rate, sellable extra-credit price, or clear post-limit billing behavior. The API documentation says an HTTP 403 can indicate that the account reached a limit included in its plan. That status does not establish whether further conversions stop, require an upgrade, or incur a charge.

For a production workload, ask Html2Pdf.app support or check the account billing interface for these specific answers:

  • Are requests rejected when monthly credits are exhausted?
  • Can extra credits be purchased, and at what price?
  • Does the service automatically upgrade or charge overages?
  • Are failed conversions charged, and how are partial or retried jobs counted?
  • Where can the account owner monitor remaining credits and reset timing?

Until those points are confirmed, budget against the included allocation and handle limit responses as a service-capacity condition. Do not encode an assumed overage amount in forecasts.

4. Choosing a plan for your workload

Plan May fit when Check carefully
Free You are evaluating the API or have a small workload that fits within 100 credits. One conversion at a time and a 1 MB per-file ceiling.
Startup You need a modest recurring workload with up to 1,000 included credits. Three parallel conversions; confirm the monthly credit estimate from actual output sizes.
Standard Your expected workload needs more volume or up to ten concurrent conversions. 5,000 credits do not mean 5,000 documents if PDFs exceed one credit each.
Scale You need the highest listed allocation and up to twenty parallel conversions. Confirm exhausted-credit behavior and peak demand; the page lists 10,000 credits, not unlimited usage.

The practical comparison is not just dollars per plan. Consider output sizes, monthly volume, peak concurrency, the free tier’s file-size ceiling, and the service’s behavior when the allocation is depleted.

5. API use and operational considerations

Html2Pdf.app is a hosted HTML-to-PDF API. Its documentation describes requests using either raw HTML or a publicly reachable URL, authenticated with an X-API-Key header. Synchronous requests return PDF bytes; an asynchronous callback option is also documented. Keep API keys on a backend, trusted script, or job runner rather than exposing them in browser JavaScript. See the official API documentation for current request fields and callback details.

The service says conversions run in headless Chromium and support modern HTML, CSS, and JavaScript. Its documentation notes that CSS media mode, available fonts and other resources, and JavaScript load timing can affect output. Before selecting a plan for production, render a representative set of pages and check the resulting PDF appearance, file size, and conversion behavior.

Reliability and cost controls

  • Measure generated output size, since credit use depends on PDF size rather than request count alone.
  • Use a queue or concurrency limiter aligned with the selected plan’s parallel-conversion limit.
  • Set timeouts and bounded retries in your calling application; retry only failures that are safe to repeat, and check how retries affect credits with the vendor.
  • Monitor HTTP status codes and remaining account usage. Treat HTTP 403 as a possible plan-limit response, not proof of an overage charge.
  • Keep an operational buffer for unusually large PDFs and traffic spikes.
  • Test font availability, remote-resource access, CSS media behavior, and client-side rendering timing on the pages you actually convert.

6. Troubleshooting plan and usage issues

Symptom Likely explanation What to do
HTTP 403 The documentation identifies reaching a plan-included limit as one possible reason. Check account usage and plan limits, then ask the vendor whether credits are exhausted or another restriction applies. Do not assume a particular overage outcome.
Conversion requests queue or fail under load The plan’s parallel-conversion allowance may be exceeded. Limit concurrency to the plan’s listed cap and queue excess work, or compare a higher tier’s allowance.
A PDF exceeds the Free plan limit The Free tier lists a 1 MB per-file limit. Reduce output size or evaluate a paid tier, which lists unlimited PDF size; still account for credits per generated size.
Credits run out earlier than expected Credit consumption tracks output-size chunks, so large PDFs use more than one credit. Measure output sizes across representative conversions and recalculate using the published 5 MB chunk rule. Confirm rounding with the vendor.
Output layout differs from the browser Media mode, fonts, remote resources, or JavaScript timing can change the rendered result. Use the documentation’s supported options, ensure resources are available to the renderer, and test a representative page before deployment.
Annual amount is unclear The pricing page has a yearly selector, but the reviewed content did not establish annual figures or terms. Check the active yearly view or account checkout before comparing annual cost.

7. ScreenshotNeo as an alternative to try first

If your requirement is a screenshot of a web page rather than a PDF conversion, ScreenshotNeo is a website screenshot API and MCP server. It returns PNG, JPEG, or WebP screenshots, or a PDF, from a GET request. This is a different product fit from an HTML-to-PDF focused API, but it can suit workflows that need screenshots and page capture controls.

ScreenshotNeo’s stated pricing is 1,000 screenshots per month free with no card, then $5 for 3,000 on Starter, $15 for 15,000 on Growth, $39 for 60,000 on Pro, $99 for 250,000 on Scale, and $249 for 1,000,000 on Business. Yearly billing gives two months free, and every feature is available on every plan. For an API specifically, the comparison points are the output you need, your expected usage, and each service’s documented billing unit.

For ScreenshotNeo setup options and parameters, see the API documentation.

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

Cookie banners, newsletter popups, and chat widgets are removed before capture; those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. It also supports full-page captures, CSS element capture, PDF settings, custom CSS and JavaScript, request controls, signed links, asynchronous jobs, bulk capture, and other options.

Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.

8. Frequently asked questions

Do unused Html2Pdf.app credits roll over?

The reviewed pricing material says credits reset on the first day of each month but does not describe rollover. Confirm the account terms if unused credits matter to your budget.

Does one API request always consume one credit?

No such rule is documented. The stated unit is PDF output size, at one credit for each 5 MB chunk.

Is there a published overage rate?

Not in the official material reviewed. It also does not clearly define post-limit billing or request behavior.

Can I calculate an annual plan price from the monthly rate?

Not reliably from the reviewed content. Check the yearly selector or checkout for the actual annual price and terms.

Does “unlimited PDF size” on a paid plan mean unlimited conversions?

No. The pricing page lists unlimited per-file PDF size for paid tiers, alongside finite monthly credit allocations and concurrency limits.