I'm building a .NET app that needs to create PDFs from templates, what do you recommend?

It depends a bit on what “templates” means in your app, but for a .NET application I’d generally recommend one of these approaches:

Best overall options

1) HTML/CSS templates + a PDF renderer

Recommendation if your PDFs are document-like, branded, or moderately dynamic.

Workflow:

• Design templates in HTML/CSS
• Inject data with a templating engine
• Render to PDF using a headless browser or PDF renderer

Popular .NET pieces:

• Templating: Razor, Scriban, Handlebars.Net
• PDF rendering: Microsoft Playwright, PuppeteerSharp, wkhtmltopdf wrappers, or commercial libraries

Pros:

• Easy to design and maintain
• Great for invoices, reports, letters, certificates
• Uses familiar web tech
• Good for complex layouts compared to pure PDF drawing

Cons:

• Page breaks and print-specific styling can be tricky
• Rendering fidelity depends on the engine

Best when: you want templates that designers or web developers can edit.

---

2) Commercial PDF libraries with template/form support

Recommendation if you need high reliability and production-grade PDF control.

Common commercial options:

• Syncfusion PDF
• Aspose.PDF
• IronPDF
• PDFTron

Pros:

• Strong support, good docs
• Better control over pagination, fonts, images, forms
• Often easier for enterprise needs
• Less fiddly than rolling your own rendering pipeline

Cons:

• Licensing cost
• Some APIs can be more verbose

Best when: PDFs are mission-critical and you need consistent output.

---

3) Generate PDFs programmatically

Recommendation if your documents are structured and you want full control.

Libraries:

• QuestPDF (very popular in .NET)
• iText 7 (powerful, but license considerations)
• PdfSharp / MigraDoc (older, simpler)

Pros:

• Full control over layout
• Strong for invoices, statements, labels, structured docs
• Very deterministic

Cons:

• Less like “templates”
• More code to define layout
• Harder for non-developers to edit

Best when: your PDFs are mostly data-driven and consistency matters more than visual editing.

---

My practical recommendation

If you’re starting a new .NET app and want template-based PDF generation, I’d usually suggest:

Razor templates + QuestPDF or Playwright

• Use Razor if you want template files that feel like MVC views
• Use QuestPDF if you want programmatic layout with excellent .NET ergonomics
• Use Playwright if your team already knows HTML/CSS and wants browser-like rendering

---

Quick decision guide

• Need editable visual templates? → HTML/CSS + Playwright
• Need precise, code-driven documents? → QuestPDF
• Need enterprise-grade feature set? → Aspose / Syncfusion / PDFTron
• Need form filling over existing PDFs? → Commercial PDF libraries or iText

---

If you want a strong default choice

For most .NET apps:
QuestPDF is an excellent first pick if you’re generating documents from data.
If your “templates” are already HTML-like or will be maintained by web folks, go with Razor + Playwright.

If you tell me:

• whether your templates are HTML or designed in code,
• whether you need exact print fidelity,
• and whether this is commercial or open-source,

I can recommend a specific stack and even show a sample implementation.