Release notes for the WebView2 SDK - Microsoft Edge Developer documentation (original) (raw)

The following new features and bug fixes are in the WebView2 Release SDK and Prerelease SDK, for SDKs during the past year.

Prerelease SDK 1.0.4071-prerelease, for Runtime 150 (Jun. 11, 2026)

Release Date: Jun. 11, 2026

NuGet package for WebView2 SDK 1.0.4071-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 150.0.4071.0 or later.

Breaking changes

Enable Windows shell handwriting support for WebView2 in WindowToVisual mode

WebView2 is introducing support for Windows shell handwriting (pen handwriting-to-text) for edit fields inside WebView2 instances that are hosted in Window to Visual (WindowToVisual) mode on Windows.

This change affects only WindowToVisual hosting mode. WindowToWindow hosting mode already supports Windows shell handwriting, and VisualToVisual hosting mode isn't supported by this change.

Before this change: WebView2 in WindowToVisual mode doesn't register an ITfHandwritingSink on the Text Services Framework (TSF) thread. Windows shell handwriting can still work, but handwriting target determination uses the OS UI Automation (UIA)-based path.

After this change: If the msAbydosForWindowlessWV2 feature flag is disabled, the behavior remains the same as before this change, including the UIA-based handwriting target determination path.

If the msAbydosForWindowlessWV2 feature flag is enabled, WebView2 in WindowToVisual mode registers a per-instance ITfHandwritingSink on the TSF thread. This enables Windows shell handwriting for edit fields inside WebView2, and changes how TSF handwriting events are routed on the shared TSF thread.

If your app already registers its own ITfHandwritingSink on its TSF thread, pen handwriting will continue to work for your app's native edit fields, and pen handwriting will also work inside WebView2 edit fields.

If your app doesn't register its own ITfHandwritingSink, pen handwriting may stop working for your app's native edit fields after this change is enabled by default. This occurs because WebView2 returns E_NOTIMPL for HWNDs that it doesn't own, expecting TSF to chain to another registered sink. If no host sink is registered, TSF doesn't fall back to the default UIA-based handwriting target resolution.

To preserve pen handwriting support for your app's native edit fields, register your own ITfHandwritingSink on the TSF thread. Pen handwriting inside WebView2 edit fields is enabled automatically by this change.

You can proactively validate your WebView2 app's behavior by enabling the following feature flag before launching your app:

set WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--enable-features=msAbydosForWindowlessWV2

In releases 149 and 150, the msAbydosForWindowlessWV2 feature flag is disabled by default, giving apps time to proactively test. Starting in release 151, the feature is planned to be enabled by default.

By testing your WebView2 app with this feature flag enabled, you can identify whether any native edit-field handwriting workflows in your app depend on registering a host ITfHandwritingSink.

See also:

General changes

Deprecation of DevToolsProtocolExtension NuGet package

NuGet package for DevToolsProtocolExtension 1.0.2901

The Microsoft.Web.WebView2.DevToolsProtocolExtension NuGet package is being deprecated, and no further versions of this package will be published. This deprecation is not linked to any WebView2 Release SDK or Prerelease SDK.

The DevToolsProtocolExtension package provides a strongly-typed .NET wrapper over the Chrome DevTools Protocol (CDP) for use in WebView2 apps. The existing published versions (1.0.824, 1.0.2271, and 1.0.2901) remain available on NuGet Gallery and are not being removed.

See also:

Recommended alternative:

All CDP calls can be made directly via the WebView2 CDP APIs, without using the extension package. See Use the Chrome DevTools Protocol (CDP) in WebView2 apps and the following:

Experimental APIs (Phase 1: Experimental in Prerelease)

No Experimental APIs have been added in this Prerelease SDK.

Promotions to Phase 2 (Stable in Prerelease)

No APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, in this Prerelease SDK.

Bug fixes

This Prerelease SDK includes the following bug fixes.

Runtime and SDK
Runtime-only
SDK-only

