← Back to Support

Raspberry Pi Setup

Turn a $45 Raspberry Pi 4 (or $60 Pi 5) into a full-featured digital signage player in under 15 minutes. Try every feature free for 30 days — no credit card required.

What You Need

Raspberry Pi 4 or 5 4 GB RAM minimum. 8 GB recommended for video-heavy schedules or YouTube/Vimeo embeds. 2 GB models work for static slideshows but struggle with long uptime once a cache fills.
Micro SD Card 16 GB or larger. Class 10 or UHS-I recommended for faster boot and caching.
HDMI Cable Micro HDMI to HDMI for Pi 4/5. Connect to your TV or display.
Power Supply Official USB-C power supply recommended. 5V 3A for Pi 4, 5V 5A for Pi 5.
Ethernet (Recommended) Wired connection for the most reliable performance. WiFi is also supported.

Total hardware cost: approximately $45–$70 depending on the Pi model and accessories you already have.

1 Download the Image

Download the pre-built DisplayCache image for Raspberry Pi. This is a complete operating system image with everything pre-configured — no terminal commands, no manual setup.

Download DisplayCache Pi Image (.img.gz)

File size is approximately 1.5 GB. The download is a compressed .img.gz file. You do not need to extract it — Raspberry Pi Imager handles that automatically.

2 Flash to SD Card

Use Raspberry Pi Imager to write the image to your SD card. It is free, cross-platform, and handles decompression automatically.

  1. Download and install Raspberry Pi Imager from raspberrypi.com/software. Available for Windows, macOS, and Linux.
  2. Insert your SD card into your computer using a built-in card reader or USB adapter.
  3. Open Raspberry Pi Imager and click Choose OS.
  4. Scroll to the bottom and select Use custom. Browse to the .img.gz file you downloaded.
  5. Click Choose Storage and select your SD card. Double-check you have selected the correct drive — this will erase everything on it.
  6. Click Write. The process takes 5–10 minutes depending on your SD card speed.
  7. When it finishes, safely eject the SD card from your computer.

Note: You do not need to configure any OS customization settings (hostname, WiFi, SSH) in the Imager. The DisplayCache image handles all of that automatically.

3 Connect and Power On

  1. Insert the SD card into your Raspberry Pi.
  2. Connect an HDMI cable from the Pi to your TV or display. Use the HDMI 0 port (closest to the USB-C power port) for best compatibility.
  3. Connect ethernet if available. A wired connection is strongly recommended — especially on Pi 3 B+ (see Tested Hardware below).
  4. Plug in the power supply. The Pi boots automatically: branded DisplayCache splash, then the kiosk takes over. First boot takes 1–2 minutes; subsequent boots about 30 seconds.

No ethernet? Use the WiFi setup hotspot.

If no ethernet is connected within 60 seconds of boot, the Pi automatically broadcasts a temporary setup network called DisplayCache-XXXX (random 4-digit suffix). To configure WiFi from your phone:

  1. On your phone, connect to the DisplayCache-XXXX network. Password: displaycache.
  2. A setup page opens automatically. If it doesn't, visit http://10.42.0.1.
  3. Pick your home or office WiFi from the list, enter the password, tap Connect.
  4. The phone will lose the hotspot connection — that's expected. The Pi is now joining your real WiFi.
  5. After 30–60 seconds, the pairing code appears on the TV. If the hotspot reappears in your phone's WiFi list, the password was wrong — reconnect and try again.

4 Pair the Device

Once the Pi finishes booting, a 6-character pairing code appears on screen. This code is unique to the device and refreshes every few minutes.

  1. Open admin.displaycache.com in your browser and sign in.
  2. Go to Devices in the sidebar.
  3. Click + Pair Device (or Add Device).
  4. Enter the 6-character code shown on the TV and click Pair.
  5. Give the device a friendly name (e.g., "Lobby TV Left") and assign it to a location.

The device connects to your organization within seconds. The pairing code disappears and the screen shows a "Connected" confirmation.

5 Assign Content

Now that the device is paired, tell it what to display.

  1. Add the device to a group (optional). Device groups let you target content to multiple screens at once (e.g., "Lobby Screens", "Classrooms").
  2. Assign a playlist directly, or create a schedule that switches playlists at different times of day.
  3. Save. The Pi downloads the assigned content immediately and begins playback within a minute or two, depending on how much content needs to be cached.

