Moving off PDFShift

Why teams move

• It converts; it does not hold your documents. Templates, versions and the data contract all stay your problem, which is fine until several documents and several people are involved.
• Rendering is browser-based, so a document is a printed web page and inherits the pagination behaviour that implies.
• Passing HTML per request means assembling markup in your application — string building, escaping, and a template layer you now own and maintain.
• There is nothing to look at. Checking a change means rendering and opening the file, rather than seeing the document as you edit it.

The checkable parts

Claims worth verifying rather than taking on trust — each links to its source, checked July 2026.

• Converts HTML or a URL to PDF; also produces screenshots and images.

  PDFShift ↗

What is different here

When to stay with PDFShift

It is often the right answer. If any of these describe you, this is not a migration worth making.

• You genuinely want a converter — you already have HTML you are happy with and just need it turned into a PDF.
• You need URL-to-PDF or screenshots, which are its own capabilities and not this product's.
• One document, rarely changed, owned by the person who wrote it. Extra machinery would only get in the way.

What moving involves

1. 1 The HTML you currently POST becomes the specification for a template rather than the input to a request.
2. 2 The variables you interpolate into that markup become the schema, and the values become the JSON payload.
3. 3 Your templating layer comes out of the application along with the markup assembly around it.

The API reference covers authentication, the render call and error handling; the template gallery has designs to start from rather than a blank page.

Other migrations