YOUR CONTENT. ON DISPLAY.
Bring your screen to life.
Choose your device, install AdPlayr, and connect it to your workspace.
AdPlayr for Windows
A dedicated player for your display. No separate browser needed.
Explore menu boards · Explore the three-screen setup
- Up to three independent displays per PC
- Starts automatically after sign-in
- Keeps playing downloaded content offline
- Installs verified updates at startup
Version 0.3.0 · Windows 10 / 11 · 64-bit
Using WebView2 0.1.x? Install this version once to enable automatic updates. Your pairing and saved media are kept.
AdPlayr for Raspberry Pi
A compact player for a dedicated screen. Built for Raspberry Pi 5.
- Starts at desktop login
- Saves your media for offline playback
- Raspberry Pi OS Desktop, 64-bit
Version 0.2.2 · Pi 5 · Desktop with labwc
Physical Pi hardware testing is still pending. Use the Windows player for an established installation.
From download to display
Set up once. Keep playing.- 1
Install on your device
Run setup on the computer connected to your screen.
- 2
Pair your screen
Open Connect a screen on another device and enter the code.
- 3
Choose what plays
Assign a playlist and save. AdPlayr remembers your screen.
Use two or three displays with one PC
Connect your displays and choose Extend these displays in Windows. Open Displays during the player startup countdown, or Display settings from the AdPlayr tray icon. Enable each player screen, choose its monitor and save.
Pair each code separately under Screens and assign its playlist. Each display uses one screen licence. Existing pairing and downloaded content are kept. If a monitor is replaced or its connection changes, select it again in Display settings.
Windows setup and automatic updates
The recommended Windows player uses WebView2. It needs .NET Framework 4.8 and Microsoft’s Evergreen WebView2 Runtime. If the runtime is missing, the app opens Microsoft’s official download page when you choose to install it.
Start with Windows is enabled for new installations. Change it from the AdPlayr tray menu. Existing startup choices are preserved. Windows must sign into the display’s account; the installer does not configure automatic sign-in or power-on.
Each time the app starts, it checks for a signed player update. An available, verified update installs and the app reopens. If offline, paused, or unable to verify an update, it keeps the installed version. A 15-second countdown follows the check; Ctrl + Alt + Q or Cancel startup stops that launch.
WebView2 0.1.x needs one manual installation of this release to gain automatic updates. Pairing and saved media stay in place. Chrome and Firefox installations use separate profiles; switching from either requires pairing the new player. Stop the old player and disable its Windows startup entry before switching.
To stop: press Ctrl + Alt + Q, close the app, or choose Stop all player screens from its tray menu. Windows may show an unknown-publisher warning because the installer is unsigned. Download it directly from this page.
Windows setup checksumRaspberry Pi setup instructions
Use Raspberry Pi 5 with Raspberry Pi OS Desktop (64-bit), labwc and Chromium. Raspberry Pi OS Lite and other signage systems are not supported by this setup.
- Download setup on the Pi. Open a terminal in the download folder and run
python3 AdPlayr-Pi-Setup.pyas your normal user, without sudo. - Enable desktop auto login and disable screen blanking in Raspberry Pi settings. Disable the previous signage app’s startup before using AdPlayr.
- Open AdPlayr Player from the applications menu, pair the code from another device, and assign a playlist.
- Use 1080p H.264 MP4 videos initially and test sound on the connected screen. Restart to check automatic playback.
The Pi checks for verified updates each time it starts. If a check fails, the current player opens. Run setup once to upgrade older installations; pairing and saved media are kept.
To stop: press Alt + F4. Remove startup with python3 ~/.local/share/adplayr-pi/player.py uninstall. Pairing and cached media are kept.
How offline playback works
Keep the device online until Player status confirms the content is saved. Downloaded media can play for up to 72 hours without internet, or until access ends if sooner. Storage supports up to 2 GB per screen and needs enough free disk space.
Pairing and content are stored on the device. Do not clear its player profile. New content, remote changes and player updates need an internet connection. The offline indicator appears while downloaded content continues playing.
Other Windows players and older computers
Chrome player: available for existing setups that need it. Requires Windows 10/11 x64 and Google Chrome. This is a separate installation from the recommended WebView2 app.
Download Chrome player 0.5.4Firefox compatibility player: an experimental option for Windows 7 SP1 and 8.1 with .NET Framework 4.8 and Firefox 115 ESR. Windows 7 remains out of support. Application updates are manual; compatibility is not guaranteed.
Download Firefox player 0.4.6Stop other players before launching either alternative. Your existing profiles are kept. See Mozilla’s instructions for the appropriate Firefox version.
SET UP ONCE. KEEP PLAYING.
Player setup tips
A few practical steps for screens that need to run unattended. Open a topic for the details.
Can one PC run three different playlists?
Yes. The recommended Windows player supports up to three independent displays. Use Extend these displays in Windows, open AdPlayr Display settings, and pair each display separately. Each can have its own playlist and schedule.
Use a compatible Windows 10 or 11 PC that supports three simultaneous display outputs. An ordinary HDMI splitter mirrors content. Test your actual displays and videos before rollout; performance depends on the PC, resolution and content.
How do I keep a menu board on screen all day?
Publish your menu board, add it to a playlist using Add content → Add menu board, then assign that playlist to a screen. With only one eligible still item, playback stays on that item without repeated transitions. Schedules and access limits still apply.
Windows or Raspberry Pi: which should I choose?
Our recommendation for now: start with Windows 11. AdPlayr’s Windows app includes playback recovery and keeps the computer awake while running. Use a dedicated display computer and test your actual videos before rollout.
Raspberry Pi 5 is an option for a single-screen pilot. Use Raspberry Pi OS Desktop (64-bit), labwc and Chromium. The current Pi player starts at desktop login and relaunches Chromium after a crash. It cannot yet detect a frozen browser that is still running. Hardware and extended playback testing are still pending, so we would not choose it yet for a hard-to-reach, unattended installation.
Neither player is a locked-down kiosk. The best choice is the one that passes a restart, network-loss and extended playback test with your screen and content.
Start AdPlayr automatically after a restart
Windows: run AdPlayr setup in the Windows account used by the display. Start with Windows is enabled for new installations; change it from the AdPlayr tray menu. Setup registers startup for that account. Existing choices are preserved on updates; you do not need an extra Startup-folder shortcut.
Raspberry Pi: run AdPlayr setup as your normal desktop user. It adds the player to labwc startup. Enable desktop auto login in Raspberry Pi settings so the desktop starts after boot. Settings may be called Control Centre or Raspberry Pi Configuration, depending on your OS version.
Restart the device and check that the correct playlist appears without help. Starting the computer, signing in and launching AdPlayr are three separate steps; the installers do not configure the first two.
Sign in automatically, without removing the password
Use a dedicated device account for the display. Keep your personal Windows account and your AdPlayr company administrator account off the player computer; pair the screen from another device.
Windows: Microsoft’s Autologon utility can sign the device account in automatically. Download it from Microsoft, run it, enter the device account credentials and choose Enable. Restart to check it works. You can use Disable to undo it.
Only enable this on a physically secured display computer: someone with access can use the signed-in session, and a local administrator can recover the stored password. This is automatic Windows sign-in, not removal of the account password or AdPlayr’s sign-in protection.
Raspberry Pi: enable desktop auto login for the dedicated player user. The same physical-access consideration applies.
Keep the computer and TV awake
The Windows player prevents idle sleep and display timeout while it runs. It cannot override a closed laptop lid, a deliberate sleep command, a lock policy or the TV’s own sleep timer.
For a dedicated plugged-in Windows device, review Settings → System → Power & battery (or Power) and its screen/sleep timeouts. On the Pi, disable screen blanking in Raspberry Pi settings. Check the TV’s automatic standby, eco timer and selected HDMI input too.
Should I schedule a nightly reboot?
Not as a default. Our recommendation is to restart for updates or a known device issue, during a planned maintenance window. A daily reboot briefly stops playback and should not replace investigating recurring freezes.
If your installation benefits from scheduled reboots, first prove that automatic sign-in and AdPlayr startup work. Choose a time outside opening hours and leave enough time for updates before the screen is needed. Use the operating system’s scheduler; AdPlayr does not currently schedule computer reboots.
For Windows updates, set your opening hours under Windows Update → Advanced options → Active hours. Keep security updates enabled. For a manual player reload, use Restart player in AdPlayr’s Windows tray menu.
Recover after a power cut
On a Windows mini PC, look for a manufacturer setting such as Restore on AC power loss in BIOS/UEFI. Its name and availability vary; use the computer manufacturer’s instructions. Also check whether your TV returns to the correct HDMI input after power returns.
Use a suitable power supply, secure cables and ventilation. Consider a UPS where power interruptions are common. Shut down through the operating system for planned maintenance instead of cutting power with a timer.
Test the complete recovery path on your installation: computer powered on, device account signed in, AdPlayr launched and TV showing the playlist.
Keep playback steady when the internet drops
Prefer wired Ethernet where practical. Keep the player online until Player status confirms the media is saved for offline playback. Allow enough free storage and keep the device clock correct.
Saved content can play for up to 72 hours offline, or until access ends if sooner, with up to 2 GB per screen. Do not use private browsing or clear the player’s browser profile: that can remove pairing and saved content. New content and remote changes require a connection.
Start with 1080p H.264 MP4 videos and test sound, transitions and your longest clips on the actual device. Keep offline email alerts enabled in Settings so an owner or admin can investigate a lost connection.
Before leaving a screen unattended
- Restart once and confirm the player opens without keyboard input.
- Check that the TV stays on the right input and does not enter standby.
- Let every playlist item play, including videos with sound.
- After media is saved, briefly disconnect the network and verify playback; reconnect and check a content update.
- Run a full-day trial and check the screen the following morning.