How to Install Plex Server on Raspberry Pi 4

Turning a Raspberry Pi 4 into a Plex Media Server is one of those “this is either brilliant or slightly unhinged”
projectsuntil you’re streaming your own movie library on the couch and feeling like you just built Netflix in your
kitchen. This guide walks you through a clean, modern Plex setup on a Raspberry Pi 4, with practical choices that
keep your server stable, fast, and (mostly) drama-free.

We’ll cover the native install (recommended for most people), storage mounting (where most people accidentally
summon chaos), permissions (Plex is picky, like a cat with a new food bowl), performance tweaks, and a Docker option
if you like your apps containerized and your weekend plans complicated.

Before You Start: Is Raspberry Pi 4 a Good Plex Server?

Yesif your goal is Direct Play (streaming files in a format your devices already support).
A Raspberry Pi 4 is small, quiet, low-power, and surprisingly capable for:

• Streaming 1080p (and sometimes 4K) without transcoding
• Serving music libraries and photo collections
• Being an always-on “home media server” that doesn’t heat your room like a space heater

Where the Pi 4 struggles is transcodingespecially high-bitrate 4K or multiple simultaneous streams.
If you expect Plex to convert huge video files on the fly for older devices, you’ll be happier with a mini PC or
NAS with a stronger CPU. The Pi can still be fantastic if you aim for Direct Play and pick sensible formats.

What You’ll Need

• Raspberry Pi 4 (4GB or 8GB recommended)
• microSD card (16GB+; higher-quality is better)
• Good power supply (stable power matters more than you think)
• Ethernet cable (strongly recommended for reliability and speed)
• USB 3.0 external drive (SSD preferred; HDD is fine if powered properly)
• A computer to flash Raspberry Pi OS (or Ubuntu) to the SD card

Step 1: Install and Update Raspberry Pi OS (Headless-Friendly)

For a Plex server, you usually want a lightweight OS. Raspberry Pi OS Lite (64-bit) is a solid choice:
fewer background processes, fewer surprises, and more resources left for Plex.

Recommended setup approach

1. Use Raspberry Pi Imager to flash Raspberry Pi OS Lite (64-bit) to your microSD card.
2. In the Imager’s advanced settings, preconfigure:
   • Hostname (example: plexpi)
   • Username/password
   • Wi-Fi (if not using Ethernet)
   • Enable SSH
3. Boot the Pi and SSH into it from your computer.

Once you’re in, update everything first. This prevents “it failed because your packages are from the Stone Age.”

Step 2: Give Your Pi a Stable IP Address (So Plex Doesn’t Play Hide-and-Seek)

Plex clients connect to your server by IP address on your local network. If your router changes that address later,
Plex will feel like it moved houses without telling anyone.

Best option

Set a DHCP reservation in your router (sometimes called “Static Lease”). This keeps the Pi on the same
local IP without hardcoding networking on the Pi itself.

Tip: You’ll want this later for Remote Access and port forwarding too. Future-you will be grateful.

Step 3: Connect and Mount Your Media Drive (The “Don’t Panic” Section)

You can store media on the microSD card, but it’s not ideal. Plex libraries can grow fast, and constant writes for
metadata can shorten SD card lifespan. A USB 3.0 SSD (or powered HDD) is much better.

Identify the drive

Look for something like /dev/sda1. If the drive is brand new or you want best Linux performance, format it
as ext4. (If you need to plug it into Windows often, NTFS/exFAT can work, but permissions take extra care.)

Create a mount point

Get the UUID (recommended for reliable mounting)

Mount it temporarily (ext4 example)

Auto-mount at boot using /etc/fstab

Edit the file:

Add a line like this (replace the UUID with yours):

Test it without rebooting:

Organize folders

Step 4: Install Plex Media Server (Native Install)

The simplest method on Raspberry Pi OS is installing the official Plex Media Server .deb package for ARM
(often labeled Armv8 for 64-bit). You’ll download it and install with dpkg.

Option A (easy): Download the package from the Pi

1. Open the Plex Media Server downloads page on the Pi.
2. Select Linux, then choose the correct ARM build (typically Armv8 for Raspberry Pi OS 64-bit).
3. Download the .deb file.

Install it from your Downloads folder:

Verify the service is running

If you want Plex to start at boot (usually already enabled, but it’s nice to confirm):

Step 5: Open Plex Web App and Claim Your Server

Plex is configured through the Plex Web App. From a computer on the same network, open a browser and go to:

Sign in with your Plex account and follow the setup wizard:

• Name your server (example: PlexPi4)
• Choose whether to enable Remote Access now or later
• Add libraries (Movies, TV, Music, etc.)

If you’re setting up from a different network

Plex may require the initial setup to look “local.” If you’re away from home, use an SSH tunnel from your laptop to
the Pi so your browser connects like it’s on the same machine:

Then open:

Step 6: Fix Permissions So Plex Can Actually See Your Media

On Linux, Plex typically runs as a dedicated user named plex. That user needs permission to read your media
folders. If Plex can’t access your files, it won’t add themno matter how politely you ask.

A clean, sane permissions strategy

Create a shared group for media access, then add both your main user and Plex to it:

Give the group ownership of your media folders:

This approach keeps your files readable by Plex without making everything world-writable. It’s the Linux equivalent
of “organized adulthood.”

Quick sanity check

Restart Plex after permission changes:

Step 7: Performance Tuning for Raspberry Pi 4 (So It Doesn’t Melt Into a Puddle)

Plex on a Pi 4 can be smoothif you optimize for what the Pi does best.

1) Prefer Direct Play over transcoding

