Skip to content
dialegein

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.

Jobs Edit Convert Extract Accessibility Merge Sign Protect

Operated by Progress Software Corporation

Visit Telerik Document Processing Libraries

Opens the vendor's own site.

Jobs covered

Open a task to see exactly what the vendor documentation supports.

Edit Browse all edit tools

editing documents with the Telerik Document Processing Libraries, where the RadPdfProcessing overview documents creating, importing and editing PDF documents, adding text, images, shapes, tables, lists, forms, annotations and bookmarks, updating selected content and interactive forms that can be created, filled, extracted, flattened and signed, the RadWordsProcessing overview documents creating and editing RadFlowDocument content including text, structure, formatting, tables, images, fields and hyperlinks, and the RadSpreadProcessing overview documents creating and editing workbooks with formulas and formatting; the scope records the documented in-process .NET editing and form operations, with no user-interface claim and no claim to edit formats beyond those the libraries document

Convert Browse all convert tools

converting documents with the Telerik Document Processing Libraries, where RadPdfProcessing imports PDF into RadFixedDocument and exports it to PDF or plain text, RadWordsProcessing imports supported word-processing formats and exports to DOCX, RTF, HTML, TXT or PDF and converts between supported formats, and RadSpreadProcessing imports and exports XLSX, XLSM, XLS, CSV, TXT and JSON and exports to PDF; the PDF format provider settings also document compliance levels including PDF/A and the accessibility-related PDF/UA target, and the scope records the documented conversion directions and conditions with no fidelity guarantee and no format outside those libraries

Extract Browse all extract tools

extracting content from PDFs with the Telerik Document Processing Libraries, where the product page lists Extract and search content among the PDF capabilities, the RadPdfProcessing overview documents exporting PDF content to PDF or plain text and extracting data from interactive forms, and the PDF library documents text extraction and search through its document model; the scope records the documented text and form extraction and search, makes no OCR claim and claims no structure or accuracy beyond the documented APIs

Accessibility Browse all accessibility tools

generating accessible PDF output with the Telerik Document Processing Libraries, where the RadPdfProcessing accessibility documentation says accessible output must target PDF/A-1a, PDF/A-2a, PDF/A-3a or PDF/UA-1 by configuring the export compliance level and tagging strategy, that RadFixedDocument auto-tagging is off by default and the structure tree can be built manually or tagged automatically, and the accessibility conformance report says PdfProcessing supports tagged authoring when meaningful structure and descriptions are supplied, WordsProcessing-to-PDF is partially tagged with tables and links not tagged, SpreadProcessing-to-PDF is untagged, DOCX/XLSX/RTF conversion preserves alt text and screen tips but not document language, and automated PDF/A and PDF/UA validation does not establish meaningful alternate text, logical heading order or natural reading order; the scope records documented generation of accessible output and does not claim accessibility certification, conformance or a compliance guarantee

Merge Browse all merge tools

merging and splitting PDFs with the Telerik Document Processing Libraries, where the RadPdfProcessing overview documents merging, splitting and appending PDF content, and the PdfStreamWriter documentation documents merging pages from different PDF documents, splitting PDF document pages, adding and positioning page content from existing PDFs and generated pages, and combining content from existing pages and new RadFixedPage instances in a new PDF stream, while noting that existing page content stays unmodified and can only be positioned in the new file; RadWordsProcessing also documents merging documents with style resolution, and the scope records the documented merge, split and append operations with no claim about preserving signatures, forms, links or annotations across a merge

Sign Browse all sign tools

signing PDFs with the Telerik Document Processing Libraries, where the RadPdfProcessing digital signature documentation says the feature signs and validates PDF documents, that a signature confirms the content came from the signer and has not been modified, that validity depends on unchanged content and a certificate chain resolving to a trusted root, and that the library uses X.509 certificates, certificate chains, trusted roots and revocation checks for signing and validation, with signature fields, signing documents with predefined signature fields, verifying existing signatures and multiple digital signing; the product page also lists timestamp servers and external signing, and the documentation says certificate issuance and certificate-authority management are outside the library scope, so the scope records the documented signing and validation and makes no certificate-authority, timestamp-authority or independent trust guarantee

Protect Browse all protect tools

