PDF API for .NET: Generate, Edit, and Secure Documents with IronPDF

Output

Understanding the ChromePdfRenderer architecture helps you get the most from this PDF API. The renderer maintains its own Chromium instance, ensuring consistent rendering regardless of the host system's browser configuration. This isolation provides predictable output across different deployment environments while supporting the latest web standards, including HTML5, CSS3, and modern JavaScript.

Converting HTML Strings to PDF

Direct HTML string conversion is valuable when generating dynamic documents from templates or building PDFs programmatically. You pass any HTML string to RenderHtmlAsPdf, and the renderer applies inline CSS, handles nested elements, and preserves complex structures like tables and multimedia content. Template engines can generate HTML dynamically, incorporating data from databases or APIs before conversion. This approach gives you complete control over structure and styling without any intermediate files.

Creating PDFs from URLs

Web page to PDF conversion enables capturing existing web content or generating documents from web applications. Use RenderUrlAsPdf to load a complete web page -- the renderer executes JavaScript, waits for content to render, and respects CSS media queries so that print-optimized layouts apply automatically. This is useful for converting existing web reports to PDF, capturing dashboard states, or archiving web content. For more details, see the URL to PDF how-to guide.

Output

Working with HTML Files

File-based conversion simplifies workflows where HTML templates reside in the file system. Use RenderHtmlFileAsPdf to load an HTML file along with its referenced resources -- CSS files, images, and scripts. Relative paths in HTML resolve correctly, maintaining file structure relationships. Organizations often use this approach with version-controlled HTML templates, separating document design from application logic. For detailed guidance, see the HTML file to PDF documentation.

Page Setup and Margins

Controlling page layout ensures documents meet specific formatting requirements. The PaperSize property supports standard formats like A4, Letter, and Legal, plus custom dimensions for specialized requirements. PaperOrientation switches between portrait and horizontal page modes. Margin settings on all four sides create consistent spacing around content, essential for a professional appearance. Access these through renderer.RenderingOptions.PaperSize, renderer.RenderingOptions.PaperOrientation, and renderer.RenderingOptions.MarginTop/Bottom/Left/Right.

Output

Headers and Footers

Professional documents often require consistent headers and footers across pages:

using IronPdf;

var renderer = new ChromePdfRenderer();
renderer.RenderingOptions.TextHeader = new TextHeaderFooter
{
    CenterText = "Confidential Report",
    RightText = "{date}",
    DrawDividerLine = true
};
renderer.RenderingOptions.TextFooter = new TextHeaderFooter
{
    LeftText = "© 2025 Company Name",
    CenterText = "Page {page} of {total-pages}"
};
var pdf = renderer.RenderHtmlAsPdf("<h1>Document with Headers</h1>");
pdf.SaveAs("headed-document.pdf");

using IronPdf;

var renderer = new ChromePdfRenderer();
renderer.RenderingOptions.TextHeader = new TextHeaderFooter
{
    CenterText = "Confidential Report",
    RightText = "{date}",
    DrawDividerLine = true
};
renderer.RenderingOptions.TextFooter = new TextHeaderFooter
{
    LeftText = "© 2025 Company Name",
    CenterText = "Page {page} of {total-pages}"
};
var pdf = renderer.RenderHtmlAsPdf("<h1>Document with Headers</h1>");
pdf.SaveAs("headed-document.pdf");

Headers and footers support both plain text and HTML content with merge fields for dynamic values. The {page} and {total-pages} tokens populate automatically with page numbers, while {date} inserts the current date. Divider lines provide visual separation between headers and main content. These elements maintain consistent positioning across all pages. Learn more in the PDF headers and footers guide.

CSS Media Types and JavaScript Support

Modern web applications often require JavaScript execution and proper CSS media handling during conversion:

using IronPdf;

var renderer = new ChromePdfRenderer();
renderer.RenderingOptions.CssMediaType = PdfCssMediaType.Screen;
renderer.RenderingOptions.EnableJavaScript = true;
renderer.RenderingOptions.WaitFor.RenderDelay(500);
var pdf = renderer.RenderUrlAsPdf("https://ironpdf.com/");
pdf.SaveAs("dynamic.pdf");

using IronPdf;

var renderer = new ChromePdfRenderer();
renderer.RenderingOptions.CssMediaType = PdfCssMediaType.Screen;
renderer.RenderingOptions.EnableJavaScript = true;
renderer.RenderingOptions.WaitFor.RenderDelay(500);
var pdf = renderer.RenderUrlAsPdf("https://ironpdf.com/");
pdf.SaveAs("dynamic.pdf");

