How to Merge PDF Files in C# with IronPDF

How Do You Install IronPDF?

Add IronPDF to your .NET project using the NuGet Package Manager or the .NET CLI:

Install-Package IronPdf
dotnet add package IronPdf

Install-Package IronPdf
dotnet add package IronPdf

IronPDF is compatible with .NET 10, .NET Framework 4.6.2+, and runs on Windows, Linux, macOS, Azure, and AWS. For detailed setup steps, visit the NuGet installation guide.

Add the using directive at the top of your file to access IronPDF's PDF controls and methods:

using IronPdf;

using IronPdf;

How Do You Merge Two PDF Files?

Here is the minimum code needed to merge two PDFs into a single output file:

using IronPdf;

// Load two PDF documents from disk
var pdf1 = PdfDocument.FromFile("Report1.pdf");
var pdf2 = PdfDocument.FromFile("Report2.pdf");

// Merge the two PDF documents
var mergedPdf = PdfDocument.Merge(pdf1, pdf2);

// Save the result
mergedPdf.SaveAs("MergedReport.pdf");

using IronPdf;

// Load two PDF documents from disk
var pdf1 = PdfDocument.FromFile("Report1.pdf");
var pdf2 = PdfDocument.FromFile("Report2.pdf");

// Merge the two PDF documents
var mergedPdf = PdfDocument.Merge(pdf1, pdf2);

// Save the result
mergedPdf.SaveAs("MergedReport.pdf");

This loads two PDF files using PdfDocument.FromFile(), combines them with the static Merge() method, and writes the result to disk. The merge preserves all original formatting and form fields. For full API documentation, see the IronPDF docs.

The Merge() method handles large documents efficiently, maintaining document integrity including metadata, bookmarks, and annotations. It works with PDFs created from various sources -- whether converted from HTML, generated from URLs, or created from images.

How Do You Merge Multiple PDF Files at Once?

When dealing with more than two documents, pass an array or list of PdfDocument objects to Merge():

using IronPdf;

// Define the files to merge
string[] pdfFiles = { "January.pdf", "February.pdf", "March.pdf", "April.pdf" };

// Load all files into PdfDocument objects
var pdfs = new List<PdfDocument>();
foreach (string file in pdfFiles)
{
    pdfs.Add(PdfDocument.FromFile(file));
}

// Merge all documents in one call
var merged = PdfDocument.Merge(pdfs.ToArray());
merged.SaveAs("QuarterlyReport.pdf");

using IronPdf;

// Define the files to merge
string[] pdfFiles = { "January.pdf", "February.pdf", "March.pdf", "April.pdf" };

// Load all files into PdfDocument objects
var pdfs = new List<PdfDocument>();
foreach (string file in pdfFiles)
{
    pdfs.Add(PdfDocument.FromFile(file));
}

// Merge all documents in one call
var merged = PdfDocument.Merge(pdfs.ToArray());
merged.SaveAs("QuarterlyReport.pdf");

This loads each file into a PdfDocument object and merges them in a single operation. The Merge() method preserves the order of the input array, which matters when document sequence is important for the reader.

For scenarios involving directories with dozens of files, add sorting and error handling to make the operation production-ready:

using IronPdf;

string pdfDirectory = @"C:\Reports\Monthly\";
string[] pdfFiles = Directory.GetFiles(pdfDirectory, "*.pdf");

// Sort for consistent ordering
Array.Sort(pdfFiles);

var pdfs = new List<PdfDocument>();
foreach (string file in pdfFiles)
{
    try
    {
        pdfs.Add(PdfDocument.FromFile(file));
        Console.WriteLine($"Loaded: {Path.GetFileName(file)}");
    }
    catch (Exception ex)
    {
        Console.WriteLine($"Skipped {file}: {ex.Message}");
    }
}

if (pdfs.Count > 0)
{
    var merged = PdfDocument.Merge(pdfs.ToArray());
    merged.MetaData.Title = "Consolidated Monthly Reports";
    merged.SaveAs("ConsolidatedReports.pdf");
    Console.WriteLine("Merge completed.");
}

using IronPdf;

string pdfDirectory = @"C:\Reports\Monthly\";
string[] pdfFiles = Directory.GetFiles(pdfDirectory, "*.pdf");

// Sort for consistent ordering
Array.Sort(pdfFiles);

