Install and optimize Jellyfin on Ubuntu: step-by-step guide

Install Jellyfin on Ubuntu using the official method, set up libraries and verify hardware acceleration without universal performance promises.

Before you start

Use an Ubuntu release supported by the Jellyfin repository, a sudo account and enough space for media, metadata and temporary transcodes. Check the official instructions for your release. Direct play often avoids transcoding; performance depends on GPU, codecs, clients and network.

Install from the official repository

Download the official script and checksum, confirm the check says OK, inspect the script and only then run it with elevated privileges. Jellyfin also documents manual repository setup if you prefer it. Check the service after installation.

sudo apt update
sudo apt install curl ca-certificates
curl -fsSLO https://repo.jellyfin.org/install-debuntu.sh
curl -fsSLO https://repo.jellyfin.org/install-debuntu.sh.sha256sum
sha256sum -c install-debuntu.sh.sha256sum
less install-debuntu.sh
sudo bash install-debuntu.sh
sudo systemctl status jellyfin --no-pager

Initial setup and access

From a trusted network open http://SERVER_IP:8096, create an administrator with a strong password, select language and media libraries, and grant the service read-only media access when practical. Do not directly expose port 8096 to the internet; use an HTTPS reverse proxy or VPN for remote access, with authentication and regular updates.

Hardware acceleration

Identify the GPU and inspect video devices. Under Dashboard > Playback > Transcoding select the documented method for your hardware: Intel QSV, AMD VA-API or NVIDIA NVENC, depending on drivers and support. Check that the jellyfin user can access the device. Enable only supported codecs and tone mapping. Test a file that actually transcodes and inspect logs, CPU/GPU load and the dashboard. No fixed CPU reduction is guaranteed.

lspci -nn | grep -Ei '3d|display|vga'
ls -l /dev/dri/
id jellyfin

Temporary storage and libraries

Do not automatically move transcodes to /tmp or RAM: an undersized tmpfs can exhaust memory and interrupt playback. Plan for space, memory and concurrent streams, and change the path only if measurements justify it. Schedule preview generation at quiet times; monitor disk space, cache and permissions.

Features and limits

Jellyfin provides media libraries, accounts, clients and plugins. Codec support, offline downloads, SyncPlay and client features vary by device and version. Verify official clients before purchasing hardware. Assess and update third-party plugins separately. Back up configuration, metadata and media as needed.

Official sources

Installation: https://jellyfin.org/docs/general/installation/linux/ ; transcoding: https://jellyfin.org/docs/general/post-install/transcoding/ ; acceleration: https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/ .