The CssMediaType setting determines which CSS rules apply during rendering. Screen media type preserves web appearance, while print media type applies print-specific styles. JavaScript enablement allows dynamic content generation, critical for modern single-page applications. The render delay ensures asynchronous content loads completely before generation begins. These options bridge the gap between interactive web applications and static PDF output.

Output

Form Creation and Manipulation

IronPDF automatically converts HTML form elements into interactive PDF forms. This feature simplifies document workflows by creating fillable PDFs directly from HTML. Form fields enable data collection without printing:

using IronPdf;

var renderer = new ChromePdfRenderer();
renderer.RenderingOptions.CreatePdfFormsFromHtml = true;
string formHtml = @"
    <form>
        <label>Name: <input type='text' name='name' /></label><br/>
        <label>Email: <input type='email' name='email' /></label><br/>
        <label>Subscribe: <input type='checkbox' name='subscribe' /></label><br/>
        <button type='submit'>Submit</button>
    </form>";
var pdf = renderer.RenderHtmlAsPdf(formHtml);
pdf.SaveAs("interactive-form.pdf");

using IronPdf;

var renderer = new ChromePdfRenderer();
renderer.RenderingOptions.CreatePdfFormsFromHtml = true;
string formHtml = @"
    <form>
        <label>Name: <input type='text' name='name' /></label><br/>
        <label>Email: <input type='email' name='email' /></label><br/>
        <label>Subscribe: <input type='checkbox' name='subscribe' /></label><br/>
        <button type='submit'>Submit</button>
    </form>";
var pdf = renderer.RenderHtmlAsPdf(formHtml);
pdf.SaveAs("interactive-form.pdf");

This feature preserves form functionality within PDF files, allowing users to fill form fields directly in PDF readers. Text inputs, checkboxes, radio buttons, and dropdown menus all convert to PDF form equivalents. The resulting forms work with standard PDF readers, enabling data collection without requiring users to print and scan documents. You can also export form data or extract text from forms programmatically for downstream processing.

Security and Encryption

Protecting sensitive documents requires strong security features. IronPDF provides complete security options to restrict document access and permissions:

using IronPdf;

var pdf = new PdfDocument("document.pdf");
pdf.SecuritySettings.UserPassword = "user123";
pdf.SecuritySettings.OwnerPassword = "owner456";
pdf.SecuritySettings.AllowUserPrinting = IronPdf.Security.PdfPrintSecurity.FullPrintRights;
pdf.SecuritySettings.AllowUserCopyPasteContent = false;
pdf.SecuritySettings.AllowUserFormData = true;
pdf.SaveAs("secured-document.pdf");

using IronPdf;

var pdf = new PdfDocument("document.pdf");
pdf.SecuritySettings.UserPassword = "user123";
pdf.SecuritySettings.OwnerPassword = "owner456";
pdf.SecuritySettings.AllowUserPrinting = IronPdf.Security.PdfPrintSecurity.FullPrintRights;
pdf.SecuritySettings.AllowUserCopyPasteContent = false;
pdf.SecuritySettings.AllowUserFormData = true;
pdf.SaveAs("secured-document.pdf");

User passwords control document opening, while owner passwords manage permission changes. Granular permissions control printing, copying, editing, and form-filling capabilities. These features ensure compliance with data protection requirements and prevent unauthorized manipulation. The encryption uses industry-standard algorithms, providing strong protection for sensitive content. For more options, see the PDF security documentation.

Output

Document Editing and Merging

IronPDF enables manipulation of existing PDF documents in .NET projects:

using IronPdf;

var pdf1 = PdfDocument.FromFile("report1.pdf");
var pdf2 = PdfDocument.FromFile("report2.pdf");
// Merge PDF documents
pdf1.AppendPdf(pdf2);
// Add watermark
pdf1.ApplyWatermark("<h2>CONFIDENTIAL</h2>", rotation: 45, opacity: 50);
// Extract pages
var extracted = pdf1.CopyPages(0, 2);
extracted.SaveAs("first-three-pages.pdf");
pdf1.SaveAs("combined-report.pdf");

using IronPdf;

