Microsoft Edge is set to deprecate the window.external.getHostEnvironmentValue() method, urging developers to transition to the more privacy-focused User-Agent Client Hints API. This change aims to enhance browser privacy by minimizing user fingerprinting. The deprecation will occur in stages, starting with warnings in Edge 135 and culminating in complete removal by Edge 14

Microsoft Edge Deprecates window.external.getHostEnvironmentValue()
In a significant move towards enhancing user privacy, Microsoft Edge has announced the deprecation of the window.external.getHostEnvironmentValue()
method. This method, which is specific to Edge, has been a non-standard way for web developers to access browser and platform information. Now, developers are encouraged to transition to the standardized User-Agent Client Hints API
.
What’s New?
The decision to phase out getHostEnvironmentValue()
stems from Microsoft’s commitment to reducing user fingerprinting. This method provided detailed information that could compromise user privacy. In contrast, the User-Agent Client Hints API offers a more privacy-conscious approach.
“The UA Client Hints API provides browser and platform information in a much more privacy-preserving way.”
Major Updates in the Deprecation Plan
Microsoft’s deprecation plan unfolds in several key steps:
- Edge 135 (April 3, 2025): Developers will receive warnings in the DevTools Console when using the deprecated method.
- Edge 137 (May 23, 2025): The method will be disabled but can still be temporarily enabled via a request.
- Edge 141 (October 2025): Complete removal of the method, depending on developer feedback.
These steps are designed to help developers adapt their code before the final removal.
What’s Important to Know?
Starting with Edge 135, developers can test their websites without the getHostEnvironmentValue()
method. To do this, simply enable the edge-deprecate-get-host-environment-value
flag in Edge’s settings. This proactive approach allows developers to identify potential issues early.
“If your website depends on the getHostEnvironmentValue() method, and you need more time, request a temporary extension.”
For those who still rely on this method, Microsoft is open to granting temporary extensions for specific domains until Edge 141 is released.
Alternatives to Consider
The getHostEnvironmentValue()
method provided access to four properties. Developers can now use standards-based alternatives such as:
os-architecture
→Sec-CH-UA-Arch Client Hint
os-build
→Sec-CH-UA-Platform-Version Client Hint
os-mode
andos-sku
have no functional equivalents.
As the web evolves, embracing standards-based APIs will ensure a more secure and privacy-friendly browsing experience.
From the Windows Blog