PDF.Core
IronPDF for .Net Core 2 and above allows developers to create, edit and extract PDF content within .Net Core Applications & Websites. The Iron PDF Core 2+ 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, Watermarks, Tables, Text and Image Assets. * Edit, Stamp and Watermark PDF files with text, images and HTML * Apply HTML or PDF backgrounds to PDF pages IronPDF can be used within ASP.NET projects, MVC, Web Services, Console & Desktop Applications. Requires .Net Core 2 or above on Windows, Linux, MacOS and Azure platyforms. 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 PDF.Core --version 4.6.0
Install-Package PDF.Core -Version 4.6.0
<PackageReference Include="PDF.Core" Version="4.6.0" />
Frameworks
Dependencies
Adoption guide
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
NuGet marks this package as deprecated and points to IronPdf as an alternative.
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.