Every account includes unlimited watermarked test documents. Test your document content and styling as much as you need, without worrying about extra charges.
Our demo lets you try the API without signing up, and all of our HTML-to-PDF source code examples include our public and free test-mode key, YOUR_API_KEY_HERE.
DocRaptor infrastructure is ready to handle any throughput or size requirements. We have no limits on document input or output size; and all documents cost the same, regardless of their size or generation time.
DocRaptor can host your PDFs at an unbranded URL, which you can provide to your end-users or input to third-party tools like Zapier and Salesforce.
High-quality PDFs can be surprisingly tricky to develop. Our support team has years of experience helping to create the perfect PDF and only an email or chat away.
DocRaptor is a REST HTML-to-PDF conversion API, but you can also generate PDFs with non-HTML libraries such as LaTex, jsKit, and PDFKit. In our experience, though, HTML and CSS offer many advantages including:
Layout & Tables
Raw HTML code supports flexible structures such as tables, flexboxes, columns, and floats. Most non-HTML-to-PDF converters force you to lay out each element or table cell to specific pixel locations.
Many PDF projects involve existing HTML or XML documents, such as web pages or Excel exports. Reusing existing code and custom CSS styling speeds up document development and keeps your code DRY.
HTML documents can be styled responsively for different size documents or displays. With DocRaptor, it's simple to transform the same document into US-Letter or A4 sizes.
Since HTML and CSS were built for creating, styling, and laying out documents, it's faster to use those programming languages for building PDF documents. Not just for the initial development, but for future edits and changes as well.
DocRaptor vs Other PDF Converters
We believe DocRaptor is the highest-quality, fastest, and most cost-effective PDF conversion tool. But you don’t have to take our word for it–do your own research. Start with these questions:
Can you reuse an existing HTML document?
Is your document long or complex?
A mostly text-based or one-page document can be created with almost any PDF conversion engine. But documents with complex layouts, dynamic references (such as indexes or table of contents), lots of charts or images, varying headers or page sizes, etc, can be difficult in many libraries. To save development time, test the most complex parts of your document first.
How much development and maintenance can you afford?
There is a wide discrepancy in feature support and bug-free operation between different converters. Maintaining a high-scale infrastructure can be costly as PDFs are slow and CPU-intensive to generate (compared to web pages). Compare the development time and maintenance costs of your PDF conversion options early in your selection process.
How much support do you need?
After answering the above questions, you should have a good understanding of the level of support you require. Selecting a professional HTML-to-PDF option with an expert support team—like DocRaptor—can dramatically speed up your implementation timelines.
Prince pioneered HTML-to-PDF technology with the first release of PrinceXML in 2003 and has been leading the category ever since. The chairman of Prince (and the inventor of CSS), Håkon Wium Lie, also wrote the first CSS Paged Media W3C specifications, which enable much of Prince and DocRaptor’s unique HTML-to-PDF functionality. DocRaptor's primary difference versus Prince is our lower starting price point and instant scalability.
There are countless HTML-to-PDF API alternatives available on the internet. Most of them are significantly cheaper than DocRaptor, but that's because they're all based on Headless Chrome and generally managed by companies less focused on reliability and security. These other APIs will struggle with complex PDFs.
wkhtmltopdf / PhantomJS
Historically, wkhtmltopdf and PhantomJS were the primary open-source HTML-to-PDF libraries. Now, they're both deprecated, buggy, lacking support for modern CSS, have poor typography, and are a pain to install. Stick with the Headless Chrome-based libraries.
We created DocRaptor because we weren’t satisfied with any of the alternatives. It is a terrific HTML-to-PDF API, and likely to be the most cost-effective solution for most PDF conversion projects when you consider the total project.
Here's a more complete list of features, to better consider DocRaptor’s key advantages: