IronPdf
IronPDF allows developers to create, edit and extract pdf content within .NET Core or Framework Apps. The Iron PDF library takes the frustration out of generating PDF documents by not relying on proprietary APIs. "Html-To-Pdf" renders pixel-perfect PDFs from open standard document types: HTML, JS, CSS, JPG, PNG, GIF, and SVG. In short, it uses skills that developers already posses. Key features include: * "Html-To-Pdf" creates PDF files from HTML, CSS, JavaScript, and Images. * "Url-To-Pdf" generates PDFs from existing html pages by simply providing their URL. * "ASPX-To-Pdf" converts ASP.NET web forms directly into downloadable pdfs. * "Image-To-PDF" creates PDF documents from image files. * PDF to Image functionality can render PDF documents to image files. * Extract text and images from existing PDFs. * Create, Fill and read data from PDF forms. * Merge, Split and Manipulate PDFs to edit PDF structure and content. * Add Page Numbers, Headers, Footers, Annotations, Bookmarks, Watermarks, Text & Image Assets. * Edit, Stamp and Watermark PDF files with text, images and HTML * Apply HTML or PDF backgrounds to PDF pages * Digitally Sign PDF documents (not supported in .Net Core) IronPDF can be used within ASP.NET Core and Framework projects for MVC, Web, Console & Desktop Applications. Requires either .Net Framework 4.0 or above on Windows, or .Net Core 2.0 or above on Windows, MacOS or Linux. Compatible with cloud hosting services including Microsoft Azure. Licensing & Support available for commercial deployments. For code examples, documentation & more visit http://ironpdf.com/ For support please email us at [email protected]
Install
dotnet add package IronPdf --version 5.2.0.1
Install-Package IronPdf -Version 5.2.0.1
<PackageReference Include="IronPdf" Version="5.2.0.1" />
Frameworks
Dependencies
Adoption guide
A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
Compatibility metadata lists 1 target framework; confirm the exact target used by your application.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.