🌿 New sprout. This tool is freshly built and still being tested against real ATEM exports — double-check anything that looks off before relying on it.
Reading an ATEM macro export in plain language #
ATEM Software Control can export a macro pool as XML, but the raw file is close to unreadable by hand — a single macro can run 250+ lines, because ATEM's macro recorder dumps the entire state of a keyer or SuperSource box even when only one thing changed. This tool loads that export and turns each macro into a short, readable summary instead of a wall of <Op> tags.
Drag a macro-export (or full config) file onto the row above, click Code to paste XML directly, or pick up a config you loaded here recently. Once it's loaded, every macro shows up in the list on the left — click one to see its detail on the right.
Reading a macro's detail
Each macro's card leads with its description field when one is set (usually the best explanation available, since it's the note whoever built the macro already wrote), then a short headline. The Overview tab groups the macro's Ops by what they target — a keyer, a SuperSource box, a media player — each as a short, readable line; click the label chip (e.g. "ME1 Key1") to fold out the raw Ops for just that one target. Raw Ops shows the complete, unfiltered list exactly as ATEM exported it, for when the summary isn't enough.
Show Layout
Every macro's Overview tab has a Show Layout button that draws that macro's SuperSource boxes and DVE keys to scale, right underneath — no need to leave the macro to go find it somewhere else. The coordinate system it's built on is inferred from mask boundary values in real exports (not documented by Blackmagic), so treat the drawing as a best effort rather than verified ground truth.
A note on defaults and unknowns
There's no official documentation of this XML format from Blackmagic — only the separate Streaming XML format (for RTMP providers) is documented. The Op-registry this tool uses to decide what counts as boilerplate was built empirically from real export files, and it's deliberately conservative: an Op is only treated as a default worth hiding when sample exports agreed on its value almost unanimously. Anything the registry doesn't recognize is always shown rather than guessed away.
Privacy
Parsing runs entirely in your browser — nothing is uploaded anywhere. That matters here specifically: ATEM configs can reveal production setups, camera names, and internal notes.