Digital Signage Offline Playback and CMS Reconnection

A digital signage player should keep showing approved content when the CMS, the WAN link or the internet gateway is unavailable, and it should resynchronise cleanly when the connection returns. In practice that means a locally cached playlist with a known expiry time, a neutral fallback screen, a watchdog that restarts the player application, and a reconnection routine that avoids duplicate or stale content. Offline behaviour is a design decision that has to be specified and tested, not a default setting.

This note is written by Singapore-based AV and IPTV integrator Prestige Solutions for facility managers, property managers and system integrators planning a digital signage network. It covers the failure types to design for, the storage and expiry values we use as a starting point, the clock and reconnection behaviour, and the acceptance tests to run before handover. The values below are planning considerations as of 2026; confirm them against the specific player hardware and CMS platform before committing to a design.

Which failures the player has to survive

Most field incidents fall into four failure types. Each one has a different recovery path, so each should have its own test case in the commissioning plan.

The stale-content case is the one most often missed. A player that keeps looping a tenant notice from three weeks ago is worse than a player showing a blank neutral screen, because the building looks unmanaged. Log the start and end of every offline period as well, so that alert thresholds are set from measured outages rather than from assumptions.

How much media the player must hold

The cache has to cover the longest outage you expect to tolerate, multiplied by the content you need to show during that outage. Work it out per screen and then total the network, because a 40-screen site multiplies small errors quickly.

Worked example: a 10-minute 1080p loop encoded at 8 Mbps contains 8 Mbit/s × 600 s = 4,800 Mbit, which is 600 MB. If each of 40 screens carries its own 600 MB loop and you want the cache to survive a 7-day outage with a single loop per screen, the sites hold 40 × 600 MB = 24 GB of cached media in total, not counting the operating system and logs. Check that total against the storage specification of the player model before the hardware is ordered.

Clock and schedule behaviour when the internet is down

Scheduled content depends on the player's clock. A player that drifts by a few minutes will start a breakfast notice late, and a player that loses time after a power cut may show the wrong day's schedule until it reconnects. Set time synchronisation so that it does not depend on the internet gateway alone.

• Local NTP: point players at an NTP source on the site LAN, such as the building management system or a site server, with the public pool as a secondary source.
• Time zone: set Singapore time (UTC+8). Singapore does not observe daylight saving time, so no seasonal change is needed, but confirm that the CMS and the players use the same zone name.
• Schedule fallback: if the clock is unknown after boot, the player should show the fallback loop rather than a time-of-day schedule that may be wrong.

Reconnection: what should happen when the CMS returns

Reconnection is where many deployments create their own outage. When a site comes back online, dozens of players may poll the CMS at the same moment. Stagger them, and only replace the cached playlist after the new one has been validated.

1. Retry the CMS every 60 seconds at first, then back off to a maximum of 10 minutes.
2. Add a random delay of 0–120 seconds on reconnection so that a multi-site property does not send all requests in the same second.
3. Download the new playlist and media in full, check the checksums, and only then switch playback.
4. Upload queued heartbeat and playback logs, oldest first.
5. Delete old media only after the new playlist has played successfully for one full cycle.

Step 5 prevents a common fault: a half-downloaded playlist that causes a black screen because the old media was removed too early.

Acceptance tests before handover

Run these tests with the production playlist, not a single test slide. A pass means the display recovers without staff action and the logs show what happened. Keep the test order fixed so that results from different sites can be compared directly.

Record the test results with timestamps and keep them with the handover pack. The same evidence is what a facility team will need after the first real outage, when the supplier may not be on site.

The monitoring side of this design, including alert thresholds for missed heartbeats, is covered in Digital Signage Remote Monitoring and Alerting Checklist. The network and DNS requirements that the player needs to reach the CMS are covered in the engineering note on network, firewall and HTTPS requirements. This note deals with what happens when those dependencies fail.

FAQ

Can a player keep showing a playlist for several days without the CMS?

Yes, if the playlist and all media are cached locally, the valid-until time is set for the content type, and the storage has been sized for the offline window. Without a valid-until time, a player will keep showing expired material, so set the expiry before relying on offline playback.

Does offline playback protect against a power cut?

No. Offline playback covers network loss. A power cut needs a UPS or generator for the player and the display, and the boot sequence must return to the last valid playlist without manual steps. Test both.

What should a player log while it is offline?

Keep heartbeat history, playback records, power events and any errors on the player itself, with timestamps from the local NTP source. Upload them after reconnection, oldest first, and confirm the CMS has accepted them before the local records are cleared.

Visit Prestige Solutions for the wider AV and IPTV service range.

Recommended next step

Contact Prestige Solutions to review your site drawings and current operating pattern. Call +65 8010 2337 or +65 9825 8218, message us on WhatsApp (+65 8010 2337), or email sales@prestigesolutions.com.sg. You can also browse the full product range before the site walk.