How to Generate PDF Dynamically in .NET Using IronPDF

What Is Dynamic PDF Generation in .NET?

Dynamic PDF generation means creating PDF documents at runtime where every piece of content -- names, figures, dates, tables, charts -- comes from live data rather than a fixed layout. The document structure may stay the same, but its payload changes with every request.

Here are the scenarios where this approach delivers the most value:

• Invoice generation -- line items, totals, tax rates, and payment terms differ for every transaction
• Financial reports -- charts and summary tables pull from a database updated throughout the day
• Certificates and diplomas -- recipient names, completion dates, and course details vary per record
• Legal documents -- contracts embed client-specific clauses and jurisdiction rules
• Medical records -- patient demographics, test results, and care plans require individual formatting

The conventional alternative is maintaining a library of static templates and editing them by hand for each variation. That approach breaks down quickly as document volume grows and business rules multiply. With IronPDF's HTML-to-PDF conversion engine, you write the generation logic once and produce thousands of correctly formatted, data-accurate PDFs without any manual intervention.

IronPDF runs on Windows, Linux, macOS, Docker, and Azure -- the same API works identically across all platforms. That cross-platform consistency means you can develop locally and deploy to a cloud container without any platform-specific adjustments. The library targets .NET 6 and later, supporting both the latest .NET releases and long-term support versions.

How Do You Install and Configure the Library?

IronPDF is distributed as a NuGet package and integrates with any .NET 6 or later project, including ASP.NET Core, Blazor, and console applications. Install it through the Package Manager Console or the .NET CLI:

Install-Package IronPdf
dotnet add package IronPdf

Install-Package IronPdf
dotnet add package IronPdf

Once the package is installed, you can start generating PDFs immediately -- no configuration file or API key is required during the free trial. For production licensing, visit the IronPDF licensing page and pick the plan that matches your deployment model.

The entry point for all rendering is ChromePdfRenderer. The snippet below shows the minimum code needed to turn a dynamic HTML string into a saved PDF file:

using IronPdf;

var renderer = new ChromePdfRenderer();

var customerName = "Alexandra Chen";
var orderNumber = "ORD-2025-001";
var totalAmount = 1499.99m;

var html = $"""
    <h1>Order Confirmation</h1>
    <p>Dear {customerName},</p>
    <p>Thank you for your order #{orderNumber}.</p>
    <p>Total amount: ${totalAmount:F2}</p>
    <p>Your order will be processed within 24 hours.</p>
    """;

var pdf = renderer.RenderHtmlAsPdf(html);
pdf.SaveAs("order-confirmation.pdf");

// Stream the bytes directly in a web response if needed
byte[] pdfBytes = pdf.BinaryData;

using IronPdf;

var renderer = new ChromePdfRenderer();

var customerName = "Alexandra Chen";
var orderNumber = "ORD-2025-001";
var totalAmount = 1499.99m;

var html = $"""
    <h1>Order Confirmation</h1>
    <p>Dear {customerName},</p>
    <p>Thank you for your order #{orderNumber}.</p>
    <p>Total amount: ${totalAmount:F2}</p>
    <p>Your order will be processed within 24 hours.</p>
    """;

var pdf = renderer.RenderHtmlAsPdf(html);
pdf.SaveAs("order-confirmation.pdf");

// Stream the bytes directly in a web response if needed
byte[] pdfBytes = pdf.BinaryData;

ChromePdfRenderer handles all rendering complexity internally. String interpolation ($"""...""") slots C# variables into HTML at the point of call, keeping templates readable and eliminating a dedicated templating library for simple cases.

For full setup guidance, including configuration for MVC views and Blazor server projects, see the IronPDF documentation.

How Do You Apply Template-Based PDF Generation?

Template-based generation separates document design from data binding. A designer creates the HTML layout once, placing named placeholders ({{TOKEN}}) wherever runtime values should appear, and your application replaces those tokens before rendering. This is the pattern recommended in Stack Overflow's PDF generation discussions for projects where templates change more often than application code.

using IronPdf;

// Reusable template -- stored in a file or database in production
var htmlTemplate = """
    <style>
        .invoice { font-family: Arial; max-width: 800px; margin: auto; }
        .header  { background: #f0f0f0; padding: 20px; }
        .label   { font-weight: bold; }
    </style>
    <div class='invoice'>
        <div class='header'>
            <h2>Invoice #{{INVOICE_NUMBER}}</h2>
            <p>Date: {{INVOICE_DATE}}</p>
        </div>
        <p>Bill to: {{CUSTOMER_NAME}}</p>
        <p class='label'>Amount due: ${{TOTAL_AMOUNT}}</p>
    </div>
    """;

