XSLT in Chrome 158 is on its way out: with stable version 158, which Google has scheduled for 17 November 2026, Chrome switches off client-side XSLT processing. The change affects the XSLTProcessor JavaScript API and XML documents that pull in an XSL stylesheet through a processing instruction. Some users have already been receiving Chrome 158 through the early stable channel since 12 November. If you run XML views, RSS feeds or internal tools that rely on XSLT in the browser, you only have a few days left to test.
XSLT in Chrome 158: what exactly is removed
According to the guide “Removing XSLT for a more secure browser” on Chrome for Developers, both ways browsers have used to run XSLT are going away:
- the
XSLTProcessorclass, for examplenew XSLTProcessor(), - the XSLT processing instruction in XML files, meaning
<?xml-stylesheet type="text/xsl" ... ?>.
XML itself is not being removed. The xml-stylesheet processing instruction also stays when it references a CSS stylesheet with type="text/css". If you only want to style raw data in the browser rather than transform it, CSS still works.
The timeline through August 2027
The removal is not a surprise. Google has been preparing it step by step since autumn 2025. According to the guide, the plan looked like this:
- Chrome 142 (October 2025): first console warnings.
- Chrome 143 (December 2025): official deprecation, warnings in the console and Lighthouse.
- Chrome 145: Canary, Dev and Beta disable XSLT by default as an early warning.
- Chrome 146 (March 2026): an enterprise policy becomes available for testing.
- Chrome 152 (August 2026): an origin trial starts that lets sites keep using XSLT past the removal date.
- Chrome 154 (September 2026): WebView pre-release channels also disable XSLT by default.
- Chrome 158 (17 November 2026): XSLT stops working in stable releases, except for origin trial participants and where the enterprise policy is set.
- Chrome 176 (17 August 2027): the origin trial and enterprise policy end, and XSLT is disabled for everyone.
On 12 November, the Chrome Releases blog announced Chrome 158 in the early stable channel: version 158.0.8127.36/.37 for Windows, with Mac to follow shortly, and 158.0.8127.36 for Android. This early rollout reaches only a small share of users. If you already have it, you can see the breakage today.
Why Google is removing XSLT
Google’s main argument is security. Browsers still only support XSLT 1.0 from 1999. The libraries behind it, libxslt in Chromium’s case, are described in the guide as complex, ageing C and C++ codebases that are prone to memory safety bugs such as buffer overflows. Google cites CVE-2025-7425 and CVE-2022-22834 in libxslt as examples. Because client-side XSLT is rarely used, these libraries get far less maintenance and scrutiny than JavaScript engines, yet they remain a direct attack surface for untrusted content.
Usage is also very low: Google’s measurements show that only about 0.02 percent of page loads use XSLT at all, and less than 0.001 percent use the processing instruction. According to Google, the WebKit and Gecko projects behind Safari and Firefox also support removing it from the web platform. In parallel, Google plans to move XML parsing in Chromium from libxml2 to a memory-safe parser written in Rust. That change is meant to be invisible to web developers.
Who is affected: RSS, sitemaps, device interfaces
The guide lists several typical use cases:
- RSS and Atom feeds: many feeds use XSLT so that a feed opened by mistake in the browser looks readable.
- Embedded devices: some devices serve XML on the local network that becomes a user interface in the browser through XSLT. Such devices are often hard or impossible to update.
- “Lazy templating”: some sites use XSLT as a simple template language for presenting semantic markup.
XML sitemaps are another common case. The sitemap of this site, like those generated by many SEO plugins, also references an XSL stylesheet via <?xml-stylesheet type="text/xsl" ...?> so it shows up as a table in the browser. That rendering is only for human readers; search engines read the XML data directly. But anyone opening their sitemap in Chrome 158 will no longer see the familiar table view.
How to migrate
Google describes several paths depending on your situation:
- Transform on the server: move the XSLT step to the server and serve finished HTML. For many feed and documentation views, this is the cleanest option.
- Switch to JSON: replace XML endpoints with JSON and build the HTML on the client with JavaScript.
- XSLT in JavaScript: libraries such as Saxonica’s bring XSLT to the browser, supporting version 3.0 instead of just 1.0.
- Polyfill: a WebAssembly-based polyfill referenced by Google replaces
XSLTProcessor, so existing code keeps working. For XML files with a processing instruction, the guide says one extra line that adds a<script>element loading the polyfill is enough. According to Google, this should not affect feed readers. - Extension: where neither the XML nor the XSLT can be changed, a Chrome extension applies the polyfill to all affected pages. When XSLT is disabled, Chrome also shows a banner that points users to a search for a suitable extension.
For feeds, Google also recommends adding <link rel="alternate" type="application/rss+xml"> to a site’s HTML instead of visibly linking to the XML file. Feed readers still find the feed, and visitors do not end up in an XML view by accident.
Finding XSLT usage in your code
Before migrating, you need to know where XSLT is still used. The guide names two approaches. The Reporting API reports deprecated features; a ReportingObserver for the deprecation type can catch reports with the ID XSLT and send them to your own endpoint. Enterprises can also use Chrome’s Legacy Technology Report, which collects usage of deprecated features centrally.
A simple search of your repositories for XSLTProcessor, xml-stylesheet and files ending in .xsl also helps. Old feed pages, microsites and internal dashboards are especially easy to overlook.
Analysis
The removal fits a pattern: browser vendors are retiring old, rarely used components written in unsafe languages because they cause a disproportionate share of security problems. How serious such bugs can get was shown recently by the actively exploited Chrome flaw CVE-2026-125350. For most sites, the impact will be small. But if you use XSLT in the browser in production, you will notice the change from Tuesday. Enterprises can buy time with the policy, but that bridge is temporary too: according to the timeline, both the policy and the origin trial end in August 2027.
If your team is cleaning up dependencies anyway, other maintenance topics in the web stack are worth a look too, such as this month’s security fixes in Symfony HTTP Foundation.
Bottom line
XSLT in Chrome 158 ends on 17 November 2026 for the vast majority of users. The change affects XSLTProcessor and XSL processing instructions in XML files, not XML or CSS stylesheets. If you run RSS views, sitemaps with a browser view, device interfaces or templates based on XSLT, test now and move to server-side transformation, JSON or the polyfill.




