A Raspberry Pi can run digital signage. It drives a screen over HDMI, and a browser in kiosk mode can show a web-based signage player or a page you built yourself. It makes sense if you enjoy Linux, already have Pis and the skills to look after them, or need something a signage box cannot do, like reacting to a button or a sensor. What it costs is time: the right power supply, SD cards, cooling, operating-system updates, and nobody to call when it stops.
On SignageStack specifically: our web player runs in a browser, and Chromium on a Pi is a browser, but the Raspberry Pi is not a qualified platform. We have not tested it and we do not promise it. For a screen that has to run unattended in a shop or a reception, a small Android box running the SignageStack app is less work.
What a Raspberry Pi signage player actually is
A Raspberry Pi is a small Linux computer on a single board. For signage, people set one up in one of three ways:
- A browser in kiosk mode. The Pi boots, logs in, and opens a browser full-screen on one address: a web-based signage player, a dashboard or a page on your own server. This is the simplest approach, and the one Raspberry Pi describes in its own kiosk tutorial, using Chromium on Raspberry Pi OS.
- A dedicated signage image. Open-source projects and some commercial products ship a ready-made system image for the Pi, with their own player and management.
- A video looper. One file, played on repeat. Fine for a trade-fair stand, not for anything that changes.
The rest of this article is about the first, because that is where the SignageStack web player would sit.
When a Raspberry Pi makes sense for digital signage
- You like building things. Configuring autostart, hiding the cursor and writing a restart script is part of the fun, not a chore.
- You already run Pis. You have spares, a way to reach them remotely, and a routine for updates. One more is a small step.
- The screen reacts to the physical world. A Pi has pins for buttons, sensors and relays. A screen that changes when someone presses a button, or shows a reading from a sensor in the room, is something a Pi does well with your own software.
- Downtime costs nothing. A dashboard in the workshop, a screen in a maker space, a school IT club's own project. If it is dark for a day, nobody loses a sale.
If none of these describes you, and the screen is above a counter or in a waiting room, the time costs below are the reason to choose a box.
What a Pi costs in time
The board is the cheap part. These are the parts that take the evenings.
The power supply
A Raspberry Pi 5 needs 5 V at 5 A, which is Raspberry Pi's own 27 W USB-C supply; a Pi 4 needs 5 V at 3 A, a 15 W supply, according to the official getting-started guide. A phone charger that fits the socket is not necessarily one that delivers this. Buy the official supply, and do not power the Pi from the TV's USB port.
The good news: a Pi boots as soon as power returns, with no button to press. Whether the browser comes back with it depends on how you set up auto-login and autostart.
The SD card
Raspberry Pi OS runs from a microSD card, and the same guide recommends at least 32 GB for the desktop version, which a kiosk browser needs. A card that is written to all day and then loses power mid-write can be corrupted, and a shop whose fuse trips now and then is exactly where that happens. Use a good card, keep a second one imaged and ready in a drawer, or boot from a USB SSD. On a Pi 5 an NVMe drive is possible through the PCIe connector, but it needs a separate M.2 adapter board, as the product page notes.
Heat
Behind a TV, in a warm room, a bare Pi gets hot. Every Raspberry Pi model progressively throttles its processor once the core reaches 80 to 85 °C, according to the Raspberry Pi documentation, and a throttled Pi can stutter on video. Use a case with proper cooling. On a Pi 5 that means the Active Cooler or a case with a fan.
Updates
Raspberry Pi OS and its browser are updated with the system's package manager. Someone has to run those updates, or schedule them and then check that nothing broke. Updates also change how the desktop works: the official kiosk tutorial now sets up autostart through labwc, the window manager in current Raspberry Pi OS, so many older guides describe files that a fresh install no longer uses. Budget an evening the first time you follow an outdated one.
The small things that add up
- Screen blanking. A desktop turns the screen off when nobody uses the mouse. Switch off screen blanking in the Raspberry Pi Configuration tool, or in raspi-config under Display Options.
- Pop-ups and first-run screens. The flags in the official tutorial suppress error dialogs, info bars and Chromium's first-run screen. The tutorial also suggests keeping a USB mouse to hand to dismiss cookie banners before you take the keyboard and mouse away. The mouse pointer is a separate job.
- Sound. Browsers mute video on a page nobody has clicked. For a screen nobody touches, Chromium takes a flag to allow it.
- The cable. Pi 4 and Pi 5 have micro-HDMI ports, so you need the right cable or adapter.
Nobody to call
When a Pi you built stops, there is no vendor. When it stops in a shop across town, you need a way in: SSH, a VPN or a remote-access tool, set up before it breaks, through a router you may not control. The alternative is a drive.
Running the SignageStack web player on a Pi
Here is what we can and cannot say.
What we can say. The web player runs in any current Chrome, Edge, Safari or Firefox. Chromium, the browser in Raspberry Pi OS, is the open-source base of Chrome. You open player.signagestack.com, the player shows a six-character code, and you type it into the dashboard under Add screen. After pairing, the address bar holds that screen's own link. That link is what a kiosk command should open.
What we cannot say. We have not qualified the Raspberry Pi. We have not measured video playback on one, how the offline cache behaves on an SD card, or whether the screen recovers after a power cut. A paired screen reports its status, last-seen time and platform to the dashboard, so you would see when it went quiet, but fixing the Pi is up to you. The SignageStack Android app does not run on Raspberry Pi OS, because it is an Android app. Unofficial Android builds for the Pi exist; we have not tested the app on them and would not build a screen on one.
If you want to try anyway, the line in the labwc autostart file from the official tutorial looks like this, with your screen's saved address in place of the placeholder:
```
chromium <your screen's saved address> --kiosk --noerrdialogs --disable-infobars --no-first-run --autoplay-policy=no-user-gesture-required &
```
The first flags come from Raspberry Pi's tutorial; the autoplay flag is the one our browser player page gives for Chrome. Use a normal browser profile, not a private window, or the cache that keeps a screen playing offline is thrown away at every restart. Try it on one screen before you plan anything bigger.
Raspberry Pi vs Android box: the total effort
| Raspberry Pi with a kiosk browser | Android box with the SignageStack app |
|---|---|---|
What you buy | Board, power supply, case with cooling, SD card or SSD, micro-HDMI cable | A box, usually with its power supply and HDMI cable |
Setup | Flash the OS, auto-login, kiosk autostart, screen blanking, remote access | Install the APK, open it, type the six-character code |
After a power cut | Boots on power; the browser returns if you set it up | The app starts at boot, if the box powers on by itself |
A frozen page | Your script, or a visit | Reload, rebuild, restart, then an offline page that keeps retrying |
Kiosk lock | Browser kiosk flag; a keyboard can leave it | Enforced by Android on Device Owner, screen pinning otherwise |
Updates | OS and browser, when you run them | The app updates itself, checked against a SHA-256 hash |
SignageStack status | Not qualified | Supported; test your model first |
An Android box that does the job typically costs somewhere between €40 and €120. Add up the Pi's parts before you assume it is cheaper: the board is only part of the bill, and the time is not on it at all. The article on Android TV boxes for digital signage covers what to look for, and the one on signage players compares every kind.
The same trade applies to other cheap routes. A Fire TV Stick is not qualified either, and the article on free digital signage software looks at where do-it-yourself setups save money and where they cost it.
Where to start
If you are a tinkerer with a Pi in a drawer, use it to explore: open the web player in Chromium, pair it, and see your content on a screen tonight. If the screen is going above a counter or into a reception, start with the Android app on a box that meets Android 8 and 2 GB of RAM, and keep the Pi for the workshop. The hardware page lists what else to check. The SignageStack trial runs for 21 days with every feature and no card, on whichever device you pair first.
