The player is the small computer that turns a screen into a sign. Get it right and the screen runs for years and you forget it exists. Get it wrong and you spend every Monday morning walking round the building unplugging things.
This guide covers what a player actually has to do, then compares Android boxes, Raspberry Pi, Windows mini-PCs and displays with a player built in. It also covers the Amazon Fire TV situation, which changed in a way that catches a lot of people out.
What a player must do that a consumer smart TV won’t
The most common first idea is to use the smart TV you already have. Sometimes that works. Usually it does not, for five specific reasons.
24/7 duty cycle. A consumer TV is designed for four to six hours a day. A shop window screen runs twelve to sixteen. A hospital corridor runs continuously. Panels rated for consumer use develop image retention and backlight failure at a rate that makes the €400 you saved look expensive around month eighteen. This applies to the display itself as much as the player.
Auto-start on power. This is the single biggest practical difference. When power is cut and restored, a signage player must boot straight into the content with no button press and no remote. Most consumer TVs come back to a standby light or a home screen and wait for a human. If your screens are on a timer or a circuit breaker, or if the cleaner unplugs one, you need auto-start. Check the setting exists before you buy.
Remote management. You need to see whether a screen is online, from somewhere that is not the room the screen is in. A proper player reports status, last content sync and storage back to the CMS so you know something broke before a customer tells you.
No ads and no UI overlays. Consumer TV platforms increasingly put their own promotional content on the home screen, show notifications over full-screen apps, and pop up “are you still watching” dialogues. Fine at home, unacceptable on a menu board.
Watchdog and recovery. Things crash. A signage player should notice its own playback has stopped and restart, without a person. Consumer devices have no such concept because they assume someone is holding a remote.
There is a sixth: portrait orientation. Many consumer devices will not rotate output at all, and those that do often only rotate the app and not the interface.
Android boxes
The default choice for most deployments, and for good reason.
What is good. Cheap, small, silent, low power, and the software support is broad because almost every signage CMS ships an Android player. Hardware decoding for H.264 and H.265 is standard, so 4K video plays without breaking a sweat on modest silicon. Boot times are short. They mount behind the screen with a bit of double-sided tape or a VESA plate.
What is not. Quality varies enormously. The €35 box from a marketplace listing is running an old Android build with no update path, a chipset the vendor has not supported in three years, and eMMC storage that will wear out. The failure mode is not dramatic, it is a screen that starts stuttering in month seven.
How to choose one. Look for a named SoC from Amlogic or Rockchip that is currently supported, at least 2GB of RAM and 16GB of storage, wired Ethernet as well as Wi-Fi, and an Android version the vendor still updates. Avoid anything sold primarily as a media streaming device for consumers, because the firmware will be tuned for a remote control and a living room.
Our Android player is €499 with a licence included and arrives with the app installed and activated, which is the version of this decision where you do not have to evaluate chipsets. If you would rather use hardware you already have, the app is a free download and the Android setup guide takes about ten minutes.
Raspberry Pi
A genuinely good signage platform with two specific problems in 2026.
What is good. Complete control over the operating system, an enormous community, excellent documentation, real GPIO if you want sensors or buttons, and a boot process you can configure precisely. For technical teams who want to own the whole stack, a Pi running a browser in kiosk mode is a solid, well-understood pattern.
Problem one: it is no longer cheap. Raspberry Pi raised prices on 1 December 2025 because of memory costs. Official list prices are now $45 for 1GB, $55 for 2GB, $70 for 4GB, $95 for 8GB and $145 for 16GB. By the time you add a case, a power supply, a good SD card or SSD, and a micro-HDMI cable, a usable 4GB Pi 5 build lands close to $120. That is no longer obviously cheaper than a purpose-built Android player, and it is a lot more work.
Problem two: SD card wear. Continuous writes kill SD cards. A Pi that has been playing signage for a year on a cheap card will eventually fail to boot, usually at the least convenient moment. Boot from an SSD, or use a high-endurance card and mount your logs to RAM. This is solvable but it is a thing you have to know.
Where a Pi genuinely wins: small deployments run by someone technical, projects needing hardware I/O, and anywhere you want the whole stack to be inspectable open source.
Straight answer on compatibility: easyCMS ships players for Windows, Android and LG webOS. We do not currently ship a Raspberry Pi player, so if the Pi is a hard requirement, we are not your best option and you should look at a CMS that supports it natively.
Windows mini-PC
The heavyweight option, and the right answer more often than its reputation suggests.
What is good. Anything runs on it. Full desktop browsers with every codec, video wall software, LED display control panels like NovaStar LCT, Colorlight or Linsn, dashboards that need a real browser, corporate VPN clients, domain join and group policy. If your IT department already manages Windows endpoints, a Windows player fits their existing tooling instead of being a special case.
Crucially, if you are driving a large LED display and need to control brightness or monitor the panel from the same device, Windows is usually the only option. Android boxes will play content to an LED wall perfectly well but cannot run the manufacturer’s control software.
What is not. More expensive, physically larger, and Windows Update will reboot your screen at an inconvenient moment unless you configure it properly. Fanless industrial units cost more than consumer NUCs but last far longer in a sealed enclosure.
How to choose one. Fanless with a metal chassis acting as a heatsink, an SSD rather than eMMC, a stripped-down Windows install with updates on a controlled schedule, and auto-login plus auto-start configured. Our Windows player setup guide covers the configuration side.
Built-in SoC displays: LG webOS and Samsung Tizen
Commercial displays from LG and Samsung include a player on the panel itself. No box, no extra power supply, no cable, nothing to steal.
What is good. The cleanest installation you can get. One power lead and one network connection. Nothing behind the screen for someone to unplug. The display and the player are a single warranty item, which removes an entire category of argument when something fails. Power scheduling and display settings are integrated properly.
What is not. You are locked to that manufacturer’s platform for the life of the panel. If the SoC turns out to be underpowered for what you want in year three, the fix is a new display rather than a €200 box. App support is narrower than Android, and platform version fragmentation is real: a webOS 4.x panel and a webOS 6.x panel are not the same target.
easyCMS supports LG webOS, and there is a dedicated page on what we support plus a webOS setup guide. We do not currently support Samsung Tizen. If you have already bought Tizen panels, an external Android or Windows player plugged into the HDMI input works fine and is what we would suggest.
The Amazon Fire TV situation in 2026
If you were planning to use Fire TV Sticks as cheap signage players, read this before you order.
Amazon’s newer Fire TV Stick 4K Select does not run the Android-based Fire OS used by every previous Fire TV device. It runs Vega OS, which Amazon built on Linux components. In Amazon’s own developer announcement, the company states plainly: “We adopted Linux components as our foundation.” Apps for Vega are written with React Native for Vega or Vega WebView, not as Android apps (Amazon developer blog, September 2025).
The practical consequence is that Android signage apps do not run on it. As AFTVnews reports, “every existing Fire TV app has to be rewritten, since it no longer runs the Android-based Fire OS used by all previous models”, and the device “does not support sideloaded apps”. Amazon’s answer for major streaming services is Amazon Cloud App Streaming, which runs Android apps in the cloud and streams the interface, but that route is aimed at video streaming services and excludes utility apps.
What this means for you:
- Older Fire TV devices running Android-based Fire OS can sideload an Android signage APK, and many people have done exactly that for years.
- The Fire TV Stick 4K Select and other Vega OS devices cannot, and there is no workaround.
- Because the two look nearly identical in a product listing, check the OS before you buy in bulk.
Our broader advice has not changed: Fire TV sticks were never a good signage platform. They are optimised for a remote control and a living room, the home screen is full of Amazon’s own promotional content, and there is no auto-start-into-app behaviour you can rely on. Vega OS just removes the loophole that made them tempting.
Comparison table
| Option | Typical cost per screen | Ease of setup | Reliability at 24/7 | 4K | Portrait | Best suited to |
|---|---|---|---|---|---|---|
| Purpose-built Android player | €150–€400 | Very easy | High | Yes | Yes | Most deployments, 1 to 500 screens |
| Cheap consumer Android box | €35–€80 | Moderate | Low to medium | Varies | Sometimes | Testing only, not production |
| Raspberry Pi 5 (4GB, built up) | ~$120 in parts | Hard | Medium to high if built well | Yes | Yes | Technical teams, GPIO projects, full OS control |
| Windows mini-PC | €300–€700 | Moderate | Very high if fanless | Yes | Yes | LED walls, dashboards, corporate IT estates |
| LG webOS built-in | Included in panel | Easy | Very high | Yes | Yes | Clean installs, no external box wanted |
| Samsung Tizen built-in | Included in panel | Easy | Very high | Yes | Yes | Same, but not supported by easyCMS |
| Fire TV (Vega OS) | €30–€60 | Not possible | n/a | Yes | No | Nothing. Android signage apps do not run |
| Consumer smart TV app | €0 | Varies | Low | Varies | Rarely | Single screen, low stakes, short term |
Costs are indicative build or purchase costs, not software. Raspberry Pi figures are official list prices as published on 1 December 2025 plus typical accessory costs; check current retail before budgeting.
Duty cycle, heat and mounting
Three things that determine whether a player survives its third year.
Heat is what kills players. Most signage players fail from thermal stress, not component defects. A box in a sealed cabinet behind a screen that is itself producing heat will run hot continuously. Fanless designs with a metal chassis acting as a heatsink handle this better than plastic boxes with a small fan, because the fan is a moving part in a dusty environment and will fail first.
Give it air. Do not tape a player flat against the back of a hot panel. Mount it to the bracket or the wall with a few centimetres of clearance. If it must go in an enclosure, the enclosure needs vents or active cooling. This costs nothing at install time and saves a callout later.
Duty cycle is a spec, so read it. Commercial displays publish a rated daily operating time, typically 16/7 or 24/7. Match it to reality. A screen that is on from 08:00 to 22:00 is a 16-hour duty cycle and a 16/7-rated panel is correct. Do not put a consumer panel on a 16-hour schedule.
Power scheduling matters more than people think. Turning screens off overnight extends panel life, cuts electricity cost and reduces heat load on the player. Every serious signage CMS can schedule this. Use it.
Secure the player physically. In public areas, a box hanging off the back of a screen on an HDMI cable will eventually walk. Use a VESA mounting plate behind the display, or choose a built-in SoC panel where there is nothing to take.
What easyCMS supports, and what we ship
We support three platforms: Windows, Android and LG webOS. That is the honest list. No Raspberry Pi player, no Samsung Tizen.
A licence is €99 one-time and works on any of the three. It is not tied to a platform, so a licence bought for a Windows player can be moved to an Android box later. Details of the whole range are on the players page.
What we sell:
- Android player, €499. Pre-configured, licence included, plug it in and it plays. Full HD and 4K ready, built for 16 to 24-hour use.
- Windows PRO player. Fanless industrial chassis, no moving parts, with NovaStar LCT included by default for LED display control. We can swap in Colorlight, Zdec or Linsn on request.
- Enterprise players at €169 for customers on the Enterprise account, which also drops licences to €49.
Bring your own hardware if you prefer. The Android app is a free download, and setup guides exist for Android, Windows and LG webOS.
How to decide, in one paragraph each
One to ten screens, standard content, no LED wall. Buy purpose-built Android players. It is the cheapest total cost of ownership and the least work.
LED display, video wall, or anything needing brightness control and panel monitoring. Buy Windows. It is the only option that runs the control software.
New displays being purchased anyway, clean install wanted. Buy LG webOS commercial panels and skip the external box entirely.
Technical team, small deployment, wants full control. Raspberry Pi is a legitimate choice, just not with us.
Testing an idea this month. Use whatever Android device is in the drawer, install the app, and decide properly once you know the project is real.
The player is a small share of the total project cost. Our cost per screen guide puts the numbers side by side over five years, and the display almost always dominates. Saving €150 on the player and spending it on a better panel is usually the right trade.
Questions about a specific device or panel model: info@myeasycms.com or +48 509 937 137. Free expert support comes with every account, and telling you a device will not work is part of that.