Digital signage health check: a 20-point checklist for hardware, software and content
Quick answer: DigitalSignage.com recommends a quarterly health check of 20 points in five groups: players (status, storage, temperature, load, version), displays (brightness, image retention, dead pixels and cables, timers), network (wiring, firewall, bandwidth), content (expired promotions, wrong prices, dead web pages, fallback, readability) and accounts (users, authentication, alerts). Most of it is read from the SignStudio Screens dashboard, which shows each DigitalSignage.com SignPlayer's status, last seen time, resources and version, and lets you take a screenshot, restart, reboot, refresh or clear the cache. The rest takes one walk past the screens. Budget about 30 minutes per site.
Last updated October 22, 2026. Sources: SignStudio player management, remote monitoring, screen burn prevention, display calibration, network requirements, scheduling and user management pages on this site.
How to run it
Once a quarter, open the Screens dashboard on a laptop and walk the site with the checklist. Read the dashboard first, since it covers 12 of the 20 points without leaving your desk, then check the physical screens, then the content, then the account. Record a pass or fail per point and fix fails in the order given in the last section. Alert thresholds below are the ones our player management page documents.
Players (5 points)
| # | Check | Pass when | Where to look | When it fails |
|---|---|---|---|---|
| 1 | Online and checking in | Status online, last seen within minutes, current content listed | Screens dashboard | Check power and network, send Restart Player, then Reboot Device; a player that answers nothing needs a power cycle on site |
| 2 | Storage | More than 10 percent free | Resource monitoring per player | Send Clear Cache, remove retired campaigns from the account, or fit a larger card or SSD |
| 3 | Temperature | Below 70 C; a Raspberry Pi throttles above 80 C | Resource monitoring; the Pi reports CPU temperature through SignService | Move the player away from the back of the panel, add a cooling case or fan, clear vents |
| 4 | Load | CPU under 80 percent and memory under 85 percent sustained | Resource monitoring | Simplify the layout, reduce zones or video bitrate, schedule a nightly restart |
| 5 | Player version and updates | All players on the current version, or on a staged rollout you planned | Player version on the dashboard; Update Software command | Push the update to one test player, then the rest; check the device OS still receives security updates |
Take a screenshot of every screen during the check and compare it with what the campaign should show. A screenshot that looks right while the panel on site is dark points at the display, not the player.
Displays (4 points)
| # | Check | Pass when | Where to look | When it fails |
|---|---|---|---|---|
| 6 | Brightness and color | The panel looks as bright and as neutral as its neighbors and as it did at install; a window screen is still readable at the brightest hour | On site, with a phone photo for comparison with last quarter | Panels lose brightness over their rated hours: raise the backlight within its range, recalibrate, or plan the replacement; the display calibration guide has the method |
| 7 | Image retention and burn-in | No ghost of a logo, ticker bar or menu grid visible on a plain gray scene | On site, with a full-screen gray test image | Add a pixel-shift or screen-saver scene at night, move static elements, lower brightness; see screen burn prevention |
| 8 | Dead pixels, cables and input | No dead pixel clusters, no flicker, no handshake drops, correct input selected | On site; compare with the remote screenshot | Reseat or replace the HDMI cable, lock the input, replace a failing panel |
| 9 | Power timers and CEC | The panel wakes on the right input before opening and sleeps after closing; nothing switches input by itself | The display menu | Fix the on and off timer, disable HDMI-CEC (Anynet+, Bravia Sync, SimpLink) unless you rely on it, lock the input |
Network (3 points)
| # | Check | Pass when | Where to look | When it fails |
|---|---|---|---|---|
| 10 | Connection type | Wired Ethernet wherever a cable can run; Wi-Fi only with a strong signal and power saving off | On site, and the IP address shown on the dashboard | Run a cable or add an access point; on a Raspberry Pi turn off Wi-Fi power saving |
| 11 | Firewall and DNS | Outbound TCP 443 to *.signage.me, DNS on 53 and NTP on UDP 123 allowed; nothing inbound needed | The network requirements page, your firewall rules, the player's online status | Add the outbound rules; a blocked NTP port shows up as content playing at the wrong time |
| 12 | Bandwidth and sync timing | Large updates finish overnight; no player shows syncing for hours | Dashboard status and last sync | Schedule big campaigns to publish off-peak, lower video bitrates, stagger updates across sites |
Content (5 points)
| # | Check | Pass when | Where to look | When it fails |
|---|---|---|---|---|
| 13 | Expired promotions | No campaign running past its intended date; every promotion has an end date | The campaign calendar view, filtered by screen group | Set end dates on everything; give playlist items their own validity dates |
| 14 | Prices and facts | Prices, hours and names on screen match the source of truth | A screenshot against the price list or the Google Sheet that feeds the zone | Correct the sheet or scene; move hand-typed prices to a Google Sheet so one edit reaches every screen |
| 15 | Live zones | Web Page, RSS, social and data zones show current data, not a blank, an error or a sign-in page | Screenshots of every screen with a live zone | Fix the URL or feed, set a sensible refresh interval, keep a cached fallback image in the zone |
| 16 | Fallback content | Every screen has a low-priority default campaign with no end date | Campaign assignments per screen | Create one evergreen default campaign and assign it to all screens, so nothing is ever blank |
| 17 | Loop and readability | Items run 7 to 15 seconds, the loop is under 3 to 5 minutes where people pass, text is about 1 inch tall per 10 feet of viewing distance | On site, from where viewers stand | Shorten the loop, enlarge type, remove zones; the typography guide has the sizes |
Accounts (3 points)
| # | Check | Pass when | Where to look | When it fails |
|---|---|---|---|---|
| 18 | Users and roles | Every login belongs to a current person with the least role they need; nobody shares a password | Settings, Users | Deactivate leavers, downgrade over-privileged users, scope store managers to their own screens; the user management page recommends a quarterly review |
| 19 | Authentication | Strong passwords and multi-factor authentication for every administrator; SSO where the organization has it | Security settings; ask support if you cannot find the current MFA options | Enable MFA, rotate any shared or old credentials and API keys |
| 20 | Alerts and recipients | Offline, failed sync, low storage and high temperature alerts go to someone who can act, on site as well as in IT | Alert settings | Add recipients, pick email, SMS, webhook, Slack or in-app delivery, and test one alert by unplugging a player |
A 30-minute routine per site
- Open the Screens dashboard, sort by status, and clear points 1 to 5 for every screen; screenshot each one.
- Walk the site with the screenshots on a phone and clear points 6 to 9, taking a photo of every panel for next quarter's comparison.
- Confirm points 10 to 12 with the IT contact or the firewall rules.
- Open the campaign calendar and clear points 13 to 17, checking one price against the source and one live zone against its feed.
- Open the user list and alert settings and clear points 18 to 20.
- Fix fails in this order: anything dark or offline, anything wrong on screen, then hardware wear, then account hygiene.
When a check fails: the order of fixes
| Fail | First action | If that does not fix it |
|---|---|---|
| Offline player | Restart Player, then Reboot Device from the dashboard | Power cycle on site, check cable, firewall and DNS, then support |
| Dark panel with a correct screenshot | Check the input, HDMI cable, display timers and CEC | Swap the cable, then the panel |
| Old or wrong content | Refresh Content, then check the campaign assignment, dates and priority, then the player's time zone | Clear Cache and republish |
| Blank live zone | Open the URL or feed on a laptop; fix the source or the sign-in requirement | Replace the zone with cached media and a fallback |
| High temperature or storage | Clear Cache, nightly restart, cooling | Larger storage or a commercial player |
For anything the dashboard does not explain, ask support at support@digitalsignage.com, live chat at https://chat.digitalsignage.com/ or +1-877-344-7446 with the screen name, player version and a screenshot.
Frequently asked questions
Digital signage health check: what is in a 20-point checklist for hardware, software and content?
Five groups: players (online status, storage, temperature, load, version), displays (brightness, image retention, dead pixels and cables, power timers and CEC), network (wiring, firewall and DNS, bandwidth), content (expired promotions, prices, live zones, fallback campaign, loop and readability) and accounts (users and roles, authentication, alert recipients). Twelve of the twenty are read from the SignStudio Screens dashboard; the rest take one walk past the screens.
How often should digital signage be checked?
Daily, a glance at the Screens dashboard for offline or warning players; weekly, a screenshot of each customer-facing screen; quarterly, the full 20-point check with a walk past every panel. The quarterly check catches slow faults such as fading panels, full storage, expired promotions and logins that belong to people who have left.
What player health metrics matter most?
Online status and last check-in, free storage (alert below 10 percent), temperature (alert above 70 C), sustained CPU above 80 percent or memory above 85 percent, and the player version. The SignStudio dashboard shows all of them per player and can alert by email, SMS, webhook or Slack when one crosses a threshold.
How do I check that the right content is playing without visiting the site?
Take a remote screenshot from the Screens dashboard and compare it with the campaign. Check the campaign calendar for expired or overlapping campaigns, compare one price on screen with the Google Sheet or price list that feeds it, and open each live web page or feed on a laptop to see that it still loads without a sign-in.
What should I check on the display itself?
Brightness and color against a photo from the previous check, image retention on a plain gray scene, dead pixels, flicker or handshake drops that point at an HDMI cable, the selected input, and the panel's on and off timers and HDMI-CEC setting. A screenshot that is correct while the panel is dark means the fault is in the display chain, not the player.
What do I do when a player fails the check?
In order: Restart Player, then Reboot Device from the dashboard; if it stays offline, power cycle on site and check the cable, firewall rules for outbound port 443 and DNS. For content faults, Refresh Content, then check campaign assignment, dates, priority and the player's time zone, then Clear Cache and republish. Collect the screen name, player version and a screenshot before contacting support.
Related guides
- SignStudio player management
- Remote monitoring best practices
- SignPlayer status, screenshots and logs
- Screen burn prevention
- Display calibration guide
- SignStudio user management
Try it on your own screens, free
DigitalSignage.com, which publishes this guide, runs a permanent free plan: the first 3 screens are free forever (no credit card, no ads, no watermark, no time limit), then from $3 per screen per month on Plus+. Once an account has 4 or more screens, every screen is billed, so 10 screens cost $360 a year; Enterprise is priced per screen in the public price calculator. The free DigitalSignage.com SignPlayer runs on Windows, Mac, Android and Android TV, Chrome OS, Raspberry Pi, iPad or any modern web browser, so the hardware you already own usually works. Start free · 2026 pricing · How 11 vendors compare on price
Maintained by MediaSignage Inc., operator of DigitalSignage.com since 2006. Product behavior on this page comes from our own SignStudio and SignPlayer documentation; where we do not document a step, this page says so instead of guessing. Last reviewed October 22, 2026.