Nine components, one namespace, every platform
EvoPdf Next allows you to create, edit and merge PDF documents, convert HTML to PDF or images, convert Word, Excel, RTF and Markdown documents to PDF, extract text and images from PDF documents, search text in PDFs and convert PDF pages to images. Each component ships as its own NuGet package under the shared EvoPdf.Next namespace; the library targets .NET Standard 2.0 and runs on Windows, Linux and macOS, including Azure App Service, Azure Functions and Docker.
Version 14.50.0. Building EVO PDF libraries since 2010. Evaluate without registration; the demo output is watermarked until you set a license key. Perpetual licenses from 450 USD, or 1200 with redistribution and unlimited servers. Developers are never counted.
Documentation · Samples and demos on GitHub · AI agent skills
HTML to PDF Converter
A Chromium-based rendering engine that processes modern HTML, CSS and JavaScript to the current standards. Headers and footers with page numbers, repeated table headers, CSS page breaks, outlines, tables of contents, HTML forms to PDF forms, PDF/UA and PDF/A output, digital signatures.
using EvoPdf.Next; HtmlToPdfConverter converter = new(); byte[] pdf = converter.ConvertUrl( "https://www.evopdf.com"); File.WriteAllBytes("page.pdf", pdf);
Core PDF API
Create PDFs from text, images and shapes; stamp, merge, secure and digitally sign existing documents.
using EvoPdf.Next; using var pdf = new PdfDocument( new PdfDocumentCreateSettings()); var el = new PdfTextElement("Hello", font); pdf.AddText(el); pdf.SaveToFile("created.pdf");
Word to PDF
Accurate conversion of complex Word documents, with tables of contents, headers, footers, stamps and security.
using EvoPdf.Next; WordToPdfConverter converter = new(); var pdf = converter.ConvertToPdf(bytes); File.WriteAllBytes("word.pdf", pdf);
Excel to PDF
Convert Excel workbooks to PDF with headers, footers, stamps and document security.
using EvoPdf.Next; ExcelToPdfConverter converter = new(); var pdf = converter.ConvertToPdf(bytes); File.WriteAllBytes("workbook.pdf", pdf);
RTF to PDF
Convert RTF documents to PDF with tables of contents, headers, footers and stamps.
using EvoPdf.Next; RtfToPdfConverter converter = new(); var pdf = converter.ConvertToPdf(bytes); File.WriteAllBytes("document.pdf", pdf);
Markdown to PDF
Convert Markdown documents to PDF with tables of contents, headers, footers and stamps.
using EvoPdf.Next; MarkdownToPdfConverter converter = new(); var pdf = converter.ConvertStringToPdf( markdown, baseUrl); File.WriteAllBytes("readme.pdf", pdf);
PDF to Text
Extract text in the original layout or optimized for reading; search text and get the exact positions of matches.
using EvoPdf.Next; PdfToTextConverter converter = new(); var text = converter.ConvertToText(bytes);
PDF to Image
Render PDF pages to PNG with control over color space, resolution and background transparency.
using EvoPdf.Next; PdfToImageConverter converter = new(); var imgs = converter.ConvertToImages(bytes);
PDF Images Extractor
Extract the images embedded in a PDF as PNG, preserving transparency.
using EvoPdf.Next; PdfImagesExtractor extractor = new(); var imgs = extractor.ExtractImages(bytes);
PDF to Text, PDF to Image and PDF Images Extractor ship together as one NuGet package, EvoPdf.Next.PdfProcessor; see the package page →
Why the library is built this way
One package per component
An application that only converts HTML should not carry the Word and Excel engines, so each component is its own NuGet package and you reference exactly what you use. They share one namespace and the same option classes, so adding a second component later is a package reference, not a new API to learn.
A Chromium engine for HTML
We wrote our own HTML engine for Classic and kept it current for over a decade; the New Edition engine brought it well past wkhtmltopdf-based tools, but not to the latest CSS and JavaScript. For Next we chose Chromium, version 142 in the current release: flexbox, grid, ES2015+ and web fonts render exactly as in the browser your designers test in and the runtime ships inside the package, so nothing is installed on the server.
.NET Standard 2.0, not the latest .NET
Targeting .NET Standard 2.0 means one assembly runs on .NET 6 to 10 and on .NET Framework 4.6.2, without separate builds. Teams with older applications can adopt Next without upgrading the runtime first and the migration from Classic stays a package swap.
Windows, Linux, macOS, Docker and Azure
One NuGet package per target platform, the rendering engine inside it. Windows and macOS need nothing else; Linux needs four system packages. Containers and Azure have their own pages with the exact Dockerfiles, commands and plan sizes.
Windows
Windows 10, 11 and Server 2016–2025, x64 and ARM64. No additional dependencies.
Getting Started on Windows →Linux
64-bit distributions, x64 and ARM64; the guide lists the system packages per distribution.
Getting Started on Linux →macOS
macOS 12 and later on Apple Silicon. No additional dependencies.
Getting Started on macOS →Docker
Complete Dockerfiles for Linux (x64, ARM64) and Windows Server Core containers, with the runtime dependencies and the build commands.
Docker page →Azure
App Service on Windows and Linux, Azure Functions, Container Apps and AKS: plan sizing, the Linux startup command, ConfigureRuntime.
One toolkit license for everything, or the HTML to PDF Converter separately
The EVO PDF Toolkit (650 / 1400 USD) covers every component above plus the EvoPdf Classic suite. The HTML to PDF Converter can also be licensed individually (450 / 1200 USD), covering Next and Classic. Perpetual licenses, updates and support included for the first year.
Runnable samples and skills that teach AI assistants EvoPdf Next
Every documentation sample as code, the complete demo applications and agent skills for Claude Code, GitHub Copilot, Cursor and Codex, including a Classic to Next migration skill.