XSLT Prism

plain.xml tree view

XML viewer for Chrome, with an XSLT tester built in

Raw XML is hard to read and harder to debug. XSLT Prism opens it as a tree you can search and query, and gives you a full-tab workbench for writing and testing stylesheets.

XSLT Prism includes an XML viewer for Chrome. Any XML document without a stylesheet opens as a collapsible tree with search, XPath queries, a breadcrumb, document stats and a raw view. Its Prism Workbench is an XSLT editor and tester with tabbed editors, parameters, a live preview and an XPath tester. Both run on your device and come with the free XSLT Prism extension.

Updated October 4, 2026 XML viewer Prism Workbench

The XML viewer

XSLT Prism's XML viewer showing a sitemap as a collapsible tree, with the XPath query //d:url[d:changefreq='weekly']/d:loc matching 5 nodes, a breadcrumb urlset / url[3] / loc and stats of 94 elements, 42 attributes and 4 levels
A sitemap in the viewer: tree, XPath with matches highlighted, breadcrumb and stats.

When you open an XML document that doesn't name a stylesheet, such as an API response, a SOAP message, a configuration file or an unstyled feed, XSLT Prism replaces Chrome's plain listing with a viewer built for reading and inspecting. The tools sit in a floating dock at the bottom of the page, so the document keeps the full height of the window.

A tree you can fold

Elements open and close with a click or the arrow keys. Fold to level opens the document to depth 1, 2 or 3, or all the way, which is the quickest way to get the shape of an unfamiliar file. Namespace prefixes are dimmed so the local names stand out.

Find and XPath

One query field has two modes. Find searches text, and you step through the matches with Enter and Shift+Enter. XPath runs an XPath 1.0 expression and highlights every node it selects, which makes the viewer a handy XPath tester on real data. If the document has a default namespace, as sitemaps and feeds usually do, the viewer gives it a prefix (usually d:) and shows it in the field, so //d:url/d:loc just works.

Breadcrumb, copy XPath and stats

Select a node and the breadcrumb shows its path from the root. One button copies that node's XPath, ready to paste into code or a stylesheet. Next to it, document stats count elements and attributes and report the depth and size.

Raw view

Switch from the tree to the raw view to see the source text, line-numbered and colour-coded, with optional line wrap. From there you can copy the whole document or download it as a file.

Built for large files

The tree renders an element's children only when you open it, in batches, and the raw view only lays out the lines near the screen. Multi-megabyte exports stay responsive instead of freezing the tab.

Keyboard shortcuts

KeyAction
/ and xFind text, or type an XPath expression
tSwitch between tree and raw view
0–3, *Fold to a level, or open everything
cCopy the selected node's XPath
w / fToggle line wrap / full screen
Alt+Shift+XOn a styled page, switch between the rendered page and its XML source

If you were looking for an XML formatter for Chrome, the tree view is it: however minified the file, it shows every element indented and colour-coded. The viewer follows your light or dark theme, works on XML files from your computer once file access is allowed, and works today, before Chrome's XSLT removal.

Prism Workbench: an XSLT editor and tester

Prism Workbench with a podcast RSS file and its XSL stylesheet in tabbed editors, an XPath tester matching two item titles, the rendered podcast page in the preview pane and the command palette listing the built-in samples
Prism Workbench: tabbed editors, XPath tester, sandboxed preview and the Ctrl+K palette.

Prism Workbench is a full-tab XSLT editor and tester. Open it with Alt+Shift+S, from the toolbar button's right-click menu, or from the popup on any page.

  • Tabbed editors for input.xml and transform.xsl, with a side-by-side split when you want both in view.
  • Parameters: give values to the stylesheet's xsl:param declarations without editing it.
  • Run with Ctrl+Enter, or turn on auto-run. The output pane has four tabs: Preview, Source, Messages (everything xsl:message printed) and Timing.
  • XPath tester: evaluate an expression against the input and see each matching node with its path and line.
  • Command palette (Ctrl+K) for samples, run, format, open a page and theme.
  • Open a live page: paste the address of an XML document and the Workbench loads it with its stylesheet, so you can see why a page renders the way it does. Addresses you type are fetched without cookies.

Five samples cover the common jobs: a podcast feed (RSS), a website sitemap, an e-invoice (UBL), a catalogue with parameters, and readings exported to CSV text. Each is a working pair of XML and XSLT you can change and run.

The preview is sandboxed: scripts, forms and network requests are switched off, so a stylesheet under test can't do anything beyond drawing its output.

What it is not

Both tools use libxslt, so they handle XSLT 1.0 with EXSLT, the level browsers always supported, and XPath 1.0. Stylesheets written for XSLT 2.0 or 3.0 need a server-side processor. Neither tool needs an account or sends documents anywhere.

The viewer and the Workbench come with XSLT Prism, which is mainly an XSLT polyfill for Chrome: it keeps styled XML rendering after Chrome's XSLT removal and can bring back the API for apps that fail with "XSLTProcessor is not defined".

Questions

When does the XML viewer open?

Whenever you open an XML document that does not name an XSLT stylesheet, such as an API response, a feed without styling or a configuration file. For a styled page, Alt+Shift+X switches between the rendered page and its XML source.

Does it work on XML files on my computer?

Yes. In chrome://extensions, open XSLT Prism's details and turn on Allow access to file URLs. Local XML files then open in the viewer, or render with their stylesheet if they declare one in the same folder or below it.

Which XSLT version can I test in Prism Workbench?

XSLT 1.0 with EXSLT extensions, run by libxslt compiled to WebAssembly, the same level browsers have always supported. Stylesheets written for XSLT 2.0 or 3.0 will not run.

Does the viewer or the Workbench upload my XML?

No. Both run inside the extension on your device. There is no account, no analytics and no server, and documents never leave your browser.