¶ What is Jellyfin?
Jellyfin enables you to collect, manage, and stream your media. Run the Jellyfin server on your system and gain access to the leading free-software entertainment system, bells and whistles included.
¶ Installation
services:
jellyfin:
container_name: jellyfin
image: lscr.io/linuxserver/jellyfin:latest
runtime: nvidia
environment:
- PUID=568
- PGID=568
- TZ=America/New_York
- NVIDIA_VISIBLE_DEVICES=all
- NVIDIA_DRIVER_CAPABILITIES=all
ports:
- '8096:8096'
restart: unless-stopped
volumes:
- /mnt/tank/configs/jellyfin:/config
- /mnt/tank/media:/media
Note this stack enables nVidia GPUs. If you don’t need this, remove all the lines with
nvidiain them.
¶ Permissions & Folder Structure
- PUID / PGID: Ensure you use a user/group with the correct permissions for accessing media folders. TrueNAS SCALE defaults to 568:568 for apps.
- Volumes: The container structure follows a common-sense naming convention, storing configurations under /mnt/tank/configs/emby
- 📌 Refer to the Folder-Structure guide for more details.
- Check the Jellyfin Server Storage box to Enable Host Path for Jellyfin Server Config Volume and select the correct path as described in the TrueNAS article.
- Click the Add button for Jellyfin Server Extra Host Path Volumes to pass the
mediadirectory into the container as /media. - Scroll to the Resource Configuration section and locate the checkbox for your GPU. If you do not see one, make sure to select the checkbox in Apps → Configuration → Settings → Install NVIDIA Drivers.
Check out the new docs from TrueNAS
¶ Jellyfin Configuration
¶ Setup Media Libraries
- Click + New Library
- Set the Content Type to match the folder (Movies for /media/movies and TV Shows for /media/tv)
- Click on the + next to Folders and add the appropriate folder
- Click the green OK at the bottom and leave the rest of the settings the same
- Do the same thing for your second library for TV Shows.
¶ Watching Content
To watch content on a device in your house on your home network, download the Jellyfin App from wherever your device gets apps from. When you start the Jellyfin app, manually add a server. Type in the IP Address of your server (for me it would look like http://192.168.1.215) and use the default port of 8096. Once its connected you should see the sign-in screen with your name on it. If not, use the manual login and type the username and password you set up earlier.
¶ Video
¶ Using NPM
If you are using Nginx Proxy Manager to route your traffic use these settings to be sure you’re not caching media:
| Field | Value |
|---|---|
| location | / |
| Cog Icon | click this to expand the box at the bottom |
| scheme | http |
| Forward Hostname / IP | private IPv4 of your media server |
| Forward Port | port media server is running on |
| expandable box | add_header Cache-Control "no-store, no-cache, must-revalidate, proxy-revalidate"; add_header Pragma "no-cache"; add_header Expires "0"; |
¶ Using an Intel iGPU
This section is under development and may not work for you
- Deploy Jellyfin using the above Docker Compose file, removing the lines with
nvidiain them - In the TrueNAS shell, run the command
cd /dev/dri && ls -l. You should see a line at the bottom that looks like:
crw-rw---- 1 root render 226, 128 Apr 15 14:44 renderD128
- To find the ID of the
rendergroup, run the commandgetent group render | cut -d: -f3. In my case the output was107. - Now, add these lines into the Docker Compose file, using your values from above:
group_add:
- "107"
devices:
- /dev/dri/:/dev/dri/
- My final Docker Compose looks like:
services:
jellyfin:
container_name: jellyfin
image: lscr.io/linuxserver/jellyfin:latest
environment:
- PUID=568
- PGID=568
- TZ=America/New_York
ports:
- "8096:8096"
restart: unless-stopped
group_add:
- "107" # Access to /dev/dri/renderD128
- "44" # Access to /dev/dri/card0
devices:
- /dev/dri/:/dev/dri/
volumes:
- /mnt/tank/configs/jellyfin:/config
- /mnt/tank/media:/media
- If done correctly, you should see these two lines in your logs:
**** creating video group videol7cu with id 107 ****
**** adding /dev/dri/renderD128 to video group videol7cu with id 107 ****
**** adding /dev/dri/card0 to video group video with id 44 ****
- Navigate to Settings → Dashboard → Playback → Transcoding
- Change Hardware Acceleration to
Intel QuickSync (QSV) - For the QSV Device add
/dev/dri/renderD128if that was the output from Step 2 - Follow the steps below to use AI to assist you in selecting the appropriate codecs for your iGPU
- Remember to hit Save at the bottom when you’re done
¶ Transcoding settings
Many people ask how to setup the transcoding section of Jellyfin for their specific GPU. I usually tell them “it depends” because each GPU has different capabilities. However, I will tell you a great way to answer this for your individual GPU is ChatGPT. To do this, take a screenshot of the transcode page and ask: "if i have <insert_GPU> which of these should i select for hardware decoding and tone mapping?"
ChatGPT can read the image and tell me which boxes to check and what my Tone Mapping settings should be.
As an example, here was the response:
With an NVIDIA Quadro P2000 GPU, you can enable several hardware decoding options thanks to its support for NVDEC (NVIDIA Video Decoder). The P2000 supports hardware decoding for a wide variety of codecs, so here’s what you should ideally enable in Jellyfin based on your screenshot:
✅ Safe to Enable with P2000:H264 ✅ (already enabled)
HEVC ✅ (Main/8-bit only; 10-bit HEVC decoding is supported via partial acceleration)
MPEG2 ✅
MPEG4 ✅
VC1 ✅ (already enabled)
VP8 ✅
VP9 ✅ (8-bit; 10-bit is partially supported)
HEVC 10bit ✅ (Partial decoding support—still useful)
VP9 10bit ✅ (already enabled; partial support)
❌ Not Supported or Questionable on P2000:
AV1 ❌ (AV1 is not supported on P2000)
HEVC RExt 8/10bit ❌ (Refers to extended profiles—unsupported)
HEVC RExt 12bit ❌
Recommended settings for you:
✅ Enable: H264, HEVC, MPEG2, MPEG4, VC1, VP8, VP9, HEVC 10bit, VP9 10bit
❌ Disable or leave unchecked: AV1, HEVC RExt 8/10bit, HEVC RExt 12bit
Bonus Tips:
Enhanced NVDEC Decoder ✅ (keep this enabled — improves decoding on newer drivers)
Enable Hardware Encoding ✅ (already enabled — the P2000 supports NVENC)
For encoding, H264 is your best option. You can enable HEVC encoding if you want smaller file sizes and are okay with slightly slower performance.
✅ Recommended Tone Mapping Settings for P2000:
Enable Tone Mapping: ✅ Yes (only if you’re playing HDR content on SDR displays).
Tone Mapping Algorithm: BT.2390 (recommended default — a perceptually better curve for HDR→SDR conversion).
Tone Mapping Mode: Auto (you can try RGB if you notice washed-out colors or blown highlights).
Tone Mapping Range: Auto (keeps the same color range as input; usually best unless you know you’re targeting limited-range SDR).