Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

HTTPS

Secure .gov websites use HTTPS
A lock () or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

evergreen webview2

From the Blog

Evergreen Webview2 | 2027 |

Because the runtime is shared across all WebView2 apps on a system, the overhead per app is negligible. For enterprises with dozens of WebView2-embedded apps, this saves gigabytes of disk space and reduces memory duplication via shared libraries.

Developers typically ensure the runtime is present on client machines through several methods:

: Perform regular testing using Edge preview channels (Beta, Dev, or Canary) to ensure your app remains compatible with upcoming runtime updates. Common Distribution Scenarios Online Clients : Distribute a small 2MB Bootstrapper

Microsoft’s WebView2, powered by Microsoft Edge (Chromium-based), solves these problems. Its Evergreen runtime model is a key innovation: the WebView2 Runtime is maintained and updated by Microsoft, separate from the host application. This paper focuses on the Evergreen model, contrasting it with the Fixed Version model, and analyzing its impact on developers and end users.

Chrome, Firefox, and Edge are evergreen browsers. The old Internet Explorer was not (it required OS-level patches). evergreen webview2

: The runtime is updated automatically on the client machine, receiving the same security patches and performance improvements as the Microsoft Edge stable channel Microsoft Learn Reduced Footprint

The WebView2 Evergreen distribution model delivers the optimal balance between application agility and desktop stability. By shifting the burden of security compliance, performance tuning, and web standard updates to Microsoft, engineering teams can focus entirely on building stellar user experiences.

Evergreen ensures support for the latest HTML, CSS, ECMAScript, and Web APIs (WebRTC, WebGL, WebUSB, etc.) without recompiling the host app.

This means that while the runtime is shared, a clean Windows machine can still run your app seamlessly—the first launch silently fetches the runtime from Microsoft’s CDN. Because the runtime is shared across all WebView2

In this model, you download a specific version of the WebView2 Runtime and package it directly with your application.

Never assume the runtime is active. Wrap your initialization logic in try-catch blocks and check CoreWebView2Environment.GetAvailableBrowserVersionString() before loading UI elements.

The rapid evolution of web technologies has led to the development of innovative solutions for building modern web applications. One such solution is WebView2, a component that enables developers to embed web content within their applications. However, managing WebView2 instances can be challenging, especially when it comes to ensuring that the component remains up-to-date and secure. In this paper, we propose the concept of "Evergreen WebView2," a comprehensive approach to building modern web applications that leverages the power of WebView2 while ensuring its perpetual updating and security.

As Microsoft's best practices documentation emphasizes, "Keep the WebView2 Runtime evergreen (i.e., updated) to future-proof your app". Common Distribution Scenarios Online Clients : Distribute a

However, weigh these benefits carefully against the trade-offs: the Fixed Version runtime doesn't receive automatic security updates, you must periodically update both your application and the bundled runtime to access new APIs, and disk usage multiplies if users have multiple Fixed Version applications installed.

Microsoft continues to enhance Evergreen WebView2 with:

A tiny executable (~2MB) bundled with your installer. If the target machine lacks the runtime, the bootstrapper downloads and installs the correct architecture-specific components in the background.

However, if your app supports older Windows environments or stripped-down enterprise deployment images, your installer should verify its presence. You can bundle the —a tiny 2MB executable provided by Microsoft—with your installer. If the installer detects the runtime is missing, the bootstrapper downloads and configures the latest shared components silently. Step 2: Code Initialization (C# Example)