var invoiceHtml = htmlTemplate
    .Replace("{{INVOICE_NUMBER}}", "INV-2025-1234")
    .Replace("{{INVOICE_DATE}}", DateTime.Now.ToString("MMM dd, yyyy"))
    .Replace("{{CUSTOMER_NAME}}", "TechCorp Industries")
    .Replace("{{TOTAL_AMOUNT}}", "5,750.00");

var renderer = new ChromePdfRenderer();

renderer.RenderingOptions.TextHeader = new TextHeaderFooter
{
    CenterText    = "Invoice",
    DrawDividerLine = true
};

var pdf = renderer.RenderHtmlAsPdf(invoiceHtml);
pdf.SaveAs("invoice.pdf");

using IronPdf;

// Reusable template -- stored in a file or database in production
var htmlTemplate = """
    <style>
        .invoice { font-family: Arial; max-width: 800px; margin: auto; }
        .header  { background: #f0f0f0; padding: 20px; }
        .label   { font-weight: bold; }
    </style>
    <div class='invoice'>
        <div class='header'>
            <h2>Invoice #{{INVOICE_NUMBER}}</h2>
            <p>Date: {{INVOICE_DATE}}</p>
        </div>
        <p>Bill to: {{CUSTOMER_NAME}}</p>
        <p class='label'>Amount due: ${{TOTAL_AMOUNT}}</p>
    </div>
    """;

var invoiceHtml = htmlTemplate
    .Replace("{{INVOICE_NUMBER}}", "INV-2025-1234")
    .Replace("{{INVOICE_DATE}}", DateTime.Now.ToString("MMM dd, yyyy"))
    .Replace("{{CUSTOMER_NAME}}", "TechCorp Industries")
    .Replace("{{TOTAL_AMOUNT}}", "5,750.00");

var renderer = new ChromePdfRenderer();

renderer.RenderingOptions.TextHeader = new TextHeaderFooter
{
    CenterText    = "Invoice",
    DrawDividerLine = true
};

var pdf = renderer.RenderHtmlAsPdf(invoiceHtml);
pdf.SaveAs("invoice.pdf");

The tokens ({{...}}) mark exactly where data enters the document, making templates readable by non-developers. Storing templates as external files means a designer can update the layout without touching the application codebase. For a deeper walkthrough of this pattern, see the IronPDF template tutorial.

How Do You Build PDFs Programmatically From Data?

When document content depends on loops, aggregations, or conditional formatting, building the HTML string in code gives you the most control. This approach is common in financial and operational reporting where the number of rows is unknown at compile time. It also lets you apply formatting rules directly in C# rather than embedding them in a static template.

using IronPdf;
using System.Text;

var orderItems = new[]
{
    new { Product = "Premium License",  Quantity = 5, Price = 399.00m },
    new { Product = "Support Package",  Quantity = 1, Price = 299.00m },
    new { Product = "Training Session", Quantity = 2, Price = 150.00m }
};

var sb = new StringBuilder();
sb.Append("<h2>Order Summary</h2>");
sb.Append("<table style='width:100%; border-collapse:collapse;'>");
sb.Append("<tr style='background:#333; color:white;'>");
sb.Append("<th style='padding:10px;'>Product</th><th>Qty</th><th>Unit Price</th><th>Total</th>");
sb.Append("</tr>");

decimal grandTotal = 0;
foreach (var item in orderItems)
{
    var lineTotal = item.Quantity * item.Price;
    grandTotal += lineTotal;
    sb.Append($"""
        <tr>
            <td style='padding:10px;'>{item.Product}</td>
            <td style='text-align:center;'>{item.Quantity}</td>
            <td style='text-align:right;'>${item.Price:F2}</td>
            <td style='text-align:right;'>${lineTotal:F2}</td>
        </tr>
        """);
}

sb.Append($"""
    <tr style='font-weight:bold; background:#f0f0f0;'>
        <td colspan='3' style='padding:10px; text-align:right;'>Grand total:</td>
        <td style='text-align:right; padding:10px;'>${grandTotal:F2}</td>
    </tr>
    """);
sb.Append("</table>");

var renderer = new ChromePdfRenderer();
var pdf = renderer.RenderHtmlAsPdf(sb.ToString());

pdf.SaveAs("order-summary.pdf");

// Get bytes for a web download response
byte[] pdfData = pdf.BinaryData;

