Six best PDF generator APIs in 2026: Nutrient vs. competitors compared
Table of contents
Templates, merging, and watermarking through Nutrient DWS - start with 50 free credits.
Choose a PDF generator API based on your input and the work that follows generation:
- Nutrient DWS Processor API — Generate from HTML or convert documents. Then combine supported PDF processing actions in a Build request.
- PDF generator API — Build visual templates and populate them with JSON data.
- APITemplate.io — Choose between visual templates and HTML-based PDF generation, with image generation available separately or in combined plans.
- PDFMonkey — Generate documents from templates and dynamic data using a visual builder or HTML/CSS.
- Anvil — Generate PDFs alongside form filling and electronic signature workflows.
- Converterer, formerly Paperplane — Convert files or capture webpages and deliver output to your cloud storage.
Jump to the comparison table to compare inputs, billing models, and plan limits. This is a documentation-based comparison, not a performance benchmark. Product and billing information was checked on 8 September 2026; confirm current terms before purchasing.
What is a PDF generator API?
A PDF generator API creates PDF files from inputs such as HTML, document templates, JSON data, or existing files. Your application sends a request, and the service returns the PDF or a way to retrieve it after processing.
A hosted API moves rendering-engine maintenance to the provider. You still manage authentication, input validation, retries, and file handling. For an implementation example, see how to generate PDF invoices from HTML in Python.
Why use a PDF generator API?
A hosted API can help when your application needs to:
- Automate generation — Create invoices or reports from application events.
- Reuse templates — Apply a common layout to changing data.
- Reduce renderer maintenance — Let the provider operate and update the rendering service.
- Handle changing volume — Use hosted capacity within the provider’s rate and concurrency limits.
- Connect processing steps — Add operations such as conversion, watermarking, or form filling where the API supports them.
Compare usage fees with the cost of running your own renderer. Neither approach is always cheaper.
Common PDF generator API use cases
The input format and required output determine which service fits each task:
- Invoicing — Turn billing data into PDFs. See examples in Python, Node.js, Java, C#, or PHP.
- Reports — Render tables, charts, and summaries with predictable page breaks.
- Contracts and forms — Generate a document or populate an existing PDF. Then send it through the required signing workflow.
- Shipping documents — Produce labels, packing lists, and customs forms from order data.
- Certificates — Apply recipient data to a reusable design.
What to look for in a PDF generator API
Test a representative document before comparing plan prices:
- Input and templates — Do you already have HTML, a PDF form, or JSON data? Check whether templates live in your application or the provider’s editor.
- Rendering — Test your fonts, long tables, images, page breaks, and JavaScript-dependent charts.
- Processing steps — Separate generation from filling, editing, extraction, and signing. They may use different endpoints and billing units.
- Delivery — Check whether the API returns bytes, a download URL, or a job ID with a webhook callback.
- Data handling — Review retention, storage destinations, regional processing, and contractual requirements for your documents.
- Operational limits — Check rate limits, concurrency, timeouts, and retry behavior against your expected workload.
If documents must stay in infrastructure you operate, evaluate a self-hosted option such as Nutrient Document Engine. Hosting choices still require configuration and a review of your deployment requirements.
Understanding PDF generator API pricing models
A credit, an API call, and a generated document aren’t interchangeable billing units. Estimate usage with the same sample workload for each provider.
Common credit-based models
The services below use different approaches:
- Operation-based credits — Nutrient charges for the tools used in a request. Combining actions doesn’t make those actions free.
- Page-based credits — The PDF generator API counts document pages in blocks of five, so a longer document can consume multiple credits.
- Document quotas — APITemplate.io and PDFMonkey offer plans with generation allowances and plan-specific features.
- Metered API usage — Anvil distinguishes PDF filling/generation calls from workflow submissions and electronic signature packets.
- Conversion quotas — Converterer counts file conversions and website captures against a shared allowance.
Compare recurring free allowances, time-limited trials, and sandbox access separately. Check watermarks, external-asset access, storage duration, and payment-method requirements before treating a free plan as suitable for production.
Top six PDF generator APIs in 2026
Use this table to shortlist services by workflow. The billing column describes what to measure rather than treating unlike quotas as equivalent prices.
| Provider | Suitable use case | Main inputs for generation | Billing and evaluation considerations |
|---|---|---|---|
| Nutrient DWS Processor API | Generation followed by PDF processing | HTML/CSS, Office documents, images | Credits depend on the operations; use the Build analysis endpoint to estimate a request |
| PDF generator API | Visual templates populated by application data | JSON with a template; HTML conversion also available | Page-based credits; template, workspace, and request limits vary by plan |
| APITemplate.io | Teams choosing between visual and HTML templates | Template data, HTML, Markdown | PDF-only and combined image/PDF plans have different allowances |
| PDFMonkey | Template-driven invoices, reports, and certificates | Template data or HTML/CSS | Monthly document quotas; free-plan restrictions include external resources |
| Anvil | Generation connected to forms and signing workflows | HTML/CSS, Markdown; existing PDFs for filling | Metered PDF usage is separate from signing and workflow usage; production API access needs billing setup |
| Converterer, formerly Paperplane | File conversion and webpage capture into cloud storage | Files, HTML, or webpage URLs | File conversions and website captures share the plan’s allowance |
Nutrient DWS Processor API
Nutrient’s PDF generator API creates PDFs from HTML and CSS. Its Build API can assemble inputs and apply supported actions such as watermarking, optical character recognition (OCR), redaction, or flattening. The Build workflow guide explains the request structure and operation order.
Key differentiators:
- Generation and conversion — Generate from HTML or use supported document conversions for Office files and images.
- Processing after generation — Combine supported actions in one Build request. Cryptographic signing uses the separate
/signendpoint after processing is complete. - Form workflows — Use form filling and flattening where the output should contain completed form values.
- Developer tools — Use the official Python client(opens in a new tab) or TypeScript client(opens in a new tab), or start with the Postman collection.
- Automation — Connect through the Zapier integration or model context protocol (MCP) server when that fits your workflow.
Quick start:
Create an API key and save an index.html file in your working directory. Replace the key placeholder before running this request. The example uploads one HTML file; include additional local stylesheets, fonts, and images as assets when your template needs them.
curl -X POST https://api.nutrient.io/build \ -H "Authorization: Bearer your_api_key_here" \ -o result.pdf \ --fail \ -F index.html=@index.html \ -F instructions='{ "parts": [ { "html": "index.html" } ] }'For asset handling, page sizes, and margins, see the PDF generation guide. Keep the API key on your server when integrating this request into a web application.
Documents supported
Nutrient supports HTML/CSS generation and conversion from Office documents and images. Existing PDFs can be assembled and processed in the same Build workflow where the requested operations are supported.
Real-world workflow examples
Choose actions based on the input:
- Invoices — Generate from HTML and add a watermark in a Build request.
- Scanned records — Run OCR before operations that depend on recognized text.
- Completed forms — Fill and flatten the document. Then send the final PDF to the digital signature endpoint if signing is required.
Nutrient is a useful candidate when generation is one step in a larger document process. If you only need an editor for business users to design templates, compare the visual-template services below as well.
Pricing
Nutrient uses operation-based credits. The credit calculation guide explains how combined requests are charged and how /analyze_build estimates usage without executing the conversion. Use Processor API pricing for current allowances and plans, and create an account(opens in a new tab) to evaluate output with your own files.
PDF generator API
The PDF generator API(opens in a new tab) combines a visual template editor with an API that accepts template identifiers and JSON data. It also offers HTML-to-PDF conversion, so its input options aren’t limited to visual templates.
Key features
- Visual editing — Design templates without writing all of the layout in HTML.
- Dynamic content — Populate templates with data, conditional content, and repeating elements.
- Workspace organization — Separate templates and users through workspaces, subject to plan limits.
- Additional PDF services — Form filling and other processing capabilities extend beyond document generation.
This service suits applications that need reusable templates maintained through an editor. Check embedded-editor access and template-management features for the plan you’re evaluating.
Documents supported
Use JSON data with a stored template, or the HTML conversion API for existing HTML content.
Pricing
Plans use credits based on document length: Each block of five pages consumes one credit. Don’t estimate cost by counting data sources or assuming one request always equals one credit. Compare page counts, templates, workspaces, and request limits when selecting a plan.
APITemplate.io
APITemplate.io(opens in a new tab) offers visual and HTML-based template options, plus API routes for generating PDFs from HTML or Markdown. It also generates images, which matters when the same application produces both PDF documents and graphics.
Key features
- Template options — Choose visual editing or HTML-based layouts.
- PDF and image generation — Use the output type required by your application.
- Automation integrations — Connect document generation to tools such as Zapier, Make, and n8n.
- Page styling — Configure PDF headers, footers, and page settings through the supported editor or API options.
It’s a candidate for teams whose template authors have different technical backgrounds. Test the chosen editor with a real document; editor features and API options aren’t identical.
Documents supported
Use template data, HTML, or Markdown for PDF generation.
Pricing
APITemplate.io separates PDF-only plans from plans covering both images and PDFs. Compare generation allowances, template limits, storage, and webhook availability for the specific plan. The free allowance includes PDF generation.
PDFMonkey
PDFMonkey(opens in a new tab) provides a visual builder and code templates that use HTML/CSS with dynamic data. Its code-template documentation covers Liquid syntax, custom JavaScript, fonts, and page layout.
Key features
- Template authoring — Choose a visual builder or code templates.
- Dynamic data — Populate the document from your application’s payload.
- Delivery workflow — Retrieve generated documents and use webhooks to respond to completion.
- External assets — Load resources such as images and fonts on plans that support them.
Use it for recurring documents that share a template. Test the intended production plan: A premium trial can allow resources that the free plan won’t load afterward.
Documents supported
Use templates with dynamic data or the HTML-to-PDF route for your own HTML.
Pricing
PDFMonkey offers monthly document quotas and a separate trial of paid features. Plan differences include document retention, external resources, and maximum generation time. Confirm how overage usage is handled before relying on a fixed monthly allowance.
Anvil PDF Generation API
Anvil’s generation API(opens in a new tab) creates PDFs from HTML/CSS or Markdown. Its wider platform includes filling existing PDF forms and electronic signature workflows. Those are distinct capabilities, not operations of the generation endpoint.
Key features
- Direct generation — Send content to the PDF generation endpoint and receive PDF output.
- Form filling — Populate existing PDF templates through a separate API.
- Electronic signatures — Connect generated or filled documents to signing workflows.
- Development mode — Test integrations with development keys, checking their limits and output watermarks.
Anvil is a candidate when the application needs generation, forms, and signing within the same platform. Check the API and billing requirements for each step.
Documents supported
Generate from HTML/CSS or Markdown. Use the filling API when the starting point is an existing PDF form.
Pricing
PDF filling/generation is metered separately from workflow submissions and electronic signature packets. Anvil’s free UI plan isn’t a recurring free production API allowance: Production API access requires adding a payment method or upgrading. Check starter-credit terms and product-specific charges before estimating ongoing use.
Paperplane
Paperplane has rebranded as Converterer(opens in a new tab). The existing screenshot above shows the earlier product. Evaluate the current service and documentation when starting a new integration.
Key features
- File conversion — Convert supported input files through its conversion API.
- Website capture — Render webpages into PDF or image output through a separate capture API.
- Storage destinations — Deliver output to supported cloud storage, including Amazon S3, Cloudflare R2, Google Cloud Storage, and Azure.
- Job completion — Use webhook callbacks to handle completed jobs.
Converterer fits applications that want conversion or capture results delivered to their own supported storage destination.
Documents supported
Inputs include files and webpages. Check the conversion matrix for the exact input/output pair and the capture documentation for HTML rendering options.
Pricing
Converterer uses conversion allowances shared by file conversion and website capture. Paid plans have overage rates. Check current allowances and overage rates before estimating your costs.
Conclusion and recommendations
Start with your source material. For an existing HTML invoice, test direct HTML conversion. For JSON data and business-managed layouts, evaluate a template editor. If the generated file then needs processing, compare the supported operations and endpoint sequence, as well as the renderer.
Test one typical document and one difficult case, such as a long table with custom fonts. Record page breaks, missing assets, generation time, and billable usage. Choose the service that meets those requirements at your expected volume.
For generation inside an application you operate, compare Nutrient’s document SDKs with the hosted API approach.
Generate a PDF from your own HTML. Then evaluate the processing steps your application needs.
FAQ
There isn’t one best option for every workload. Compare the PDF allowance, watermarks, external-asset support, retention, and API access. A trial of paid features or a free UI plan isn’t equivalent to an ongoing free production API plan.
Yes. Call the API from your backend and return the generated file or download link to the application. Keep secret API keys out of browser code, and handle errors and asynchronous jobs where required.
Some services store templates in a visual editor and accept JSON data at generation time. Others accept HTML rendered by your application. Check who can edit templates and how you promote tested changes into production.
Check request and concurrency limits, job timeouts, file-size limits, and billing units. Test bursts of requests and long documents rather than estimating capacity from a single small PDF.
Yes. Nutrient’s Build API combines generation with supported processing actions such as watermarking or flattening. Use the separate signing endpoint for cryptographic signatures. Combined requests still incur the applicable operation costs.
There’s no reliable universal timing. Measure your own templates, fonts, images, page counts, and network conditions. For asynchronous services, include queueing and file delivery in the time your application records.
Many support custom fonts through uploaded assets, CSS @font-face, or editor settings. Verify supported font formats and test character coverage, line wrapping, and page breaks in the generated PDF.
Yes, if the service supports document conversion. Nutrient accepts Office documents and images for PDF conversion. Confirm the exact input format; HTML generation alone doesn’t imply Office conversion support.
Read the provider’s error response before retrying. Correct invalid inputs and missing assets first. For transient failures and rate limits, follow the documented retry guidance and use idempotency controls where available to avoid duplicate work.
Assess the provider’s documented retention, access controls, processing locations, and contractual terms against your requirements. Include output storage and application logging in that review. A hosted API doesn’t automatically make the surrounding application compliant.
HTML-to-PDF generation converts markup and styles supplied by your application. Template-based generation combines a stored layout with data supplied at runtime. Both can produce repeatable documents; the distinction is where the layout is authored and maintained.
Cost depends on the billing unit, allowance, and required features. Estimate document length, generation volume, processing actions, storage, and overages. Compare that workload across plans instead of equating one credit with one PDF.
The services in this comparison provide evaluation options, but the terms differ. Check whether testing requires a payment method, whether output is watermarked, and which features remain available after a trial ends.
Hosted APIs move renderer operations to a provider and charge for service usage. With a local library or browser renderer, your team manages dependencies, capacity, and updates. Compare total operating cost and deployment requirements; high volume alone doesn’t determine the cheaper option.
