Aspose.PDF
Commercial PDF library and API for .NET, Java, C++ and Python, sold under a perpetual per-developer licence.
Operated by Aspose Pty Ltd
Where your files are processed
No server involved
An in-process library distributed as NuGet, Maven and pip packages, with no vendor service involved in processing. A hosted REST API exists as a separate cloud product and is not what this record describes. 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.
Architectural: an in-process library installed via NuGet, Maven or pip, with no hosted component in the download products. The docs describe it as usable in any .NET or Java application and it loads and saves files from the host application's own filesystem or streams. Aspose separately sells cloud REST APIs, which are a different product with a different host; this record covers the self-hosted libraries.
What it does
Aspose.PDF is a commercial library for creating, editing, converting and securing PDFs from application code, with editions for .NET, Java, C++ and Python plus REST APIs. Its documented feature set is broad: a document object model over pages, text, images, annotations and forms, conversion to and from Word, HTML, XPS, Markdown, OFD and image formats, PDF/A, PDF/X and PDF/UA conformance, encryption, digital signatures with PAdES, and a redaction API that removes the underlying content rather than drawing over it. It runs in-process inside the customer's own application, so documents never leave the customer's infrastructure.
Best for: Teams shipping a .NET, Java, C++ or Python product who need one library to cover editing, conversion, forms, signing and genuine redaction, and who can budget for a perpetual per-developer licence.
Worth knowing: Two things to know before the price. The evaluation mode is both watermarked and limited to the first four pages, so a pipeline tested on a short sample can look as though it works; the vendor documents the limit, and a temporary licence removes the restriction for testing, so the validation requirement is a full-document test rather than a sample one. What exactly happens past page four is not established here: a page limit is not the same finding as a silent truncation, and no versioned test was run. The second thing is that local processing does not mean no external contact at all. The .NET licensing page documents metered-key activation and a licence server, so licensing connectivity is a separate matter from document-content transfer, and that page contains inconsistent grace periods during an outage, which is not published here as settled.
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
- Windows · macOS · Linux · API · Self-hosted
- Website
- products.aspose.com
- Requires an account
- Not applicable
- Free tier
- No
- Watermark on trial output
- Yes
- Maximum file size
- Not verified
- Batch processing
- Yes
- Data residency
- Self-hosted
- Open source
- No
- Self-hostable
- Yes
- Licence
- Proprietary commercial, perpetual per-developer licence in named tiers (Developer, Site, Metered) with the location and commercial-deployment rights set by the tier
- Redaction
- Removes the content
- Programmatic access
- Embeddable library · HTTP API
- Last availability check
- Responded in 138 ms 16 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.
“Use this example when matching text should be covered by redaction annotations before the redaction is permanently applied. … This example permanently applies redaction annotations that already exist on the page. … Call redact() on each collected annotation and save the updated file.”
What that does not establish: Removal is a second step, not the act of adding the annotation. The vendor documents marking text as COVERED, and a separate redact() call as what "permanently applies" it. The three passages above sit under the vendor's own headings, "Mark text with redaction annotations" and "Apply existing redactions", and the fragments are joined with an ellipsis because they are separate passages rather than one sentence. Code that only adds the RedactionAnnotation and saves has drawn over the text and left it in the file. Read from vendor documentation, not tested by us.
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.
-
“The evaluation version of Aspose.PDF for .NET provides full product functionality, but all pages in the generated PDF documents are watermarked with the text "Evaluation Only. Created with Aspose.PDF. Copyright 2002-2025 Aspose Pty Ltd." at the top. In the evaluation version, you can only process the first four pages of a document.”
Checked by us — the source says this Read 22 September 2026
Confirmed verbatim: the claim joins two bullets of the same list, and both appear unaltered — the watermark bullet, quoting the exact text stamped on generated pages, and the page-limit bullet. Two details belong with it. The watermark string in the claim contains a copyright year range, "2002-2025", which is the vendor's current text and will change the moment Aspose updates it; the claim will drift with it, and that is the kind of quotation that silently goes stale. And the two limitations are independent rather than alternatives: an evaluation document is both watermarked and restricted to the first four pages, which is worth knowing because a developer testing page five will see truncated output rather than an error. Recorded as the vendor's documentation; no library was installed 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
- 63b18fb5032260fab6a409d897002b6856e65a4bf80dac2470f1d423c35a6a88
How we checked: Re-verified on 2026-09-22: https://docs.aspose.com/pdf/net/licensing/ re-rendered in headless Chrome with scripts/render-page.mjs and every sentence of this claim found in the rendered text, though not as one continuous passage. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-docs-aspose-com-pdf-net-licensing-4bb5b235.txt.
-
“The Developer Small Business License does not support distribution of end user software to third parties, public facing websites/applications, extranets, multi-site intranets or SaaS project usage scenarios. Only OEM Licenses support this form of distribution.”
Checked by us — the source only partly supports this Read 21 September 2026
The two sentences are verbatim, and the claim's concluding absolute is not supported by the rest of the same page, so this is partial rather than confirmed. Under the Developer Small Business License the page says it "does not support distribution of end user software to third parties, public facing websites/applications, extranets, multi-site intranets or SaaS project usage scenarios. Only OEM Licenses support this form of distribution." But the Developer SDK License row, further down the same page, says it "allows distribution of end user software to third parties, public facing websites/applications, extranets, multi-site intranets or SaaS project usage scenarios", subject to Commercial Deployment conditions and a limit of fifty deployments, with the Site SDK License allowing two hundred and fifty. So the word "Only" is doing more work than the page supports: SDK licences also permit that distribution, conditionally. This matters commercially rather than academically — a reader who takes "only OEM" at face value could buy an OEM licence when an SDK licence would cover them. Recorded as an internal inconsistency in the vendor's own policy page. The claim's first sentence, about the Developer Small Business tier specifically, is accurate as recorded.
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
- 2b3ef2b5161bd4b123fae93472b05fc1ddb25de9f9b3c033eabe0b2010fb41af
How we checked: https://purchase.aspose.com/policies/license-types/ rendered in headless Chrome with scripts/render-page.mjs on 2026-09-21 (visible text 12388 bytes), and the claim checked against that text, including a search for every other licence row that mentions distribution. sourceHash is the SHA-256 of the rendered text.
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
- Checking a PDF for accessibility — what makes a PDF accessible, and how it is checked.
- Which PDF tools really redact — which tools remove the content rather than cover it.
- Which PDF tools keep your file on your machine — what we count as processing on your own device.