• Use modern formats like H.264 or H.265 inside MP4/MKV containers where your playback devices support them.
• Avoid forcing subtitles that trigger transcoding (some subtitle formats can do that).
• Set client apps to “Original” quality at home when possible.

2) Use Ethernet if you can

Wi-Fi works, but wired networking is more consistentespecially for high-bitrate files.

3) Keep it cool

Sustained scanning, metadata downloads, and any transcoding can warm up the Pi. A small case fan or decent passive
cooling helps prevent throttling.

4) Consider moving Plex metadata to SSD (optional but helpful)

Plex stores artwork, posters, databases, and other library data in its “data directory.” This can grow large and
causes frequent writes. Moving this to an SSD can speed up browsing and reduce SD wear.

High-level steps:

1. Stop Plex
2. Move the Plex data directory to SSD storage
3. Create a symlink back to the original path
4. Start Plex

Example commands (adjust paths carefully):

If that makes you nervous, that’s normal. The safe approach is: back up first, go slow, and keep the original
folder until you confirm Plex works.

Step 8: Remote Access (Optional) and Security Basics

If you want to stream your personal media away from home (or share with family), you can enable Remote Access in Plex.
Plex can try automatic router configuration via UPnP/NAT-PMP, or you can set up manual port forwarding.

Remote Access checklist

• Make sure your Pi has a stable local IP (remember Step 2).
• In Plex Web App: Settings → Server → Remote Access.
• If manual forwarding: forward an external TCP port to internal port 32400 on the Pi.

Security tips that are actually worth doing

• Use a strong Plex account password and enable 2FA if available for your account.
• Keep your Pi updated: sudo apt update && sudo apt full-upgrade -y
• Only share with people you trust (your future self will thank you).
• If you’re security-minded, consider using a VPN instead of opening ports to the internet.

Note: Always stream content you own or have rights to use. Plex is a media organizer and streamerwhat you feed it
should be legal and yours.

Option B: Install Plex with Docker (For Tinkerers and People Who Label Cables)

Running Plex in Docker can make updates and migrations easier, but it adds complexity around permissions and mounts.
If you’re new to Linux servers, native install is typically simpler.

Docker Compose example (linuxserver/plex)

This is a common pattern: bind-mount your media and store Plex config on persistent storage.

With network_mode: host, Plex behaves more like a normal app on the network (helpful for discovery).
Once it’s running, you’ll still use:

Troubleshooting: Quick Fixes for Common Plex-on-Pi Problems

Plex Web App won’t load

• Confirm the service is running: sudo systemctl status plexmediaserver
• Check the IP address: hostname -I
• Try rebooting (yes, really): sudo reboot
• Make sure you’re on the same local network (for initial setup, especially)

Plex can’t see your media folders

• This is almost always permissions or mount issues.
• Confirm the drive is mounted: df -h
• Confirm folder permissions allow the plex user to read the directories.

Playback stutters

• Prefer Ethernet.
• Reduce the need for transcoding (use Direct Play-friendly formats).
• Check the Pi’s temperature and cooling.

Real-World Experiences: What It’s Like Running Plex on a Raspberry Pi 4 (About )

Here’s what tends to happen after the install high wears off and you start using Plex daily on a Raspberry Pi 4:
everything works… until you ask the Pi to do something that feels like running a marathon while carrying groceries.

The first big “experience moment” is the initial library scan. If you dump a large collection onto the drive
and point Plex at it, the Pi will start downloading posters, background art, cast info, theme music, and metadata.
It’s impressivelike watching a tiny librarian sprint through a warehouse with sticky notes. It can also take a while.
During this phase, the Plex interface might feel slower, and the Pi might run warmer. That’s normal. Let it finish.
(This is also when decent cooling goes from “nice-to-have” to “why is my Pi doing hot yoga?”)

Next comes the classic: permissions confusion. You’ll add a library, browse to your folder, and Plex will act
like your media doesn’t exist. The files are there. You can see them. Your dog can probably see them. Plex cannot.
That’s usually because Plex runs as its own user and doesn’t automatically get access to drives mounted under your
home directory or with restrictive permissions. The fix is nearly always a clean group strategy (like the media
group above) or carefully applied ownership/ACLs.

Then you’ll hit the performance reality check: transcoding is the Pi’s kryptonite. If you mostly watch on devices
that can Direct Play your files (modern smart TVs, streaming sticks, phones), the Pi feels surprisingly powerful.
But if a client forces transcodingmaybe it can’t handle the codec, or it needs burned-in subtitles, or you try to
stream a huge 4K file over a limited connectionthe Pi may struggle. The practical experience is: optimize your media,
set home clients to Original quality, and avoid making the Pi convert video formats live if you can help it.

Storage brings its own lessons. External drives sometimes sleep aggressively or draw more power than the Pi’s USB
can comfortably provide. If you see random disconnects, use a powered USB hub or a drive with its own power supply.
Also, placing Plex metadata on an SSD tends to make the interface feel snappiercover art loads faster, browsing is
smoother, and you reduce write wear on the microSD card.

Finally, remote access is where people either celebrate or spiral. Automatic UPnP might “just work,” or your router
might respond with the networking equivalent of a shrug. The stable experience is: reserve a local IP, forward the
correct ports if you must, and consider a VPN if you prefer not to expose services to the open internet. Once dialed
in, it’s genuinely satisfying to pull out your phone, open Plex, and stream your own library from anywherelike a
personal streaming service you control.

Conclusion

Installing Plex on a Raspberry Pi 4 is a high-reward project when you set expectations correctly: aim for Direct Play,
use reliable storage, give Plex proper permissions, and keep the Pi cool. Do that, and you get a compact, low-power
home media server that feels way more “grown-up” than it has any right to.