XSLT workbench

A three-pane XSLT 3.0 editor that runs entirely in your browser — paste or load your XML, edit the stylesheet, and see the output on every keystroke. Or describe the transformation and let a Claude agent write the stylesheet in front of you: it runs each draft, reads the compiler errors, and fixes its own mistakes until the output is right. Built for the loop every integration consultant knows — ask for XSLT in a chat window, paste it into your editor, discover it doesn't compile, repeat.

Loading the XSLT engine (Saxon-JS 2.7)…Auto-run on change

Source XML

Load file

<?xml version="1.0" encoding="UTF-8"?>
<wd:Report_Data xmlns:wd="urn:com.workday.report/INT001_Employee_Snapshot">
  <wd:Report_Entry>
    <wd:Employee_ID>100234</wd:Employee_ID>
    <wd:Legal_Name>Rivera, Dana</wd:Legal_Name>
    <wd:Hire_Date>2023-04-17</wd:Hire_Date>
    <wd:Base_Pay wd:Currency="USD">84500.00</wd:Base_Pay>
    <wd:Cost_Center>CC-4200 Field Operations</wd:Cost_Center>
  </wd:Report_Entry>
  <wd:Report_Entry>
    <wd:Employee_ID>100871</wd:Employee_ID>
    <wd:Legal_Name>Okafor, Chidi</wd:Legal_Name>
    <wd:Hire_Date>2021-09-01</wd:Hire_Date>
    <wd:Base_Pay wd:Currency="USD">102300.00</wd:Base_Pay>
    <wd:Cost_Center>CC-1100 Corporate IT</wd:Cost_Center>
  </wd:Report_Entry>
  <wd:Report_Entry>
    <wd:Employee_ID>101508</wd:Employee_ID>
    <wd:Legal_Name>Sato, Yuki</wd:Legal_Name>
    <wd:Hire_Date>2025-01-13</wd:Hire_Date>
    <wd:Base_Pay wd:Currency="USD">67200.00</wd:Base_Pay>
    <wd:Cost_Center>CC-4200 Field Operations</wd:Cost_Center>
  </wd:Report_Entry>
</wd:Report_Data>

1,020 characters · stays in your browser

XSLT stylesheet

Tab indents. Edits auto-run when the toggle is on.

Output

Output appears here after the first run.

Ask the agent

session: 0 in / 0 out tokens · ~$0.0000

Anthropic API keyRemember key in this browser (localStorage)

ModelSend the full XML (default: first 6,000 characters)

What should the stylesheet do?

Sends your task, the current stylesheet, and the full XML (1,020 characters) directly from this tab to api.anthropic.com — nowhere else. Billing goes to your own API account (Claude Sonnet 5).

Version timeline

Nothing saved yet. Versions are captured automatically on every agent attempt, or manually with “Save version” — stored in this browser only.

Where your data goes

Transforms run locally — the engine is Saxon-JS 2.7 by Saxonica, loaded with this page and executed right in your tab. Your XML and XSLT are never uploaded to this site; there is no backend.

The agent is the one exception, and it's opt-in: when you click “Write the XSLT”, your task, the current stylesheet, and an XML sample (truncated by default — there's a toggle for the full document) are sent directly from your browser to api.anthropic.com using your own API key. Nothing passes through this site's servers, and the exact payload size is described under the button before you click. Don't paste production data containing real personal information — a hand-built sample with the same structure works just as well.

Both editors and the version timeline are saved to your browser's local storage — they survive a refresh on this machine but exist nowhere else.

Bring your own key

The agent bills your own Anthropic API account — this site charges nothing and never sees your key (it stays in this tab unless you tick “remember”, which keeps it in your browser's localStorage). Create a key in the Anthropic Console and load a few dollars of credit; a typical write-run-fix session is a few cents on Sonnet. A live estimate accumulates in the panel as you go, computed from the token counts the API reports.

A Claude Pro or Max subscription can't be used here — subscriptions cover Anthropic's own apps, not third-party tools. The API key is the mechanism for everything else.

Notes for Workday work

Saxon-JS is a full XSLT 3.0 / XPath 3.1 processor, so stylesheets that run here behave the same in Studio and Document Transformation — both are Saxon underneath.
The sample XML is RaaS-shaped (wd:Report_Data / wd:Report_Entry) as a reminder that Workday XML is namespaced — the most common reason a stylesheet silently matches nothing is a missing namespace declaration.
The agent knows this context: it's prompted as an XSLT 3.0 developer working on Workday-style integration output (CSV, fixed-width, JSON, XML reshaping) and told to double-check namespaces before anything else.
Transforms run synchronously in the page, so a genuinely infinite loop will hang the tab — if that happens, reload: both editors and all saved versions are restored automatically.