var pdfs = new List<PdfDocument>();
foreach (string file in pdfFiles)
{
    try
    {
        pdfs.Add(PdfDocument.FromFile(file));
        Console.WriteLine($"Loaded: {Path.GetFileName(file)}");
    }
    catch (Exception ex)
    {
        Console.WriteLine($"Skipped {file}: {ex.Message}");
    }
}

if (pdfs.Count > 0)
{
    var merged = PdfDocument.Merge(pdfs.ToArray());
    merged.MetaData.Title = "Consolidated Monthly Reports";
    merged.SaveAs("ConsolidatedReports.pdf");
    Console.WriteLine("Merge completed.");
}

How Do You Merge Specific Pages from PDF Documents?

IronPDF's CopyPage() and CopyPages() methods let you extract only the pages you need before merging. This is useful when combining chapters from different reports or pulling together relevant sections from multiple sources:

using IronPdf;

// Load source documents
var doc1 = PdfDocument.FromFile("PdfOne.pdf");
var doc2 = PdfDocument.FromFile("PdfTwo.pdf");

// Extract a single page from doc2 (page index 0 = first page)
var coverPage = doc2.CopyPage(0);

// Extract a page range from doc1 (pages 3 through 5, zero-indexed)
var selectedPages = doc1.CopyPages(2, 4);

// Merge the selected pages
var result = PdfDocument.Merge(coverPage, selectedPages);
result.SaveAs("CustomPdf.pdf");

using IronPdf;

// Load source documents
var doc1 = PdfDocument.FromFile("PdfOne.pdf");
var doc2 = PdfDocument.FromFile("PdfTwo.pdf");

// Extract a single page from doc2 (page index 0 = first page)
var coverPage = doc2.CopyPage(0);

// Extract a page range from doc1 (pages 3 through 5, zero-indexed)
var selectedPages = doc1.CopyPages(2, 4);

// Merge the selected pages
var result = PdfDocument.Merge(coverPage, selectedPages);
result.SaveAs("CustomPdf.pdf");

CopyPage() extracts one page by zero-based index. CopyPages() extracts a range. Both return new PdfDocument instances that you can pass directly to Merge(). The page manipulation feature gives precise control over document structure. You can also add headers and footers or apply watermarks to the final output.

For a more involved example that draws from three source documents and applies headers to identify sections:

using IronPdf;

var contract = PdfDocument.FromFile("Contract.pdf");
var appendix = PdfDocument.FromFile("Appendix.pdf");
var terms    = PdfDocument.FromFile("Terms.pdf");

// Extract relevant sections from each document
var contractPages  = contract.CopyPages(0, 5); // First 6 pages
var appendixCover  = appendix.CopyPage(0);     // Cover page only
var termsHighlight = terms.CopyPages(3, 4);    // Pages 4 and 5

// Merge selected sections
var customDoc = PdfDocument.Merge(contractPages, appendixCover, termsHighlight);

// Add a text header across all pages
customDoc.AddTextHeaders(
    "Contract Package -- {page} of {total-pages}",
    IronPdf.Editing.FontFamily.Helvetica,
    12
);

customDoc.SaveAs("ContractPackage.pdf");

using IronPdf;

var contract = PdfDocument.FromFile("Contract.pdf");
var appendix = PdfDocument.FromFile("Appendix.pdf");
var terms    = PdfDocument.FromFile("Terms.pdf");

// Extract relevant sections from each document
var contractPages  = contract.CopyPages(0, 5); // First 6 pages
var appendixCover  = appendix.CopyPage(0);     // Cover page only
var termsHighlight = terms.CopyPages(3, 4);    // Pages 4 and 5

// Merge selected sections
var customDoc = PdfDocument.Merge(contractPages, appendixCover, termsHighlight);

// Add a text header across all pages
customDoc.AddTextHeaders(
    "Contract Package -- {page} of {total-pages}",
    IronPdf.Editing.FontFamily.Helvetica,
    12
);

customDoc.SaveAs("ContractPackage.pdf");

How Do You Merge PDFs from Memory Streams?

In web and cloud applications, PDF data often arrives as byte arrays or streams rather than as files on disk. IronPDF supports loading PdfDocument objects directly from MemoryStream instances:

using IronPdf;