Release SDK 1.0.4022.49, for Runtime 149 (Jun. 11, 2026)

Release Date: Jun. 11, 2026

NuGet package for WebView2 SDK 1.0.4022.49

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 149.0.4022.49 or later.

Promotions to Phase 3 (Stable in Release)

The following APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, and are now included in this Release SDK.

Enable background processing and offline support (WebView2 Worker APIs)

The WebView2 Worker APIs allow host applications to interact with Web Workers to offload tasks from the main thread, improve responsiveness, and support background operations. These Web Workers include Dedicated Workers, Shared Workers, and Service Workers.

These APIs provide:

Bug fixes

This Release SDK includes the following bug fixes.

Runtime-only
SDK-only

Prerelease SDK 1.0.4015-prerelease, for Runtime 149 (May 11, 2026)

Release Date: May 11, 2026

NuGet package for WebView2 SDK 1.0.4015-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 149.0.4015.0 or later.

Breaking changes

EnhancedSecurityModeLevel replaced by EnhancedSecurityModeState

The CoreWebView2Profile.EnhancedSecurityModeLevel property and the CoreWebView2EnhancedSecurityModeLevel enum are deprecated and will be removed in a future release. Replace all usage of these APIs in your WebView2 application, as follows.

The old property, CoreWebView2Profile.EnhancedSecurityModeLevel, controlled whether Enhanced Security Mode (ESM) is enabled or disabled for all WebView2 instances associated with a profile. This property has been renamed to EnhancedSecurityModeState, to more clearly communicate the state of Enhanced Security Mode.

Before this change: The CoreWebView2Profile.EnhancedSecurityModeLevel property used the CoreWebView2EnhancedSecurityModeLevel enum with values Off and Strict.

After this change: The CoreWebView2Profile.EnhancedSecurityModeState property uses the CoreWebView2EnhancedSecurityModeState enum with values Disabled and Enabled:

See also:

Experimental APIs (Phase 1: Experimental in Prerelease)

The following APIs are in Phase 1: Experimental in Prerelease, and have been added in this Prerelease SDK.

Enhanced security mode state

The EnhancedSecurityModeState property on CoreWebView2Profile controls whether Enhanced Security Mode (ESM) is enabled or disabled for all WebView2 instances that are associated with a profile.

When enabled, Enhanced Security Mode disables JavaScript Just-in-Time (JIT) compilation and enables additional operating system protections, reducing the attack surface, at the cost of some JavaScript performance.

The default value is Disabled. Changes apply immediately to new navigations; existing pages require a reload.

This setting does not persist, and resets when the profile is destroyed and recreated.

Promotions to Phase 2 (Stable in Prerelease)

The following APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, and are included in this Prerelease SDK.

Enable background processing and offline support (WebView2 Worker APIs)

The WebView2 Worker APIs allow host applications to interact with Web Workers to offload tasks from the main thread, improve responsiveness, and support background operations. These Web Workers include Dedicated Workers, Shared Workers, and Service Workers.

These APIs provide:

Bug fixes

This Prerelease SDK includes the following bug fixes.

Runtime-only

Release SDK 1.0.3967.48, for Runtime 148 (May 11, 2026)

Release Date: May 11, 2026

NuGet package for WebView2 SDK 1.0.3967.48

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 148.0.3967.48 or later.

Promotions to Phase 3 (Stable in Release)

No additional APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, in this Release SDK.

Bug fixes

This Release SDK includes the following bug fixes.

Runtime-only

Prerelease SDK 1.0.3965-prerelease, for Runtime 148 (Apr. 13, 2026)

Release Date: April 13, 2026

NuGet package for WebView2 SDK 1.0.3965-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 148.0.3965.0 or later.

Breaking changes

Granular process failure reasons for the ProcessFailed event

The ProcessFailed event fires when a WebView2-associated process (such as a renderer or GPU process) exits unexpectedly, allowing apps to respond with recovery logic or diagnostics.

