You can find the official links on the Microsoft Edge WebView2 "Download the WebView2 Runtime" page. You should choose the "Evergreen Standalone Installer" option matching your target architecture (X64, X86, or ARM64).
For environments without internet connectivity—air-gapped systems, secure enterprise networks, or computers in remote locations—Microsoft offers the Evergreen Standalone Installer. This is a complete, full-sized installer that can install the Evergreen Runtime in an offline environment. Standalone installers are available for x86, x64, and ARM64 architectures, each approximately 130 MB in size depending on the version.
If you want to dive deeper into deploying this framework, let me know:
Smaller application footprint; automatic security updates; access to the latest web capabilities.
While the Evergreen model is recommended for most scenarios, it's important to understand its limitations. evergreen webview2
| Feature | Evergreen Mode | Fixed Version Mode | | :--- | :--- | :--- | | | Low (Shared Runtime) | High (Per-App Runtime) | | Security | Auto-updated by Microsoft | Manual updating required | | Web Standards | Always up-to-date | Frozen at specific version | | Internet Required | Yes (for install/updates) | No (can work offline) | | Best For | Consumer apps, SaaS, general tools | Kiosks, medical devices, strict enterprise envs |
Modern desktop development is undergoing a fundamental transformation, driven by the need to deliver rich, web-powered user interfaces without the bloat of bundling entire browser engines. At the heart of this shift is Microsoft Edge WebView2—a Chromium-based embedded web control that allows developers to host modern web content directly within native applications. But one question consistently emerges as a critical decision point for developers:
The benefits of Evergreen WebView2 include:
Here is a deep dive into what the Evergreen distribution mode is, how it works, and why it matters for developers. You can find the official links on the
: The runtime is managed by the Microsoft Edge update service, requiring no manual intervention from developers once installed. Distribution & Deployment
Through registry keys and administrative templates, organizations can:
Why was WebView2 re-installed after I uninstalled it? - Microsoft Q&A
[Native Desktop App] │ ▼ 1. Checks Registry/System for Evergreen Runtime │ ├───► Found? ───► 2. Launches Chromium Processes (Independent Setup) │ └───► Missing? ─► 3. Triggers Bootstrapper / Prompt to Download This is a complete, full-sized installer that can
If you rely on brand-new web APIs, use feature detection in your JavaScript code to ensure the current runtime version supports them. Conclusion
By choosing Evergreen, you:
┌────────────────────────────────────────────────────────┐ │ Your Native Application │ │ (WPF, WinForms, WinUI, C++, Win32, .NET MAUI, etc.) │ └───────────────────────────┬────────────────────────────┘ │ Calls WebView2 SDK APIs ▼ ┌────────────────────────────────────────────────────────┐ │ Evergreen WebView2 Runtime │ │ (Maintained and auto-updated by Microsoft) │ └───────────────────────────┬────────────────────────────┘ │ Renders ▼ ┌────────────────────────────────────────────────────────┐ │ Web Content / Assets (HTML, CSS, JS, WASM) │ └────────────────────────────────────────────────────────┘
The Evergreen WebView2 is Microsoft’s solution for embedding web technologies (HTML, CSS, JavaScript) into native desktop applications (WinForms, WPF, WinUI, C++). Unlike the fixed-version model, the "Evergreen" runtime automatically stays up-to-date on the user’s machine, similar to Chrome’s auto-update mechanism.