.zip
A folder per switcher
One directory per device, named after it, holding that switcher's config.xml. It's the same tree the desktop app writes to a folder you pick, delivered as a download instead. Unzip it onto a stick and walk the room.
ATEM Fleet Admin
Build every switcher's config, download the folders
Twelve switchers, one set of forms, a folder each.
Build every ATEM's configuration through forms that already know what that model can do, then download one folder per switcher containing a config.xml that ATEM Software Control will load. The alternative is typing the same settings into the same dialogs twelve times, on a flight case, the night before.
This is the browser build of a desktop app, and it does the important part: the XML is generated here in the page by the same code the download runs. What it can't do is reach a switcher, because a web page has no way to open a socket to one, so the desktop app is what you want if you'd rather apply the config live over the network than load a file at each unit.
What comes out
.xml
A loadable ATEM profile
Matched to real autosaves
A <Profile> in ATEM Software Control's own format, with element names, nesting and ordering matched against real autosave files. Load it with Software Control's own Load button, as nothing here talks to the switcher.
.json
The fleet, saved
The whole fleet as one project file you can save, reopen and hand to someone else. It's written and read entirely in the page (Save downloads it, Open reads it back), so the fleet never leaves your machine.
.txt
A media manifest
Each device folder that has media-pool items carries a MEDIA.txt naming what belongs in which slot, and where you said the source file was. The browser can't read a file from a path you typed, so it lists them rather than pretending to gather them.
What to check before a show
- 01
Live apply is desktop only, by construction
Connect & apply opens a TCP connection to the switcher. A web page can't do that at any privilege level, so the button is missing here rather than present and failing. Everything else (the forms, the model catalogue, the generated XML) is identical to the download.
- 02
Media files aren't bundled
The export carries the XML and the manifest, not your stills and clips. Load the media pool from ATEM Software Control as you normally would; the pool slots and names are already in the config either way.
- 03
Verify the Mini streaming and recording sections on hardware
The XML generator was matched against real ATEM autosave files, but no ATEM Mini save existed to check against, so the Mini <Streaming> and <Recording> sections are reconstructed from the protocol rather than copied from a known-good file. For those settings the desktop app's live apply is the one to trust.
- 04
Nothing is uploaded
There's no backend and no upload endpoint. The XML is generated and the zip is assembled in your own tab, which matters here because a fleet file is a list of your switchers, their names and their addresses.
Run your own copy
There's no container for ATEM Fleet Admin, so the hosted copy is the one to use, or the app you install from its project page.