Jellyfin Guide: Self-Hosted Media Server Setup & Streaming

If you’ve got a folder of ripped DVDs, downloaded home videos, or a personal music collection sitting on a hard drive, you’ve probably wished for a clean way to stream it to your TV, phone, or laptop — without uploading anything to the cloud. Jellyfin is the free, open-source answer: a full media server that organizes your library, fetches artwork and metadata, and streams to nearly any device, all running entirely on hardware you control.

Unlike Plex, Jellyfin has no parent company, no account requirement, and no premium tier gating features like hardware transcoding behind a paywall. Everything is free, forever, because there’s no business model behind it beyond the community that builds it.

This guide walks through the full Docker deployment, library setup, hardware transcoding, remote access, and backup strategy for running Jellyfin at home.

1. How Jellyfin Works

Jellyfin is built around three cooperating pieces: a media library on disk, a server process that indexes and serves that library, and client apps that connect to the server to play content.

The server scans the folders you point it at on a schedule you set, matching file and folder names against metadata providers to pull in posters, descriptions, cast lists, and episode data. That metadata, along with playback history and user accounts, is stored in an embedded SQLite database — there’s no separate database container to manage. When a client requests playback, the server either sends the file as-is (direct play) or transcodes it on the fly into a format the requesting device supports, using the CPU or a hardware encoder if one is available. Clients — the web UI, mobile apps, smart TV apps, and Kodi/Jellyfin Media Player — talk to the server over a standard HTTP API, so any of them can browse the same library and pick up playback where another device left off.

• Library Scanner: Watches your media folders and indexes new files, matching them to metadata from providers like TheMovieDB and TheTVDB.
• SQLite Storage: Holds user accounts, watch history, playback state, and library metadata in a single embedded database.
• Transcoding Engine: Converts video on the fly when a client can’t direct-play the source file, optionally offloaded to a GPU for hardware acceleration.
• User & Access Layer: Supports multiple accounts with individual watch histories, parental controls, and per-library permissions — no shared login required.
• Client Apps: Official and community apps exist for web browsers, Android, iOS, Android TV, Roku, and most smart TVs, plus Kodi integration.

2. System Prerequisites

Jellyfin’s baseline footprint is light, but transcoding is where resource needs jump — plan your hardware around how much transcoding you’ll actually need.

• CPU: Any modern x86_64 quad-core handles a couple of simultaneous transcodes; more demanding 4K libraries benefit heavily from a hardware encoder instead.
• RAM: 2 GB minimum for the server itself; 4 GB+ recommended if you’re running other containers alongside it.
• Storage: The application itself is small, but budget generously for your media library plus space for transcode caching.
• GPU (optional but recommended): An Intel Quick Sync-capable CPU, or an Nvidia GPU with NVENC, dramatically reduces CPU load during transcoding.
• Software: Docker and Docker Compose installed on a Linux host.

If you haven’t set up Docker yet, our guide on installing Docker on Ubuntu covers the full setup from a clean system.

3. Step-by-Step Docker Installation

Create a dedicated directory for the deployment:

mkdir -p ~/jellyfin
cd ~/jellyfin

The Docker Compose File

nano docker-compose.yml

version: "3.8"

services:
  jellyfin:
    container_name: jellyfin
    image: jellyfin/jellyfin:latest
    user: 1000:1000
    volumes:
      - ./config:/config
      - ./cache:/cache
      - /path/to/movies:/data/movies
      - /path/to/tvshows:/data/tvshows
    ports:
      - 8096:8096
    restart: unless-stopped

Explaining the Configuration

• ./config volume: Persists the SQLite database, user accounts, and all server settings across restarts and upgrades.
• ./cache volume: Stores transcode buffers and image cache separately from config, so it can be cleared without touching your library data.
• Media volumes: Mount each media folder read-only where possible (:ro) since Jellyfin only needs to read your files, not write to them.
• Port 8096: The default web dashboard and streaming port. You’ll place this behind a reverse proxy in step 6 rather than exposing it directly.

Launch the stack:

sudo docker compose up -d

Check the logs to confirm a clean startup:

sudo docker compose logs -f

4. Initial Setup & First Library

1. Navigate to http://<YOUR_SERVER_IP>:8096 in your browser.
2. Walk through the setup wizard: choose a display language, then create your administrator account.
3. Click Add Media Library and configure your first library:

4. Repeat for each additional library (TV Shows, Music, etc.), then finish the wizard.

Once a library is added, Jellyfin scans it in the background: it walks each folder, matches filenames against its metadata providers, and fills in the library with posters and details as matches come in. Well-organized folder and file names (e.g., Movie Name (Year)/Movie Name (Year).mkv) produce far more accurate matches than loosely named files, so it’s worth renaming your library before the first scan if it’s currently messy.

