Skip to main content
OSSAlt

Self-Host Jellyfin: Plex Alternative Media Server 2026

·OSSAlt Team
jellyfinplexmedia-serverself-hostingdockerstreaming2026
Share:

TL;DR

Jellyfin is a completely free, open source media server — GPL 2.0, ~35K GitHub stars, no subscription, no server-side account required. It streams movies, TV shows, music, live TV (with a TV tuner), and photos to all your devices. Plex charges $5–8/month for Plex Pass features (hardware transcoding, offline sync, live TV). Jellyfin gives you everything for free. The tradeoff: Plex has more polished apps and better third-party device support.

Key Takeaways

  • Jellyfin: GPL 2.0, ~35K stars — 100% free, no subscription ever
  • vs Plex: Same core features; Plex has slicker apps, Jellyfin has no paywalled features
  • vs Emby: Jellyfin is a fork of Emby after it went closed-source
  • Hardware transcoding: Free (Plex requires Plex Pass for this)
  • Requirements: 1–2GB RAM + storage for your media library
  • Clients: Web, iOS, Android, Apple TV, Roku, Fire TV, Android TV, Smart TVs

Jellyfin vs Plex vs Emby

FeatureJellyfinPlexEmby
LicenseGPL 2.0ProprietaryProprietary
CostFreeFree + $120/yr Plex PassFree + $54/yr Emby Premiere
Hardware transcoding✅ FreePlex Pass requiredEmby Premiere required
Live TV / DVR✅ FreePlex Pass requiredEmby Premiere required
Offline sync✅ FreePlex Pass requiredEmby Premiere required
Mobile apps✅ FreeFree (with limitations)Emby Premiere or pay
Client countGoodExcellentGood
Third-party plugins✅Limited✅
Account required❌ (fully local)✅ Plex account✅ Emby account
GitHub Stars~35K——

Server Requirements

  • CPU: 2+ cores (transcoding is CPU/GPU intensive)
  • RAM: 1–2GB (4GB if running alongside other services)
  • Storage: Depends on library. 1080p files: 4–15GB each. 4K: 30–80GB each.
  • Network: Gigabit LAN for local 4K, 10–25 Mbps for remote 1080p streams

Part 1: Docker Compose Setup

# docker-compose.yml
version: '3.8'

services:
  jellyfin:
    image: jellyfin/jellyfin:latest
    container_name: jellyfin
    restart: unless-stopped
    network_mode: host    # Enables network discovery (device auto-detection)
    environment:
      JELLYFIN_PublishedServerUrl: "https://media.yourdomain.com"
    volumes:
      - ./config:/config          # Jellyfin config files
      - ./cache:/cache            # Metadata cache
      - /mnt/media/movies:/media/movies:ro     # Your movie library (read-only)
      - /mnt/media/tv:/media/tv:ro             # TV shows
      - /mnt/media/music:/media/music:ro       # Music
    # Hardware transcoding (choose one based on GPU):
    # devices:
    #   - /dev/dri/renderD128:/dev/dri/renderD128    # Intel/AMD GPU
    # environment:
    #   JELLYFIN_DATA_DIR: /data

Or without host networking (ports mode):

services:
  jellyfin:
    image: jellyfin/jellyfin:latest
    ports:
      - "8096:8096"    # HTTP
      - "8920:8920"    # HTTPS
      - "7359:7359/udp"  # Local discovery
      - "1900:1900/udp"  # DLNA
    volumes:
      - ./config:/config
      - ./cache:/cache
      - /mnt/media:/media:ro

docker compose up -d

Visit http://your-server:8096 → setup wizard → add your media libraries.

Part 2: HTTPS with Caddy

media.yourdomain.com {
    reverse_proxy localhost:8096
}

For remote access, set in Jellyfin → Dashboard → Networking:

  • Public HTTPS port: 443
  • Custom SSL certificate path (or let Caddy handle TLS)

Part 3: Initial Setup Wizard

  1. Select language → Next
  2. Create admin user → username + password
  3. Add media libraries:
    • Click + → Select type: Movies
    • Add folder: /media/movies
    • Language: English
    • Scan automatically: Yes
  4. Repeat for TV, Music
  5. Let the initial metadata scan complete (10–30 minutes depending on library size)

Part 4: Hardware Transcoding

Hardware transcoding drastically reduces CPU load for streaming:

Intel Quick Sync (Intel GPU)

services:
  jellyfin:
    devices:
      - /dev/dri:/dev/dri
    environment:
      - JELLYFIN_PublishedServerUrl=https://media.yourdomain.com
    group_add:
      - "109"   # video group (check with: stat -c "%g" /dev/dri/renderD128)