using IronPdf;
using System.Text;

var orderItems = new[]
{
    new { Product = "Premium License",  Quantity = 5, Price = 399.00m },
    new { Product = "Support Package",  Quantity = 1, Price = 299.00m },
    new { Product = "Training Session", Quantity = 2, Price = 150.00m }
};

var sb = new StringBuilder();
sb.Append("<h2>Order Summary</h2>");
sb.Append("<table style='width:100%; border-collapse:collapse;'>");
sb.Append("<tr style='background:#333; color:white;'>");
sb.Append("<th style='padding:10px;'>Product</th><th>Qty</th><th>Unit Price</th><th>Total</th>");
sb.Append("</tr>");

decimal grandTotal = 0;
foreach (var item in orderItems)
{
    var lineTotal = item.Quantity * item.Price;
    grandTotal += lineTotal;
    sb.Append($"""
        <tr>
            <td style='padding:10px;'>{item.Product}</td>
            <td style='text-align:center;'>{item.Quantity}</td>
            <td style='text-align:right;'>${item.Price:F2}</td>
            <td style='text-align:right;'>${lineTotal:F2}</td>
        </tr>
        """);
}

sb.Append($"""
    <tr style='font-weight:bold; background:#f0f0f0;'>
        <td colspan='3' style='padding:10px; text-align:right;'>Grand total:</td>
        <td style='text-align:right; padding:10px;'>${grandTotal:F2}</td>
    </tr>
    """);
sb.Append("</table>");

var renderer = new ChromePdfRenderer();
var pdf = renderer.RenderHtmlAsPdf(sb.ToString());

pdf.SaveAs("order-summary.pdf");

// Get bytes for a web download response
byte[] pdfData = pdf.BinaryData;

StringBuilder handles large HTML strings efficiently. The foreach loop expands to however many rows your data source provides, and the running grandTotal calculation shows how business logic integrates naturally with HTML construction. For very large datasets, this approach pairs well with IronPDF's multi-page rendering options.

How Do You Handle Dynamic Tables That Span Multiple Pages?

Reports generated from databases often contain unpredictable row counts. Handling automatic page breaks correctly -- without cutting a row in half -- requires specific CSS alongside IronPDF's rendering options. The page-break-inside: avoid rule, combined with correct margin configuration, keeps every row intact as the table flows across pages.

using IronPdf;

var salesData = Enumerable.Range(1, 30).Select(i => new
{
    Month   = $"Month {i}",
    Revenue = 10_000 + (i * 500),
    Growth  = 2.5 + (i * 0.3)
});

var tableHtml = """
    <style>
        table { width: 100%; border-collapse: collapse; page-break-inside: auto; }
        th    { background: #2c3e50; color: white; padding: 12px; }
        td    { padding: 8px; border-bottom: 1px solid #ddd; }
        tr:nth-child(even) { background: #f9f9f9; }
        tr    { page-break-inside: avoid; page-break-after: auto; }
    </style>
    <h2>Sales Performance Report</h2>
    <table>
        <thead><tr><th>Period</th><th>Revenue</th><th>Growth %</th></tr></thead>
        <tbody>
    """;

foreach (var row in salesData)
{
    tableHtml += $"""
        <tr>
            <td>{row.Month}</td>
            <td>${row.Revenue:N0}</td>
            <td>{row.Growth:F1}%</td>
        </tr>
        """;
}

tableHtml += "</tbody></table>";

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

renderer.RenderingOptions.TextFooter = new TextHeaderFooter
{
    CenterText = "{page} of {total-pages}",
    FontSize   = 10
};

var pdf = renderer.RenderHtmlAsPdf(tableHtml);
pdf.SaveAs("sales-report.pdf");

using IronPdf;

var salesData = Enumerable.Range(1, 30).Select(i => new
{
    Month   = $"Month {i}",
    Revenue = 10_000 + (i * 500),
    Growth  = 2.5 + (i * 0.3)
});

var tableHtml = """
    <style>
        table { width: 100%; border-collapse: collapse; page-break-inside: auto; }
        th    { background: #2c3e50; color: white; padding: 12px; }
        td    { padding: 8px; border-bottom: 1px solid #ddd; }
        tr:nth-child(even) { background: #f9f9f9; }
        tr    { page-break-inside: avoid; page-break-after: auto; }
    </style>
    <h2>Sales Performance Report</h2>
    <table>
        <thead><tr><th>Period</th><th>Revenue</th><th>Growth %</th></tr></thead>
        <tbody>
    """;

