List icon Contents

System requirements

This page describes the software and hardware configurations required to run a program based on DotNetBrowser.

Software requirements


  • .NET Framework 4.5 — 4.8.1 (Windows only)
  • .NET Core 2.2 (core functionality only)
  • .NET Core 3.0, 3.1
  • .NET 5 - 8

Avalonia UI

  • 11.0.4 and higher


DotNetBrowser supports x86, x64, and ARM64:

  • Windows 11
  • Windows 10
  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016

Windows 7/8/8.1 and the corresponding Windows Server versions are no longer supported.


DotNetBrowser supports the following Linux distributions (x64 and ARM64):

  • Ubuntu 18.04 or later
  • Debian 10 or later
  • Fedora Linux 38 or later
  • openSUSE 15.5 or later
  • RedHat Enterprise Linux 7 or later

Chromium does not work in the headless environment. In order to use DotNetBrowser in headless environments including Linux-based Docker containers and WSL, you need to start X server.


DotNetBrowser supports macOS 10.15 Catalina and higher (x64 and ARM64).

Hardware requirements

HiDPI monitors

DotNetBrowser recognizes the device scale factor that is used in the environments with HiDPI displays and renders HTML content with the respect to that scale factor.

The WPF and WinForms BrowserView controls are compatible with different DPI awareness modes. DotNetBrowser gets the DPI awareness settings from the application configuration where it is used and configures Chromium processes to use the same DPI awareness mode.

DotNetBrowser supports high DPI only if your .NET desktop application supports it.

These MSDN articles describe how to create DPI-aware .NET desktop applications:


DotNetBrowser does not support mobile devices with iOS and Android.

Other Environments

You can try running DotNetBrowser on other platforms or versions not listed here, but we do not guarantee that all DotNetBrowser functionality will work properly there.

DotNetBrowser cannot be used in the environments that prevent the User32/GDI32 APIs from being called, such as Azure App Services or Azure Functions. With these limitations, it is not possible to launch the Chromium engine.

Go Top