Windows
Windows
Beginning with , Microsoft Edge supports Brotli as an HTTP content-encoding method. This change will be released to stable builds with the Windows 10 Creator’s Update early next year, but you can preview it now via . With this release, Brotli will be broadly interoperable across browsers, with support in the latest versions of Microsoft Edge, Firefox, and Chrome.
Brotli is a compression format defined in , previously available as part of the . When used as an HTTP content-encoding method, Brotli achieves up to 20% better compression ratios with similar compression and decompression speeds (). This ultimately results in substantially reduced page weight for users, improving load times without substantially impacting client-side CPU costs. As compared to existing algorithms, like Deflate, decompression with Brotli is much less expensive without sacrificing compression ratios.
In the current preview release, Microsoft Edge supports Brotli on HTTPS and HTTP connections. In a future preview release, we will update this behavior to only advertise Brotli support on HTTPS connections. Like Chrome, we will continue to decode Brotli content on HTTP connections. Note that in the current preview release, there is a known issue which results in the F12 Developer Tools incorrectly not showing the accept encoding response header. This is tracked as issue 9771399 on issues.microsoftedge.com.
As always, we welcome your feedback on Brotli in Microsoft Edge! Let us know or in the comments below if you have any questions or issues. We’re very much looking forward to making the web just a little bit lighter with Brotli!
― Rob Trace, Senior Program Manager, Microsoft Edge
Brotli is a compression format defined in , previously available as part of the . When used as an HTTP content-encoding method, Brotli achieves up to 20% better compression ratios with similar compression and decompression speeds (). This ultimately results in substantially reduced page weight for users, improving load times without substantially impacting client-side CPU costs. As compared to existing algorithms, like Deflate, decompression with Brotli is much less expensive without sacrificing compression ratios.
In the current preview release, Microsoft Edge supports Brotli on HTTPS and HTTP connections. In a future preview release, we will update this behavior to only advertise Brotli support on HTTPS connections. Like Chrome, we will continue to decode Brotli content on HTTP connections. Note that in the current preview release, there is a known issue which results in the F12 Developer Tools incorrectly not showing the accept encoding response header. This is tracked as issue 9771399 on issues.microsoftedge.com.
As always, we welcome your feedback on Brotli in Microsoft Edge! Let us know or in the comments below if you have any questions or issues. We’re very much looking forward to making the web just a little bit lighter with Brotli!
― Rob Trace, Senior Program Manager, Microsoft Edge