1. IronPDF
  2. Comenzar
  3. Uso en Windows

Using IronPDF for .NET on Windows

Curtis Chau
Curtis Chau
Actualizado:
This article was translated from English: Does it need improvement?
Translated
View the article in English

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.Slim
SHELL

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"));
' 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"))
$vbLabelText   $csharpLabel

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

Preguntas Frecuentes

¿Qué versiones de Windows son compatibles con la herramienta PDF?

IronPDF es compatible con Windows 10, 11, y las versiones de Windows Server 2022, 2016, 2019, y 2012 en el modo de Experiencia de Escritorio. Sin embargo, Windows Server 2019 y 2012 no son soportados en modo Core.

¿Cómo puedo manejar tareas PDF en versiones no compatibles de Windows?

Para versiones no compatibles de Windows, puedes usar IronPDF en Modo Engine. Esto te permite manejar funciones intensivas en rendimiento de manera remota, evitando problemas de compatibilidad específicos de la plataforma.

¿Existen requisitos de hardware específicos para ejecutar IronPDF?

Sí, el requisito mínimo es 1 Núcleo y 1.75 GB de RAM, mientras que la especificación recomendada es 2 Núcleos y 8 GB de RAM o más, debido a la dependencia de IronPDF en el motor Chromium para el renderizado.

¿Se puede usar IronPDF sin conexión?

Sí, IronPDF se puede usar sin conexión descargando el DLL y añadiéndolo como referencia en tu proyecto. También hay un instalador disponible para Windows para facilitar el uso sin conexión.

¿Cuál es el proceso para configurar IronPDF en Modo Engine?

Para configurar IronPDF en Modo Engine, instala el paquete `IronPdf.Slim` desde NuGet, configura los ajustes de conexión para apuntar IronPDF a tu instancia de IronPdfEngine usando el código proporcionado, y conéctalo al host remoto.

¿Por qué puede haber problemas de compatibilidad con Windows Nano Server?

Windows Nano Server no soporta IronPDF debido a la falta de DLLs de medios/gráficos requeridos por el motor Chromium. Sin embargo, se está desarrollando soporte para Windows Server Core, que podría extenderse a Nano Server en el futuro.

¿Qué paquetes de NuGet son necesarios para la herramienta PDF?

El paquete principal de IronPDF NuGet depende de IronPdf.Native.Chrome.Windows, que incluye los binarios necesarios de Chrome para arquitecturas x86 y x64.

¿Cómo utiliza IronPDF Chromium para el renderizado?

IronPDF utiliza el motor Chromium para convertir HTML a PDF, asegurando una precisión pixel-perfecta similar a la función de impresión de Chrome. Este proceso requiere una potencia de cálculo significativa, de ahí las especificaciones de hardware.

Curtis Chau
Curtis Chau
  Chatea con el equipo de ingeniería ahora
Escritor Técnico

Curtis Chau tiene una licenciatura en Ciencias de la Computación (Carleton University) y se especializa en el desarrollo front-end con experiencia en Node.js, TypeScript, JavaScript y React. Apasionado por crear interfaces de usuario intuitivas y estéticamente agradables, disfruta trabajando con frameworks modernos y creando manuales bien ...

Leer más
¿Listo para empezar?
Nuget Descargas 16,154,058 | Versión: 2025.11 recién lanzado