From this point on, any changes you make in the web admin are pushed to the Pi automatically. No need to touch the device again.

Tested Hardware

Heads up: our internal test bench is currently Raspberry Pi 3 B+. Pi 4 and Pi 5 run the exact same image and we expect them to work identically — the underlying Pi 4/5 + Bookworm + Wayland stack is one of the most widely deployed Linux configurations in the world. But we haven't yet had a Pi 4 or Pi 5 on a real customer fleet ourselves. If you deploy on Pi 4 or Pi 5 and hit something odd, please email hello@displaycache.com — we'll prioritize it.

DisplayCache runs on Raspberry Pi 4 and Pi 5. Pi 3 B+ also works but with caveats — details below.

Recommended PREVIEW — not yet customer-tested

  • Raspberry Pi 4 (4 GB or 8 GB) — hardware H.264 video decode up to 1080p, dual micro-HDMI, gigabit ethernet, dual-band WiFi. Our intended default Pi target once we've validated it on real hardware.
  • Raspberry Pi 5 (4 GB, 8 GB, or 16 GB) — faster CPU, more RAM, but the H.264 hardware decoder was removed. Its Cortex-A76 cores software-decode 1080p H.264 with headroom, so practical outcome is the same as Pi 4 for typical signage. Pi 5 has hardware HEVC decode.

Works with caveats

  • Raspberry Pi 3 Model B+ — the cheapest signage option, but its onboard WiFi (Broadcom BCM4345) is genuinely flaky. The kernel's WiFi firmware load fails on roughly 1-in-20 cold boots; DisplayCache auto-recovers by reloading the driver, but it adds a ~10 second boot delay. Ethernet is strongly recommended on Pi 3 B+. Video performance is also weaker: the Cortex-A53 cores software-decode H.264 at ~50% of one core, fine for static slides and 720p clips but stresses 1080p.

Minimum requirements

  • RAM: 4 GB minimum, 8 GB recommended for video-heavy schedules or YouTube/Vimeo embeds. 2 GB models work for static slideshows but struggle with long uptime once a cache fills.
  • SD card: 16 GB or larger, Class 10 / UHS-I. SD card speed affects boot time and cache flush throughput.
  • Power supply: Official Raspberry Pi PSU strongly recommended — marginal phone chargers cause SDIO transfer errors that look like "WiFi randomly stopped working."
  • Network: Ethernet (always recommended) or 2.4 GHz / 5 GHz WiFi.

Not supported

  • Pi Zero / Zero 2 W — not enough RAM, no hardware video acceleration the kiosk can use.
  • Pi 1, 2, 3 (non-B+) — insufficient CPU for modern Chromium kiosk.
  • Pi 400 / Pi 500 — technically Pi 4/5 internals so the image will boot, but the integrated keyboard form-factor isn't a sensible signage deployment.

Features

  • Offline caching — Content is downloaded and stored on the SD card. Screens keep playing even if the internet goes out.
  • HDMI-CEC TV control — The Pi can turn your TV on and off on a schedule via HDMI-CEC. No separate smart plug or remote needed.
  • Auto-updates — The agent checks for updates, downloads them, and restarts automatically. No SSH, no manual intervention.
  • Runs headless — No keyboard, mouse, or monitor needed after initial setup. Manage everything from the web admin.
  • Low power — The Pi draws about 5–7 watts. Leave it running 24/7 for pennies a month in electricity.
  • Chromium kiosk — Full-screen playback with no browser chrome, no toolbars, no distractions.

Recommended Accessories

Optional add-ons that make a Pi deployment more reliable. Unlike the NUC, the Pi has HDMI-CEC built in, so no CEC adapter is needed.

HDMI Ghost Display Emulator (~$10)

For Pis whose TV is powered off most of the day (overnight, weekends, summer break), the HDMI signal physically drops when the TV goes to standby. The Pi sees “no display attached,” the Wayland compositor stops drawing, and when the TV comes back on the slideshow may not return until the Pi reboots.

