Will your XSLT survive Chrome 158?
Chrome 158 stops running XSLT on 17 November 2026. Give this page your project's scripts, templates, XML documents and stylesheets, and it tells you which of them depend on the browser's XSLT, how much of that the one-line migration covers, and what to install.
Nothing is uploaded. This page reads the files in your browser, runs the
same analysis as npx xslt-migrate-check . and forgets them when you close
the tab. You can disconnect from the network once the page has loaded.
Your files
Read: scripts and templates (.js, .ts, .html, .php, .vue and more), .xml, .xsl and .xslt, and the root package.json. Left out, as on the command line: node_modules, dist, build, vendor and other generated folders. Up to 50 MB and 5,000 files; zip archives without encryption.
Migration readiness:
Recommended migration:
What to do
Findings
| File | Reason and fix |
|---|
Next: the full report and the migration
This page shows the summary. On your machine, the command line adds line numbers, the details of every stylesheet, a patch with the changes and a report to send to a client:
npx xslt-migrate-check . --html- Migrate in five steps: scan, install, add one line, test, deploy.
- Migrating from native XSLT: the how-to, with why each step works.
- Checker reference: what each rating means and every option.