XSLT Bridge

Keeps XSLT-based web apps working after Chromium removes native XSLT. Runs only on sites you or your administrator approve.

Chrome and Edge remove built-in XSLT by default starting with version 158 (November 2026). Web applications that turn XML into pages with XSLT, Internet Explorer era apps that use MSXML, and CDISC define.xml files stop working. XSLT Bridge restores them, inside your browser, on the websites and local folders you or your organization approve. >WHAT IT DOES XML pages with an XSLT stylesheet render again The standard XSLTProcessor API keeps working MSXML compatibility (ActiveXObject, DOMDocument, selectNodes, transformNode, XSLTemplate) for Internet Explorer era business apps (paid edition) CDISC define.xml renders from web servers and from approved local folders (pharma) PRIVACY AND SECURITY Runs only on sites and folders that are approved; nothing else is touched Sends nothing to us automatically: no telemetry, no analytics, no license server The XSLT engine (libxslt) is built into the extension; no remote code FOR IT TEAMS Deploy and configure with Group Policy or Intune (managed policy) Offline license keys; security questionnaire pack and GxP validation pack available Free edition: XSLT and XML rendering on approved sites. Paid edition (license key): MSXML compatibility, a JavaScript engine for sites whose security policy blocks WebAssembly, and diagnostic export. Support: support@zingersoftwaresolutions.com · https://zingersoftwaresolutions.com/xslt-bridge/