foreach (var row in salesData)
{
    tableHtml += $"""
        <tr>
            <td>{row.Month}</td>
            <td>${row.Revenue:N0}</td>
            <td>{row.Growth:F1}%</td>
        </tr>
        """;
}

tableHtml += "</tbody></table>";

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

renderer.RenderingOptions.TextFooter = new TextHeaderFooter
{
    CenterText = "{page} of {total-pages}",
    FontSize   = 10
};

var pdf = renderer.RenderHtmlAsPdf(tableHtml);
pdf.SaveAs("sales-report.pdf");

{page} and {total-pages} are IronPDF's built-in tokens for automatic footer numbering. Margins keep content away from the edges on every page, giving the finished report a professional appearance even when the table runs to dozens of pages.

For formatting guidance on complex table layouts including merged cells, refer to the IronPDF rendering options reference.

How Do You Add Conditional Content to a PDF?

Many document types include sections that should appear only when certain conditions are true -- a premium badge for top-tier customers, a discount block when a promotion applies, a warning when an account is overdue. C# conditional logic maps directly to this requirement, and because the condition is evaluated before the HTML string is built, no empty placeholder elements end up in the final PDF.

using IronPdf;

var customer = new
{
    Name           = "Global Tech Solutions",
    IsPremium      = true,
    HasDiscount    = true,
    DiscountPct    = 15,
    LoyaltyPoints  = 2500
};

var html = $"""<h2>Customer Profile: {customer.Name}</h2><div style='border:1px solid #ddd; padding:20px;'>""";

if (customer.IsPremium)
{
    html += """<div style='background:gold; padding:10px; margin-bottom:10px;'>PREMIUM MEMBER -- Exclusive benefits applied</div>""";
}

if (customer.HasDiscount)
{
    html += $"""<div style='background:#e8f5e9; padding:10px; margin-bottom:10px;'>Special discount: {customer.DiscountPct}% off all orders</div>""";
}

if (customer.LoyaltyPoints > 0)
{
    html += $"""<div style='background:#f3e5f5; padding:10px;'>Loyalty points balance: {customer.LoyaltyPoints:N0} points</div>""";
}

html += "</div>";

var renderer = new ChromePdfRenderer();
var pdf = renderer.RenderHtmlAsPdf(html);
pdf.SaveAs("customer-profile.pdf");

using IronPdf;

var customer = new
{
    Name           = "Global Tech Solutions",
    IsPremium      = true,
    HasDiscount    = true,
    DiscountPct    = 15,
    LoyaltyPoints  = 2500
};

var html = $"""<h2>Customer Profile: {customer.Name}</h2><div style='border:1px solid #ddd; padding:20px;'>""";

if (customer.IsPremium)
{
    html += """<div style='background:gold; padding:10px; margin-bottom:10px;'>PREMIUM MEMBER -- Exclusive benefits applied</div>""";
}

if (customer.HasDiscount)
{
    html += $"""<div style='background:#e8f5e9; padding:10px; margin-bottom:10px;'>Special discount: {customer.DiscountPct}% off all orders</div>""";
}

if (customer.LoyaltyPoints > 0)
{
    html += $"""<div style='background:#f3e5f5; padding:10px;'>Loyalty points balance: {customer.LoyaltyPoints:N0} points</div>""";
}

html += "</div>";

var renderer = new ChromePdfRenderer();
var pdf = renderer.RenderHtmlAsPdf(html);
pdf.SaveAs("customer-profile.pdf");

You can extend the same pattern to any rule-based content: jurisdiction-specific legal disclaimers, promotional sections triggered by cart value, or safety warnings triggered by product category. The resulting PDF contains exactly the content it should -- nothing more and nothing less.

How Do You Render JavaScript-Powered Charts in a PDF?

Modern dashboards often rely on JavaScript charting libraries such as Chart.js or D3.js to draw graphs at render time. IronPDF can execute JavaScript before capturing the page, so the chart renders fully before the PDF snapshot is taken. This means you do not need a separate screenshot service or a server-side chart rendering library.

using IronPdf;

var chartHtml = """
    <script src='https://cdn.jsdelivr.net/npm/chart.js'></script>
    <canvas id='revenueChart' width='500' height='250'></canvas>
    <script>
        var ctx = document.getElementById('revenueChart').getContext('2d');
        new Chart(ctx, {
            type: 'bar',
            data: {
                labels: ['Q1', 'Q2', 'Q3', 'Q4'],
                datasets: [{
                    label: 'Revenue (thousands)',
                    data: [120, 195, 230, 285],
                    backgroundColor: '#3498db'
                }]
            },
            options: { animation: false }
        });
    </script>
    """;

