How to Self-Host Jellyfin
Jellyfin free media server for streaming movies, television, music, and personal videos to browsers, televisions, phones, and other clients. It was added to SelfHub after appearing in What I Self-Host, What I Don't, and Why; the product facts below were checked against the project's official site and source repository.
When Jellyfin is a good fit
Choose Jellyfin when you want this capability on infrastructure you control and are prepared to own updates, access control, monitoring, and recovery. Review the upstream documentation before selecting a version because deployment requirements can change between releases.
Deployment notes
Install the official package or container, persist configuration and cache, mount media read-only, and pass through a supported GPU when hardware transcoding is needed.
Place any browser-accessible interface behind HTTPS. Pin a release rather than an unqualified latest tag, apply updates deliberately, and keep the service reachable only from the networks and users that need it.
Data and recovery
Back up configuration, users, watch history, and metadata separately from the much larger media library.
Write down the restore sequence, required secrets, exposed ports, and external dependencies. A scheduled backup is not complete until a clean host can restore it and pass a functional check.
Important limitation
Remote streaming can consume significant upload bandwidth and transcoding resources; benchmark representative clients before exposing it.
Production checklist
- Pin and record the deployed version.
- Persist every documented data and configuration path.
- Terminate TLS at a maintained reverse proxy or trusted tunnel.
- Restrict administrative interfaces and rotate default credentials.
- Monitor uptime, disk space, certificate expiry, and failed jobs.
- Test an off-host backup with a real restore.
