Updating 3 to 5 screens is a walk-time decision. If one round trip on foot covers every screen in under 15 minutes and you publish monthly, offline players with a card or USB swap are the simplest answer, with no subscription. Past about 4 screens, weekly updates, or locked rooms, sync players over your LAN or move to a cloud CMS, and keep the MP4 loop either way.
You built the pilot the simple way: a slide deck exported to MP4, playing full screen on a Windows kiosk. It works, and the marketing team likes it. Adding screens changes one thing: the update. With one screen you walk over; with five, you need a plan. There are three plans: swap a card or USB stick at each screen, sync players over your LAN from a small server you run, or put the fleet on a cloud CMS (a hosted content management system) with a per-screen subscription. The choice comes down to walk time and screen count. If one round trip on foot reaches every screen in under 15 minutes and you publish monthly, keep swapping cards. Past about 4 screens, weekly updates, or rooms you cannot walk into on demand, manage the players over the network. Whichever you pick, keep the MP4 loop; it plays on everything.
The three ways to update a small fleet
Card or USB swap. The loop lives on removable storage. Load it at your desk, walk the route, swap at each screen. The screen needs no network at all. Our player is built for this: it plays images and MP4 from microSD or USB, keeps a copy in internal memory so the loop keeps playing while the card is out, and a hidden PIN-protected menu lets site staff reload the card or check the screen without opening the case. After a power cut it starts by itself and brings the show up full screen, and if the app stops it is designed to restart within seconds.
LAN sync. A small server, any PC or NAS on the same network that stays powered during business hours, holds the current files. Players pull a playlist from it on a timer. Our player is designed to pull one over HTTPS from your own web server, with nothing to subscribe to. Copy the new loop to the server once, and every screen collects it on its next check.
Cloud CMS. A vendor runs the server. You log in from a browser, assign a playlist to each screen, and the players fetch content over the internet. You pay a per-screen subscription. In exchange, the marketing team can publish without a ticket to you, and schedules get richer.
If you are still choosing hardware for the screens themselves, the guide on how to choose a digital signage player covers the basics; this page stays on the update path.
One separation worth making: all three paths update content. Patching each player's own operating system is a separate chore; with fewer than 10 units, a sheet of models and locations and a manual pass each quarter does the job.
Side by side
| Card or USB swap | LAN sync | Cloud CMS | |
|---|---|---|---|
| Network at the screen | None | Your LAN | Internet |
| Who walks | You, every update | Nobody | Nobody |
| Update from | Your desk, then the route | Any PC on the LAN | Any browser |
| Subscription | None | None, self-hosted | Per screen |
| Different content per screen | Yes, one card each | Yes, one playlist per player | Yes, one playlist per screen |
| Schedule control | Daily on and off times | Daily on and off times | Typically full time-of-day schedules |
| Formats | H.264 MP4, JPG, PNG, WebP | Same | MP4 works across CMS products |
| Best fit | Up to 4 screens within one 15-minute walk | 4 to 10 screens on one network | 8 to 10 screens or more, or several sites |
Where each path wins
Card swap wins when the campus is compact. A round trip that reaches every screen in under 15 minutes means a monthly update takes 3 hours a year of walking (15 minutes x 12 updates). That is a coffee break a month, for screens in public spots such as lobbies and entrances where anyone on staff can reach the player.
LAN sync wins when updates speed up or the walk grows. Weekly card runs at 20 minutes each take about 17 hours a year (20 x 52). Screens in locked rooms, store cupboards or meeting rooms that you cannot enter on demand push the same way, and the LAN reaches them even when you cannot. A screen with power but no network drop can still take updates over a phone hotspot. Two identical screens hung side by side are one update, not two: one signage player can drive several displays.
Cloud CMS wins when the fleet outgrows one campus network or one gatekeeper. The broader offline-versus-cloud tradeoff has its own guide, Offline or cloud signage: how to choose; the short version for a fleet of 8 to 10 screens or several buildings is that a hosted service earns its subscription, especially when marketing must publish from their own browsers. For how the software market splits into freemium, open source and DIY, see free digital signage software: freemium, open source or DIY.
One honest limit: our player sets a daily on time and off time and has no dayparting, so one loop plays all day. If content must change by hour, a full CMS is the right tool.
Example: four screens, one 300 MB loop
Scenario: a campus lobby, two corridor walls and the canteen, four screens in all. Content is a 300 MB H.264 MP4 exported at 1920 x 1080. Marketing revises the deck about once a month.
Card route: the walking loop past all four screens takes 12 minutes. Each stop takes 2 minutes to swap storage and confirm the first slide, so 4 x 2 = 8 minutes. One update takes 20 minutes; twelve a year take 4 hours (20 x 12 = 240 minutes). Prep adds a copy of 300 MB onto the card, about 10 seconds at the 30 MB/s a USB 2.0 port sustains (300 / 30 = 10), so call the job 20 minutes all in.
LAN route: copy the same 300 MB file to the server once. On a 100 Mbps switch port that is 24 seconds of wire time (300 MB x 8 = 2400 Mbit; 2400 / 100 = 24 s), and a real copy lands under a minute. Each player pulls the playlist on its timer; hourly is a sensible example interval, so every screen has the new loop within the hour, with no walking. The first update still deserves a walk to confirm; after that, trust it and spot-check.
Cloud route: nothing to host, no walking, a per-screen subscription. The same file lands the same way.
Decision for this campus: 4 screens, a 12-minute round trip, monthly updates, so swap cards. The same campus at 7 screens, or with weekly updates, moves to LAN sync.
Keep the MP4 pipeline
The conversion step you already run is the right one. Your slide software exports a deck to video through its export menu; check its own documentation for the exact path. Keep the export as H.264 MP4: H.265 and VP9 playback depends on the unit, so H.264 is the safe choice, and it is what we recommend for our player. Still images play as JPG, PNG or WebP. PowerPoint files, PDFs, HEIC and GIF do not play on our player, so the export stays part of the workflow.
Render at the screen's native resolution. A 1920 x 1080 loop fills a 1080p panel edge to edge; a size mismatch shows up as the loop shrunk into one corner, which has its own fix. Set the transition while you are in there: slides crossfade by default, the fade runs up to 5 seconds, or cut hard.
The decision
Recommendation: keep the MP4 loop, and choose the update path by walk time. With 3 or 4 screens that one round trip covers in under 15 minutes, updated monthly or less, run offline players and swap the card or USB stick; our player plays the loop from the card, costs no subscription and is designed to come back on its own after a power cut. From about 4 screens, or once updates go weekly or the round trip passes 15 minutes, put a small server on the LAN and let the players sync on a timer. Move to a cloud CMS at 8 to 10 screens, across several buildings, or when the marketing team must publish from their own browsers.
That reads as three cases:
- Screens inside one 15-minute walk, monthly content: card swap, no network needed at the screen.
- Weekly updates, a round trip past 15 minutes, or locked rooms that sit on the LAN: self-hosted sync on a timer.
- 8 to 10 screens, several sites, time-of-day schedules or marketing self-service: a cloud CMS.
Year two: if the plan adds another 3 to 5 screens, decide again at about 8. Past that point one walk no longer covers the fleet, and the LAN path or a hosted service stops being optional.
Questions
Is this about updating content or managing the devices?
Content. The three paths above publish new loops and playlists to the screens. Patching each player's own operating system is a separate job. With fewer than 10 units, keep a sheet of models, locations and admin credentials, and update the players by hand during a scheduled off window.
Why does my exported MP4 play with no sound?
Our player ships with video muted unless you turn sound on in the settings. For lobby and corridor loops that is usually what you want. If the loop carries narration or music, enable sound in the player settings and check that the screen or its audio output has its volume set.
Can one player feed two identical screens?
For identical content on two nearby screens, yes. An HDMI splitter sends one player's output to both, and a passive HDMI run at 1920 x 1080 is dependable to about 15 m in practice. Where content differs per screen, each screen needs its own player: one card per screen on the card route, one playlist per player with sync.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.