5. Hardware-Accelerated Transcoding

Direct play — sending the original file untouched — is always the fastest option, but it only works when the client device supports the file’s codec, resolution, and container natively. Anything else triggers a transcode, and software transcoding on the CPU alone can max out a modest server with just one or two simultaneous 4K streams.

Enabling Hardware Acceleration

1. Go to Dashboard > Playback.
2. Under Hardware acceleration, select your GPU type (Intel Quick Sync, Nvidia NVENC, or AMD AMF, depending on your hardware).
3. Enable the specific codecs you want accelerated (H.264, HEVC, VP9, AV1 where supported).
4. For Intel Quick Sync or Nvidia GPUs in Docker, you’ll also need to pass the device through in docker-compose.yml — for Intel, this typically means mounting /dev/dri; for Nvidia, it means adding the runtime: nvidia directive alongside the appropriate environment variables.
5. Save, then test playback of a file you know requires transcoding and confirm GPU usage rises in Dashboard > Activity.

Hardware transcoding is one of the areas where Jellyfin’s no-paywall model matters most — Plex historically required a paid Plex Pass subscription for the same feature, while Jellyfin includes it for every user by default.

6. Securing the Dashboard with a Reverse Proxy

Never expose port 8096 directly to the internet without HTTPS in front of it. Route it through a reverse proxy with TLS termination. If you’re already running Nginx Proxy Manager for other self-hosted services, our Nginx Proxy Manager security guide covers hardening it properly — the same proxy host pattern applies here:

1. In Nginx Proxy Manager, add a new Proxy Host.
2. Set the domain (e.g., jellyfin.yourdomain.com), forward hostname to your server’s internal IP, and forward port 8096.
3. Enable Force SSL and request a Let’s Encrypt certificate.
4. Enable WebSockets Support — Jellyfin uses WebSockets for real-time UI updates like live transcode status and sync-play.
5. Under the proxy host’s Advanced tab, raise the client body size limit if you plan to upload large subtitle or artwork files through the web UI.

Also make sure your firewall only allows the reverse proxy to reach port 8096, not the wider internet. Our Linux security commands guide and Fail2Ban guide are useful next steps for locking down the host this container runs on.

7. Remote Access & Client Apps

Once the reverse proxy is in place, you can add your domain in each client app’s server address field to connect from outside your home network — no port forwarding of the raw Jellyfin port required.

• Mobile: Official apps are available for Android and iOS, supporting offline downloads for on-the-go viewing.
• Smart TVs: Native apps exist for Android TV and most major smart TV platforms; where a native app isn’t available, casting from a mobile app or using a browser typically fills the gap.
• Desktop: The web client works in any modern browser, and the Jellyfin Media Player app offers a more native desktop experience with better subtitle and audio track handling.
• Kodi: The Jellyfin add-on syncs your library and watch state directly into Kodi’s interface for users who prefer that front end.

For remote streaming specifically, keep an eye on your upload bandwidth — a 4K remux being transcoded for a remote device can require significantly more upload throughput than most home internet plans provide, which is another good reason to lean on hardware transcoding.

8. Backing Up Your Jellyfin Data

Your entire server configuration — accounts, watch history, library metadata, and settings — lives inside the config volume as a set of files and an SQLite database. Your actual media files should already be backed up separately as part of your general storage strategy, but the config directory needs its own routine:

#!/bin/bash
BACKUP_DIR="/home/suresh/jellyfin/backups"
TIMESTAMP=$(date +%F)
mkdir -p "$BACKUP_DIR"

# Stop the container briefly to ensure a consistent database snapshot
docker stop jellyfin
tar -czf "$BACKUP_DIR/jellyfin_config_$TIMESTAMP.tar.gz" -C /home/suresh/jellyfin config
docker start jellyfin

# Retain only the last 14 days of backups
find "$BACKUP_DIR" -type f -name "jellyfin_config_*.tar.gz" -mtime +14 -delete

Schedule it with cron for regular execution, and sync the backup directory offsite using the same rsync pattern covered in our self-hosted backup strategies guide.

9. Troubleshooting & Maintenance

10. Jellyfin vs. Alternatives

11. Conclusion

Jellyfin turns a folder of media files into a proper streaming service, without a subscription, an account requirement, or a paywall in front of features other platforms charge extra for. Paired with a hardened reverse proxy and a solid backup routine, it becomes the entertainment layer for any home lab or personal server stack.

Once your media server is live, make sure the rest of your self-hosted stack is watching over it too. Check out our guides on setting up Uptime Kuma monitoring and the complete home server security checklist to keep an eye on what Jellyfin is running on.