DotNetBrowser.Wpf.x64
4.3.1
Prefix Reserved
dotnet add package DotNetBrowser.Wpf.x64 --version 4.3.1
NuGet\Install-Package DotNetBrowser.Wpf.x64 -Version 4.3.1
<PackageReference Include="DotNetBrowser.Wpf.x64" Version="4.3.1" />
<PackageVersion Include="DotNetBrowser.Wpf.x64" Version="4.3.1" />
<PackageReference Include="DotNetBrowser.Wpf.x64" />
paket add DotNetBrowser.Wpf.x64 --version 4.3.1
#r "nuget: DotNetBrowser.Wpf.x64, 4.3.1"
#:package DotNetBrowser.Wpf.x64@4.3.1
#addin nuget:?package=DotNetBrowser.Wpf.x64&version=4.3.1
#tool nuget:?package=DotNetBrowser.Wpf.x64&version=4.3.1
DotNetBrowser
DotNetBrowser is a .NET library for embedding a Chromium-based web browser into .NET applications. It renders web pages built with HTML5, CSS3, and JavaScript and gives you programmatic access to the browser, the DOM, the network, and more.
DotNetBrowser is a commercial product. To use it, you need a license key. A free 30-day evaluation license is available through the evaluation form.
The current release uses Chromium 153.0.8010.37. See the release notes for the changes in each version.
Installation
For a desktop application, install the package for your UI framework. It fetches the engine and the Chromium binaries for you, so one package is enough:
| UI framework | Package |
|---|---|
| WPF | DotNetBrowser.Wpf |
| Windows Forms | DotNetBrowser.WinForms |
| WinUI 3 | DotNetBrowser.WinUi3 |
| Avalonia UI 11.2 or later | DotNetBrowser.AvaloniaUi |
| Avalonia UI 12 | DotNetBrowser.AvaloniaUi.v12 |
For a console or headless application without a UI framework, install one engine package instead:
| Target platforms | Package |
|---|---|
| Windows, any CPU | DotNetBrowser |
| Windows, Linux, and macOS | DotNetBrowser.CrossPlatform |
| One platform only | DotNetBrowser.Win-x64, DotNetBrowser.Linux-arm64, DotNetBrowser.macOS-arm64, and so on |
See the NuGet installation guide for the full list of packages, including the x86, x64, and ARM64 variants of the UI packages.
You can also create a ready-to-run project from a template:
dotnet new install DotNetBrowser.Templates
dotnet new dotnetbrowser.wpf.app -o Example.Wpf
The templates are dotnetbrowser.wpf.app, dotnetbrowser.winforms.app,
dotnetbrowser.winui.app, dotnetbrowser.avalonia.app,
dotnetbrowser.avalonia12.app, dotnetbrowser.blazor.avalonia.app, and
dotnetbrowser.console.app. The WPF, Windows Forms, Avalonia UI, and console
templates also come in VB.NET: add -lang VisualBasic to the command.
Requirements
DotNetBrowser runs on .NET Framework 4.6.2 to 4.8.1 and on .NET 5 to 10. It supports Windows on x86, x64, and ARM64, plus Linux and macOS on x64 and ARM64. The system requirements page lists the supported OS versions.
Features
Chromium integration
DotNetBrowser exposes the Chromium features you would otherwise reach only through a browser UI:
- DOM API: access the Document Object Model of the loaded web page, find elements, interact with them, and handle and dispatch DOM events for particular nodes.
- JavaScript bridge: execute JavaScript on the web page and process the results, or inject a .NET object into the page and call it from JavaScript.
- Printing: initiate and configure printing programmatically, including printing to PDF.
- Network: intercept, redirect, handle, and suppress network requests, override HTTP headers and POST data, filter cookies, and change proxy settings on the fly.
The examples repository shows these and other features in working C# and VB.NET projects.
Deployment
The Chromium binaries ship inside the DotNetBrowser.Chromium.* packages and
are extracted automatically at run time. You do not need to install Chromium,
Google Chrome, or any other browser runtime on the target machine.
DotNetBrowser also supports trimming and Native AOT.
Headless mode
DotNetBrowser works in Windows services, server applications, and Linux environments without a desktop session. A web page is loaded and rendered in memory, and you can then take a screenshot of it. See the headless Linux guide for the required setup.
User input simulation
You can simulate mouse and keyboard input and interact with a web page the same way a user does.
UI controls
DotNetBrowser provides the BrowserView control for
WPF, Windows Forms,
WinUI 3, and Avalonia UI. You can
also embed DotNetBrowser into VSTO add-ins.
Usage
The example below creates an IEngine, loads a web page, reads two elements
from its DOM, and disposes the engine. It needs only the engine package, so
it works the same way on every supported platform. Replace <LICENSE_KEY>
with your license key. The license guide describes other
ways to provide the key, such as an embedded dotnetbrowser.license file.
using System;
using DotNetBrowser.Browser;
using DotNetBrowser.Dom;
using DotNetBrowser.Engine;
EngineOptions.Builder builder = new EngineOptions.Builder();
builder.LicenseKey = "<LICENSE_KEY>";
using (IEngine engine = EngineFactory.Create(builder.Build()))
{
IBrowser browser = engine.CreateBrowser();
browser.Navigation
.LoadUrl("https://quotes.toscrape.com/random").Wait();
IDocument document = browser.MainFrame.Document;
string quote = document.GetElementByClassName("text")?.InnerText;
string author = document.GetElementByClassName("author")?.InnerText;
Console.WriteLine(quote);
Console.WriteLine($"— {author}");
}
In a desktop application, the engine and the browser are created the same way.
The BrowserView control of your UI framework then displays the browser. Each
quick start below shows the complete window, and the matching template creates
a project with that code:
| Application | Quick start | Template |
|---|---|---|
| WPF | Quick start | dotnet new dotnetbrowser.wpf.app |
| Windows Forms | Quick start | dotnet new dotnetbrowser.winforms.app |
| WinUI 3 | Quick start | dotnet new dotnetbrowser.winui.app |
| Avalonia UI 11.2 or later | Quick start | dotnet new dotnetbrowser.avalonia.app |
| Avalonia UI 12 | Quick start | dotnet new dotnetbrowser.avalonia12.app |
| Console | Quick start | dotnet new dotnetbrowser.console.app |
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
| .NET Core | netcoreapp3.0 is compatible. netcoreapp3.1 was computed. |
| .NET Framework | net462 is compatible. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
-
.NETCoreApp 3.0
- DotNetBrowser.Win-x64 (>= 4.3.1)
-
.NETFramework 4.6.2
- DotNetBrowser.Win-x64 (>= 4.3.1)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on DotNetBrowser.Wpf.x64:
| Package | Downloads |
|---|---|
|
ClientTools
ClientTools is dll containing all controls related code for Uniconta application. To use the ClientTools you will need your own Uniconta APP identifier. http://www.uniconta.com/en/developers/ |
|
|
ClientTools.Core
Package Description |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.3.1 | 67 | 9/15/2026 |
| 4.3.0 | 172 | 8/28/2026 |
| 4.2.3 | 155 | 8/17/2026 |
| 4.2.2 | 248 | 8/3/2026 |
| 4.2.1 | 144 | 7/21/2026 |
| 4.2.0 | 240 | 7/7/2026 |
| 4.1.1 | 191 | 6/17/2026 |
| 4.1.0 | 242 | 5/28/2026 |
| 4.0.1 | 283 | 5/4/2026 |
| 4.0.0 | 168 | 4/28/2026 |
| 3.5.1 | 394 | 3/26/2026 |
| 3.5.0 | 404 | 2/18/2026 |
| 3.4.0 | 741 | 1/21/2026 |
| 3.3.7 | 817 | 12/18/2025 |
| 3.3.6 | 933 | 11/26/2025 |
| 3.3.5 | 3,711 | 11/7/2025 |
| 3.3.4 | 377 | 10/10/2025 |
| 2.27.20 | 312 | 11/26/2025 |
| 2.27.19 | 286 | 11/7/2025 |
| 2.27.18 | 299 | 10/10/2025 |
We've bumped Chromium to version 153.0.8010.37.
Find more about fixes and improvements in our release notes:
https://teamdev.com/dotnetbrowser/release-notes/2026/v4-3-1.html