Google and Microsoft are moving forward with a phased removal of client-side Extensible Stylesheet Language Transformations support across Chrome and Edge, ending a 25-year-old browser capability. According to reports from technical outlets including Doctor SEO, Google plans to disable built-in XSLT by default starting with Chrome version 158, scheduled for release on November 17, 2026. This change will terminate browser support for the XSLTProcessor JavaScript API and xml-stylesheet processing instructions. Microsoft is coordinating its roadmap in parallel, alerting enterprise administrators through Microsoft 365 message center notification MC1509789 that Edge version 159 will disable client-side XSLT by default in mid-December 2026, followed by a total code purge from the browser engine in Edge version 176 during the summer of 2027.
The push to eliminate the technology stems from severe, ongoing security risks contrasted with historically low adoption. Major browser engines have long relied on libxslt, a C-based open source library that has suffered from stagnant maintenance and recurring memory-corruption flaws, including buffer overflows. These weaknesses have turned the parsing engine into a frequent target for exploits, imposing heavy security maintenance costs. Meanwhile, Google usage metrics indicate that XSLT is now present in only about 0.02% of all page loads, while pages utilizing the xml-stylesheet processing instruction account for less than 0.001%. Although the World Wide Web Consortium advanced the standard to versions 2.0 in 2007 and 3.0 in 2017, browser vendors froze their implementations at the 1999 1.0 recommendation, leaving the feature isolated as modern development shifted entirely toward JSON and JavaScript frameworks. Similar deprecation efforts are now underway across Mozilla Firefox and Apple WebKit.
While modern web services will largely escape disruption, legacy internal enterprise environments face immediate breakage once browser defaults shift. Search engine crawling of XML sitemaps and backend server-side XSLT transformation pipelines operate outside browser rendering engines and will function without modification. However, older corporate intranets and specialized utilities, including Windows Server Remote Desktop Web Access and government regulatory document viewers that rely on client-side XML styling, will fail to render properly. Technical teams maintaining these environments must either migrate transformation logic to backend server-side architectures or integrate WebAssembly polyfills before the 2026 deprecation deadlines take effect.