PDF Export for ASP.NET Web Forms

Where the Gap Shows Up

A Web Forms page usually renders its invoice, statement, or report as styled HTML already. Staff and customers then want that same view as a portable file they can save, email, or print. A separate PDF template means a second layout that drifts from the first. The browser print dialog yields different results on every machine. What teams need is a server-side PDF that mirrors the page on screen.

Rendering the Page in Place

IronPDF converts the live ASPX page from inside the Page_Load event. The AspxToPdf.RenderThisPageAsPdf method reuses the page already built for the web view, so styling, links, and form fields carry over.

using IronPdf;

public partial class Invoice : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        AspxToPdf.RenderThisPageAsPdf(AspxToPdf.FileBehavior.Attachment, "Invoice.pdf");
    }
}

using IronPdf;

public partial class Invoice : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        AspxToPdf.RenderThisPageAsPdf(AspxToPdf.FileBehavior.Attachment, "Invoice.pdf");
    }
}

Imports IronPdf

Public Partial Class Invoice
    Inherits System.Web.UI.Page

    Protected Sub Page_Load(sender As Object, e As EventArgs)
        AspxToPdf.RenderThisPageAsPdf(AspxToPdf.FileBehavior.Attachment, "Invoice.pdf")
    End Sub
End Class

FileBehavior.Attachment triggers a download with a chosen filename. FileBehavior.InBrowser displays the document inline instead.

Controlling the Output

Rendering options cover the details that make output fit for distribution: headers, footers, page numbering, and a print stylesheet that strips screen-only navigation.

var options = new ChromePdfRenderOptions
{
    CssMediaType = IronPdf.Rendering.PdfCssMediaType.Print,
    TextFooter = new TextHeaderFooter
    {
        LeftText = "{date} - {time}",
        RightText = "Page {page} of {total-pages}"
    }
};
AspxToPdf.RenderThisPageAsPdf(AspxToPdf.FileBehavior.Attachment, "Invoice.pdf", options);

var options = new ChromePdfRenderOptions
{
    CssMediaType = IronPdf.Rendering.PdfCssMediaType.Print,
    TextFooter = new TextHeaderFooter
    {
        LeftText = "{date} - {time}",
        RightText = "Page {page} of {total-pages}"
    }
};
AspxToPdf.RenderThisPageAsPdf(AspxToPdf.FileBehavior.Attachment, "Invoice.pdf", options);

Imports IronPdf.Rendering

Dim options As New ChromePdfRenderOptions With {
    .CssMediaType = PdfCssMediaType.Print,
    .TextFooter = New TextHeaderFooter With {
        .LeftText = "{date} - {time}",
        .RightText = "Page {page} of {total-pages}"
    }
}
AspxToPdf.RenderThisPageAsPdf(AspxToPdf.FileBehavior.Attachment, "Invoice.pdf", options)

Settings That Decide a Clean Conversion

A handful of choices determine whether conversion holds up under load:

• Dynamic content: Pages using Ajax or client-side charts need EnableJavaScript along with a WaitFor rule so rendering captures the finished page. See the WaitFor guide.
• Print styling: Setting CssMediaType to Print applies a dedicated stylesheet, which keeps buttons and menus out of the document.
• Throughput: Chromium rendering is resource intensive, so async processing keeps high-traffic endpoints responsive.

One line, no rewrite

That single call inside an existing page gives a Web Forms application invoice downloads, printable statements, and exportable reports, no migration required. Full method reference and configuration options live in the ASPX to PDF guide.