Web Environment Integrity

Web Environment Integrity (WEI) is an abandoned API proposal previously under development for Google Chrome. ^[1] A Web Environment Integrity prototype existed in Chromium ^{[2] [3]} from May ^[4] to November 2023 after extensive criticism by many tech groups. ^[5] Its purpose was to verify that interactions with websites were human and authentic as defined by third-party attesters.

Proposal

Sequence diagram showing WEI attestation

The draft proposed an API for websites to get a digitally signed token that contains the certifier's name and whether or not they deem the web client to be authentic. The stated goal was for sites to be able to restrict access to human users instead of automated programs and "allow web servers to evaluate the authenticity of the device and honest representation of the software stack and the traffic from the device". Access to this API would not be allowed in non-secure (HTTP) contexts. ^[6]

History

The proposal first showed up as a commit to Chromium in April before being announced by its developers, Google engineers, in May. It received a few concerned comments from those who followed the browser's rendering engine's development. After discussion at W3C in late April, its working draft specification was published as part of the process to develop standards for the web on July 21, 2023. As a result, users flooded the proposal's GitHub repository with critical comments and flaming of the proposal's authors. As a result, the Google engineers limited comment to those who have contributed to the repository and added a code of conduct. ^[7] On the same day, Chromium's preliminary code to implement the standard was enabled. ^[2]

On November 2, 2023, Google abandoned the proposal, removed the prototype implementation from Chromium, and proposed a replacement API named "Android WebView Media Integrity API" limited to WebViews on Android. Google tested the new API with partners in early 2024. ^[5] As of late 2024, WebView Media Integrity API is available to all developers. ^[8]

Reception

The proposal received widespread criticism for limiting general purpose computing, with some comparing WEI to digital rights management (DRM). ^[9] Others have accused the standard of being evidence of Google abusing Chrome's near-monopoly of browser share. ^[7] Some have issued official statements on the matter in 2023:

• On July 25, Mozilla opposed it, stating "Any browser, server, or publisher that implements common standards is automatically part of the Web  ... Mechanisms that attempt to restrict these choices are harmful to the openness of the Web ecosystem and are not good for users." ^[10]
• On July 27, Vivaldi opposed it as "simply dangerous" and feared that attestation providers would not be trustworthy. ^[11]
• On July 29, the Free Software Foundation opposed it as "an all-out attack on the free Internet" and claimed it would significantly limit the browsers that could be used. ^[12]
• On August 1, Brave Software announced they will not include WEI in their web browser. ^[13]
• On August 7, the Electronic Frontier Foundation opposed it as "a bad idea that Google should not pursue" and opposed its proposal of selecting a "small percentage" of random users to simulate behavior without WEI in order to prevent websites from blocking unattested users. The EFF claimed that "[m]any websites will consider that 'small percentage' of users an acceptable price to pay" and feared Google would set the percentage extremely low to combat ad fraud. ^[14]
• On August 11, the World Wide Web Consortium refrained from taking a stance as it was "not being worked on in W3C, nor has there been any submission [for W3C] review". ^[15]

See also

• Private Access Tokens
• Remote attestation

References

1. Amadeo, Ron (August 3, 2023). "Google's nightmare "Web Integrity API" wants a DRM gatekeeper for the web". Ars Technica . Retrieved August 3, 2023.
2. "[wei] Ensure Origin Trial enables full feature · chromium/chromium@6f47a22". GitHub. Retrieved August 19, 2023.
3. "Feature: Web environment integrity API". Chrome Platform Status. May 9, 2023. Retrieved August 23, 2023.
4. Kalla, Ryan. "Add WebEnvironmentIntegrity feature". Chromium Source. Retrieved July 30, 2025.
5. Claburn, Thomas (November 2, 2023). "Google abandons Web Environment Integrity proposal". The Register . Retrieved November 10, 2023.
6. "Web-Environment-Integrity/explainer.md at main · RupertBenWiser/Web-Environment-Integrity". GitHub. Retrieved July 26, 2023.
7. Claburn, Thomas (July 25, 2023). "Google's next big idea for browser security looks like another freedom grab to some". The Register . Retrieved August 19, 2023.
8. "WebViewMediaIntegrityApiStatusConfig". Android Developers. Retrieved July 30, 2025.
9. Amadeo, Ron (July 24, 2023). "Google's nightmare "Web Integrity API" wants a DRM gatekeeper for the web". Ars Technica . Retrieved July 26, 2023.
10. "Request for Position: Web Environment Integrity API · Issue #852 · mozilla/standards-positions". GitHub. Retrieved July 26, 2023.
11. "Unpacking Google's new "dangerous" Web-Environment-Integrity specification". Vivaldi Browser. July 25, 2023. Retrieved July 26, 2023.
12. Farough, Greg (July 28, 2023). ""Web Environment Integrity" is an all-out attack on the free Internet". Free Software Foundation. Retrieved July 28, 2023.
13. Snyder, Peter (August 1, 2023). "Web Environment Integrity": Locking Down the Web . Retrieved August 29, 2023.
14. Doctorow, Cory; Hoffman-Andrews, Jacob (August 7, 2023). "Your Computer Should Say What You Tell It To Say". www.eff.org. Retrieved August 7, 2023.
15. "Web Environment Integrity has no standing at W3C; understanding new W3C work". www.w3.org. August 11, 2023. Retrieved August 11, 2023.

External links

• Web-Environment-Integrity on GitHub
• Web environment integrity API - Chrome Platform Status