using var stream1 = new MemoryStream(File.ReadAllBytes("Doc1.pdf"));
using var stream2 = new MemoryStream(File.ReadAllBytes("Doc2.pdf"));

var pdf1 = new PdfDocument(stream1);
var pdf2 = new PdfDocument(stream2);

var merged = PdfDocument.Merge(pdf1, pdf2);
merged.SaveAs("Output.pdf");

using IronPdf;

using var stream1 = new MemoryStream(File.ReadAllBytes("Doc1.pdf"));
using var stream2 = new MemoryStream(File.ReadAllBytes("Doc2.pdf"));

var pdf1 = new PdfDocument(stream1);
var pdf2 = new PdfDocument(stream2);

var merged = PdfDocument.Merge(pdf1, pdf2);
merged.SaveAs("Output.pdf");

This pattern is ideal for ASP.NET applications processing uploaded files, services reading from database BLOB fields, and deployments on cloud platforms where file system access may be restricted. For more on this approach, see the IronPDF features page.

Memory-based merging is particularly valuable in these scenarios:

• Processing PDFs received from web form uploads
• Retrieving documents from cloud storage and merging without writing to disk
• Building APIs that accept PDF bytes and return a merged result
• Implementing document signing pipelines that keep data in memory

After merging, you can also extract text from the resulting PDF for indexing or search purposes, or convert pages to images to generate preview thumbnails. These operations use the same PdfDocument object returned by Merge(), so no additional loading or re-parsing step is required. The in-memory approach keeps latency low and avoids temporary file cleanup code in your application.

How Do You Apply Best Practices When Merging PDFs?

Following a consistent pattern improves reliability and performance when merging PDFs in production applications. The table below summarizes key recommendations:

For production deployments, configure a license key before any IronPDF call. A free trial license is available and removes all trial restrictions for evaluation.

Common issues to watch for when merging PDFs:

1. Memory pressure with large files -- load files in batches and call Dispose() on processed documents.
2. Font embedding gaps -- IronPDF embeds fonts by default, but PDFs from external sources may have incomplete font subsets.
3. Form field name collisions -- when source PDFs contain identically named fields, rename fields before merging to avoid conflicts. See the PDF forms guide for field management.
4. Password-protected inputs -- unlock documents using PdfDocument.FromFile(path, password) before passing them to Merge().
5. Page orientation mismatches -- the output inherits each source page's orientation; apply rotation after merging if needed.

For detailed troubleshooting advice, consult the IronPDF documentation or the PDF Association standards for interoperability guidance. Community Q&A is also available on Stack Overflow.

How Do You Build a Complete Report Compilation Workflow?

A common production use case is assembling a quarterly report from separately generated sections. The following example creates a dynamic cover page from HTML, merges it with pre-existing PDF sections, applies metadata and security settings, and saves the final document:

using IronPdf;

var reportDate = DateTime.Now;
string quarter = $"Q{(int)Math.Ceiling(reportDate.Month / 3.0)}";

// Generate a dynamic cover page from HTML
string coverHtml = $@"
<html>
<body style='text-align:center; padding-top:200px;'>
  <h1>Financial Report {quarter} {reportDate.Year}</h1>
  <h2>{reportDate:MMMM yyyy}</h2>
  <p>Confidential -- Internal Use Only</p>
</body>
</html>";

var renderer = new ChromePdfRenderer();
renderer.RenderingOptions.PaperSize = IronPdf.Rendering.PdfPaperSize.A4;

var dynamicCover = renderer.RenderHtmlAsPdf(coverHtml);

// Load pre-existing report sections
var executive  = PdfDocument.FromFile("ExecutiveSummary.pdf");
var financial  = PdfDocument.FromFile("FinancialData.pdf");
var charts     = PdfDocument.FromFile("Charts.pdf");
var appendix   = PdfDocument.FromFile("Appendix.pdf");

// Merge all sections in the correct reading order
var fullReport = PdfDocument.Merge(dynamicCover, executive, financial, charts, appendix);

// Set document metadata
fullReport.MetaData.Title   = $"Financial Report {quarter} {reportDate.Year}";
fullReport.MetaData.Author  = "Finance Department";
fullReport.MetaData.Subject = "Quarterly Financial Performance";

