Best PDF SDK – the commercial options, compared honestly

Four vendors show up on most PDF SDK shortlists, and each grew out of a different product: Nutrient from a document viewer, Apryse from document processing, PDFMonkey from hosted HTML templates, and Polotno from a design editor that learned to read PDF. Which one you want depends on what your users do with the file. This page says where each vendor wins, including where we lose. For the open-source libraries, see JavaScript PDF libraries compared.

Four vendors, four different products

Nutrient – viewing, annotation, forms

Formerly PSPDFKit. It renders a document faithfully and lets your users layer things on top: highlights, comments, AcroForm fields, signatures, certified redaction. It ships native iOS and Android SDKs as well. Buy it when your users review and mark up documents. See the Nutrient comparison.

Apryse – document processing at scope

Formerly PDFTron. It covers more ground than anything else on this page: viewing, annotation, forms, OCR, classification, extraction, digital signatures, and PDF/A archiving, across .NET, Java, Python, C++, iOS, and Android. You pay for that range. See the Apryse comparison.

PDFMonkey – hosted HTML templates

You send it an HTML and CSS template plus a JSON payload, and it returns a PDF. There is nothing to embed in your app. It fits when your team already maintains the same content as HTML and your documents run as flowing text. See the PDFMonkey comparison.

Polotno SDK – a design editor that reads PDF

A visual canvas over a JSON design schema. It parses a PDF into editable text, images, tables, and vector paths, and writes vector PDF back out. Buy it when your users design documents inside your product. See the PDF SDK overview.

Ask who owns the layout

If a developer owns it and it never changes, a template service or a drawing library will do. If a document arrives from outside and its internal structure has to survive intact, you want a document library. If a marketer or an end user owns the layout and needs to change it without a deploy, you want an editor, and most PDF SDKs do not compete there at all.

Then ask what happens to the file after that. Reviewing and signing a document is one product. Redesigning it is another. Few teams need both from one vendor, and the ones that do tend to buy two.

Where Polotno is the wrong choice

You need a viewer. There is no read-only viewer component and no annotation layer.
You need interactive forms. AcroForm text imports as static text, and the fields stop being fillable.
You need OCR. A scan imports as images with nothing to edit as text.
You need certified redaction or digital signatures. Deleting an element is an edit, and we will not sell it as a compliance feature.
You need file-level operations. Re-rendering a document through a schema does not compress it.
You are not on JavaScript. There are no Java, .NET, or Python bindings.
Your source is HTML. Polotno renders its own schema, not arbitrary markup.

Any one of those points you at Nutrient, Apryse, or PDFMonkey instead.

Where Polotno wins outright

Your users edit documents in your product. They work on the same canvas Polotno uses for images, text, and video.
A non-developer owns the template. They author it visually, you store it as JSON, and it changes without a release.
Layout is positional. Certificates, tickets, labels, badges, business cards, and packaging get designed rather than typeset, and HTML pagination fights that.
PDF is one output among several. The same design exports PNG, JPG, SVG, HTML, PPTX, GIF, and MP4.
You need print-ready output. CMYK, spot colours, bleed, crop marks, and PDF/X-4 or PDF/X-1a.

A shortlist in four questions

Do your users read, annotate, or sign documents? → Nutrient, or Apryse for the wider platform
Do you need OCR, extraction, or compliance archiving? → Apryse
Do developers own your templates, written as HTML, running as flowing text? → PDFMonkey
Do your users design the document, or does a non-developer own the template? → Polotno SDK

FAQ

Is there a single best PDF SDK?

No. The category bundles four unrelated jobs, and different companies lead each one. Any vendor who tells you otherwise is describing their roadmap.

Which one is cheapest?

Hosted template services cost least to start and enterprise document platforms cost most, but per-seat and per-document pricing make direct comparison misleading. Your bill turns on volume and on whether you also need an editor.

Can I combine two?

Yes, and plenty of teams do. Running a viewer SDK for review workflows alongside a design SDK for authoring is a normal split, because neither category handles the other job well.