protecting PDFs with the Telerik Document Processing Libraries, where the PdfFormatProvider settings documentation documents encryption import and export with the IsEncrypted option, the EncryptionType values AES256, AES128 (introduced in Q4 2025) and RC4 as the default, a UserPassword and an OwnerPassword, and UserAccessPermissions governing printing, copying and modifying operations, and the RadPdfProcessing overview documents password protection for importing encrypted documents and exporting password-protected documents with supported algorithms; the scope records the documented password, encryption-type and user-access-permission settings and notes that compliance levels other than none exclude encryption, making no claim about how other readers enforce the permissions

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 commercial set of five UI-independent .NET libraries - 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 libraries target .NET Standard 2.0, .NET 8 and .NET 10 and are embedded in the customer's own .NET applications.

The PDF library creates and edits documents, imports existing ones, fills and flattens forms, applies and validates digital signatures, extracts and searches content, merges and splits pages, protects documents with passwords and can generate accessible output. The product is not sold with a published standalone price on the pages read; it is included in Progress's DevCraft bundles, which run from USD 1,149 to USD 1,649 per developer per year depending on tier, and a free 30-day trial includes technical support with no credit card required.

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 published standalone price for the libraries on the product, documentation or purchase pages read. The route the site leads with is the DevCraft bundles, currently DevCraft UI at USD 1,149, Complete at USD 1,299 and Ultimate at USD 1,649 per developer per year, and the libraries are included in those bundles and in other Telerik products; a DevCraft price is therefore the price of a large bundle containing UI components and far more than document processing, not a standalone DPL price.

The bundles are licensed per developer per year, so cost scales with team size rather than usage. A 30-day trial with technical support and no credit card is offered, which is a trial rather than a free tier.

The suite is five libraries, and the AI agent tooling described on current pages is newer than the document libraries and is not itself one of the five. The accessibility claim is documented generation, not certification: accessible output requires targeting PDF/A-1a, PDF/A-2a, PDF/A-3a or PDF/UA-1 and configuring compliance level and tagging, the auto-tag option is off by default, and the accessibility conformance report says WordsProcessing-to-PDF output is partially tagged with tables and links not tagged, SpreadProcessing-to-PDF output is untagged, and automated PDF/A and PDF/UA validation does not establish whether alternate text is meaningful or headings are in a logical order.

Digital signatures use X.509 certificates, chains, trusted roots and revocation checks, but certificate issuance and certificate-authority management are outside the library scope, and timestamping and external signing are configured paths rather than included trust services. Password protection documents AES-256, AES-128 and RC4 settings and user-access permissions, but PDF/A-compliant documents exclude encryption.

These are in-process .NET libraries consumed by a host application, not a hosted API, cloud service or self-hosted server product.

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
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
Self-hosted
Open source
No
Self-hostable
Yes
Licence
Commercial.

Commercial. Telerik Document Processing is a commercial five-library .NET suite and is included in Progress's DevCraft bundles, currently DevCraft UI at USD 1,149, Complete at USD 1,299 and Ultimate at USD 1,649 per developer per year, and in other Telerik products such as UI for ASP.NET Core and UI for Blazor.

No standalone DPL price is published on the product, documentation or purchase pages read, so no standalone figure is recorded; the DevCraft prices are bundle prices and are not used as the price of the libraries alone. A free 30-day trial including technical support and requiring no credit card is offered for evaluation, and commercial use requires a Telerik licence under the Telerik commercial licence agreement.

The libraries target .NET Standard 2.0, .NET 8 and .NET 10 and run inside the customer's application; there is no hosted or self-hosted service component.

Redaction
No redaction feature
Programmatic access
Embeddable library
Last availability check
Responded in 375 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.

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.

https://www.telerik.com/document-processing-libraries

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
    Read
    https://www.telerik.com/document-processing-libraries
    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.

    What this hash proves, and what it does not

  • “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
    Read
    https://www.telerik.com/document-processing-libraries
    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.

    What this hash proves, and what it does not

  • “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
    Read
    https://www.telerik.com/document-processing-libraries
    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.

    What this hash proves, and what it does not

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

How this record was put together

Editorial review.
No editor has signed this record off. That is not the same as nothing having been checked, and the lines below say what has.
Source reading.
3 claims taken from the vendor's own pages, read between 22 September 2026 and 22 September 2026.
Website availability.
The vendor's site was last checked on 21 October 2026.
Behaviour testing.
We ran this ourselves. The file handling was watched directly.

Sources: telerik.com, read 2026-09-22 with headless Chrome: the Document Processing Libraries product page (visible text 4820 bytes), including the headline, the five libraries, the PDF capability list and the UI-independence sections, and the purchase page at telerik.com/purchase.aspx (5127 bytes) for the DevCraft tier pricing. Vendor documentation, not independently tested; no trial was started, no library was installed and no document was produced.