Using IronPDF for .NET on Windows
IronPDF supports Windows 10, 11, and Windows Server for .NET 8, 7, 6, Core, .NET Standard, and .NET Framework.
Important Notes about Windows Server
We support Windows Server 2022 and 2016 both in Desktop Experience and Core variants, while only supporting 2019 and 2012 in the Desktop Experience version.
Windows Server 2022 & 2016
- Windows Server 2022 & 2016 with a UI ("Desktop experience")
- Windows Server 2022 & 2016 command-line only ("Core").
Windows Server 2019 & 2012
- Windows Server 2019 & 2012 with a UI ("Desktop experience")
- Windows Server 2019 & 2012 command-line only ("Core").
IronPDF version 2023.3.2 - 2024.2.2 are not compatible with Window Server 2012.
We are making an effort to support the Core and Nano versions of Windows Server. There isn't an issue with the operating system architecture that is blocking our support. It is likely due to the media/graphics DLLs that Chromium (Chrome Renderer) requires to render HTML to PDF, which are present in the "Desktop" version of Windows Server but missing from the stripped-down version.
Furthermore, since Windows Nano Server is a stripped-down version of Windows Server Core, once we fully support Windows Server Core, we will look into supporting Windows Nano Server.
Windows Nano Server / Server Core in .NET 6 do not support System.Drawing
More details
If your version of Windows is not supported, consider using IronPDF in Engine Mode
What's the difference between Native & Engine?
IronPDF has some performance-intensive functions that you may choose to run remotely. While IronPDF does not require IronPdfEngine to run, setting up IronPdfEngine as a remote service is an optional way to avoid platform-specific Chrome compatibility issues on older operating systems and mobile environments.
How does using Engine change the way I code with IronPDF?
This will allow you to use older versions of Windows such as Windows Server 2012.
When using the Engine configuration, we recommend installing IronPdf.Slim instead of the full IronPdf package from NuGet, as the Engine manages all the extra bulk included in the Native package.
# Install the IronPdf.Slim package using Package Manager Console
:InstallCmd Install-Package IronPdf.Slim# Install the IronPdf.Slim package using Package Manager Console
:InstallCmd Install-Package IronPdf.SlimAfter installing IronPdf.Slim, configure the connection settings by pointing IronPDF to your IronPdfEngine instance. Add the following code at the startup of your application (or before calling any IronPDF method):
// Configure IronPDF to connect to the remote IronPdfEngine instance
// Replace "123.456.7.8:33350" with the actual remote host and port
Installation.ConnectToIronPdfHost(IronPdf.GrpcLayer.IronPdfConnectionConfiguration.RemoteServer("123.456.7.8:33350"));// Configure IronPDF to connect to the remote IronPdfEngine instance
// Replace "123.456.7.8:33350" with the actual remote host and port
Installation.ConnectToIronPdfHost(IronPdf.GrpcLayer.IronPdfConnectionConfiguration.RemoteServer("123.456.7.8:33350"));' Configure IronPDF to connect to the remote IronPdfEngine instance
' Replace "123.456.7.8:33350" with the actual remote host and port
Installation.ConnectToIronPdfHost(IronPdf.GrpcLayer.IronPdfConnectionConfiguration.RemoteServer("123.456.7.8:33350"))Windows Server Standard & DataCenter
Based on the differences highlighted in the Microsoft documentation "Comparison of Standard and Datacenter editions of Windows Server 2016", Windows Server DataCenter contains all the components of Windows Server Standard, along with additional storage enhancement components. IronPdf would also work on Windows Server DataCenter Desktop Experience.
Windows Specific Install
NuGet
The main IronPdf NuGet package depends on IronPdf.Native.Chrome.Windows, which contains the Chrome binary for both x86 and x64 architectures.
- The IronPdf package supports x86 and x64 Windows architectures.
If targeting a specific runtime, you can delete the /runtimes folder not in use (either x86 or x64).
DLL Download
For offline usage, you can download the DLL and add a reference to your project.
Installer
We also provide an installer for Windows. In Visual Studio Solution Explorer, right-click on Dependencies and select Add Project Reference. Then, click Browse and include all the DLL files extracted from the installer.
Hardware Specification
IronPDF uses Chromium to render HTML to PDF. The Chromium engine renders PDFs with pixel-perfect accuracy akin to Chrome's print feature. The hardware specifications are primarily for running the Chromium engine, which takes most of the computing power.
- Minimum: 1 Core & 1.75 GB of RAM
- Recommended: 2 Cores & 8 GB of RAM or above
Frequently Asked Questions
What Windows versions are compatible with the PDF tool?
IronPDF supports Windows 10, 11, and Windows Server versions 2022, 2016, 2019, and 2012 in Desktop Experience mode. However, Windows Server 2019 and 2012 are not supported in Core mode.
How can I handle PDF tasks on unsupported Windows versions?
For unsupported Windows versions, you can use IronPDF in Engine Mode. This allows you to handle performance-intensive functions remotely, bypassing platform-specific compatibility issues.
Are there specific hardware requirements for running IronPDF?
Yes, the minimum requirement is 1 Core and 1.75 GB of RAM, while the recommended specification is 2 Cores and 8 GB of RAM or above, due to IronPDF's reliance on the Chromium engine for rendering.
Can IronPDF be used offline?
Yes, IronPDF can be used offline by downloading the DLL and adding it as a reference in your project. An installer is also available for Windows to facilitate offline use.
What is the process for setting up IronPDF in Engine Mode?
To set up IronPDF in Engine Mode, install the `IronPdf.Slim` package from NuGet, configure the connection settings to point IronPDF to your IronPdfEngine instance using the provided code, and connect to the remote host.
Why might there be compatibility issues with Windows Nano Server?
Windows Nano Server does not support IronPDF due to missing media/graphics DLLs required by the Chromium engine. However, support for Windows Server Core is being developed, which might extend to Nano Server in the future.
Which NuGet packages are necessary for the PDF tool?
The main IronPDF NuGet package relies on IronPdf.Native.Chrome.Windows, which includes the necessary Chrome binaries for x86 and x64 architectures.
How does IronPDF utilize Chromium for rendering?
IronPDF uses the Chromium engine to render HTML to PDF, ensuring pixel-perfect accuracy similar to Chrome's print feature. This process requires significant computing power, hence the hardware specifications.
%20-107C10?logo=visual-studio-code&color=106E58){kind=icon}
