# Show content on your screens

Publish approved artwork to Mestra Player screens, how the loop plays, what a screen can play, and how to set sound and pull an ad.

There are two ways to put content on Mestra Player screens. You can publish artwork from an approved run or review in Mestra, the same way as to your other screen networks, with **Publish to screens**. Or you can upload a picture, video or HTML5 package in Mestra Player and book it there: see [Put content on your screens](https://withmestra.com/docs/player/scheduling/). This page covers publishing from Mestra, and what is the same for both.

> **Before you start:**
>
> - Publishing from Studio to your screens needs Mestra Player (or Network). Studio on its own makes and exports sizes.
> - You need screens that are [added and online](https://withmestra.com/docs/player/install/).
> - Publishing to a screen takes artwork that has passed your layout checks. Owners can publish a held size with a reason. An owner decides who else can publish, under **Settings** > **Publishing from Studio** in the player web app.

## Publish

1. Open an approved run or review, choose the menu and select **Publish to screens**. If you have more than one screen system connected, choose **Mestra Player**.
2. Check the **Start date** and **End date**. If a screen is in a different time zone from yours, the dialog says "Dates are in the screen's time" and names the zone.
3. Choose **All day**, or **Custom** to pick hours and **Slots**.
4. For each size, tick the screens to publish to. A screen with a problem shows it beside the name. Some problems stop you publishing to it. Others need a reason in **Reason for publishing anyway**.
5. For a picture, enter its **Play length (seconds)**. Mestra shows the shortest and longest it allows. A video or a package plays for its own length. Mestra Player needs no slot length: a video or package plays its own length, so the dialog doesn't warn about one.
6. Select **Publish**. Studio stays where you were and shows **See it in Mestra Player**, which opens the **Published** page in the player web app.

Publishing makes drafts. Nothing plays until someone chooses **Go live** on the **Published** page in the player web app and confirms **Send to screens**. Publishing again after a new approved round swaps the artwork in the existing booking, and asks you to confirm first if it is already live. A screen with frames is listed by its frames, each named after its screen, such as **Lobby · Left**. See [Windows and frames](https://withmestra.com/docs/player/windows-and-frames/). See [Doohly](https://withmestra.com/docs/integrations/doohly/#publish) for the dialog in more detail.

On the player web app's **Published** page each size has a pill: **Sending**, **Draft**, **Live**, **Played** (with a count), **Replaced**, **Ended** or **Failed**. Each publication has one status of its own too: **Draft**, **Live**, **Ended**, **Waiting**, **Sending**, **Some failed** or **Failed**. They are the same as on **Bookings**: see [Booking statuses](https://withmestra.com/docs/player/scheduling/#booking-statuses). A publication from a run or review in a Studio campaign also shows under that campaign in Player's **Campaigns** and the **Campaign** filter on **Bookings**. Select **Retry the rest** to resend only what didn't go through, or **End the old booking** to end the booking an update replaced.

## The loop

A screen plays its bookings in turn, in a loop. Each booking takes its number of consecutive **Slots**.

- A booking has a date range and an optional daily window, like 07:00 to 22:00. Both are read on the wall clock of the screen's time zone, including the days daylight saving starts and ends.
- A window that ends before it starts runs overnight. It belongs to the night it starts, and the part after midnight plays on the morning after each booked night, including the last. See [Overnight windows](https://withmestra.com/docs/player/scheduling/#overnight-windows).
- A screen's page shows the loop, with what is playing now and what is next.
- If the loop can't play, the screen shows its cached, verified pictures that are live now, and if there are none, its stop show.
- A stop or takedown reaches a screen straight away. See [Run your screens](https://withmestra.com/docs/player/screens/#when-a-screen-is-stopped).

## What a screen can play

| Format           | Notes                                                                                                                          |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Still images** | PNG or JPEG, the approved export for the screen's size.                                                                        |
| **Video**        | An MP4. H.264 plays on every PC. H.265, VP9 and AV1 play only on a screen whose PC reports it can decode them.                 |
| **HTML5**        | A zipped package. It runs in a sandbox with no network access. An uploaded package can only be shown on Mestra Player screens. |

A video plays without a gap, from two video layers that take turns. A screen can also play in part of the PC's output, or in several frames at once: see [Windows and frames](https://withmestra.com/docs/player/windows-and-frames/). A screen group plays stills and video up to 30 fps, and no HTML5. See [Screen groups and video walls](https://withmestra.com/docs/player/video-walls/).

### The decode report

Each PC tests what it can decode and reports it. The screen's **Playback** section shows it, such as "Plays H.264 · H.265 up to 3840×2160 at 30 fps · HTML5 on". Mestra uses it three times:

- **Before you publish.** A file a screen can't play is marked on that screen, with why: it doesn't decode that codec, it's bigger or faster than the screen decodes, HTML5 is off, or the screen hasn't said what it plays yet.
- **While it plays.** A screen is never sent a file it can't play.
- **On the screen's page.** **Playback** lists **Files this screen can't play**. Upload a version the screen can play, or leave it off that screen.

HTML5 can be off on a screen for a reason: the network lock isn't confirmed, the player hasn't started it, sound can't be kept off, or the player is starting. Mestra keeps it off until the player confirms its protections hold.

If one file fails to decode, the player doesn't take it as proof that the PC lacks the codec. It tries again later, and lowers the report only if several different files fail.

## Files are checked

Every file is identified by its SHA-256 hash. A file downloads to a temporary file, is checked, and only then used. A file that fails its check is deleted and fetched again, and the screen's page records it. Mestra sends a file only to a screen that has a live booking for it.

## Sound

Everything is silent unless an owner turns sound on for the site or screen, under **Sound** in the panel settings. Then, on the player web app's **Published** page, set an **Ad volume** for each booking from 0 to 100 and select **Save ad volume**. A booking with no volume is muted. An HTML5 package has **Ad sound on** instead of a volume. The page says "Sound is off at this site" where sound is off.

## Offline

A screen keeps playing its last schedule when the internet drops, and each booking ends at its own end time on the PC's clock. Plays are saved on the PC and sent when it is back online.

## Pull an ad or stop screens quickly

An owner or editor can **Stop** a screen from its menu. To pull an ad from many screens at once, use a takedown through the API, or an AI assistant connected with a Screens key at the **Takedown** level. A takedown is confirmed screen by screen. See [API](https://withmestra.com/docs/api/) and [Connect your agent](https://withmestra.com/docs/mcp/).
