The RTF to PDF converter allows you to easily convert RTF strings and documents to PDF with just a few lines of code. The RTF to PDF Converter library for .NET can be linked into any .NET application, either ASP.NET web sites or desktop applications, to add rtf to pdf conversion capabilities to your application.
Classic v14.0 · Windows, .NET Framework 2.0+ and .NET 6–10 · Evaluate without registration — demo mode by default (watermarked) · Licensed with the HTML to PDF Converter license or EVO PDF Toolkit
dotnet add package EvoPdf.HtmlToPdfWindows · .NET Framework 2.0+ and .NET 6–10 (.NET Standard 2.0) · the EvoPdf metapackage bundles the Classic HTML to PDF library
using EvoPdf; var converter = new PdfConverter(); byte[] pdf = converter.GetPdfBytesFromRtfString(rtf); File.WriteAllBytes("document.pdf", pdf);
EvoPdf namespace, one converter class, synchronous calls. API reference →With the RTF to PDF Converter library for .NET you can easily convert RTF strings and RTF files to PDF documents. You can convert the RTF document to a PDF document in a memory buffer or to a PDF file. The integration is extremely easy and no other third party tools are necessary to be installed.
The library is distributed as a simple .NET assembly that you reference in your applications. Samples and documentation are available in the downloadable software package.
EvoPdf.HtmlToPdfEvoPdfPdfConverter protected void btnConvert_Click(object sender, EventArgs e)
{
PdfConverter pdfConverter = new PdfConverter();
pdfConverter.PdfDocumentOptions.PdfPageSize = PdfPageSize.A4;
pdfConverter.PdfDocumentOptions.PdfPageOrientation = PDFPageOrientation.Portrait;
pdfConverter.PdfDocumentOptions.PdfCompressionLevel = PdfCompressionLevel.Normal;
pdfConverter.PdfDocumentOptions.ShowFooter = false;
pdfConverter.PdfDocumentOptions.ShowHeader = false;
byte[] downloadBytes = pdfConverter.GetPdfBytesFromRtfString(MyRTFString);
System.Web.HttpResponse response = System.Web.HttpContext.Current.Response;
response.Clear();
response.AddHeader("Content-Type", "binary/octet-stream");
response.AddHeader(
"Content-Disposition",
"attachment; filename=" + "Rendered.pdf" + "; size="
+ downloadBytes.Length.ToString());
response.Flush();
response.BinaryWrite(downloadBytes);
response.Flush();
response.End();
}The Classic library is a managed .NET assembly plus a Windows rendering engine shipped inside the NuGet package — nothing to install on the server, xcopy deployment, works in Azure Cloud Services and Virtual Machines. It targets Windows only; for Linux and macOS use EvoPdf Next.
API reference and usage notes for the RTF to PDF component.
Open the docs →The user guide chapters of the Classic documentation, with the C# code for each feature: options, merging, bookmarks, forms, security, deployment.
Read the guide →EvoPdf Classic is the original engine, fully supported and licensed alongside EvoPdf Next. New projects should start with Next: Chromium rendering, Windows, Linux and macOS.
Migration guide →The HTML to PDF Converter license (450 USD Deployment / 1200 USD Company) covers the Classic and the Next converter; the EVO PDF Toolkit (650 / 1400 USD) covers every component on this site, Classic tools included. The Company License includes redistribution.