Will my site break on November 17?

Almost certainly not. It only affects sites that display XML with an XSLT stylesheet in the browser. Chrome puts that at around 0.02% of page loads.

Is XML being removed too?

No. Chrome says XML stays and styling with CSS keeps working. What goes away is the conversion with XSLT.

Will my RSS feed stop working?

Feed readers keep reading the data. What changes is that if you open the feed directly in Chrome, you'll see it unformatted.

Yes. Chrome's trial (the Origin Trial) and the enterprise policy let you keep using it until August 17, 2027.

Chrome turns off XSLT on November 17: what to check if your site shows styled feeds or XML

What happened

On October 29, 2025, the Chrome team published a plan to remove XSLT from the browser. According to its schedule, Chrome 158 ships on November 17, 2026, and from that day XSLT stops working in the stable version for almost everyone. The exceptions are sites enrolled in a Chrome trial (an Origin Trial) and companies with a specific policy. Those exceptions end on August 17, 2027, with Chrome 176.

What it means

XSLT is a language that turns an XML file, which is plain data with no design, into a page you can read. Think of a raw spreadsheet and the template that turns it into a formatted report. When you open an XML file in the browser and it links to an XSLT stylesheet, the browser does that conversion for you. That is what Chrome is about to stop doing.

Chrome gives two reasons. The first is security: the code that processes XSLT is old and prone to memory bugs, and the page cites two recorded vulnerabilities (CVE-2025-7425 and CVE-2022-22834). The second is that almost nobody uses it, around 0.02% of page loads. Chrome says XML itself isn't going away, and styling with CSS keeps working.

Firefox and WebKit have also said they plan to remove it, though without dates.

How it affects you

If your site is an ordinary website, nothing probably changes. A site that doesn't serve XML with XSLT stylesheets won't notice.

It does affect you if:

Your RSS or Atom feed looks like a readable page when opened in the browser, thanks to XSLT. After November 17, Chrome would show the raw XML. Feed readers shouldn't notice, because they read the data, not the presentation.
You run a system that generates XML with XSLT to display it in the browser, such as a device's admin screen. Chrome's page mentions this case and says an extension is usually the most realistic option when the device can't be updated.
You use XSLT in the browser to format content on your own site.

As for WordPress: we found no official source saying whether it uses XSLT in its feeds or sitemaps, and no WordPress notice about this change. Chrome's page doesn't mention sitemaps either. We're not assuming it applies, and we're not ruling it out.

What you can do

Ask whoever maintains your site whether anything uses XSLT. It takes a minute.
Open your feed and any public XML file in Chrome. If it looks formatted, check whether that formatting comes from an XSLT stylesheet.
If you use XSLT, you have four options, according to Chrome's page:
- Generate the HTML on the server, or serve JSON and draw it with JavaScript. This is the long-term fix.
- Use the XSLT polyfill, a replacement that runs in the browser. For an XML file with a stylesheet, you add one line with the script.
- Use a library such as Saxon-JS, which runs XSLT in JavaScript.
- Join Chrome's trial (the Origin Trial) to buy time until August 2027.
Check whether your site still uses it. Since Chrome 143, the console and Lighthouse show deprecation warnings, and the Reporting API can detect it.

If you don't use XSLT, there's nothing to do.

Source

Chrome for Developers, Removing XSLT for a more secure browser, published October 29, 2025. The plan is confirmed on the Chrome Platform Status entry, updated November 4, 2026.