Before this change: The CoreWebView2ProcessFailedEventArgs.Reason property returned Unexpected for three distinct exit scenarios (normal exit, abnormal exit, and code integrity failure), making it impossible for apps to distinguish between them.

After this change: When the msWebView2GranularProcessFailedReason feature flag is enabled, the CoreWebView2ProcessFailedEventArgs.Reason property returns the following new, granular CoreWebView2ProcessFailedReason enum values, instead of Unexpected:

The msWebView2GranularProcessFailedReason feature flag is disabled by default in releases 148 and 149, giving apps two releases to proactively test. Starting in release 150, the feature will be enabled by default, and apps will receive the granular values. To validate your WebView2 app's behavior, enable the feature flag, as follows:

set WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--enable-features=msWebView2GranularProcessFailedReason

This is a bug fix for the Runtime and SDK. These enum members are a modification of an existing stable API, and are available as part of this Prerelease SDK.

See also:

Experimental APIs (Phase 1: Experimental in Prerelease)

The following APIs are in Phase 1: Experimental in Prerelease, and have been added in this Prerelease SDK.

Origin Configuration API for WebView2

The Origin Configuration API enables WebView2 apps to apply different feature and security policies based on the origin of hosted content. By default, WebView2 enforces a uniform policy across all origins. This API allows apps to selectively enable or disable specific features (such as Enhanced Security Mode) for individual origins or origin patterns.

