PlexBeam

← Back to Blog

Run Plex Media Server on a Raspberry Pi

October 15, 2026 · PlexBeam

A Raspberry Pi can run Plex Media Server for a small library with direct-play clients. It draws under 5 watts, costs under $100, runs silently, and fits in a pocket. But it has real limitations — no hardware transcoding, limited RAM, and slow USB storage. This guide covers how to set it up, what it can and cannot do, and how to optimize it for the best experience within its constraints.

Which Raspberry Pi Model to Use

ModelCPURAMEthernetUSBPlex Rating
Raspberry Pi 5 (8 GB)Cortex-A76 quad-core 2.4 GHz8 GBGigabit2x USB 3.0Best Pi for Plex
Raspberry Pi 5 (4 GB)Cortex-A76 quad-core 2.4 GHz4 GBGigabit2x USB 3.0Good for small libraries
Raspberry Pi 4 (4-8 GB)Cortex-A72 quad-core 1.8 GHz4-8 GBGigabit2x USB 3.0Adequate for direct play
Raspberry Pi 4 (2 GB)Cortex-A72 quad-core 1.8 GHz2 GBGigabit2x USB 3.0Barely usable, library browsing is slow
Older models (3B+, Zero)Cortex-A53 / A71 GB100 MbpsUSB 2.0Not recommended

The Raspberry Pi 5 with 8 GB is the clear choice. The Pi 4 works but is noticeably slower for library browsing and metadata operations. Older models are too slow for a usable Plex experience.

What You Need

Installation

Step 1: Install Raspberry Pi OS

Flash Raspberry Pi OS (64-bit, Lite — no desktop needed for a headless server) to your microSD card or NVMe SSD using the Raspberry Pi Imager. Enable SSH during the flashing process so you can configure headlessly.

Step 2: Install Plex Media Server

SSH into your Pi and run:

curl https://downloads.plex.tv/plex-keys/PlexSign.key | gpg --dearmor | sudo tee /usr/share/keyrings/plex-archive-keyring.gpg > /dev/null

echo "deb [signed-by=/usr/share/keyrings/plex-archive-keyring.gpg] https://downloads.plex.tv/repo/deb public main" | sudo tee /etc/apt/sources.list.d/plexmediaserver.list

sudo apt update

sudo apt install plexmediaserver

Plex starts automatically. Access the web interface at http://pi-ip-address:32400/web.

Step 3: Mount Your Storage

Connect your USB hard drive and mount it. Find the drive:

lsblk

Create a mount point and mount it:

sudo mkdir -p /mnt/media

sudo mount /dev/sda1 /mnt/media

Add to /etc/fstab for auto-mount on boot:

/dev/sda1 /mnt/media ext4 defaults,nofail 0 2

Use nofail so the Pi still boots if the drive is disconnected.

Set permissions so Plex can read the media:

sudo chown -R plex:plex /mnt/media

Step 4: Add Libraries

In the Plex web interface, add libraries pointing to your mounted storage. Plex will scan and index your media. The initial scan on a Pi is slower than on a PC — a library of 1,000 movies may take 30-60 minutes to fully index with metadata and artwork.

Performance: What a Pi Can and Cannot Do

Direct Play (What It Does Well)

When a client can play the original file without conversion, the Pi just reads the file from storage and sends it over the network. This requires almost no CPU — the Pi handles it easily. A Pi 5 can serve 3-5 simultaneous direct-play streams depending on the bitrate and storage speed.

Transcoding (What It Cannot Do)

The Raspberry Pi has no hardware video encoder. All transcoding is software-only on the ARM CPU. A Pi 5 can barely transcode a single 1080p stream in real time — expect stuttering and buffering. 4K transcoding is not possible.

This means: every client must direct-play your files. If a client needs transcoding (wrong codec, remote quality setting too low, subtitle burn-in), the Pi will choke.

How to Avoid Transcoding

Optimizing Performance

Use an NVMe SSD for the Plex Database

The Plex database (stored in /var/lib/plexmediaserver/) is the performance bottleneck on a Pi. Library browsing, search, and metadata loading all depend on database read speed. A microSD card is slow (20-40 MB/s random read). An NVMe SSD via the Pi 5 M.2 HAT provides 10-20x faster random I/O, making library navigation noticeably snappier.

Keep your media on the USB hard drive (capacity matters more than speed for sequential reads) and put the Plex data directory on the NVMe.

Overclock the Pi 5

The Pi 5 can be overclocked from 2.4 GHz to 2.8-3.0 GHz with adequate cooling:

Add to /boot/firmware/config.txt:

arm_freq=2800

over_voltage=4

Requires active cooling (a fan) to prevent thermal throttling. The performance gain is roughly 15% — noticeable during library scans and metadata processing.

Disable Unnecessary Services

On Raspberry Pi OS Lite, there is not much to disable. But ensure you are not running a desktop environment, Bluetooth services (if unused), or other servers that compete for the Pi's limited resources.

Networking

Always use ethernet, not Wi-Fi. The Pi 5 has true gigabit ethernet (the Pi 4's gigabit is shared with USB, limiting real throughput to roughly 300-400 Mbps under load). A 4K remux file can hit 100 Mbps — this is fine for 1-2 streams on gigabit ethernet but would saturate Wi-Fi 5 (802.11ac) easily.

When a Pi Is Enough

A Raspberry Pi is a good Plex server if:

A Pi is NOT enough if:

Alternatives at Similar Price Points

If the Pi's limitations are too restrictive, consider:

Need Expert Help?

Our team can take a look. Get a fast, honest diagnosis.

Get Started →

Related Articles

More Articles

Browse our full library of guides and tutorials.

Related guides

More from LuxuriousComputers: LuxuriousComputers · Computer Repair · Remote Fix · Phone Repair · HVAC · Plex Support