.NET PDF library comparisons and alternatives.
Moving an application off another HTML to PDF library, or choosing one? Each page shows what changes in your code, what stays the same, and where SelectPdf behaves differently.
Ten .NET PDF libraries. Same tasks, measured.
Ten C# PDF libraries put through the same 14 tasks, with compilable samples and a benchmark on Windows and Linux: speed, throughput, memory, rendering fidelity, PDF/A and PDF/UA, PDF tasks and Docker deployment. The results are published in full, including the measures where other libraries lead.
Maintained by SelectPdf, one of the libraries compared. The source code, raw results, methodology and limitations are public.
DinkToPdf alternative for .NET
Keep your DinkToPdf code and render with Chromium instead of wkhtmltopdf, on Windows, Linux, macOS on Apple Silicon and Docker.
SelectPdf vs IronPDF: an IronPDF alternative for .NET
Chromium HTML to PDF at half the price for a single developer, on Windows, Linux, macOS and Docker, with the IronPDF to SelectPdf API mapping, code side by side and a measured comparison.
iText alternative for .NET
HTML to PDF with Chromium instead of pdfHTML's own layout, under a published perpetual license instead of the AGPL, with the API mapping and a measured comparison.
Playwright PDF alternative for .NET
HTML to PDF with Chromium from a NuGet package instead of a browser install, with PDF/A, PDF/UA and PDF editing, the Playwright API mapping and a measured comparison.
PuppeteerSharp alternative for .NET
HTML to PDF with Chromium and no browser to download or launch, with PDF/A, PDF/UA and PDF editing, the PuppeteerSharp API mapping and a measured comparison.
wkhtmltopdf alternative for .NET
wkhtmltopdf is archived. Move your .NET wrapper or command line calls to Chromium rendering, keeping the API for DinkToPdf and WkHtmlToPdfDotNet.
Ready to try it? The free Community Edition converts documents up to 5 pages, and the how-to guides show complete C# programs for common PDF tasks.