FULLTVBOX
PROMPT ◆ NEW · By FullTVBox Test Bench ·

Plex or Jellyfin for Your Setup? An AI Decision Prompt

Describe your server, files, devices, and remote viewers; get a Plex vs Jellyfin verdict and first setup steps. Tested example inside.

Works with ClaudeChatGPTOllama
// The prompt
Help me choose between Plex and Jellyfin for my home media server, then tell me how to start.

- Server hardware: {server}
- Library: {library}
- Devices we watch on: {clients}
- Remote viewers (outside my home): {remote}
- Budget for software: {budget}
- My comfort level with tinkering: {skill}

Decide based on my details, not on general popularity. Cover:
1. Your verdict in one sentence.
2. Whether my files will direct-play on my devices or need transcoding, and whether my hardware can handle that.
3. The 2 biggest risks with your pick for my setup.
4. The first 5 setup steps.

Fill in: {server}{library}{clients}{remote}{budget}{skill}

◆ Tested on Claude Opus 5.5 · October 5, 2026. The example below is that model's actual output for the sample details shown. AI answers vary between runs, so check anything important.

Example input

  • server: Raspberry Pi 5 (8 GB) with a 4 TB USB SSD, wired Ethernet
  • library: about 400 films, mostly 1080p H.264 MKV, some 4K HEVC rips
  • clients: Fire TV Stick 4K Max (living room), iPad, a parent’s Roku in another city
  • remote: one parent, a couple of times a week
  • budget: don’t want a subscription
  • skill: comfortable with SSH and Docker

Example output

Verdict: Jellyfin. You don’t want a subscription, you’re comfortable with Docker, and a Pi 5 can’t do the heavy transcoding that Plex Pass would unlock anyway.

Direct play vs transcoding:

  • 1080p H.264 MKV direct-plays on the Fire TV Stick 4K Max and iPad. The Pi just serves the file.
  • 4K HEVC direct-plays on the Fire TV Stick 4K Max (it supports HEVC). The iPad should too, through the Jellyfin app. Don’t expect the Pi to transcode 4K; if a device can’t direct-play it, it will stutter.
  • The remote Roku is the risk: upload speed and codec support decide whether it direct-plays. Set its maximum streaming bitrate below your home upload speed.

Biggest risks:

  1. Remote access setup. Plex handles this for you; with Jellyfin you set up a reverse proxy or a VPN (Tailscale/WireGuard) yourself. For one parent, a VPN is the safer choice.
  2. Subtitles (especially image-based PGS in 4K rips) can force burn-in transcoding. Use SRT subtitles where possible.

First 5 steps:

  1. Install Docker on Raspberry Pi OS (64-bit) and mount the SSD at a fixed path via /etc/fstab.
  2. Run the official jellyfin/jellyfin image with the media folder mounted read-only.
  3. Add libraries split into “Movies” and “Movies 4K” so you can limit 4K to the Fire TV.
  4. Install the Jellyfin app on the Fire TV and iPad and test direct play (Dashboard › Activity shows “Direct Play” vs “Transcode”).
  5. Set up Tailscale on the Pi and on the parent’s side before opening anything to the internet.

Tips

  • List what codecs your files use. Direct play vs transcoding decides almost everything on Pi-class hardware.
  • Prefer to keep your library details private? Run this prompt on a local model with Ollama. It’s a reasoning task that mid-size local models handle well.
  • The full comparison is in our Plex vs Jellyfin on Raspberry Pi guide.
// From the bench

Read next

// Prompt library

More prompts

All in group →