- What to check before you move off Apryse
- Full PDF SDKs for web, mobile and server
- Viewers, document APIs and leaner libraries
- Browser viewer or server engine
- A whole suite, one component or a free embed
- Licences, hosting and who's behind the code
- An hour with your own files
- What the bill depends on
- Picking by how your app handles documents
Apryse, formerly PDFTron, sells developer SDKs for building PDF viewing, editing, annotation, redaction and OCR into your own app. Its alternatives come in three types: commercial PDF SDKs that span web, mobile and server, viewer components and document APIs, and leaner options such as a C library or Adobe's free embed API.
Swapping a PDF SDK isn't like swapping a note-taking app. The viewer sits inside your product, your code calls its API all over the place, and your customers look at its toolbar every day. Get the replacement wrong and you'll be rewriting the integration twice. So before any names, pin down what the new tool has to do on day one.
What to check before you move off Apryse
- Where the PDF work happens: in the user's browser, on your server, in a mobile app or on a desktop. Write down every platform you ship today, because each SDK family covers its own set.
- Which features your code calls now. List the real calls (viewing, annotation, form filling, redaction, OCR, signatures, data extraction), not everything on Apryse's product menu.
- Whether redaction removes the content. Redact a line in a test file, save it, then open it in another reader and try to search for or copy the hidden text.
- How it copes with your worst files: scanned pages, huge drawings, broken forms and output from old software. A tidy demo PDF proves nothing.
- Who owns it. Apryse also owns PDF.js Express and iText, and Pdftools says it's joining Apryse, so moving to one of those keeps you with the same company.
- Whether you can run it on your own servers, use it as a hosted API, or both, and what your security team will accept for the files you handle.
- What happens to existing annotations. If users have built up comments and markups, test that the new viewer can read them and save them back in a form you can migrate.
- How you'll be charged and on what basis. Read each vendor's pricing page and get the answer in writing before a single line of code changes.
If two of those answers knock a tool out, good: that's the shortlist doing its job. A product that misses a platform you ship, or fails the redaction test, is gone however polished its demo looks.
Full PDF SDKs for web, mobile and server
Nutrient
Web, mobile and server SDKs with a web viewer, document authoring and markup, sold for building PDF features into your own apps.
Foxit PDF SDK
One SDK family covering Web, Windows, Mac, Linux, Android and iOS, handling viewing, rendering and digital signatures.
ComPDF SDK
Web, Server, Mobile and Desktop PDF SDKs sit next to a cloud API and a self-hosted option for adding PDF features to apps.
Datalogics PDF SDK
Built on the Adobe PDF Library engine, it bundles PDF SDKs, command line tools and REST APIs for editing, securing and automating PDFs.
LEADTOOLS
A document imaging SDK that puts a viewer, editor, annotations and eSignature components next to OCR and barcode recognition.
Viewers, document APIs and leaner libraries
Syncfusion PDF Viewer SDK
An embeddable viewer component for opening, annotating, filling forms in and signing PDFs inside web and other apps.
Accusoft PrizmDoc
A collection of REST APIs for secure document viewing and processing in web apps, with redaction and annotation included.
MuPDF
Fast C library for managing PDFs, with bindings for Python, Node.js and C#, and its own PDF WebViewer.
Adobe PDF Embed API
Adobe's JavaScript API for dropping a PDF viewer into a web page, with collaboration features and analytics on top.
DynamicPDF
Generator, merger, converter and viewer components as .NET, Java and COM libraries, alongside a hosted API.
Browser viewer or server engine
Apryse's own range spans both sides: WebViewer for the browser, plus server, mobile, document scanner, barcode and data capture SDKs. So the first thing to settle is which half you're replacing. It might be one, it might be all of it.
A viewer SDK lives where the user is. It renders the page in the browser or app, and the user reads, highlights, comments, fills in a form or signs. A server library works where nobody's watching: it merges, converts, redacts in batches, stamps, secures and pulls data out of files before they're stored or sent on. Some vendors sell both, which means one contract can cover the whole job. You don't have to buy that way, though. A viewer component on the front and a separate processing library on the back is a perfectly sensible stack, and it can be easier to replace one part later.
A quick way to see which you need: sketch your document flow on paper. Where does a file come in, who looks at it, what happens to it before it's saved, and what leaves the system at the end? Mark each step as viewing or processing. If almost every box says processing, you're shopping for a library or API, not a viewer.
A whole suite, one component or a free embed
A suite gives you one vendor, one support desk and one set of docs across web, mobile and server. That's tidy, but you're trading one large dependency for another of similar size, and the next move will be just as hard.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
A component does a narrower job and does it inside your existing app. Syncfusion's PDF Viewer SDK, for one, lists highlights, sticky notes, freehand drawing and comment threads as built-in viewer features. If your users only ever view and mark up, that's the size of tool to look at first, and it leaves your server side untouched.
Then there's the embed. Adobe's PDF Embed API is a free JavaScript embed, which makes it the no-cost baseline for simple viewing. Before you pay for any viewer, ask an honest question: do your users only read these documents? If they do, try the embed first and check its feature set against your list. If they redact, edit or sign, you'll need something with those features built in.
Licences, hosting and who's behind the code
Read the licence of any library you put inside a product you sell, and read it for distribution, not just for development. A library that's fine on an internal tool can carry very different terms once it ships inside your customers' copies of your software. Have whoever signs contracts read it before your developers fall in love with the API.
Hosting is the other fork. A hosted API is quicker to wire in, but your files leave your servers to be processed. A self-hosted library or server keeps them at home and puts the upkeep on your team. ComPDF, as one example, offers a monthly allowance of free API calls on its portal and also sells a self-hosted deployment, so you can start hosted and move later. If your files hold contracts, ID documents or financial records, ask each vendor where processing happens and how long files are kept, then check that answer against what your own customers have been promised.
And look at ownership. Apryse has gathered several PDF brands, so a tool that looks independent may not be. PDF.js Express runs on a page that says it's powered by Apryse, iText sits in Apryse's product menu, and Pdftools says it's joining. That's why none of those are on this list. If the reason for leaving is the vendor, check the footer and the about page before you shortlist.
An hour with your own files
Demos are built on files that behave. Yours won't, so test with them. Pick five ugly ones: a scanned contract, a large drawing, a form someone filled in on an old tablet, a file with existing annotations, and the biggest file in your system. Load each one into each shortlisted tool's demo or trial build.
Time how long the first page takes to appear. Zoom right in on the drawing. Fill the form, save it, close it and reopen it somewhere else. Redact a line, then search for the text. Add a comment, export, and open the result in a different reader to see if it survived. Do it again on a phone if you ship mobile. Keep a plain pass or fail grid; it's the most useful document you'll have when you sit down to decide.
Then take the two survivors into a small spike in your real codebase. Swap the viewer on one screen, or route one batch job through the new library, and note every call you had to change. That count tells you more about the move than any sales deck, and it gives you a real estimate to put in front of whoever approves the budget.
What the bill depends on
Licence prices for the SDKs here aren't printed on their product pages, so you'll be asking. DynamicPDF is the one that shows a monthly from-price for its hosted API on its own site. For everything else, go to each vendor's pricing page and, where there isn't a public figure, ask for a quote based on your platforms and your expected volume.
Ask exactly how usage is counted for your deployment, because the answer decides the bill far more than the headline figure does. Ask what happens when you add a platform, a second app or a new region, and whether moving from a trial to production changes the terms. Where a vendor offers a trial, run the hour test above inside it rather than on a demo page.
Picking by how your app handles documents
If your users view, annotate and fill forms in the browser and nothing else, I'd start with a viewer component and leave the server alone. If you ship on web, mobile and server and want one vendor for all three, a commercial multi-platform SDK is the fair swap, and the ownership check matters most there. If you only display documents on a site, try the free embed before paying for anything.
If the real work happens on the server, look at processing libraries and hosted document APIs first; my guide to the best PDF APIs compares that side in more depth, and if you mainly create documents from data, the round-up of the best PDF generation APIs is the closer match. And if it turns out your team just needs to edit files on their own machines rather than inside an app, you don't need an SDK at all.
Do you make PDF SDKs, viewers or document APIs? Tool makers can ask to be considered for a featured place on this list.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.


