US What a digital signage CMS does
A digital signage CMS, or content management system, is the software that controls what appears on a network of signage screens. It is to screens what a website CMS is to web pages: a place to store media, build layouts, decide who can publish and push changes out without touching the hardware.
Most signage CMS products run in a web browser. An operator uploads images, videos and web content, arranges them into playlists, assigns those playlists to individual screens or groups, and sets a schedule. Each screen has a player, either a separate box or a chip built into the display, running the CMS vendor’s player app. The player downloads its content, stores it locally, plays it on time and reports back.
The CMS is the part of a signage system people use every day, so it has more effect on running costs than the hardware. A system that is hard to schedule or slow to update tends to end up showing the same out-of-date loop for months.
Core features of a digital signage CMS
Feature lists vary, but almost every signage CMS is built around the same set of tools.
-
//
Media library and templates. Stores images, video, documents and web pages, with templates so non-designers can produce on-brand content.
-
//
Playlists and loops. Content is arranged into a playlist that repeats in a loop, each item showing for a set time.
-
//
Layouts and zones. One screen can be split into zones, for example a video, a news ticker and a clock, each running its own playlist.
-
//
Scheduling and dayparting. Content switches automatically by time, day or date, such as breakfast and lunch menus or a weekend promotion.
-
//
Screen groups and user roles. Screens are grouped by site, region or purpose, and users get permission to publish only to their own groups, often with an approval step.
-
//
Data feeds and integrations. Live data such as menus, prices, transport times, production figures, calendars, social feeds and emergency alerts can be pulled in automatically.
-
//
Proof of play and monitoring. Logs show what played where and when, and screen health dashboards show which players are offline, with screenshots and remote restart.
Cloud vs on-premises signage CMS
The biggest architectural choice is where the CMS runs. Cloud software is now the usual choice, but on-premises and hybrid set-ups still suit secure and isolated networks.
| Deployment | Where it runs | Strengths | Watch out for | Suits |
|---|---|---|---|---|
| Cloud (SaaS) | Vendor’s servers, accessed by browser | Quick to start, updates handled by the vendor, easy multi-site control | Needs outbound internet from every player; per-screen subscription | Retail, hospitality, offices, small networks |
| On-premises server | Your own server or virtual machine | Content and data stay on site; works on closed networks | You maintain the server, backups and updates | Defense, healthcare, factories, secure sites |
| Hybrid or edge cache | Cloud CMS with a local cache server | Large files download once per site, saving bandwidth | More parts to manage | Large sites with many screens |
| Standalone or USB | No CMS; content loaded by hand | Simple and cheap for one screen | No scheduling, monitoring or remote updates | A single screen with fixed content |
Open-source CMS projects can be self-hosted on-premises or in a private cloud. They avoid a per-screen license but move the work of hosting, updating and supporting the software onto your own team.
How the CMS works with the player
A CMS is only as good as its support for the player at each screen. Every vendor publishes a list of supported player operating systems, typically Android, Windows, Linux, ChromeOS and the system-on-chip players built into commercial displays. Some also support Raspberry Pi. Choosing the CMS first and the hardware second avoids buying players the software will not run on.
Our digital signage players cover Android players on Rockchip processors and Intel and AMD players that run Windows or Linux. OPS computers slot into the back of a compatible display, so the CMS player app runs inside the screen with no separate box. For interactive content, Android panel PCs combine touchscreen and player in one housing.
Players download content in the background and play from local storage, so the screen keeps running if the connection drops. Before roll-out, check that the network allows the ports and web addresses the CMS needs, and whether the player supports proxy servers and secure network login such as 802.1X.
CMS vs device management
A signage CMS manages content, and most can restart the player app or reboot the device. It cannot fix a player that has frozen, lost its operating system or dropped off the network, because the player app is not running. That is the job of device management: mobile device management (MDM) for Android players, and out-of-band tools for x86 players, such as Intel vPro or our guide to managing industrial PCs out of band with Allxon. Large networks normally run both.
Quick answers on digital signage CMS
Digital signage CMS: common questions
Is there a free digital signage CMS?
Yes, with limits. Open-source projects are free to self-host, and many commercial vendors offer free plans for one or two screens. Free options usually limit screen count, support or features such as user roles and reporting.
What is a loop playlist in digital signage?
A sequence that repeats. A loop playlist is a set of content items, each shown for a fixed time, that plays from start to finish and then starts again until the schedule changes.
What is the difference between digital signage software and a CMS?
Mostly naming. Digital signage software usually means the whole package: the CMS where content is managed plus the player app on each screen. The CMS is the management side.
Can one CMS run different players?
Usually. Most commercial CMS products support several operating systems, so Android and Windows players can sit in one network. Check each player model against the vendor’s supported hardware list.
Does a digital signage CMS work offline?
The players do. Content is cached on each player, so screens keep playing through an outage. New content and reports wait until the connection returns.
We supply signage players with the operating system and your CMS vendor’s player app installed and tested as standard, so each screen is ready to pair with your account when it is connected.