Is PDFShift Free for Testing HTML to PDF Conversions?
Yes. PDFShift offers 50 free monthly credits and an account-free Playground. Learn how credits, file limits, authentication, and watermarks affect testing.
Yes. PDFShift says a free account includes 50 credits per month, with no charge and no credit card required. You can also try conversion customization in its Playground without creating an account. The Playground is for exploring options; to test the API, create an account, log in, and send an authenticated request. See the PDFShift FAQ and pricing page.
The main detail to plan around is that a credit is based on the generated PDF’s size, not simply on the number of requests. One credit covers up to 5 MB; larger outputs use additional credits, rounded up. PDFShift lists a 15 MB maximum file size and a 30-second timeout for the free plan. These are vendor-published terms and may change, so check the current pricing page before relying on them.
Two ways to try PDFShift
| Route | Account needed? | Good for | Important detail |
|---|---|---|---|
| Playground | No | Exploring conversion customization and code samples | It is separate from authenticated API use. |
| API with a free account | Yes | Testing actual API requests and integration behavior | Log in and send the X-API-Key header to authenticate. |
Use the Playground when you only need to inspect customization options. Use the API when you need to exercise your application’s request flow, authentication, and response handling. PDFShift’s FAQ describes both routes.
What 50 free credits cover
PDFShift counts credits using the size of the generated PDF. Its Help Center says one credit covers up to 5 MB and that the required credits are rounded upward. For example, a 23 MB output uses five credits. As a result, “50 conversions” is only a useful approximation for small, ordinary outputs; a larger document can consume several credits in one conversion. See How PDFShift counts credits.
| Item | Free-plan detail in the research | What it means when testing |
|---|---|---|
| Monthly allowance | 50 credits | Track credits, not just request count. |
| Credit unit | Up to 5 MB of generated PDF per credit, rounded up | Check output size, especially for image-heavy pages. |
| Maximum file size | 15 MB | A conversion may exceed the free plan’s listed file limit. |
| Timeout | 30 seconds | Complex or slow conversions may not finish within the listed limit. |
| Payment details | No charge and no card required for the free account | You can explore free API use without entering card details. |
The 15 MB limit and 30-second timeout are listed on the PDFShift pricing page. The exact allowance and plan terms are service details, not independent performance measurements.
How to test without a watermark
- Create a free PDFShift account and log in.
- Use the API key for that account in the request’s
X-API-Keyheader. - Check the returned PDF for the expected content and inspect its size so you can estimate credit use.
- If a watermark appears, first verify that the request actually sent the API key in the required header.
PDFShift’s Help Center says authenticated free users can make 50 conversions without a watermark. It also explains that an unauthenticated request may receive a watermark even when the caller sets the sandbox option to false. Authentication is the key check; changing the sandbox setting alone does not establish that the request is authenticated. Details: PDFShift’s watermark troubleshooting article.
Keep HTML conversion tests efficient
If the HTML is already available to your test, PDFShift’s Python guide recommends submitting raw HTML as the source value when practical. This avoids a network fetch to retrieve the HTML page and can reduce network requests and conversion time. It is useful for repeatable tests of known markup; use the route that matches what you need to validate. See the PDFShift raw HTML Python guide.
For each test, record the input case, whether you submitted a URL or raw HTML, the generated PDF size, and whether the output has the expected layout. That gives you a clearer view of both correctness and credit consumption than counting requests alone.
Common problems and fixes
| Symptom | Likely cause | What to check |
|---|---|---|
| The PDF has a watermark | The request was unauthenticated, or the API key header was missing or incorrect. | Confirm that the account is logged in for API use and the request includes X-API-Key. The sandbox setting by itself does not prevent this case. |
| The free allowance runs down faster than the request count suggests | Some output PDFs consume more than one credit because of their size. | Inspect generated file sizes and apply the 5 MB-per-credit rule, rounded up. |
| A conversion is too large for the free plan | The pricing page lists a 15 MB maximum file size. | Reduce the output size or check the current plan terms for a suitable limit. |
| A conversion does not finish within the listed limit | The free plan lists a 30-second timeout. | Check whether the input or its resources make conversion slow; use raw HTML when practical to avoid fetching the source page. |
| You can customize in the Playground but cannot validate your integration | The Playground is an account-free exploration route, not the same as authenticated API use. | Create a free account, log in, and test with the API key header. |
Performance, reliability, and cost considerations
- Cost: the free tier is listed as 50 monthly credits without a charge or card requirement. Budget based on generated megabytes, not one credit per document.
- Output size: larger PDFs consume credits in 5 MB increments rounded up. Image-heavy content can therefore use more of the allowance than small text documents.
- Time limit: the free plan lists a 30-second timeout. The dossier does not establish how often conversions finish within that limit; treat it as a plan constraint, not a speed guarantee.
- Repeatability: providing raw HTML can remove a source-page fetch from a test where the markup is already available, reducing network requests and conversion time according to PDFShift’s Python guide.
- Changing terms: quotas and plan features can change. Verify the current pricing details before designing a longer test or production workflow.
ScreenshotNeo as an alternative for webpage capture
PDFShift is the relevant option here when you need to convert HTML to PDF. If your actual goal is to capture a live webpage as a PDF or image, ScreenshotNeo is a website screenshot API with PDF output. It is an alternative for URL-based webpage capture, not a general-purpose replacement for converting arbitrary HTML into a PDF.
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.pdfSee the ScreenshotNeo API documentation for the request options. ScreenshotNeo removes cookie banners, popups, and chat widgets 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; paid plans start at $5 for 3,000. Sign up free for ScreenshotNeo.
FAQ
Can I try PDFShift without creating an account?
Yes. Use its Playground to explore customization. API use requires a registered, logged-in account, according to the FAQ.
Does one API request always use one credit?
No. Credits depend on generated PDF size. A larger output can use multiple credits; PDFShift’s example says a 23 MB output uses five.
Will setting sandbox to false remove a watermark?
Not if the request is unauthenticated. PDFShift says to authenticate with the X-API-Key header for watermark-free free conversions.
Can I use the free plan for large or slow documents?
The listed free-plan constraints are a 15 MB maximum file size and a 30-second timeout. Check the current pricing page against your document before relying on the free tier.
