GDPR Compliance

We have updated our privacy policy to meet the new EU data protection regulation requirements. We have also created a legal agreement promising the protection of all personally identifiable information and sensitive information that we collect and store.

Privacy Policy

Data Processing Agreement

API Version 4

We have released the new major version of our HTML to PDF API, here are the highlights:

  • Page Headers and Footers
  • Custom Page Sizes
  • Ad / EU Cookie Warning Blocking

New Features

Page Headers and Footers
One of the most requested features. We now support automatically injecting header and footer templates to generated PDF documents. You can create these segments in full HTML and customize as you wish. It is also possible to insert dynamic data such as page number, document title etc into the headers and footers.

Custom Page Sizes
In addition to pdf_page parameter, now it’s possible to send pdf_width and pdf_height parameters to set up a custom page size.

Ad / Cookie Warning Blocking
We have two new options, block_ads and block_cookie_warnings in order to apply blocking rules to the page before conversion.


  • We used to generate PDFs on print CSS media. However, the API now defaults to screen media in order to generate documents as close as to how they look on a browser. You can switch to print using emulate_media: print setting


V4 is completely backwards compatible and can be used by just changing the API call url to

API Version 3

We have a new and exciting release of the HTML to PDF API with many improvements, a brand new rendering engine and new features.

In order to switch to the new version you will need to change your API url from v2 to v3, as in

It is mostly backwards compatible so you should be able to switch without any issues.

Faster Rendering: The version 3 of PDF API is around twice as fast compared to v2.

Better Engine: Our rendering engine now uses the latest Chromium releases, providing better standards compliance.

New Wait Modes: In previous versions the API would wait for the window load event before rendering the pdf. Now you have an option to wait for network to become idle using wait=network parameter to ensure pages load completely even with a lot of async resources.

Shutter: If you need to control the precise moment of capture, you can use shutter=<css selector> parameter to wait for a DOM element before capture. Combined with js injection, you can control the render time as you wish.

Media Emulation: Now it’s possible to emulate print css media using emulate_media=print parameter if you wish to capture pages in printing mode.

More Metadata: Using the json=true parameter now returns details regarding to the page and server response, as well as the CDN url of the captured image as it always did.

Better Error Reporting: The new API is more transparent regarding to the errors caused by the remote server or on our end. You can work around errors more easily due to this granular error information.

Ability To Capture Error Pages: The previous API would only capture pages with status code of 200-299, now you can override this behavior using allow_failed=true parameter.