In Jellyfin Dashboard → Playback → Transcoding:

  • Hardware acceleration: Intel Quick Sync Video
  • Enable: H.264, HEVC, VP8, VP9, AV1

NVIDIA GPU

deploy:
  resources:
    reservations:
      devices:
        - driver: nvidia
          count: 1
          capabilities: [gpu, video]

In Dashboard → Transcoding: NVIDIA NVENC

No GPU (CPU Transcoding)

CPU transcoding works but uses significant CPU. On a 4-core server, expect 1–2 simultaneous 1080p streams before maxing out.

Part 5: Media Organization

Jellyfin follows Emby/Plex naming conventions:

movies/
  The Matrix (1999)/
    The Matrix (1999).mkv
    The Matrix (1999).nfo    # Optional: custom metadata

tv/
  Breaking Bad/
    Season 01/
      Breaking Bad S01E01.mkv
      Breaking Bad S01E02.mkv
    Season 02/
      Breaking Bad S02E01.mkv

music/
  Artist Name/
    Album Name (Year)/
      01 - Track Name.flac
      02 - Track Name.flac

Jellyfin auto-downloads metadata (posters, descriptions, ratings) from:

  • TheMovieDB (movies/TV)
  • MusicBrainz (music)
  • TheTVDB (TV)

Part 6: Client Apps

Web Browser

Visit https://media.yourdomain.com — full web client.

iOS / Android

Official Jellyfin app:

Third-party clients with better UI:

Smart TVs and Streaming Devices

DeviceClientNotes
Apple TVInfuse 7 or SwiftfinInfuse has best performance
RokuJellyfin RokuOfficial channel
Fire TVJellyfin for Fire TVIn Amazon App Store
Android TVJellyfin for Android TVOfficial
Samsung/LG TVWeb browserSmart TV web app
Xbox/PlayStationWeb browserBrowser-based

Part 7: Live TV and DVR

Requires a TV tuner connected to your server:

  • HDHomeRun (network TV tuner, recommended)
  • Hauppauge WinTV (USB tuner)
devices:
  - /dev/dvb:/dev/dvb    # USB DVB tuner

In Jellyfin Dashboard → Live TV:

  1. Add tuner device (HDHomeRun auto-discovered on network)
  2. Add TV guide: Schedules Direct ($25/year) or XMLTV
  3. Configure DVR storage location
  4. Start watching live TV and recording shows

Part 8: Plugins and Extensions

Jellyfin has a plugin catalog:

Dashboard → Plugins → Catalog:

  • Playback Reporting: Track what you've watched
  • Trakt.tv: Sync watch history to Trakt
  • Fanart.tv: Better artwork from Fanart.tv
  • Open Subtitles: Auto-download subtitles
  • Bookshelf: Add books to your library
  • Kodi Sync Queue: Sync watched status with Kodi

Remote Access and Security

Secure Remote Access

Never expose Jellyfin directly on port 80/443 without a reverse proxy. With Caddy:

media.yourdomain.com {
    reverse_proxy localhost:8096

    # Rate limit to prevent brute force:
    rate_limit {
        zone dynamic {
            key    {remote_host}
            events 10
            window 1m
        }
    }
}

Enable HTTPS Only

In Jellyfin → Dashboard → Networking:

  • Require HTTPS: On
  • Allow remote connections: On
  • Remote IP whitelist: Leave blank (all IPs), or restrict to trusted IPs

Maintenance

# Update Jellyfin:
docker compose pull
docker compose up -d

# Backup:
tar -czf jellyfin-config-$(date +%Y%m%d).tar.gz ./config

# Rebuild metadata (if images are missing):
# Dashboard → Libraries → Scan all libraries

# Check logs:
docker compose logs -f jellyfin

Why Self-Host Jellyfin?

The case for self-hosting Jellyfin comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Jellyfin means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Jellyfin, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Jellyfin headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Jellyfin data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Jellyfin without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Jellyfin's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Jellyfin backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Jellyfin's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Jellyfin's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Jellyfin's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Jellyfin's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f jellyfin

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Jellyfin's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

  1. Confirm the container is running: docker compose ps
  2. Test locally on the server: curl -I http://localhost:PORT
  3. If local access works but external doesn't, check your firewall: ufw status
  4. If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats jellyfin. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Jellyfin Updated

Jellyfin follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Jellyfin is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See all open source media server tools at OSSAlt.com/alternatives/plex.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)

Step-by-step: infrastructure setup, data migration, backups, and security for 15+ common SaaS replacements. Used by 300+ developers.

Join 300+ self-hosters. Unsubscribe in one click.