var renderer = new ChromePdfRenderer();
renderer.RenderingOptions.EnableJavaScript = true;
renderer.RenderingOptions.WaitFor.RenderDelay(1500);

var pdf = renderer.RenderHtmlAsPdf(chartHtml);
pdf.SaveAs("revenue-chart.pdf");

using IronPdf;

var chartHtml = """
    <script src='https://cdn.jsdelivr.net/npm/chart.js'></script>
    <canvas id='revenueChart' width='500' height='250'></canvas>
    <script>
        var ctx = document.getElementById('revenueChart').getContext('2d');
        new Chart(ctx, {
            type: 'bar',
            data: {
                labels: ['Q1', 'Q2', 'Q3', 'Q4'],
                datasets: [{
                    label: 'Revenue (thousands)',
                    data: [120, 195, 230, 285],
                    backgroundColor: '#3498db'
                }]
            },
            options: { animation: false }
        });
    </script>
    """;

var renderer = new ChromePdfRenderer();
renderer.RenderingOptions.EnableJavaScript = true;
renderer.RenderingOptions.WaitFor.RenderDelay(1500);

var pdf = renderer.RenderHtmlAsPdf(chartHtml);
pdf.SaveAs("revenue-chart.pdf");

EnableJavaScript = true activates script execution inside the headless Chrome engine. RenderDelay(1500) adds a 1.5-second pause after the page loads, giving asynchronous chart rendering time to complete before the snapshot is taken. Setting animation: false in the Chart.js options prevents animated frames from being captured mid-transition.

This technique works with any JavaScript library. You can pass server-side data into the <script> block using C# string interpolation, so every chart reflects live database figures at the moment of generation. For more detail on JavaScript configuration, see IronPDF's JavaScript rendering guide.

How Do You Export and Deliver the Generated PDF?

Once RenderHtmlAsPdf returns a PdfDocument object, you have several delivery options depending on your application type. Saving to disk is the simplest approach and works for background batch jobs. For web APIs and MVC controllers, streaming the bytes directly to the HTTP response avoids writing temporary files and keeps the server filesystem clean.

using IronPdf;
using Microsoft.AspNetCore.Mvc;

// In an ASP.NET Core controller action:
public IActionResult DownloadInvoice(int orderId)
{
    var renderer = new ChromePdfRenderer();
    var html     = BuildInvoiceHtml(orderId);   // your data-binding method
    var pdf      = renderer.RenderHtmlAsPdf(html);

    return File(pdf.BinaryData, "application/pdf", $"invoice-{orderId}.pdf");
}

using IronPdf;
using Microsoft.AspNetCore.Mvc;

// In an ASP.NET Core controller action:
public IActionResult DownloadInvoice(int orderId)
{
    var renderer = new ChromePdfRenderer();
    var html     = BuildInvoiceHtml(orderId);   // your data-binding method
    var pdf      = renderer.RenderHtmlAsPdf(html);

    return File(pdf.BinaryData, "application/pdf", $"invoice-{orderId}.pdf");
}

pdf.BinaryData returns the raw bytes as a byte[], which maps directly to ASP.NET Core's File() result. The browser receives the correct MIME type (application/pdf) and triggers a download dialog with a meaningful filename.

Additional output capabilities include PDF merging, digital signatures, PDF/A archival format, password protection, and text and image extraction. These features operate on the same PdfDocument object returned by the renderer, so you can chain operations without creating intermediate files.

What Are Your Next Steps?

Dynamic PDF generation in .NET comes down to three building blocks: an HTML string that varies with your data, ChromePdfRenderer to convert that string into a PDF, and the delivery mechanism that fits your application. IronPDF handles everything in between -- page breaks, headers and footers, JavaScript execution, and cross-platform compatibility.

To move from reading to building, start by installing the package and running one of the examples above against your own data:

dotnet add package IronPdf

dotnet add package IronPdf

From there, explore the IronPDF documentation for platform-specific setup (Azure, Docker, Linux), advanced rendering options, and the full API reference. When you are ready to deploy, visit the licensing page to choose a plan that fits your production volume. The free trial gives you full-featured access with no credit card required, so you can validate your implementation before committing.

Additional guides that pair well with dynamic generation:

• Generate a PDF from an HTML template in C#
• Convert a URL to PDF
• Merge and split PDF documents
• Add digital signatures to PDFs
• PDF/A compliance for archival documents