# Put content on your screens

Add pictures, video and HTML5 packages in Mestra Player, book them onto screens, see the week on the Schedule page, group bookings in campaigns, and end a booking.

You can put content on your screens without the Mestra app. Add the file in the player web app at `player.withmestra.com`, book it onto screens, and watch it play. If your artwork comes from a run or review in Mestra, see [Show content on your screens](https://withmestra.com/docs/player/showing-content/) instead. Both end up in the same place: the **Bookings** page.

Booking content in Mestra Player needs Mestra Player (or Network). Studio on its own doesn't include it, and Mestra says "Your plan doesn't include scheduling on Mestra screens."

## Who can do what

- **Reviewers** (the Reviewer role) see everything: content, bookings, the schedule and campaigns. They can't change anything.
- **Editors** also add and remove content, book, go live, end bookings, make campaigns, put screens in a site and make sites.
- **Owners** can do all of that, and also make screen groups with **New group** on the **Screens** page. See [Screen groups and video walls](https://withmestra.com/docs/player/video-walls/).

## Add content

1. Open **Content** and select **Add content**.
2. Choose one or more files. Several files go up one at a time.

Mestra takes:

| Format            | Notes                                                                                                                                                                                                                                                                                                                          |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Picture**       | PNG or JPEG, up to 25 MB.                                                                                                                                                                                                                                                                                                      |
| **Video**         | MP4, up to 500 MB and 5 minutes long.                                                                                                                                                                                                                                                                                          |
| **HTML5 package** | A zip, up to 100 MB (it can't unpack to more than that), with an `index.html` at its top level that gives its size, like `<meta name="ad.size" content="width=1080,height=1920">`. A `mestra.json` with `{"durationMs": 15000}` gives its length. It runs in a sandbox with no network access. Screen groups don't play HTML5. |

A large video is sent in parts, with a progress figure beside its name. If a part fails, the page tries it again a few times and carries on from where the upload was. If you close the page part way, it ends the upload and Mestra throws away what it had received, so you start that file again. When the last part is in, Mestra checks and stores the file, which can take a little while for a large one.

An uploaded file is marked **Not checked**. Mestra doesn't check it against a layout, so look at it yourself before it goes on a screen. A screen that can't play a file says so on the screen's page and on the booking's page. See [what a screen can play](https://withmestra.com/docs/player/showing-content/#what-a-screen-can-play).

A picture has no length of its own, so you say how long it plays when you book it. A video plays for its own length. An HTML5 package without a `mestra.json` asks how many seconds it plays when you add it, and again when you book it if it still has none.

Content stays until you remove it. Select **Remove** on a tile to take it out of the library. Removing content doesn't stop bookings that use it: they keep playing until they end.

## Book it

On **Content**, select **Book** on a tile, or select **Book content** on the **Bookings** page. There are four steps.

1. **What.** Pick the content. For each picture, and each HTML5 package with no length, enter **Plays for (seconds)**. Choose **Paid** or **House**. For a paid booking, optionally pick the **Customer** it is for, or select **New customer**, and set **This ad's own cap**. House content has no customer and no cap. See [Who plays when](https://withmestra.com/docs/player/loop/).
2. **Where.** Pick screens, whole sites, or screen groups.
3. **When.** Choose a **Start date** and **End date**. Then choose **All day**, or **Custom** to pick days and hours and the number of **Slots**. A booking takes its number of turns in the screen's loop, so more slots means a bigger share of it. If you set a loop length, caps or an order, Mestra works out the turns on the server: see [Who plays when](https://withmestra.com/docs/player/loop/). See [the loop](https://withmestra.com/docs/player/showing-content/#the-loop). Hours are read on the screen's own clock. A window that ends after midnight, such as 8 pm to 3 am, is an overnight window: see [Overnight windows](#overnight-windows).
4. **Review.** Check what, where and when. Optionally add the booking to a campaign. A screen that can't play the booking says why, for example when it is shorter than the screen's shortest slot.

Then choose how it goes out:

- **Book** sends it to the screens in one step. Confirm **Send to screens**.
- **Save as draft** keeps it so you can check it first. Nothing plays. A draft goes live from **Bookings**: open it and select **Go live**.

If you picked several files, each one makes its own booking.

Mestra doesn't show how much room is left. If the screens are full at those times, it says so when you book, takes you back to **When** and marks the full hours. Change the times or the screens.

New bookings and go-lives pause while a Mestra Player invoice is more than 30 days overdue. What is already playing keeps playing. Pay the invoice and book again.

## Bookings

**Bookings** lists everything booked on your screens, newest first, with its dates and a status pill. Open a booking to see its content, its screens and its plays, to **Go live**, or to retry the screens that failed.

### Booking statuses

| Status          | What it means                                                                                                   |
| --------------- | --------------------------------------------------------------------------------------------------------------- |
| **Draft**       | The booking is saved but hasn't been sent to its screens, so nothing plays. Choose **Go live** to send it.      |
| **Live**        | A screen is playing it, or will on its dates.                                                                   |
| **Ended**       | Nothing of it is live or waiting.                                                                               |
| **Waiting**     | It is queued to go to the screens.                                                                              |
| **Sending**     | It is being sent to the screens now.                                                                            |
| **Some failed** | Some screens took it and some didn't. Open it and select **Retry** to send it again to the screens that failed. |
| **Failed**      | None of the screens took it.                                                                                    |

A booking that is still sending, or where some screens failed, also shows **Live** if a screen is already playing it. Inside a booking, each screen has its own state: sending, draft, live, replaced, failed or ended.

Above the list, filter by **Status** (**Any status**, **Live**, **Draft**, **Ended**, **Waiting**, **Sending**, **Some failed** or **Failed**), **Site**, **Campaign** or **Customer**.

Select **End** to take a booking off its screens. You are asked first. The screens stop playing it on their next check, and each one confirms it. Ending doesn't delete the content.

## The Schedule page

**Schedule** shows a week for each screen, with what each booking plays and when. **Today** is marked in the screens' own time zone: the one most of the screens in view keep. With no screens to say, it is the organisation's. See [Time zones](https://withmestra.com/docs/account/time-zones/). At the top, **Playing now** shows what each screen is playing. It refreshes while the page is open. On a phone it shows one screen at a time, day by day.

## Campaigns

A campaign is a name for a group of bookings, such as "Summer sale". It can have start and end dates. The dates and daily window are used when its bookings play: a booking never plays outside them, and a booking that falls outside its campaign's hours says **Outside its campaign's hours** on **Bookings**. Nothing is refused when you book. A campaign can also name a customer and set a cap for its bookings. Make one on **Campaigns**, or pick one in the **Review** step. Archiving a campaign takes it out of the list. It doesn't end its bookings.

A booking you publish to Mestra Player from a run or review in a Studio campaign appears under a Player campaign for it, so you can find it on **Campaigns** and with the **Campaign** filter on **Bookings**. Publishing the same Studio campaign again joins the same Player campaign.

## Overnight windows

A booking window that runs past midnight, like 8 pm to 3 am, belongs to the night it starts. The part after midnight plays on the morning after each booked night, including the last one.

For example, a booking from Friday 13 Nov to Friday 13 Nov with a Friday window of 8 pm to 3 am plays on Friday evening and carries on until 3 am on Saturday. A booking that starts on Saturday 14 Nov doesn't play that Saturday morning, because the night it belongs to, Friday, was before it started.

## If you also use Mestra for artwork

Bookings made by publishing from a run or review in the Mestra app show on **Bookings** beside the ones you made here, marked **From Mestra**. The **Published** page in the player web app shows the same bookings. Each one links to the other: **See it in Published** on a booking here, and **Open the booking** on **Published**. After you publish in the Mestra app, **See it in Mestra Player** opens **Published**.

## Customers and the loop

Name the businesses you book for under [Customers](https://withmestra.com/docs/player/customers/). Then set how a screen's loop is built, and check it before it plays, in [Who plays when: customers and the loop](https://withmestra.com/docs/player/loop/).

## Do the same from an assistant or the API

An AI assistant connected with a Screens permission can list content and bookings, book content, go live and end bookings. See [Connect your agent](https://withmestra.com/docs/mcp/tools/#mestra-player-screens). The operations are in the [Mestra Player API](https://withmestra.com/docs/player/api/).
