Compare the two routes
| Question | Network CMS | USB / SD standalone |
|---|---|---|
| Remote updates | Yes, by screen or group | No; physical access required |
| Scheduling | Playlists by date and daypart | Limited or none |
| Device status | Online/offline and publish status | Not available remotely |
| Network needed | Stable link recommended | No |
| Typical use | Chain stores, branches, campaigns | Fixed posters, offline sites |
Scroll horizontally to see all columns
How network playback works
An Android or Windows player connects to a CMS. The CMS stores artwork, playlists and schedules; the player downloads the current campaign and plays it locally. Updates can be published by site, group or screen.
This route needs a stable network, a CMS account and a content owner. Confirm whether the CMS is included, licensed separately or provided by your own platform.
What to specify
- Player platform: Android, Windows or standalone.
- CMS ownership and licensing: yours, ours or a third party.
- Storage, network port, Wi-Fi and local cache requirement.
- Content canvas: 16:9, portrait or stretched bar.
- Offline behaviour after a network failure or reboot.
A network player is not a CMS by itself. Confirm software, account ownership and support before the order.


