Pick a player with a documented local-network mode: its free desktop software publishes the finished show straight to the player's IP address, with no cloud account. One HDMI output split to seven screens shows the same slide deck everywhere; a 1-in-8-out powered splitter covers seven screens with one spare. Our panel-mount players also pull a playlist from your own web server on a timer.
Buy the player whose documentation says it takes updates on the LAN: switch it to its local-network mode once, and its free desktop software publishes the show to the player's IP address, for example 192.168.1.50, with no cloud account. One publish moves a new deck from any PC on your network to the player, while the screens keep playing whatever the internet is doing. For one building, that documented LAN mode plus playback that survives a pulled network cable are the two features that decide the purchase. This article sets out the four things that decide the choice, compares the options, works the splitter math for seven screens on one 1-in-8-out powered HDMI splitter, and covers the PowerPoint export. The offline-versus-cloud basics sit in our guide to offline or cloud signage.
What decides the choice
No standard governs how a signage player takes updates, so the method is always one maker's documented feature. Four things decide whether a model fits the building.
A documented local-network mode. Several makers document one: switch the player to LAN mode once, and their free desktop software publishes the show to that address on your switch. No account, no subscription, nothing past your firewall. If the maker's documentation covers only the cloud path, keep shopping. The same push pattern appears elsewhere in a building; a knowledge-base page on signage updates in push mode shows control software feeding a screen that way.
Playback that survives the network. The show and its files have to live on the player. Our panel-mount players play JPG, PNG and WebP images and MP4, M4V and WebM video from microSD or USB, and keep a copy of the show in internal memory, so the screens carry on when the card comes out. The network then only carries new shows.
Files you can produce. PowerPoint files do not play on the player itself; slides cross as images or video, with H.264 MP4 the recommended video form, since H.265 and VP9 playback depends on the unit. That is a check on the workflow, not on the LAN feature.
One HDMI output. Our units have one HDMI port and it is an output, made to feed a screen or a splitter. Rotation is one setting, so the same unit hangs portrait or landscape if a screen is mounted that way.
The options compared
| Option | How updates land | Fits when | The trade-off |
|---|---|---|---|
| Player with vendor LAN software | Free desktop software publishes the show to the player's IP address, no account | 1 to 8 screens, one building, one editor | The software drives only that maker's players |
| On-premise content server | Players pull their playlists from a server in your rack | 10 or more screens, several buildings, several editors, per-screen schedules | You patch, back up and power that server |
| Android player with a CMS app | The app pulls from a server you point it at | IT already runs a content system | Confirm the app keeps playing with the network down |
| Our panel-mount player | Pulls a playlist from your own web server on a timer, or takes a memory card or USB stick | One screen or one split, LAN-only updates, nothing new to run | The schedule is one daily on time and off time |
| Memory card or USB walk-up | Show written to the card; the player keeps a copy internally | Updates monthly or less | Someone walks to the screen each update |
Rows one to three are product categories to shop across makers. Rows four and five are the paths our own catalog documents.
Example: feeding seven screens from one HDMI output
The case is the one-input split: seven screens fed VGA across a building, all driven by one player. The example takes seven screens, the larger count of the pair. Inputs: one HDMI output on the player, documented on our panel-mount units; seven existing VGA screens that stay on the wall; common powered splitter sizes step 2, 4, 8 and 16 outputs.
Rule in words: one output feeds any number of screens that all show the same thing, through a powered 1-in-N-out splitter. Buy either a splitter that converts HDMI to VGA inside, or a plain HDMI splitter with one HDMI-to-VGA converter on each screen output.
Arithmetic: outputs needed = 7. The first common size at or above 7 is 8. Spare ports = 8 - 7 = 1.
Result: one 1-in-8-out powered splitter covers the building with one port spare.
Decision: at 8 screens or fewer, all showing the same deck, one player and one splitter finish the job. A ninth screen takes the spare port, and a second splitter fed from that port covers the ones after it. The first screen that must show its own content ends the split model; from that point it is one player per screen, and that article works the choice for four screens.
Getting the PowerPoint slides onto the player
The player plays files, so the deck becomes files first. Two routes.
Export it yourself. The presentation software saves the deck as JPG or PNG images, or as MP4 video. Keep video at H.264 MP4, Full HD, 1920 x 1080, 30 frames per second. A deck of H.265 or VP9 files is the usual story behind a signage player showing a black screen on video.
Hand the file to IMD Signage Studio. IMD Signage Studio is our free Windows app, no subscription and no account, on Windows 10 and 11 64-bit. It takes a PowerPoint file straight in: the deck is saved as PDF first and each page becomes a slide, up to 200 pages. Video the screen cannot play is converted on the computer to H.264 MP4, at most Full HD and 30 frames a second. Watch it plays the show back with its real timings before anything ships.
The show goes to a memory card or USB stick, where every file is read back and checked and the card is made safe to take out. It can also go over the internet, where the free online service allows 25 screens, 200 MB of files in all, one file up to 25 MB, and each screen checks every 2 minutes; that is the cloud path you are declining, and the card path needs none of it. Shows made in Studio run on IMD Signage displays with IMD Signage Player 1.1.0 or newer.
Since the split shows every screen the same slide, set the type for the farthest viewer. The FHWA planning figure is 30 ft of viewing distance per inch of capital height; 20 ft per inch is the safer figure for fast reading, and line spacing runs at 1.7 x the capital height. A headline meant to read across a 30 ft lobby needs 1 in capitals, or 1.5 in at the safer figure.
Cabling the run from the player to the screens
Keep the HDMI leg short: player to splitter is typically 1 to 2 m. Passive HDMI at 1080p is dependable to about 15 m, or 50 ft, and past that an active cable carries it. Let VGA take the long legs. On decent coax VGA cable, 1280 x 1024, a common resolution for building screens, holds a clean picture past 30 m; at 1920 x 1080 over VGA, plan on 10 m as the working limit. A poor cable halves both numbers.
Count the power on install day. A splitter that outputs VGA directly needs one adapter of its own; a plain HDMI splitter plus seven converters needs eight, so plan the outlets before the ladder goes up.
One safety rule on the cable itself: any new run through ceiling voids that move air must be plenum-rated cable, which the electrical code for those spaces requires, and the electrical inspector on the job enforces it.
When an on-premise server earns its keep
Past about ten screens, or across two buildings, per-player software turns into clerical work: no shared media library, no user accounts, no record of which screen got which show. An on-premise content system runs on a server in your rack, players pull their playlists from it on a schedule, and nothing leaves your network. You take on the patching and backups for that server.
Our player has a pull path of its own for the small version of this: it pulls a playlist from your own web server on a timer. Put that server on the same switch and updates never leave the building. The player's schedule is one daily on time and one off time; anything richer belongs to a content system. If a content system is already running, an Android player pointed at it is the light version, and choosing an Android signage app for a remote screen walks through that pick. Where the content barely moves, the walk-up model wins on simplicity; USB photo playback or cloud software for a review board works through that comparison.
What to ask before you buy
- Is the local-network mode in the manual, and does the desktop software publish to the player's IP address with no account? Ask for the page it is documented on.
- Which port does the player listen on for publishes, and for its browser page if it has one? One known port means one firewall rule.
- Does the player keep playing its current show with the network down, and is it designed to start again on its own after a power cut?
- Which file formats does it take, and does PowerPoint need exporting first?
- Is the HDMI port an output the maker supports splitting to seven screens?
- How does the player get its address, and does a router reservation keep that address stable?
Recommendation
Recommendation: For one building and up to eight screens all showing the same deck, buy a player with a documented LAN mode whose free desktop software publishes to the player's IP address, and run one 1-in-8-out powered splitter with VGA outputs. If updates land monthly or less, our panel-mount player fed from a USB stick prepared in IMD Signage Studio does the whole job with the network out of it. When a screen needs its own content, or the count passes eight, move to one player per screen or an on-premise server; for one screen on the LAN, our player pulling from your own web server needs no new software at all.
Questions
Does the signage player need a static IP address?
No. Let the router hand out addresses by DHCP and reserve one for the player in its DHCP table. A reserved address behaves like a static one: the desktop software finds the player at the same IP on every publish, and a replaced player inherits the reservation with nothing typed into its settings. Typing a fixed address into the player works too, but it is easier to get wrong.
Does a PC have to stay on for updates to reach the player?
Only in the pull model. Desktop software that pushes sends the show when you click publish, so the PC can be off the rest of the time. A player pulling a playlist from a web server needs that server running whenever you expect updates to land; the screens keep playing the show they already have either way. Card and USB updates need nothing on the network at all.
What happens to the show after a power cut?
On our panel-mount players the show is designed to come back with no one in the room: set up as the home app, the player brings the show up full screen at power-on, and if the app stops it is designed to start again within seconds. Set a daily on time and off time so the screens sleep at night; outside those hours the player shows black at minimum brightness, because the app cannot switch the backlight off.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.