Back to blog
Technical

Why a screen has to keep working when the internet drops

signagewall3 min read
A blank screen in a shop

Key takeaways

  • The latest snapshot and media can remain local.
  • Network apps do not become offline by joining a playlist.
  • Validate fallback content with a real disconnection test.

“Works offline” is not a single property of an entire digital signage system. It depends on whether the player has already received the content, what was stored locally, and whether an item must contact an external service. That distinction matters: a locally cached image and a public web page can share a playlist but behave differently during the same outage.

What SignageWall stores locally

The player persists its latest received snapshot in local IndexedDB storage. Images and video are prefetched and cached according to player rules, so previously synchronized media can remain available when the connection disappears. A data-backed app may have last successfully prepared data with freshness information, but that does not mean every source continues updating without a network.

Network equipment
Cached media keeps playing offline; Web, YouTube and other network-only apps cannot. · Photo: Pascal 📷 / Pexels

What still needs the internet

Apps marked as network-only are skipped when the player is offline. This includes experiences that load a remote page or service, such as Web, YouTube and Canva. A live stream also has no source without networking. If a rotation contains only those items, the player has no business content it can reliably continue and may show a branded fallback. The claim that a display can never be left without content is therefore not unconditionally true.

Build an offline core

Keep at least one verified local item in every important rotation: an image, supported video or PDF that has already downloaded. Its message should remain useful without current data, such as basic opening information, on-site directions or a contact. Do not use a dynamic price, availability figure or emergency message as a fallback when it may change while the connection is unavailable.

  • The local core should not depend on an iframe page.
  • Time-sensitive data should show when it was last updated.
  • Every network source needs an agreed tolerance for stale data.
  • A responsible person at the site should know how to report an outage.

Test the content you actually publish

  1. Connect the player and allow it to receive the latest snapshot and media.
  2. Review the full rotation while the device is online.
  3. Disconnect networking without switching off the device.
  4. Watch a complete cycle and record which items are skipped.
  5. Restore the connection, edit one item and confirm the new version arrives.

Repeat the test whenever you introduce another app type. Offline behavior is not validated forever because one playlist worked once. Live preview and online state help while a connection is available, but they are not proof-of-play reports and do not establish what appeared throughout an outage. For a critical site, keep a separate operational record of checks.

Do not confuse networking with power

Caching addresses part of a network interruption; it does not power a television and does not guarantee that every hardware model restarts automatically after a power cut. That behavior depends on the display, player device, operating system and player build. Test it separately on the exact model. You then have two clear procedures: one for lost networking and another for lost power, without a blanket promise the real setup may not meet.

Put something on your screens today.

Start free for 21 days with every feature switched on, or get in touch and we will show you how it works in your space.

Start free trial