| title | Introduction |
|---|---|
| page_title | Welcome to Telerik Document Processing Libraries |
| description | Telerik Document Processing is a bundle of UI-independent, cross-platform libraries that let you create, import, modify, and export flow, fixed, and spreadsheet document formats without external dependencies. |
| slug | introduction |
| tags | document, processing, pdf, docx, xlsx, telerik, libraries, dotnet |
| published | true |
| position | 0 |
Telerik Document Processing is a bundle of UI-independent, cross-platform libraries that let you process the most commonly used flow, fixed, and spreadsheet document formats for web and desktop. The Document Processing libraries allow you to create, import, modify, and export documents without relying on external dependencies like Adobe Acrobat or Microsoft Office.
{% if site.has_cta_panels == true %} {% include cta-panel-introduction.html %} {% endif %}
Telerik Document Processing features the following libraries:
| Feature | Description |
|---|---|
| UI-Independent | The libraries are UI-Independent and cover all .NET technologies, from desktop and web to mobile, and can be deployed in client, server-side and cloud apps. |
| No Need for Third-Party Software - No Server Deployment Fees | Enable document manipulation within your application without relying on third-party software such as Microsoft Office or Adobe Acrobat Reader. |
| Convenient API | Add document processing capabilities to your applications quickly by using the convenient APIs. Create, edit, and convert documents with a few lines of code. |
| Performance and Speed | The libraries are decoupled from UI and deliver great performance in different cases, especially when you work with large Excel files. |
| Any Document. Any Business. | Telerik Document Processing is suitable for various business cases and scenarios where document creation or manipulation is required. |
| Support for a Variety of File Formats | Telerik Document Processing includes five libraries for manipulating Office Open XML document formats and PDF documents in your application. |
| Timeout Mechanism | The [document import and export timeout mechanism]({%slug timeout-mechanism-in-dpl%}) applies to importing and exporting documents. The Import and Export methods of all FormatProviders have a mandatory TimeSpan? timeout parameter after which the operation is cancelled. |
| GenAI-powered Document Insights | Extract insights from PDF documents using Large Language Models (LLMs). This feature lets you summarize document content and ask questions about it, with the AI providing relevant answers based on the document content. [Explore GenAI-powered PDF document insights]({%slug radpdfprocessing-features-gen-ai-powered-document-insights-overview%}) |
| AI Coding Assistant | Provides specialized context to AI models, enabling them to produce higher-quality code samples. [Learn about the Document Processing AI Coding Assistant]({%slug ai-coding-assistant%}) |
| Automatic Output Stream Clearing on Export | Automatically clears the output stream before writing new content. [Review automatic output stream clearing during export]({%slug common-export-output-stream-clearing%}) |
For more details about the benefits of using Telerik Document Processing, see the Telerik Document Processing product overview page.
The Telerik Document Processing libraries support the following file formats:
| Format | Library | Provider |
|---|---|---|
| DOCX (Word Document) | [RadWordsProcessing]({%slug radwordsprocessing-overview%}) | [DocxFormatProvider]({%slug radwordsprocessing-formats-and-conversion-docx-docxformatprovider%}) |
| DOC (Word 97-2003 Document) | [RadWordsProcessing]({%slug radwordsprocessing-overview%}) | [DocFormatProvider]({%slug radwordsprocessing-formats-and-conversion-doc-docformatprovider%}) Import only |
| DOT (Word 97-2003 Template) | [RadWordsProcessing]({%slug radwordsprocessing-overview%}) | [DocFormatProvider]({%slug radwordsprocessing-formats-and-conversion-doc-docformatprovider%}) Import only |
| HTML | [RadWordsProcessing]({%slug radwordsprocessing-overview%}) | [HtmlFormatProvider]({%slug radwordsprocessing-formats-and-conversion-html-htmlformatprovider%}) |
| [RadWordsProcessing]({%slug radwordsprocessing-overview%}) [RadPdfProcessing]({%slug radpdfprocessing-overview%}) [RadSpreadProcessing]({%slug radspreadprocessing-overview%}) |
[PdfFormatProvider in RadWordsProcessing]({%slug radwordsprocessing-formats-and-conversion-pdf-pdfformatprovider%}) Export only [PdfFormatProvider in RadPdfProcessing]({%slug radpdfprocessing-formats-and-conversion-pdf-pdfformatprovider%}) [PdfFormatProvider in RadSpreadProcessing]({%slug radspreadprocessing-formats-and-conversion-pdf-pdfformatprovider%}) Export only |
|
| RTF | [RadWordsProcessing]({%slug radwordsprocessing-overview%}) | [RtfFormatProvider]({%slug radwordsprocessing-formats-and-conversion-rtf-rtfformatprovider%}) |
| TXT | [RadWordsProcessing]({%slug radwordsprocessing-overview%}) [RadPdfProcessing]({%slug radpdfprocessing-overview%}) [RadSpreadProcessing]({%slug radspreadprocessing-overview%}) |
[TxtFormatProvider in RadWordsProcessing]({%slug radwordsprocessing-formats-and-conversion-txt-txtformatprovider%}) [TextFormatProvider in RadPdfProcessing]({%slug radpdfprocessing-formats-and-conversion-plain-text-textformatprovider%}) Export only [TxtFormatProvider in RadSpreadProcessing]({%slug radspreadprocessing-formats-and-conversion-txt-txtformatprovider%}) |
| MD (Markdown) | [RadWordsProcessing]({%slug radwordsprocessing-overview%}) | [MarkdownFormatProvider]({%slug radwordsprocessing-formats-markdownformatprovider%}) |
| XLSX (Excel Workbook) | [RadSpreadProcessing]({%slug radspreadprocessing-overview%}) [RadSpreadStreamProcessing]({%slug radspreadstreamprocessing-overview%}) |
[XlsxFormatProvider]({%slug radspreadprocessing-formats-and-conversion-xlsx-xlsxformatprovider%}) |
| XLS (Excel 97-2003 Workbook) | [RadSpreadProcessing]({%slug radspreadprocessing-overview%}) | [XlsFormatProvider]({%slug radspreadprocessing-formats-and-conversion-xls-xlsformatprovider%}) |
| XLSM (macro-enabled spreadsheet created by Microsoft Excel) Macros are only preserved during import and export. They cannot be executed or changed in the code. | [RadSpreadProcessing]({%slug radspreadprocessing-overview%}) | [XlsmFormatProvider]({%slug radspreadprocessing-formats-and-conversion-xlsm-xlsmformatprovider%}) |
| CSV | [RadSpreadProcessing]({%slug radspreadprocessing-overview%}) [RadSpreadStreamProcessing]({%slug radspreadstreamprocessing-overview%}) |
[CsvFormatProvider]({%slug radspreadprocessing-formats-and-conversion-csv-csvformatprovider%}) |
| JSON | [RadSpreadProcessing]({%slug radspreadprocessing-overview%}) | [JsonFormatProvider ]({%slug radspreadprocessing-formats-and-conversion-json-jsonformatprovider%}) Export only |
| DataTable | [RadSpreadProcessing]({%slug radspreadprocessing-overview%}) | [DataTableFormatProvider]({%slug radspreadprocessing-formats-and-conversion-using-data-table-format-provider%}) |
| ZIP | [RadZipLibrary]({%slug radziplibrary-overview%}) | [ZipArchive]({%slug radziplibrary-gettingstarted%}) |
| Image | [RadPdfProcessing]({%slug radpdfprocessing-overview%}) | [SkiaImageFormatProvider]({%slug radpdfprocessing-formats-and-conversion-image-using-skiaimageformatprovider%}) Export only [OcrFormatProvider]({%slug radpdfprocessing-formats-and-conversion-ocr-ocrformatprovider%}) Import only |
The Telerik Document Processing libraries are available in .NET Framework, {{site.dotnetversions}} (or newer) for Windows and .NET Standard 2.0 (Support for {{site.dotnetversions}}) compatible versions. You can download the references for the libraries from the following products:
| .NET Framework Products | {{site.dotnetversions}} for Windows | .NET Standard |
|---|---|---|
| UI for ASP.NET MVC | UI for .NET MAUI | |
| UI for ASP.NET AJAX | UI for ASP.NET Core | |
| UI for WPF | UI for WPF | UI for Blazor |
| UI for WinForms | UI for WinForms | UI for WinUI |
You can find all packages in the [complete list of available NuGet packages]({%slug available-nuget-packages%}) article.
To start using the libraries right away, follow the [Document Processing first steps tutorial]({%slug getting-started-first-steps%}) to create a sample application that uses the libraries.
Telerik Document Processing is a commercial library. You are welcome to explore its full functionality and get technical support from the team when you register for a free 30-day trial. To use it commercially, you need to purchase a Telerik license. Review the Telerik commercial license agreement to get acquainted with the full terms of use.
Telerik Document Processing is available as part of DevCraft, UI for ASP.NET Core, UI for ASP.NET MVC, UI for ASP.NET AJAX, UI for Blazor, UI for .NET MAUI, UI for WPF, UI for WinForms. The libraries are subject to the license under which you have obtained the packages.
For any issues you might encounter while working with Telerik Document Processing, use any of the available support channels:
- License holders and active trialists can take advantage of our outstanding customer support delivered by the developers building the library. To submit a support ticket, use the Telerik Document Processing support ticket system. Learn [how to get the most out of Document Processing support]({%slug submit-support-tickets%}).
- Our Telerik Document Processing forums are part of the free support you can get from the community and from the team on all kinds of general issues.
- Our Document Processing feedback portal provides information on the features/bugs in discussion and also the planned ones for release.
- You may still need a tailor-made solution for your project. In such cases, go straight to Progress professional services.
- Document Processing online demos
- Document Processing Knowledge Base
- Telerik Document Processing virtual classroom
The documentation for a product is at its best when the content is a collaboration between the builders and consumers of that product. Everybody can play a role in making the documentation better and we encourage you to help with that task in the way that you choose:
- Submit a New Issue at GitHub
If you find an issue with our docs that needs to be addressed, the best way to let us know is by creating an issue in the Telerik Document Processing documentation issue tracker. When creating an issue, provide a descriptive title, be as specific as possible, and link to the documentation in question. If you can provide a link to the closest anchor to the issue, that is even better.
- Update the Documentation at GitHub
Creating an issue is great, but what we really love are pull requests. This is the most direct method. So, if you find an issue in the docs, or even feel like creating new content, we are happy to have your contributions! The basic steps are that you fork our documentation and submit a pull request. That way you may contribute to exactly where you found the error. After that, our technical writing team just needs to approve your change request. Use only standard markdown. For more detailed instructions, follow the GitHub documentation contribution instructions.
- Forums
You can visit the Telerik Document Processing community forum and leave feedback. This method takes a bit longer to reach the documentation team. However, if you need a fast reply from the support team, leaving feedback in the forum guarantees a support number for your suggestions, and that we will follow up on it.
Thank you for your contribution to the Telerik Document Processing documentation!
- [Document Processing Libraries Overview]({%slug getting-started%})
- [First Steps in using Telerik Document Processing]({%slug getting-started-first-steps%})
- [What Versions of Document Processing Libraries are Distributed with the Telerik Products]({%slug distribute-telerik-document-processing-libraries-net-versions%})
- [How to Get the Most Out of the Telerik Document Processing Support]({%slug submit-support-tickets%})