DocRaptor

Author: Team DocRaptor

Managing Errors in your HTML to PDF Pipeline

When you view an ordinary web page, many errors may occur without your knowledge. The page itself may fail to load, or resources (such as images and stylesheets) may fail to download, be sent using bad encoding, have unknown MIME types, or any number of other common errors.

As long as the page loads, your browser attempts to display the page and it ignores any errored images or stylesheets... Continue Reading

DocRaptor vs PDFreactor

DocRaptor vs PDFreactor

PDFreactor is a fantastic HTML to PDF engine, and provides several features that DocRaptor does not yet support. However, DocRaptor has an entirely different pricing and delivery model that many organizations find a better fit. Here’s a summary of the differences between DocRaptor and PDFreactor:

  1. Do you want PDF forms, thumbnails, digital signatures, or 508 accessibility compliance?
.. Continue Reading

DocRaptor vs PhantomJS

DocRaptor vs PhantomJS

PhantomJS is a “headless browser” (a web browser, just for programming, without a visible interface). Exporting screen captures to PDF, PNG, and JPG is just one of many PhantomJS features. DocRaptor uses PrinceXML, an engine designed specifically for creating PDFs. PhantomJS is built on the WebKit browser, as does the other major open-source PDF generator, wkhtmltopdf... Continue Reading

DocRaptor vs PrinceXML

DocRaptor vs PrinceXML

PrinceXML is part of the backend processing engine for DocRaptor. All PDFs created by DocRaptor use PrinceXML as the rendering engine. We love the PrinceXML product and their team. They recommend DocRaptor as a cloud solution and we recommend Prince for all self-hosted PDF generation.

So what’s the difference between DocRaptor and Prince?.. Continue Reading

Gone in 60 Seconds: How We Moved From Linode to AWS With Less Than a Minute of Downtime

Recently we moved DocRaptor from Linode to AWS, increasing average document creation speed by 6.9%, reducing network errors by an incredible 84.1%, and saving ourselves a ton of devops time related to scaling. Our move to AWS also allowed us to double our simultaneous request limit, scale up to meeting customer demand in a matter of minutes instead of hours, and gave us more time to help you create the documents you need... Continue Reading

TL;DR: Outages, even short ones, are bad.

Lately we’ve been hit by a few incidents of network problems at Linode’s Newark data center, causing interruptions for some of our users and frustration all around. We’re adding more data centers so this problem won’t happen in the future.

We’ve been happy customers of Linode for 4 years. They have been an amazing partner, helping us grow and improve without spending all of our time building out physical hardware... Continue Reading