About htmltopdfapi.co

Why we built it

Most web apps end up producing PDFs sooner or later: invoices, reports, contracts, certificates. Each of the usual tools fails in its own way. DomPDF has no flexbox or grid, so layouts get rebuilt with tables. wkhtmltopdf was archived in January 2023 and renders with an old QtWebKit. Puppeteer works, but then you own a Chromium process that wants hundreds of MB of RAM, crashes under load, and doesn't fit in a standard Lambda deployment package.

htmltopdfapi.co puts that work behind one endpoint. You keep writing HTML and CSS the way you already do, and we keep the browser patched and running. We built it with Laravel developers in mind (the official SDK is a fluent, auto-discovered Laravel package), but anything that can send an HTTP request can use it.

Who writes our guides

The articles on this site are written by the engineers who build and operate the API and maintain the open-source PHP SDK. They cover the problems that come up once PDFs go to real users: table rows split across pages, fonts falling back to a default serif, charts captured before they finish drawing. Code samples are written against the documented REST API and the SDK.

How it works

1. Your app sends HTML or a URL to POST /api/v1/pdf/generate with an API key.
2. The Laravel API validates the request, rejecting URLs that point at private networks or cloud metadata addresses, and checks your plan quota.
3. An isolated AWS Lambda function launches headless Chromium, loads the page, waits for your chosen condition and prints it to PDF.
4. The PDF comes back as the body of the same HTTP response. Nothing is queued or emailed.

The full option reference is in the integration guide, and What is an HTML to PDF API? explains the approach in depth.

Company facts

Get in touch

Questions, bug reports or enterprise enquiries go to support@htmltopdfapi.co or the contact form. Follow development on GitHub.