Apryse
Commercial PDF SDK best known for WebViewer, its in-browser document SDK.
Operated by Apryse
Opens the vendor's own site.
Jobs covered
Open a task to see exactly what the vendor documentation supports.
Edit
Browse all edit toolsediting text and images directly within PDF files using WYSIWYG PDF content editing in the Apryse WebViewer JavaScript library from version 10.3, changing, replacing, deleting, moving, resizing and reformatting existing content and adding new paragraphs and images, as a separate PDF Editing add-on that works with PDF files only
Protect
Browse all protect toolspassword-based PDF encryption with user passwords at AES-128 or AES-256, and setting permissions that the Standard Security Handler records but does not enforce, requiring the Full API and Security package for production use, in Apryse WebViewer
Sign
Browse all sign toolsdigitally signing and certifying PDFs in Apryse WebViewer, using PKI signing with PFX digital certificates or self-signed certificates, importing and exporting signature fields and data through XFDF or FDF, and signing with images, ink annotations or custom appearances, with document timestamping and long term validation documented as separate features and the Digital Signature package required for production use
Convert
Browse all convert toolsdocument conversion between PDF, XPS, EMF and WMF, SVG and raster images, including HTML to PDF, XPS or SVG, through the server and desktop SDK and its conversion tools
OCR
Browse all ocr toolsOCR through the server and desktop SDK and its optional OCR module, producing searchable text from images or PDFs
Compress
Browse all compress toolsoptimising PDF file size through the server and desktop PDF Optimizer: redundant resource removal, data stream and image compression, and optional downsampling
Where your files are processed
Mixed - depends on version and feature
The vendor's own documentation separates them. On the device: Apryse SDK linked into an application, and the configured client-side WebViewer. On their servers: Server-backed viewers, hosted products and any configured service. A single answer for the whole product would be wrong for one of them. That is a property of the library itself: what an application built with it does with your file depends on that application, not on this.
It depends on the deployment. The SDK is linked into the application and runs where that runs, and the client-side WebViewer can be configured to work in the browser, while server SDKs and server-backed viewers process on a server and hosted products have their own terms.
Multiple regions is not a meaningful guarantee at family level, so it is not recorded as one. Applied redaction and sanitisation are distinct operations, and removal is attributed to the documentation until outputs are tested.
What it does
Apryse, formerly PDFTron, sells a document SDK family built around WebViewer, a JavaScript viewer and editor that runs in the browser. With the Full API option enabled, WebViewer loads a WebAssembly build of Apryse's C++ engine so tasks such as redaction and encryption can be done entirely on the client.
Server, mobile and desktop SDKs cover the same ground for other architectures, and the company also owns the Xodo end-user apps.
Best for
Teams that need a mature commercial SDK with a genuine in-browser engine for destructive redaction and encryption, and that can accept a negotiated, usage-metered licence.
Worth knowing
The only published figure is a vague 'starting as low as $1,500' with no unit stated, and the licence meters document events, so real cost depends on contract terms only sales can give you. The licence also forbids shipping it as a stand-alone PDF application that could compete with an Apryse product.
The official pricing guide states entry packages from $1,500 a year, while the actual feature, deployment and volume pricing requires a quote, so the unit is known and the figure is not. The evaluation documentation establishes watermarking, but the trial, key and product should be identified rather than treating every trial as identical: the WebViewer documentation describes a seven-day keyless evaluation, and the no-tracking demo key is a separate option.
An account need distinguishes buying or licensing from evaluating or using an integrator’s viewer. Windows and macOS belong in the scope where the full SDK family is described, and a concrete REST product would be needed before assigning HTTP API access.
The contract should be verified before asserting event metering or a universal prohibition on standalone PDF applications, because the surfaced terms are product-specific for one viewer while the core SDK documentation expressly supports standalone commercial applications. The estimate that it roughly doubles download size needs a current version or build measurement.
The entry package is a base rather than the whole SDK: DOCX editing, spreadsheets, digital signatures, smart data extraction, PDF editing and conversion are all named as strategic add-ons to it, and the pricing page says the figure depends on features, document volume and whether you deploy server side or client side.
Details, and where each comes from
Vendor statements, our own reading of their pages, and the things nobody has established yet, each answered separately. Where we have not confirmed something it says so rather than guessing, and a row nobody has established is greyed out.
- Versions covered
- Web · Linux · iOS · Android · API · Self-hosted
- Website
- apryse.com
- Requires an account
- Not applicable
- Free tier
- No
- Watermark on trial output
- Not verified
- Maximum file size
- Not verified
- Batch processing
- Not verified
- Data residency
- Multiple regions
- Open source
- No
- Self-hostable
- Yes
- Licence
- Proprietary commercial, term subscription metered by document events
- Redaction
- Removes the content
- Programmatic access
- Embeddable library · Browser JavaScript
- Last availability check
- Responded in 156 ms 21 October 2026
Checked automatically by our own runner, not reported by the vendor. 100% of our last 30 checks got a response.
What the redaction verdict rests on
From the vendor's own documentation, read 22 September 2026. Not tested by us.
“Apryse SDK’s Sanitizer ensures that if specified content categories are present in a document, the content is permanently destroyed, not simply disabled or obscured.”
What that does not establish
THE STRONGEST WORDING IN THIS BATCH, AND ABOUT A DIFFERENT API. This is the Sanitizer, which destroys specified content categories such as metadata and embedded scripts.
The marked-area redaction this verdict is about is the Redactor, documented separately. So the quote establishes that Apryse destroys rather than obscures when the Sanitizer is called - not that Redactor does.
It should be replaced with the Redactor documentation.
What the vendor says
Claims are labelled rather than repeated as fact. Where we have checked something ourselves, it says so and shows when. Checked means we read the vendor's own page and it says what we recorded - not that we tested the behaviour, unless the note says we did.
-
“entry-level pricing for simple use cases starting as low as $1,500”
Checked by us - the source says this Read 22 September 2026
Confirmed verbatim: the sentence appears unaltered in an FAQ answer, and the same figure appears independently in the page's opening copy as "Entry-level packages from $1,500 and scale as your product grows". One thing the claim does not carry and the page does not supply: a period.
"$1,500" is given with no indication of whether that is per year, per developer or one-off, and for a tier whose purpose is to tell a buyer what entry costs, a figure without a billing basis is only half an answer. That gap is the vendor's, not ours - the claim quotes them exactly - and it is recorded here rather than smoothed over.
Currency is also implied rather than stated. No purchase was made and no control was run.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- b8c7bdea0307a1bb803c368aba646e11f83f5b5cce88931c318e995fc3350d3d
How we checked
Re-verified verbatim on 2026-09-22: https://apryse.com/pricing re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-apryse-com-pricing-5bf87b11.txt.
-
“Tasks that previously would have required a server can now be done completely client side.”
Checked by us - the source says this Read 22 September 2026
Confirmed verbatim: the sentence is the page's own description of the full API WebAssembly module. What a reader needs is that it describes an optional module rather than a property of the product.
The same page says the full API is not available when the document is loaded on a server, and that passing the fullAPI option makes WebViewer "automatically switch to client side document handling after the initial load", so the client-side behaviour is a configuration and a document-loading question. It also states the trade-off plainly: the full API module is "~2-3 times larger than the default client-side module that only supports rendering", which slows start-up, and recommends a custom server for mobile devices and older browsers because performance "may not be acceptable" there.
So "completely client side" is true of a configuration that costs load time, and the vendor's own advice is to move processing back to a server for some users. Recorded as the vendor's description of their SDK; we have not run WebViewer and no control was run.
Standing: Re-read, and the recorded hash was not reproduced
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 51afc495e8182bdbd47a51381b43a01170baa2546ac3f586535ee928243d7a7d
- Note
- the rendered page now opens with a cookie notice that was not present when it was read, so the rendered text differs from the first character. Not re-read for the claim itself.
How we checked
Re-verified verbatim on 2026-09-22: https://docs.apryse.com/web/guides/full-api-overview re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-docs-apryse-com-web-guides-full-api-overview-e4ea610a.txt.
Each claim is quoted from the vendor's own pages. This section describes what we have and have not checked - it is not a judgement about anyone.
Sponsorship is distribution, not an endorsement or a promise of search rankings, AI citations, traffic, or sales. This listing is a free entry, compiled from published sources.
Related reading
- Which PDF tools really redact - which tools remove the content rather than cover it.
Compared head to head
- Apryse vs iText Two developer PDF libraries, and one company owns both.