Appearance
What export produces
Export playout graphic writes two files side by side: the graphic, an
.airzplayfile the playout server plays, andbindings.json, a list of everything the graphic lets someone change.
File › Export playout graphic… in the File menu, or Ctrl+E. Choose where to save and a name: the name comes without an extension, because the type you pick under Save as type puts it on. There are two:
| Type | When |
|---|---|
| airZ playout graphic (.airzplay) | The usual choice: airZ Engine plays it, and a double-click opens it in airZ Player |
| For other players (.riv) | The same graphic, under the name other players of the format expect, and for an older airZ Engine |
If a file with that name is already there and the save window has not asked about it, the editor asks: "<file> already exists. Replace it?"
When it is done:
Exported lower-third.airzplay and lower-third.bindings.json to D:\Graphics.
with Show in folder.
Export straight after picking a scanned look and its pictures may still be getting ready: the status then reads "Preparing pictures… (2 of 3)" and counts up, and the editor stays usable while it does.
The graphic: lower-third.airzplay
The whole graphic in one file: every artboard, timeline, Animation States and view model, the fonts and pictures it uses, and its scripts. Nothing else is needed to play it.
- It is what you see. The editor's stage shows this same file, so what plays on air matches the stage.
- It opens on the artboard marked Default. That artboard's view model is what the control system fills, and its default Animation States are the ones that runs. See Artboard › Default.
- It is a standard
.rivfile under our own name..airzplayand.rivhold the same bytes. Other players that read the format open it too; save it as.rivfor them. Where they cannot do what airZ Engine does, such as play a live source in a slot, they show the placeholder. - It is not the document. Keep the
.airzdocument to go on working. File › Import playout graphic… can read an exported file back, but not everything the editor keeps for you, such as undo or the default source of a slot.
The list: lower-third.bindings.json
A plain text file for the controller and for anyone wiring the graphic into a newsroom or a data feed. It says:
| What | For each one |
|---|---|
| Properties | Every property marked Visible to controller: its name (nested ones as home/name), its type, and what it starts as |
| Enums | The values an enum property can take |
| Image slots | The placeholder size, the default source, and for live slots the role, label, sound, what shows when the source stops, and the colour space |
| Lists | The item view model, which artboards can draw a row, and the items it starts with |
| Animation States | Their names, the default one first, and any trigger, boolean or number inputs |
| Timelines | Their names |
| Events | Each event the graphic can report, with its properties |
A short one:
json
{
"artboard": "Lower third",
"viewModel": "Lower third",
"bindings": [
{ "name": "name", "type": "string", "default": "Jane Doe" },
{ "name": "role", "type": "string", "default": "Presenter" },
{ "name": "onAir", "type": "boolean", "default": false },
{ "name": "accent", "type": "color", "default": "#2F6BD8" }
],
"stateMachines": [ { "name": "Main", "default": true, "inputs": [] } ],
"timelines": [ "In", "Out" ],
"events": []
}A property that is not Visible to controller is left out. See Naming properties.
Where the files go
A playout server plays graphics from its template folder. Copy both files there, or let Send to air do it: it sends the same graphic and the same list, and the controller files them where its engines find them.
For an OGraf renderer: an OGraf package
File › Export OGraf package… writes the graphic as one .zip that any renderer of EBU OGraf, the open broadcast standard for graphics played in a browser, can load and play: a broadcaster's own OGraf system, without airZ Engine. Like Export playout graphic… it needs a licence; without one it reads Export OGraf package… (needs a licence).

The dialog, Export OGraf package, says the graphic's name and size, "for any OGraf renderer (EBU OGraf v1)", and gives each of the graphic's triggers a role:
| Row | What it is | Empty choice |
|---|---|---|
| Play | The trigger that brings the graphic on. Each trigger shows how long its animation runs, such as Animate In · 1.3 s | Starts the graphic: "Play starts the graphic; until then it waits, hidden." |
| Stop | The trigger that takes it off | None, in amber: "With Stop on None, stop takes the graphic off at once." |
| Next step | The trigger that moves the graphic on, for a graphic in several steps | None |
| Previous step | The trigger that goes back a step | None |
The rows start set from the triggers' names, such as In and Out, takeIn and takeOut, next and prev, so a graphic in several steps comes out as one. A trigger has one role: choosing it in one row takes it from another. With Next step set: 'Next step fires "<next>" and Previous step fires "<prev>". Controllers show step buttons, since the number of steps is not fixed.'
Under the rows it counts what an operator will have, such as "8 fields an operator can fill in." for the football lower third, with ", and K other triggers as custom actions" when the graphic has triggers without a role. In amber it lists what does not come across:
| Note | Why |
|---|---|
"Not carried: "<name>" is a live video slot: it shows its placeholder picture." | An OGraf field holds a value, not a camera or a clip |
"Not carried: "<name>" is a list whose rows have no view model." | A list's rows carry only when each row is a view model, as a ticker's headlines are |
"Not carried: "<name>" chooses an artboard: not available in an OGraf renderer." |
Text, numbers, true/false, colours, enums and pictures do carry, and so do scripts and 3D: the package plays them as the editor does. A picture becomes a field for the address of a PNG or JPEG; left empty, it keeps the picture made in the editor.
Lists carry too, such as a ticker's headlines or a table's rows: the OGraf system sends them as rows, each with an ID and the row's text, numbers, true/false and colours. A list starts with the rows the graphic was made with, and when it changes, rows that stay keep their place, as on air.
Export… asks where, and names the file after the graphic, such as airz-lower-third.zip. When it is done: "Exported the OGraf package <file> to <folder>." with Show in folder. A graphic with no triggers at all exports too: Play starts it.
A field whose property was renamed after the graphic was first published still accepts data sent under its old names, so an OGraf system or an automation that still uses an old name keeps filling it. The operator's form shows each field once, under its current name. See Renaming later.
Inside the package are the graphic itself, the same as an .airzplay, the list of its fields, and the airZ Player for the web, which plays it. The graphic is not turned into HTML: the player draws it as airZ Engine does. As the dialog says, "The package carries the airZ Player for the web, so it plays where the renderer's browser has WebGPU": a page served over https, or from localhost.
Export, or send to air?
| Use | When |
|---|---|
| Send to air | The graphic goes to a gallery that runs a controller. It updates a template that is already there, keeping its place in the rundown |
| Export playout graphic | Everything else: a server you copy files to by hand, a colleague, an archive, a test in another player |
| Export OGraf package | The broadcaster plays graphics on an OGraf renderer of their own |
Before you export
Look at the preflight chip. It lists what would go wrong on air. Export works whatever it says, and so does Send to air, which asks first when there are errors.
One thing does stop an export, an OGraf export and a send to air: a 3D scene lit by a picture (an HDR or a sky) whose reflections are not ready yet, right after the document opens. The editor waits for them, and if they are still not ready it writes nothing rather than a graphic that reflects white on air: "The reflections could not be prepared from "<picture>" in time, so nothing was sent (a graphic without them reflects white on air). Try again in a moment; if it keeps happening, the picture may not be readable."