Click or drag to resize

Requirements and Recommendations

ExpertPdf Anywhere runs on Windows, Linux and macOS, on .NET and on .NET Framework.

Frameworks
  • .NET 11, .NET 10, .NET 9 and .NET 8, and every framework that runs .NET Standard 2.0 libraries: .NET Framework 4.6.1 and later, .NET Core 2.0 and later.

  • Console applications, services, ASP.NET Core and ASP.NET web applications, Azure Functions, AWS Lambda functions and desktop applications.

  • The managed library is AnyCPU. The process can be 32-bit or 64-bit with either engine package: when the architectures differ, the Chromium engine runs in a separate process.

Platforms

Platform

Native package

Notes

Windows x64

ExpertPdf.Anywhere.Native.win-x64

Windows 10, Windows 11, Windows Server 2016 and later; Windows Server Core containers.

Windows x86

ExpertPdf.Anywhere.Native.win-x86

32-bit processes on the same systems.

Linux x64

ExpertPdf.Anywhere.Native.linux-x64

glibc 2.30 or later: Ubuntu 20.04+, Debian 11+, RHEL 9 and compatible, Amazon Linux 2023, the official .NET container images. No system package is needed: the Chromium libraries come with the package.

Linux ARM64

ExpertPdf.Anywhere.Native.linux-arm64

The same distributions on ARM64 (AWS Graviton, Azure Cobalt, Ampere).

macOS

ExpertPdf.Anywhere.Native.osx-arm64

macOS 13 and later on Apple Silicon.

Alpine Linux (musl) and Windows Nano Server are not supported: the Chromium engine needs glibc on Linux and the Windows desktop libraries on Windows.

Fonts

The library uses the fonts installed on the system. On Linux and macOS hosts without fonts - Docker images, AWS Lambda, Azure App Service on Linux - add the ExpertPdf.Anywhere.Fonts package (Noto fonts for every script); without it only Latin text has a font there. Fonts added to a fonts folder next to the application are used on every platform.

Resources

A conversion needs memory in proportion to the size of the page; complex pages with many images can need several hundred MB. The Chromium engine runs inside the application by default and keeps its browser processes for the life of the application, which makes each conversion faster. For high volumes, see Multithreading Support.

See Also