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 Windows 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.
After 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"))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 operating systems are compatible with IronPDF on Windows?
IronPDF supports Windows 10, 11, as well as various versions of Windows Server, including 2022, 2019, 2016, and 2012, with different levels of compatibility depending on the specific server configuration.
Can IronPDF be used on Windows Server Core or Nano?
Currently, IronPDF is working towards supporting Windows Server Core and Nano. Issues arise due to missing DLLs required by Chromium that are present in the Desktop version but absent in the more stripped-down versions.
What to do if my Windows version is not fully supported?
If your Windows version is not fully supported, consider using IronPDF in Engine mode. This configuration allows running IronPDF remotely and can help avoid platform-specific compatibility issues.
How does using Engine mode in IronPDF affect my coding?
When using Engine mode with IronPDF, you should install the IronPdf.Slim package and configure it to connect to your IronPdfEngine instance. This setup manages the extra functionalities in the Native package remotely.
What hardware specifications are recommended for running IronPDF?
IronPDF requires Chromium for rendering, so the minimum hardware specification includes 1 core and 1.75 GB of RAM, while the recommended setup is 2 cores and 8 GB of RAM or above.
How can I install IronPDF for offline usage?
For offline usage of IronPDF, you can download the IronPdf.dll file and add it to your project references, enabling you to work without internet dependency.
Is there a NuGet package available for IronPDF?
Yes, IronPDF offers a NuGet package that includes dependencies such as IronPdf.Native.Chrome.Windows, which contains the necessary Chrome binary for different architectures.
What is the importance of Windows Server DataCenter for IronPDF functionality?
Windows Server DataCenter edition, being more comprehensive than the Standard edition, contains all components necessary for running IronPDF and additional storage enhancements, making it advantageous for robust PDF operations.
Are there any compatibility issues with specific IronPDF versions on Windows Server?
Yes, versions 2023.3.2 - 2024.2.2 of IronPDF are not compatible with Windows Server 2012.
What are the benefits of using the IronPdf.Slim package?
The IronPdf.Slim package is beneficial for those using IronPDF in Engine mode, as it includes just the essentials, allowing the bulkier functions to be managed by the remote IronPdfEngine.
Curtis Chau holds a Bachelor’s degree in Computer Science (Carleton University) and specializes in front-end development with expertise in Node.js, TypeScript, JavaScript, and React. Passionate about crafting intuitive and aesthetically pleasing user interfaces, Curtis enjoys working with modern frameworks and creating well-structured, visually appealing manuals.
