EVO PDF Merge library allows you to combine existing PDF documents in a single PDF document. It can be integrated into any .NET application, both ASP.NET web sites and desktop applications, to add pdf merge capabilities to your application.
Classic v14.0 for Windows, .NET Framework 4.0+ and .NET 6–10. Evaluate without registration; the demo output is watermarked until you set a license key. Licensed with the EVO PDF Toolkit.
dotnet add package EvoPdf.PdfMergeWindows · .NET Framework 4.0+ and .NET 6–10 (.NET Standard 2.0)
using EvoPdf.PdfMerge; var merge = new PDFMerge(new PdfDocumentOptions()); merge.AppendPDFFile("part1.pdf"); merge.AppendPDFFile("part2.pdf"); merge.SaveMergedPDFToFile("merged.pdf");
EvoPdf.PdfMerge namespace, one converter class, synchronous calls. API reference →With EVO PDF Merge library for .NET you can you can combine existing PDF documents and images in a single PDF document. The integration is extremely easy and no additional installation is necessary in order to get it working.If you need a simple ready to use tool for combining your PDF documents and images we offer you a command line utility.
It allows you to specify the merge elements in any order with a simple syntax.
EvoPdf.PdfMergeEvoPdf.PdfMergePDFMerge PdfDocumentOptions pdfDocumentOptions = new PdfDocumentOptions();
pdfDocumentOptions.PdfCompressionLevel = PDFCompressionLevel.Normal;
pdfDocumentOptions.PdfPageSize = PdfPageSize.A4;
pdfDocumentOptions.PdfPageOrientation = PDFPageOrientation.Portrait;
PDFMerge pdfMerge = new PDFMerge(pdfDocumentOptions);
pdfMerge.AppendPDFFile(pdfFilePath);
pdfMerge.AppendImageFile(imageFilePath);
pdfMerge.AppendEmptyPage();
pdfMerge.SaveMergedPDFToFile(outFile);The Classic library is a managed .NET assembly with a Windows rendering engine inside the NuGet package, so there is nothing to install on the server: xcopy deployment and it 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 PDF Merge 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.