var pdf1 = PdfDocument.FromFile("report1.pdf");
var pdf2 = PdfDocument.FromFile("report2.pdf");
// Merge PDF documents
pdf1.AppendPdf(pdf2);
// Add watermark
pdf1.ApplyWatermark("<h2>CONFIDENTIAL</h2>", rotation: 45, opacity: 50);
// Extract pages
var extracted = pdf1.CopyPages(0, 2);
extracted.SaveAs("first-three-pages.pdf");
pdf1.SaveAs("combined-report.pdf");

Document manipulation features enable complex workflows without external tools. Merging combines multiple files into a single document, useful for report compilation or document packages. Watermarking adds text or image overlays for branding or security purposes, with control over transparency and rotation. Page extraction creates new documents from existing page ranges, facilitating document splitting or selective sharing. These operations preserve document quality throughout the manipulation process. Learn more in the PDF merging guide.

How Do You Optimize HTML for PDF Output?

Well-structured HTML produces better PDF results. Use semantic HTML elements to create a logical document structure. Tables should use proper thead, tbody, and tfoot elements for consistent rendering across pages. Avoid absolute positioning when possible, as relative layouts adapt better to page boundaries. Include print-specific CSS rules to optimize appearance:

using IronPdf;

string optimizedHtml = @"
    <style>
        @media print {
            .no-print { display: none; }
            .page-break { page-break-after: always; }
        }
        table { border-collapse: collapse; width: 100%; }
        th, td { border: 1px solid #ddd; padding: 8px; }
    </style>
    <div class='content'>
        <h1>Optimized Report</h1>
        <table>
            <thead><tr><th>Item</th><th>Value</th></tr></thead>
            <tbody><tr><td>Sales</td><td>$1,000</td></tr></tbody>
        </table>
        <div class='page-break'></div>
        <h2>Next Section</h2>
    </div>";
var renderer = new ChromePdfRenderer();
var pdf = renderer.RenderHtmlAsPdf(optimizedHtml);
pdf.SaveAs("optimized-report.pdf");

using IronPdf;

string optimizedHtml = @"
    <style>
        @media print {
            .no-print { display: none; }
            .page-break { page-break-after: always; }
        }
        table { border-collapse: collapse; width: 100%; }
        th, td { border: 1px solid #ddd; padding: 8px; }
    </style>
    <div class='content'>
        <h1>Optimized Report</h1>
        <table>
            <thead><tr><th>Item</th><th>Value</th></tr></thead>
            <tbody><tr><td>Sales</td><td>$1,000</td></tr></tbody>
        </table>
        <div class='page-break'></div>
        <h2>Next Section</h2>
    </div>";
var renderer = new ChromePdfRenderer();
var pdf = renderer.RenderHtmlAsPdf(optimizedHtml);
pdf.SaveAs("optimized-report.pdf");

This HTML structure includes print media queries, proper table formatting, and explicit page breaks. The CSS ensures consistent styling while the semantic structure improves accessibility and rendering reliability. Page break controls give you precise control over content flow across pages.

Output

Handling Complex Layouts

Complex layouts require careful attention to rendering behavior. Set appropriate viewport widths to control responsive design breakpoints. Use the FitToPaper options to scale content appropriately. For multi-column layouts, consider using CSS columns instead of floats or flexbox for better page flow. Test layouts with different content volumes to ensure consistent appearance.

When working with large documents, consider file size optimization. Compress images before embedding them in HTML, use system fonts where possible, and avoid unnecessary embedded resources. Large PDFs can impact both generation time and end-user experience.

Deployment Considerations

IronPDF supports various deployment scenarios, including Windows services, web applications, Docker containers, and cloud platforms. The library includes native dependencies that must be present in the deployment environment. For Linux deployments, ensure required packages are installed. Docker deployments benefit from using official base images that include necessary dependencies.

Container deployments require specific attention to font availability. Include custom fonts in your container image or reference system fonts consistently. The Chrome rendering engine adapts to available system resources, but adequate memory allocation improves performance for complex documents. Server-side PDF generation benefits from proper resource management and caching strategies.

IronPDF also supports accessibility standards, ensuring generated PDFs comply with Section 508 requirements. For troubleshooting deployment issues, the Stack Overflow IronPDF tag provides community-driven solutions. IronPDF's cross-platform compatibility guide covers Linux and Docker deployment in detail. For performance tuning in high-throughput scenarios, Microsoft's .NET performance guidance provides relevant background on memory management and async patterns that apply to server-side document generation.