Best way to conver HTML content in to PDF

Nithishkumar K

6mo709General

I am working on a WPF application where I need to implement a document generation and printing feature.

My Goal: I have dynamically generated HTML content (with CSS). I need to:

Convert this HTML content into a PDF document.
Ensure the output is strictly formatted to fit an A4 sheet (handling page breaks, margins, etc.).
Send this generated PDF directly to a printer.

My Question: What is the most reliable, industry-standard approach to achieve this in a modern WPF application?

I am looking for recommendations on the best libraries or built-in approaches to use. Specifically, I’d love to know:

Which libraries are best suited for this (e.g., WebView2, PuppeteerSharp, wkhtmltopdf, iText7, QuestPDF)?
Are there any caveats I should watch out for regarding CSS support and A4 pagination?
How can I handle the printing part smoothly (e.g., silent printing vs. showing the Windows print dialog)?

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Margaret Lewis6mo ago
Accepted answer
Here are direct answers to your questions without extra framing.
1) Which libraries are best?
Best overall (recommended)
- PuppeteerSharp or Playwright for .NET
  These use a real Chromium engine, so they render HTML/CSS exactly like a browser. This is the most reliable and widely adopted approach today for HTML ? PDF.
Good alternative (simpler, commercial)
- IronPDF
  Easier setup, still Chromium-based, but paid.
Situational options
- QuestPDF
  Excellent if you are willing to build documents in C# instead of rendering HTML. Not suitable if your source is already HTML.
- iText7 (pdfHTML)
  Works for simpler HTML, but limited CSS support compared to browsers.
Not recommended for new work
- wkhtmltopdf (and wrappers like DinkToPdf)
  Outdated rendering engine, poor support for modern CSS (flexbox, grid), and no longer actively maintained.
2) Caveats (CSS support, A4 pagination)
CSS support
- Chromium-based tools (PuppeteerSharp / Playwright / IronPDF):
  Full support for modern CSS (flexbox, grid, media queries, print styles)
  Best fidelity with real browser output
- Non-browser engines:
  Often fail with flexbox, grid, advanced layouts
  Require workarounds or simplified HTML
A4 pagination
Regardless of library, correct pagination depends on your CSS.
Key rules:
```
@page {
  size: A4;
  margin: 20mm;
}

.page-break {
  break-before: page;
}

.no-break {
  break-inside: avoid;
}
```
Important points:
- Use @page to define A4 size and margins
- Use break-before, break-after, break-inside
- Avoid relying on pixel-perfect layout without print CSS
- Test with real content (long tables, images, etc.)
Common pitfalls
- Content overflowing due to missing margins
- Tables splitting awkwardly across pages
- Fonts not embedding correctly
- Differences between screen CSS and print CSS
3) Printing (silent vs dialog)
Show print dialog (simplest)
- Open the PDF with default viewer and trigger print:
```
Process.Start(new ProcessStartInfo {
    FileName = pdfPath,
    Verb = "print"
});
```
- This depends on the system’s default PDF viewer and shows UI.
Silent printing (recommended for production)
Option A: Use a PDF rendering library
- PDFium (via PdfiumViewer or similar)
- Load PDF and send directly to a printer:
```
using (var document = PdfiumViewer.PdfDocument.Load(pdfPath))
{
    using (var printDoc = document.CreatePrintDocument())
    {
        printDoc.PrinterSettings.PrinterName = "YourPrinter";
        printDoc.PrintController = new StandardPrintController(); // no dialog
        printDoc.Print();
    }
}
```
Option B: Use WebView2
- Load the PDF and call:
```
await webView.CoreWebView2.PrintAsync();
```
- Can be configured to suppress UI in some cases, but less predictable than PDFium.
Bottom line
- Use PuppeteerSharp or Playwright for HTML ? PDF.
- Control layout using proper print CSS (@page, page breaks).
- Use PDFium-based printing for reliable silent printing.
This combination is currently the most robust and production-proven approach for WPF applications.
+1
pilalo Jovanitho1mo ago
There isn’t really one “best” option here—it depends on how closely your PDF needs to match the original HTML/CSS.
A few options worth considering:
- WebView2 – A good fit if the HTML is already designed for browser rendering. It supports both printing to PDF and printing directly to a printer, including programmatic/silent printing.
- PuppeteerSharp – A good choice when you want Chromium-based rendering and more control over PDF generation. It supports A4, margins, page ranges, headers/footers, and CSS page sizing.
- iText 7 + pdfHTML – More PDF-focused. It can convert HTML/CSS to PDF and is worth considering when you need more control over the resulting PDF.
- Spire.PDF – A good option for .NET/WPF applications when you need to generate and further manipulate the PDF within the same application, without relying on a browser-based rendering engine.
- QuestPDF – Worth considering if HTML is not a strict requirement. It uses a C# API to build the PDF layout directly, which can give you more predictable control over A4 pages and document structure.
- wkhtmltopdf – Still useful for some existing projects, but for a new WPF application I would generally look at the more actively integrated Chromium or .NET-based options first.
For your particular case, I’d first decide whether browser-level HTML/CSS compatibility or PDF/document control is more important. That choice will narrow down the options considerably.
For A4 output, also test your actual templates with @page, margins, break-* rules, fonts, images, and tables, since pagination behavior can vary between rendering engines.
0
williamswelsh4mo ago
If preserving the original HTML layout is important, the conversion engine matters more than the output format itself. CSS support, embedded fonts, images, page breaks, and JavaScript-rendered content can all affect the final PDF. For simple HTML, many libraries work well, but for complex or responsive pages, it's worth testing a few options to see which produces the most accurate results. Also, if you're converting multiple HTML files, choosing a solution that supports batch processing can save a lot of time.
0
Deepika Sawant6mo ago
WebView2 ? Export to PDF ? PdfiumViewer ? Print silently or via dialog. This balances modern CSS support, native integration, and smooth printing workflows.
- Use WebView2 or PuppeteerSharp for HTML ? PDF conversion (best CSS fidelity).
- Apply CSS print styles for A4 formatting.
  Use CSS print styles (@page { size: A4; margin: 20mm; }).
  Control page breaks with page-break-before, page-break-after, or break-inside.
  Test with complex layouts—tables, images, headers/footers.
  PuppeteerSharp and WebView2 handle CSS print rules best; wkhtmltopdf is more limited.
- Use PdfiumViewer or WPF’s PrintDialog for printing.
  Silent Printing:
  Use System.Printing or PrintDocument in WPF to send PDFs directly to a printer.
  Requires a PDF rendering backend (e.g., Adobe Reader COM automation, or libraries like PdfiumViewer).
  Windows Print Dialog:
  Use PrintDialog in WPF for user-controlled printing.
  More user-friendly, but not silent.
  Best Practice:
  Generate PDF ? Load into a lightweight viewer (PdfiumViewer or Syncfusion PDF Viewer) ? Print via WPF print APIs.
  This avoids relying on external apps like Adobe Reader.
- For enterprise-grade compliance (PDF/A, accessibility), consider iText7.
0

Best way to conver HTML content in to PDF

1) Which libraries are best?

Best overall (recommended)

Good alternative (simpler, commercial)

Situational options

Not recommended for new work

2) Caveats (CSS support, A4 pagination)

CSS support

A4 pagination

Common pitfalls

3) Printing (silent vs dialog)

Show print dialog (simplest)

Silent printing (recommended for production)

Bottom line