Use the SetOriginFeatures method on CoreWebView2Profile to configure feature settings for one or more origins. Origins can be specified as exact strings (such as https://contoso.com) or wildcard patterns (such as https://[*.]contoso.com) to match subdomains, protocols, or ports.

When multiple configurations apply to the same origin, the most specific pattern takes precedence, evaluated by hostname, then scheme, then port.

Use GetEffectiveFeaturesForOrigin to asynchronously retrieve the computed feature settings for a given origin.

Phase 2 (Stable in Prerelease)

The following enum members are a modification of an existing stable API, and are available as part of this Prerelease SDK.

Granular process failure reasons for the ProcessFailed event

Supplemented the CoreWebView2ProcessFailedReason.Unexpected enum member by adding more granular values, for the CoreWebView2ProcessFailedReason enum that's returned by the CoreWebView2ProcessFailedEventArgs.Reason property.

This is a breaking change; see Granular process failure reasons for the ProcessFailed event, above.

Bug fixes

This Prerelease SDK includes the following bug fixes.

Runtime and SDK
Runtime-only
SDK-only

Release SDK 1.0.3912.50, for Runtime 147 (Apr. 13, 2026)

Release Date: Apr. 13, 2026

NuGet package for WebView2 SDK 1.0.3912.50

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 147.0.3912.50 or later.

Promotions to Phase 3 (Stable in Release)

No additional APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, in this Release SDK.

Bug fixes

This Release SDK includes the following bug fixes.

Runtime-only

Prerelease SDK 1.0.3908-prerelease, for Runtime 147 (Mar. 16, 2026)

Release Date: Mar. 16, 2026

NuGet package for WebView2 SDK 1.0.3908-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 147.0.3908.0 or later.

Experimental APIs (Phase 1: Experimental in Prerelease)

No Experimental APIs have been added in this Prerelease SDK.

Promotions to Phase 2 (Stable in Prerelease)

The following APIs skipped Phase 1: Experimental in Prerelease, and have been directly added to Phase 2: Stable in Prerelease, and are included in this Prerelease SDK.

Manage persistent storage permissions for web content

The PersistentStorage permission allows a WebView2 app to handle requests from web content to persist data that's created by Storage APIs, service workers, and related technologies. The PersistentStorage permission is an enum member in the CoreWebView2PermissionKind enum.

When this permission is granted, the browser doesn't evict stored data during low-disk-space scenarios. This ensures reliable offline and caching behavior for the site.

Bug fixes

This Prerelease SDK includes the following bug fixes.

Runtime-only

Release SDK 1.0.3856.49, for Runtime 146 (Mar. 16, 2026)

Release Date: Mar. 16, 2026

NuGet package for WebView2 SDK 1.0.3856.49

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 146.0.3856.49 or later.

Promotions to Phase 3 (Stable in Release)

No additional APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, in this Release SDK.

Bug fixes

This Release SDK includes the following bug fixes.

Runtime-only

Prerelease SDK 1.0.3848-prerelease, for Runtime 146 (Feb. 16, 2026)

Release Date: Feb. 16, 2026

NuGet package for WebView2 SDK 1.0.3848-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 146.0.3848.0 or later.

Breaking changes

Enable WebView2-specific Javascript APIs for service workers

The new AreWebViewScriptApisEnabledForServiceWorkers setting provides an explicit and reliable way to control the availability of WebView2‑specific JavaScript APIs (chrome.webview) within service worker scripts.

This setting is disabled by default for WebView2 applications. Apps that don't explicitly enable this setting won't have access to WebView2‑specific JavaScript APIs in service worker scripts. As a result, service worker–based chrome.webview.postMessage communication with the WebView2 host application will not function unless the setting is enabled.

Going forward, WebView2 will rely on the AreWebViewScriptApisEnabledForServiceWorkers setting as the authoritative mechanism for enabling WebView2‑specific JavaScript APIs in service worker scripts. This ensures predictable, secure, and deterministic behavior.

You can proactively validate your WebView2 app's behavior by enabling service worker JavaScript API exposure in your WebView2 app. To do so, configure your app to enable the following setting:

AreWebViewScriptApisEnabledForServiceWorkers = true

By testing your WebView2 app with this setting enabled, you can identify any workflows that depend on WebView2‑specific service worker APIs, such as chrome.webview.postMessage communication between service workers and the host application.

Currently, the chrome and chrome.webview objects are available to service worker scripts when using the ServiceWorkerRegistered event. However, starting with the next release, the AreWebViewScriptApisEnabledForServiceWorkers setting will be the sole mechanism that determines whether these objects are exposed to service worker scripts. Please test this setting before the next release, and report any issues you encounter. For details, see [Breaking Change] Enabling WebView2 specific JavaScript API's for Service Workers.

See also Control whether WebView Script APIs are enabled for service workers, below.

Local Network Access (LNA) in WebView2

The Chromium browser engine has introduced Local Network Access (LNA). LNA is a security feature that prevents web pages from making requests to private or local network resources, unless the webpage has explicit permission to access the private or local network resources. Examples of such resources are localhost, 192.168.*, or 10.*.

LNA is currently disabled by default for WebView2 apps, but you can enable LNA support via the msWebViewAllowLocalNetworkAccessChecks flag. For WebView2 apps, no action is required at this time. For information about the flag, see Available WebView2 browser flags in WebView2 browser flags.

After the upstream, Chromium code base stabilizes, we plan to add additional enum values in the CoreWebView2PermissionKind enum, to support LNA via the SetPermissionState method. These new enum values will be used by the UWP WebView.PermissionRequested event, to give your WebView2 app explicit control over the Local Network Access (LNA) feature.

You can proactively test the Local Network Access (LNA) feature in your WebView2 app. To test your app with the LNA feature, launch your WebView2 app with the following flag:

--enable-features=LocalNetworkAccessChecks,msWebViewAllowLocalNetworkAccessChecks

By testing your app when launched with this flag, you can then identify any workflows that might be affected by the LNA feature.

After the LNA feature stabilizes, we'll share an updated timeline for enabling the LNA feature. For details, see [Breaking Change] Local Network Access (LNA) in WebView2 - Rollout Plan.

Experimental APIs (Phase 1: Experimental in Prerelease)

The following APIs are in Phase 1: Experimental in Prerelease, and have been added in this Prerelease SDK.

Control whether WebView Script APIs are enabled for service workers

Use the AreWebViewScriptApisEnabledForServiceWorkers property on CoreWebView2Profile to control whether WebView Script APIs are enabled for service workers.

See also Enable WebView2-specific Javascript APIs for service workers, above.

Promotions to Phase 2 (Stable in Prerelease)

No APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, in this Prerelease SDK.

Bug fixes

This Prerelease SDK includes the following bug fixes.

Runtime-only

Release SDK 1.0.3800.47, for Runtime 145 (Feb. 16, 2026)

Release Date: Feb. 16, 2026

NuGet package for WebView2 SDK 1.0.3800.47

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 145.0.3800.47 or later.

Promotions to Phase 3 (Stable in Release)

No additional APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, in this Release SDK.

Bug fixes

This Release SDK includes the following bug fixes.

Runtime-only

Prerelease SDK 1.0.3796-prerelease, for Runtime 145 (Jan. 19, 2026)

Release Date: Jan. 19, 2026

NuGet package for WebView2 SDK 1.0.3796-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 145.0.3796.0 or later.

Experimental APIs (Phase 1: Experimental in Prerelease)

The following APIs are in Phase 1: Experimental in Prerelease, and have been added in this Prerelease SDK.

Enhanced Security Mode Level

The Enhanced Security Mode Level API enables configuring Enhanced Security Mode (ESM) for WebView2 instances. ESM reduces the risk of memory-related vulnerabilities by disabling JavaScript Just-in-Time (JIT) compilation and enabling additional operating system protections.

To control the ESM level for all WebView2 instances that share the same profile, use the EnhancedSecurityModeLevel property on CoreWebView2Profile (or ICoreWebView2ExperimentalProfile9):

Promotions to Phase 2 (Stable in Prerelease)

No APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, in this Prerelease SDK.

Bug fixes

This Prerelease SDK includes the following bug fixes.

Runtime-only
SDK-only

Release SDK 1.0.3719.77, for Runtime 144 (Jan. 27, 2026)

Release Date: Jan. 27, 2026

NuGet package for WebView2 SDK 1.0.3719.77

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 144.0.3719.77 or later.

Promotions to Phase 3 (Stable in Release)

The following APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, and are now included in this Release SDK.

Customize the drag and drop behavior (DragStarting API)

The DragStarting API overrides the default drag and drop behavior when running in visual hosting mode. The DragStarting event notifies your app when the user starts a drag operation in the WebView2, and provides the state that's necessary to override the default WebView2 drag operation with your own logic.

Bug fixes

This Release SDK includes the following bug fixes.

Runtime-only
SDK-only

Prerelease SDK 1.0.3712-prerelease, for Runtime 144 (Dec. 8, 2025)

Release Date: Dec. 8, 2025

NuGet package for WebView2 SDK 1.0.3712-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 144.0.3712.0 or later.

Experimental APIs (Phase 1: Experimental in Prerelease)

The following APIs are in Phase 1: Experimental in Prerelease, and have been added in this Prerelease SDK.

Customize port range behavior

The Allowed Port Range APIs enable restricting or customizing the network port ranges that WebView2 can use for various transport protocols and scopes. This provides enhanced security control.

Promotions to Phase 2 (Stable in Prerelease)

The following APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, and are included in this Prerelease SDK.

Customize the drag and drop behavior (DragStarting API)

The DragStarting API overrides the default drag and drop behavior when running in visual hosting mode. The DragStarting event notifies your app when the user starts a drag operation in the WebView2, and provides the state that's necessary to override the default WebView2 drag operation with your own logic.

Bug fixes

This Prerelease SDK includes the following bug fixes.

Runtime-only

Release SDK 1.0.3650.58, for Runtime 143 (Dec. 8, 2025)

Release Date: Dec. 8, 2025

NuGet package for WebView2 SDK 1.0.3650.58

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 143.0.3650.58 or later.

Promotions to Phase 3 (Stable in Release)

No additional APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, in this Release SDK.

Bug fixes

Runtime-only

Prerelease SDK 1.0.3650-prerelease, for Runtime 143 (Nov. 7, 2025)

Release Date: Nov. 7, 2025

NuGet package for WebView2 SDK 1.0.3650-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 143.0.3650.0 or later.

Experimental APIs (Phase 1: Experimental in Prerelease)

No Experimental APIs have been added in this Prerelease SDK.

Promotions to Phase 2 (Stable in Prerelease)

No APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, in this Prerelease SDK.

Bug fixes

This Prerelease SDK includes the following bug fixes.

Runtime-only

Release SDK 1.0.3595.46, for Runtime 142 (Nov. 3, 2025)

Release Date: Nov. 3, 2025

NuGet package for WebView2 SDK 1.0.3595.46

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 142.0.3595.46 or later.

Promotions to Phase 3 (Stable in Release)

No additional APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, in this Release SDK.

Bug fixes

This Release SDK includes the following bug fixes.

Runtime-only

Prerelease SDK 1.0.3590-prerelease, for Runtime 142 (Oct. 7, 2025)

Release Date: Oct. 7, 2025

NuGet package for WebView2 SDK 1.0.3590-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 142.0.3590.0 or later.

Experimental APIs (Phase 1: Experimental in Prerelease)

The following APIs are in Phase 1: Experimental in Prerelease, and have been added in this Prerelease SDK.

Sensitivity label support

A new Sensitivity Info API in WebView2 enables applications to access sensitivity label information communicated by webpages through the Page Interaction Restriction Manager. This feature helps host applications detect and respond to sensitive content.

Key capabilities:

Sensitivity label support is initially available on Win32 only. Support for .NET and WinRT is planned for a future release.

Promotions to Phase 2 (Stable in Prerelease)

No APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, in this Prerelease SDK.

Bug fixes

This Prerelease SDK includes the following bug fixes.

Runtime-only
SDK-only

Release SDK 1.0.3537.50, for Runtime 141 (Oct. 6, 2025)

Release Date: Oct. 6, 2025

NuGet package for WebView2 SDK 1.0.3537.50

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 141.0.3537.50 or later.

Promotions to Phase 3 (Stable in Release)

No additional APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, in this Release SDK.

Bug fixes

This Release SDK includes the following bug fixes.

Runtime-only
SDK-only

Prerelease SDK 1.0.3530-prerelease, for Runtime 141 (Sep. 8, 2025)

Release Date: Sep. 8, 2025

NuGet package for WebView2 SDK 1.0.3530-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 141.0.3530.0 or later.

General changes

This Prerelease SDK focuses on making WebView2 work better, through behind-the-scenes improvements.

These foundational improvements provide stable, thoroughly tested functionality for building WebView2 apps.

Experimental APIs (Phase 1: Experimental in Prerelease)

No Experimental APIs have been added in this Prerelease SDK.

Promotions to Phase 2 (Stable in Prerelease)

No APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, in this Prerelease SDK.

Bug fixes

This Prerelease SDK includes the following bug fixes.

SDK-only

Release SDK 1.0.3485.44, for Runtime 140 (Sep. 8, 2025)

Release Date: Sep. 8, 2025

NuGet package for WebView2 SDK 1.0.3485.44

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 140.0.3485.44 or later.

General changes

This Release SDK focuses on making WebView2 work better, through behind-the-scenes improvements.

These foundational improvements provide stable, thoroughly tested functionality for building WebView2 apps.

Promotions to Phase 3 (Stable in Release)

No additional APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, in this Release SDK.

Bug fixes

There are no bug fixes in this Release SDK.

Prerelease SDK 1.0.3477-prerelease, for Runtime 140 (Aug. 11, 2025)

Release Date: Aug. 11, 2025

NuGet package for WebView2 SDK 1.0.3477-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 140.0.3477.0 or later.

Experimental APIs (Phase 1: Experimental in Prerelease)

No Experimental APIs have been added in this Prerelease SDK.

Promotions to Phase 2 (Stable in Prerelease)

No APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, in this Prerelease SDK.

Bug fixes

Runtime-only

Prerelease SDK 1.0.3415-prerelease, for Runtime 140 (Jul. 14, 2025)

Release Date: Jul. 14, 2025

NuGet package for WebView2 SDK 1.0.3415-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 140.0.3415.0 or later.

Experimental APIs (Phase 1: Experimental in Prerelease)

The following APIs are in Phase 1: Experimental in Prerelease, and have been added in this Prerelease SDK.

Enable background processing and offline support (WebView2 Worker APIs)

The WebView2 Worker APIs allow host applications to interact with Web Workers to offload tasks from the main thread, improve responsiveness, and support background operations. These Web Workers include Dedicated Workers, Shared Workers, and Service Workers.

These APIs provide:

Render custom title bars (Window Controls Overlay API)

The Window Controls Overlay API enables developers to create custom title bars by rendering caption buttons (minimize, maximize, restore, close) directly inside the WebView2 window. The Window Controls Overlay appears in the top corner of the WebView, and integrates seamlessly with your app's UI.

Use this API when:

This API is ideal for apps that require a modern, immersive UI experience.

Promotions to Phase 2 (Stable in Prerelease)

The following APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, and are included in this Prerelease SDK.

Customize the Find behavior (Find API)

The Find API allows you to programmatically control Find operations, and enables adding the following functionality to your app:

There are known issues with the Find API for PDF documents. When you view a PDF document within a WebView2 control, the Find feature currently only provides the first index and the number of matches found. For example, if the string occurs three times in a PDF, the UI would say 1/3 and would not support programmatically calling Next or Previous.

We're actively investigating these issues, and we encourage you to report any problems you encounter, by using the WebView2Feedback repo.

Bug fixes

Runtime-only

Release SDK 1.0.3405.78, for Runtime 139 (Aug. 11, 2025)

Release Date: Aug. 11, 2025

NuGet package for WebView2 SDK 1.0.3405.78

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 139.0.3405.78 or later.

Promotions to Phase 3 (Stable in Release)

The following APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, and are now included in this Release SDK.

Customize the Find behavior (Find API)

The Find API allows you to programmatically control Find operations, and enables adding the following functionality to your app:

There are known issues with the Find API for PDF documents. When you view a PDF document within a WebView2 control, the Find feature currently only provides the first index and the number of matches found. For example, if the string occurs three times in a PDF, the UI would say 1/3 and would not support programmatically calling Next or Previous.

We're actively investigating these issues, and we encourage you to report any problems you encounter, by using the WebView2Feedback repo.

Bug fixes

Runtime-only

Release SDK 1.0.3351.48, for Runtime 138 (Jul. 1, 2025)

Release Date: Jul. 1, 2025

NuGet package for WebView2 SDK 1.0.3351.48

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 138.0.3351.48 or later.

Promotions to Phase 3 (Stable in Release)

The following APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, and are now included in this Release SDK.

Allow input event messages to pass through the browser window

The CoreWebView2ControllerOptions class now has an AllowHostInputProcessing property, which allows user input event messages (keyboard, mouse, touch, or pen) to pass through the browser window, to be received by an app process window.

Bug fixes

Runtime-only

Prerelease SDK 1.0.3344-prerelease, for Runtime 138 (Jun. 3, 2025)

Release Date: Jun. 3, 2025

NuGet package for WebView2 SDK 1.0.3344-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 138.0.3344.0 or later.

Experimental APIs (Phase 1: Experimental in Prerelease)

No Experimental APIs have been added in this Prerelease SDK.

Promotions to Phase 2 (Stable in Prerelease)

The following APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, and are included in this Prerelease SDK.

Allow input event messages to pass through the browser window

The CoreWebView2ControllerOptions class now has an AllowHostInputProcessing property, which allows user input event messages (keyboard, mouse, touch, or pen) to pass through the browser window, to be received by an app process window.

Bug fixes

Runtime-only

See also

API Reference: