Using EvoPdf Chromium for .NET on Azure App Service for Windows
EvoPdf Chromium for .NET is a library that can be easily integrated into applications running on Azure App Service for Windows, enabling conversion of web pages and HTML strings to PDF documents or images.
The HTML to PDF converter component uses a Chromium-based rendering engine capable of processing modern HTML, CSS and JavaScript content in compliance with the latest web standards.
Platform Compatibility
EvoPdf Chromium for .NET runs in Azure App Service 64-bit applications without requiring any installation or prior configuration of the deployment environment. The steps required to use the library in your own applications deployed to Azure App Service are detailed below.
The library targets .NET Standard 2.0 and is compatible with any .NET Core or .NET Framework application that supports this standard.
Create a .NET Application for Azure App Service on Windows
Create a new .NET project in Visual Studio and use the NuGet Package Manager to add a reference to the EvoPdf.Chromium.Windows package.
After installing the package, add the using EvoPdf.Chromium; directive at the top of your source files to access the EvoPdf Chromium API.
Example code snippets and usage details are available in the Getting Started on Windows documentation section.
Publish Your Application to Azure App Service on Windows
Uncheck the Deploy as ZIP package option when creating the publish profile in Visual Studio.
HTML to PDF conversion can be resource-intensive and may require significant CPU and memory depending on the complexity of the HTML content being processed.
The B1 plan (1 core, 1.75 GB RAM) is the minimum supported hosting option and may be used for basic or low-volume scenarios. For development and testing, we recommend at least a B2 plan (2 cores, 3.5 GB RAM).
For production environments, especially when processing complex or large documents, a Premium plan such as P1v3 (2 vCPUs, 8 GB RAM) or higher is strongly recommended. Premium plans provide the performance and reliability required for consistent PDF generation under load.
The Free and Shared plans are not suitable for running the converter.
After the profile is created, ensure that Portable is selected as the Target Runtime before publishing.
Publish the application to Azure App Service on Windows.
Run Application
At this point, everything should be configured and you can run your application. Alternatively, you can follow the same steps from this guide to build and publish our ASP.NET demo application to Azure App Service on Windows.