Create, edit, merge and secure PDF documents from C#
The Core PDF API is the component of the EvoPdf Next Library for .NET for programmatically creating, manipulating and securing PDF documents. Create PDFs by adding text, images and other graphical elements, then apply encryption, permissions, digital signatures, custom headers, footers and stamps. The library targets .NET Standard 2.0 and runs on Windows, Linux and macOS, including Azure App Service, Azure Functions and Docker.
Version 14.60.1. Building EVO PDF libraries since 2010. Evaluate without registration; the demo output is watermarked until you set a license key. Licensed as part of the EVO PDF Toolkit.
Documentation · Samples and demos on GitHub · AI agent skills
dotnet add package EvoPdf.Next.Core.Windows
This is the Windows package; EvoPdf.Next.Core.Linux and EvoPdf.Next.Core.MacOS work the same way, or use the all-components EvoPdf.Next.* metapackage for your platform.
using EvoPdf.Next; var settings = new PdfDocumentCreateSettings { PageSize = PdfPageSize.A4, Margins = new PdfMargins(36, 36, 36, 36) }; using var pdf = new PdfDocument(settings); var font = PdfFontManager.CreateStandardFont( PdfStandardFont.Helvetica, 16f, PdfFontStyle.Bold, PdfColor.Black); pdf.AddText(new PdfTextElement("Hello", font)); pdf.SaveToFile("created.pdf");
- Windows 10, 11 and Windows Server 2016 to 2025 (x64 and ARM64)
- Linux 64-bit distributions (x64 and ARM64)
- macOS 12.0+ (Apple Silicon / ARM64)
- .NET 10.0, 9.0, 8.0, 7.0, 6.0, .NET Standard 2.0
- .NET Framework 4.6.2 to 4.8.1
- Azure App Service and Azure Functions
- Azure Cloud Services and Virtual Machines
- Web, console and desktop applications
What the Core PDF API component does
- Create, edit and merge PDF documents
- Generate PDF documents by adding text, images and other elements
- Encrypt, set permissions and passwords for the PDF documents
- Control the PDF document display with PDF viewer preferences
- Create PDF documents with digital signatures
- Edit PDF documents by applying stamps, headers and footers
- Merge PDF documents
- Asynchronous methods that can be used with async and await
- Docker containers for Windows and Linux
NuGet packages
Reference EvoPdf.Next.Core.Windows, .Linux, .MacOS or the .Arm64 variants, or the EvoPdf.Next.* metapackage for your platform, which includes every component.
dotnet add package EvoPdf.Next.Core.Windows
On nuget.org: EvoPdf.Next.Core.Windows · .Linux · .MacOS · .Windows.Arm64 · .Linux.Arm64 · metapackage EvoPdf.Next
Install and run on Windows, Linux and macOS
The Core PDF API has no native dependencies: reference the NuGet package and it runs on Windows, Linux and macOS as-is. Only the HTML to PDF runtime needs system packages on some Linux distributions.
Windows
Windows 10, 11 and Windows 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 (ARM64). No additional dependencies.
Getting Started on macOS →Docker
Complete Dockerfiles for Linux (x64, ARM64) and Windows Server 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.
Included in the EVO PDF Toolkit
Core PDF API is licensed as part of the EVO PDF Toolkit, which covers every component on this site, Next and Classic: 650 USD for a Deployment License (one application on a single server) or 1400 USD for a Company License (unlimited developers, applications and servers, redistributable). Perpetual, with updates and support for the first year.
