Telerik Document Processing Libraries
Progress's .NET libraries for creating, editing and converting PDF, Word and Excel files with no Office, Acrobat or UI dependency.
Operated by Progress Software Corporation
Where your files are processed
No server involved
A set of .NET libraries compiled into the application you build. The vendor makes the point explicitly — no Microsoft Office or Adobe Acrobat installation is required and the libraries are UI-independent — so there is no vendor service and no document ever leaves the process it runs in. 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 is an embedded .NET library, so documents are processed inside the application that hosts it. That describes the library and not the application: the absence of an Office or Acrobat dependency does not establish an absence of network traffic, and the official documentation covers accessible output, GenAI insights, timestamp servers and external signing, each of which is a configured external path rather than a local document operation. Whether a given deployment contacts anything is a property of how it is configured.
What it does
The Telerik Document Processing Libraries are a set of .NET libraries — five of them, covering PDF, Word, spreadsheets, streaming spreadsheets and ZIP — for generating, reading, editing and converting business documents inside an application, with no installation of Microsoft Office or Adobe Acrobat and no user interface involved. The PDF library creates and edits documents, imports existing ones, fills form fields, applies digital signatures and extracts and searches content, and the product line includes a claim to generate accessible PDFs. It is sold both on its own and as part of Progress's larger DevCraft developer bundles, which is the practical detail that decides what it costs.
Best for: Teams already building on .NET who need documents produced or manipulated server-side as part of an application — reports, invoices, exports, batch conversion — without licensing desktop software on the server or driving Office through interop. The absence of UI dependencies is the point: it works in a service, a function or a container. It is a good fit for an organisation already using other Telerik or Kendo UI components and a harder sell for anyone who only needs one PDF library and would otherwise buy a bundle to get it.
Worth knowing: There is no standalone price published on the pages read, and the route the site leads with is the DevCraft bundles, which run from $1,149 to $1,649 per developer per year depending on tier. That is a large bundle covering UI components far beyond document processing, so buying it for these libraries alone means paying for a great deal you may not use — and because the bundles are licensed per developer per year, cost scales with team size rather than with usage. A 30-day trial with support and no credit card is offered. The accessibility capability is a single bullet reading "Generate accessible PDFs", and it should be read with the same care as every other accessibility claim in this index: a library can produce correctly tagged output, but whether a document is genuinely accessible still turns on judgements a generator cannot make, which is what the accessibility guide is about. The AI and agent tooling described on the product page is newer than the document libraries themselves, and the pages read do not document what it does beyond a summary. And because the suite is five libraries rather than one, what is included at a given licence level is worth confirming rather than assuming. Accessible output is a documented capability rather than a certificate: generating tagged or PDF/UA output does not mean the document passes accessibility testing, and the GenAI, timestamp and signing features are configured paths with their own endpoints.
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 · Self-hosted
- Website
- telerik.com
- Requires an account
- Not applicable
- Free tier
- Not verified
- Watermark on the free tier
- Not verified
- Maximum file size
- Not verified
- Batch processing
- Yes
- Data residency
- Not verified
- Open source
- No
- Self-hostable
- Yes
- Licence
- Commercial. The product page states the libraries are also included in Progress's DevCraft bundles, which the purchase page prices per developer per year; a standalone price and licence terms are not given on the pages read.
- Redaction
- No redaction feature
- Programmatic access
- Embeddable library
- Last availability check
- Responded in 162 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.
What that does not establish: Recorded as `none` on absence, and the evidence is weaker here than on most `none` verdicts in this index — which is why it is stated rather than glossed. The vendor's PDF capability list is six bullets: create and edit PDFs, import existing documents, fill PDF forms, add digital signatures, extract and search content, and generate accessible PDFs. Redaction appears nowhere in it, and neither does anything else that removes content. What it does not establish: that a document-manipulation library cannot delete content, because editing a PDF and removing content from it are the same operation at the API level even when no redaction feature is advertised. A six-item summary is not a feature matrix, and the full API documentation was not read. Anyone for whom content removal matters should check the API reference rather than trust this absence.
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.
-
“Create, edit, convert and analyze PDF, Word and Excel documents in any .NET app—without Microsoft Office, Adobe Acrobat or UI dependencies.”
Checked by us — the source says this Read 22 September 2026
Present verbatim as the page's headline, and corroborated twice more on the same page: a section headed "No Third-Party Dependencies" says the libraries "Enable document manipulation within your application without relying on 3rd party software such as Microsoft Office or Adobe Acrobat Reader", and the UI-independence section says they are decoupled from UI and can be deployed in client, server-side and cloud applications. That combination — no desktop dependency, no UI thread — is the substantive claim and it is the reason a reader would choose this over driving Office through interoperation on a server, which is the alternative most .NET teams are trying to escape.
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
- 40a05d67e0d6def14435a847234b9201ab0fb382d56e504207676f8146a26c33
How we checked: https://www.telerik.com/document-processing-libraries rendered in headless Chrome with scripts/render-page.mjs on 2026-09-22 (visible text 4820 bytes) and the claim checked against that rendered text, including the capability list and the UI-independence section beneath it. sourceHash is the SHA-256 of that text.
-
“Generate accessible PDFs”
Checked by us — could not be settled Read 22 September 2026
Present verbatim as one of six bullets under "Key Capabilities" for PDF Processing, and it is the entire accessibility claim on the page — no standard is named, no conformance level is given, and no documentation for the feature is linked from here. Recorded with a verdict of unverifiable rather than confirmed because the strong reading of the bullet is not supported: a library can tag structure as it writes, which is genuinely valuable and is the better answer to accessibility, but whether a document is accessible still depends on judgements software cannot make — whether alternative text describes its image, whether a reading order makes sense. That is the argument the accessibility guide makes at length and the reason the axis4 records in this index are careful about their own checkers. The capability is real enough to earn the accessibility job tag; the conformance implication is not established.
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
- 40a05d67e0d6def14435a847234b9201ab0fb382d56e504207676f8146a26c33
How we checked: Same rendered page and hash as the claim above; the bullet was read in the PDF Processing capability list, and the page was searched for any further detail about accessibility support beyond the bullet itself.
-
“30-day FREE trial including technical support. No credit card required.”
Checked by us — the source says this Read 22 September 2026
Confirmed verbatim on the product page. The trial terms matter more than usual here because the pricing model is a bundle: a reader evaluating these libraries is being asked to assess a component of a much larger product, and 30 days with support and no card is the only way to do that before committing to a per-developer annual bundle. The purchase page read in the same session lists DevCraft UI at $1,149, DevCraft Complete at $1,299 and DevCraft Ultimate at $1,649 per developer per year, with the document processing libraries attributed to the UI tier. Those figures are recorded here and in watchOutFor rather than in priceFromGbp, because the cheapest way to buy the libraries on their own was not established — see internalNotes.
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
- 40a05d67e0d6def14435a847234b9201ab0fb382d56e504207676f8146a26c33
How we checked: Same rendered page and hash as the claims above; the trial terms were read from the page and the bundle pricing was taken from https://www.telerik.com/purchase.aspx rendered in the same session (visible text 5127 bytes), where the DevCraft tiers are given per developer per year.
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.
Visit Telerik Document Processing Libraries Report a problem
Related reading
- Checking a PDF for accessibility — what makes a PDF accessible, and how it is checked.
- Which PDF tools keep your file on your machine — what we count as processing on your own device.