A 1920×1080 HDMI Ghost Display Emulator plugs into the Pi’s second micro-HDMI port (Pi 4/5 both have two) and emulates a connected display 24/7. The Pi always thinks a screen is attached, the compositor never sleeps, and the slideshow resumes the instant the TV powers back on.

  • Recommended: Fueran 1920×1080 HDMI Headless Ghost Display Emulator on Amazon. You’ll also need a micro-HDMI to HDMI adapter for the Pi side.
  • Required for: Pis with a scheduled TV power-off, plus any Pi running fully headless.
  • Setup: Plug into the unused micro-HDMI port. No driver, no config. The agent doesn’t need to know about it.

Getting CEC to Work With Your TV

HDMI-CEC is the standard that lets the Pi power the TV on and off over the HDMI cable. The Pi has native CEC built in — no adapter needed — but every TV vendor implements roughly half of the spec and disables most of that by default. To get reliable power-on/off:

Pick the right HDMI port

  • Use HDMI 1 on the TV. Many TVs only honor CEC on HDMI 1 and ignore commands on other ports.
  • Avoid ports labeled “ARC” or “eARC” unless that’s the only CEC port. ARC expects an audio-system handshake the Pi doesn’t fully implement.
  • On the Pi side, use HDMI 0 (the port closest to the power connector). HDMI 1 on the Pi exists but CEC behavior on the secondary port varies by firmware revision.

Enable CEC in the TV menu

CEC is called something different on every brand. Find the right name and turn it on:

  • LG: SimpLink
  • Samsung: Anynet+
  • Sony: BRAVIA Sync / Control for HDMI
  • Panasonic: Viera Link
  • Sharp: Aquos Link
  • Hisense: HDMI-CEC / Anyview
  • Vizio: Settings → System → CEC → Enabled
  • Roku TVs (Westinghouse, TCL, Hisense Roku, etc.): Settings → System → Control other devices (CEC) → 1-touch play: ON and System standby: ON. Both default to off; without 1-touch play, only power-off works.

Disable eco / fast-start tradeoffs

  • Quick Start / Fast TV Start / Instant On — enable this. Many TVs disable the CEC chip in standby to save power. Without Quick Start, the TV cannot be woken by CEC because the chip isn’t listening when the TV is off.
  • Auto power-off / Sleep timer — disable on the TV side. The DisplayCache schedule should be the only thing powering the TV down.
  • Eco mode — turn off if it has its own switch separate from Quick Start.
Some TVs refuse CEC wake regardless of settings — typically cheap generic-vendor sets that didn’t implement the wake half of CEC at all. Two fallback strategies: leave the TV on 24/7 (the slideshow blanks on schedule, the TV doesn’t), or use a $10 WiFi smart plug to cut power. The TV cold-boots in the morning and picks up the Pi’s HDMI signal automatically. Works on any TV regardless of CEC compliance.

Troubleshooting

No display output

Make sure you are using the HDMI 0 port (the one closest to the power connector). Try a different HDMI cable. Some TVs require you to select the correct HDMI input manually. If you see a rainbow screen or no signal at all, the image may not have flashed correctly — re-flash the SD card using Raspberry Pi Imager.

WiFi setup

If no ethernet cable is connected, the Pi creates a WiFi hotspot named DisplayCache-Setup. Connect to it from your phone or laptop and follow the on-screen instructions to enter your WiFi network name and password. Once connected, the Pi switches to your WiFi network and the pairing code appears.

Pairing code not appearing

If the screen shows the DisplayCache logo but no pairing code, the Pi may not have internet access. Check your ethernet cable or WiFi connection. The pairing code only appears once the device can reach the DisplayCache server.

SD card errors or boot loops

If the Pi does not boot or gets stuck in a loop, the SD card may be corrupted or the flash failed. Re-flash the SD card using Raspberry Pi Imager. If the problem persists, try a different SD card — cheap or older cards can be unreliable.

Re-flashing the device

To start fresh, simply remove the SD card, re-flash it with Raspberry Pi Imager using the latest DisplayCache image, and insert it again. The Pi will boot as a new device with a new pairing code. You will need to pair it again in the web admin.

Still need help?

Email us at hello@displaycache.com and we will get back to you within one business day.