// Add headers and footers
fullReport.AddTextHeaders($"{quarter} Financial Report", IronPdf.Editing.FontFamily.Arial, 10);
fullReport.AddTextFooters("Page {page} of {total-pages} | Confidential", IronPdf.Editing.FontFamily.Arial, 8);

// Apply security settings
fullReport.SecuritySettings.UserPassword  = "reader123";
fullReport.SecuritySettings.OwnerPassword = "admin456";
fullReport.SecuritySettings.AllowUserPrinting = true;
fullReport.SecuritySettings.AllowUserCopyPasteContent = false;

// Compress and save
fullReport.CompressImages(90);
fullReport.SaveAs($"Financial_Report_{quarter}_{reportDate.Year}.pdf");

Console.WriteLine($"Report saved: {fullReport.PageCount} pages");

using IronPdf;

var reportDate = DateTime.Now;
string quarter = $"Q{(int)Math.Ceiling(reportDate.Month / 3.0)}";

// Generate a dynamic cover page from HTML
string coverHtml = $@"
<html>
<body style='text-align:center; padding-top:200px;'>
  <h1>Financial Report {quarter} {reportDate.Year}</h1>
  <h2>{reportDate:MMMM yyyy}</h2>
  <p>Confidential -- Internal Use Only</p>
</body>
</html>";

var renderer = new ChromePdfRenderer();
renderer.RenderingOptions.PaperSize = IronPdf.Rendering.PdfPaperSize.A4;

var dynamicCover = renderer.RenderHtmlAsPdf(coverHtml);

// Load pre-existing report sections
var executive  = PdfDocument.FromFile("ExecutiveSummary.pdf");
var financial  = PdfDocument.FromFile("FinancialData.pdf");
var charts     = PdfDocument.FromFile("Charts.pdf");
var appendix   = PdfDocument.FromFile("Appendix.pdf");

// Merge all sections in the correct reading order
var fullReport = PdfDocument.Merge(dynamicCover, executive, financial, charts, appendix);

// Set document metadata
fullReport.MetaData.Title   = $"Financial Report {quarter} {reportDate.Year}";
fullReport.MetaData.Author  = "Finance Department";
fullReport.MetaData.Subject = "Quarterly Financial Performance";

// Add headers and footers
fullReport.AddTextHeaders($"{quarter} Financial Report", IronPdf.Editing.FontFamily.Arial, 10);
fullReport.AddTextFooters("Page {page} of {total-pages} | Confidential", IronPdf.Editing.FontFamily.Arial, 8);

// Apply security settings
fullReport.SecuritySettings.UserPassword  = "reader123";
fullReport.SecuritySettings.OwnerPassword = "admin456";
fullReport.SecuritySettings.AllowUserPrinting = true;
fullReport.SecuritySettings.AllowUserCopyPasteContent = false;

// Compress and save
fullReport.CompressImages(90);
fullReport.SaveAs($"Financial_Report_{quarter}_{reportDate.Year}.pdf");

Console.WriteLine($"Report saved: {fullReport.PageCount} pages");

This single workflow covers HTML-to-PDF generation, file-based merging, header and footer insertion, metadata authoring, security settings, and image compression -- all using the same IronPDF API. For text extraction from merged results, or converting pages to images for thumbnails, see the IronPDF how-to guides.

What Licensing Options Are Available for Production Use?

IronPDF requires a valid license key for production deployments. Set the key once at application startup before making any IronPDF calls:

using IronPdf;

IronPdf.License.LicenseKey = "YOUR-LICENSE-KEY-HERE";

// All subsequent IronPDF calls are now fully licensed
var pdf = PdfDocument.FromFile("input.pdf");

using IronPdf;

IronPdf.License.LicenseKey = "YOUR-LICENSE-KEY-HERE";

// All subsequent IronPDF calls are now fully licensed
var pdf = PdfDocument.FromFile("input.pdf");

IronPDF offers flexible licensing tiers suited to individual developers, teams, and enterprises. A free trial license removes trial watermarks and lets you evaluate the full feature set without a time limit. Additional capabilities available with a full license include custom watermarks, digital signing, advanced HTML to PDF conversion, and form field management.

For detailed pricing and a feature comparison, visit the IronPDF licensing page. The IronSoftware product suite also includes libraries for OCR, barcode reading, Excel generation, and more -- all available under the same licensing umbrella.