Skip to content

Jellyfin in Container Manager on a Synology NAS (Hardware Transcoding)

Last updated on 28 January 2024

Important or Recent Updates
Historic UpdatesDate
New DSM7.2 Container Manager Update (Beta/RC)30/04/2023
Amended the devices mounted to the container as had reports of better performance with them.17/05/2023
Added additional security option to the compose to restrict the container from gaining new privileges as well as umask variable25/10/2023
Historic Updates

In this guide I am going to take you through the setup of Jellyfin in Container Manager using Docker Compose.

Does my Synology support Hardware Transcoding?

Before we do anything else, you need to make sure your model of Synology has hardware transcoding capabilities. You need to do a quick lookup via the linked Google Sheet below, this is updated by Plex however it’s perfectly relevant for Jellyfin.

If you find that your model does not support hardware transcoding you can jump back over to the standard guide.

Let’s Begin

As usual, it’s important you complete the three preceding guides which will get your folder structure and docker, user and bridge network setup.

Folder Setup

Let’s start by getting some folders set up for the container to use. Open up File Station create the following.


Container Manager

Next we are going to set up a ‘Project’ in Container Manager. Open up Container Manager and click on Project then on the right-hand side click ‘Create’.

In the next screen we will set up our General Settings, enter the following:

Project Name:jellyfin
Source:Create docker-compose.yml

Next we are going to drop in our docker compose configuration copy all the code in the box below and paste it into line ‘1’ just like the screenshot.

What on earth is a Docker Compose?
Docker Compose allows us to define how Docker should set up one or more containers within a single configuration file. This file is yaml formatted and Container Manager uses the Projects feature to manage them.

    image: linuxserver/jellyfin:latest
    container_name: jellyfin
      - PGID=65432 #CHANGE_TO_YOUR_GID
      - TZ=Europe/London #CHANGE_TO_YOUR_TZ
      - UMASK=022
      - JELLYFIN_PublishedServerUrl=SEE_TABLE_BELOW
      - /volume1/docker/jellyfin:/config
      - /volume1/data/media:/data/media
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/dri/card0:/dev/dri/card0
      - 8096:8096/tcp #web port
      - 8920:8920/tcp #optional
      - 7359:7359/udp #optional
    network_mode: synobridge
      - no-new-privileges:true
    restart: always

The two optional ports in the above can be removed if you will not use them. 7359 is for automated discovery of Jellyfin by the apps, and 8920 is the HTTPS port which is useful if not using the reverse proxy later in the guide.

Environment Variables

We need to make some changes in order for the container to have the correct permissions to save its configuration files and to have access to your media.

PUID(required) The UID you obtained in the user setup guide
PGID(required) The GID you obtained in the user setup guide
TZ(required) Your timezone
JELLYFIN_PublishedServerUrlThis will be your NAS IP or if you are going to be accessing via your DDNS address use this. (You can change this later if you wish)


We can now pass through our file paths into the container they are mounted using the volume’s section of the compose file.

I have pre-filled this section to pass the correct paths, the only thing that you may need to change is the /volume1/ if your file paths are on a different volume.

Click ‘Next’

You do not need to enable anything on the ‘Web portal settings’ screen click ‘Next’ again.

On the final screen click ‘Done’ which will begin the download of the container images and once downloaded they will be launched!

The image will now be downloaded and extracted. You should see ‘Code 0’ when it has finished.

You will now see your Jellyfin running and should have a green status on the left-hand side.

Firewall Exceptions

(Skip if you don’t have the Firewall configured)

If you have enabled and configured the Synology Firewall you will need to create exceptions for any containers that have a Web UI or have any incoming or outgoing connections. This section covers the basics of how to add these. (Please note this is a generic section and will not show the specific ports used in this guide however it applies in the same way)

Also, I would like to refer people to the great guide on getting the Firewall correctly configured over on WunderTechs site.

Head into the Control Panel> Security > Firewall, from here click Edit Rules for the profile you set up when you enabled the Firewall.

Next click on Create and you will see the screen below. Source IP and Action will be automatically selected to All and Allow, I will leave it up to you as to your own preference on whether you want to lock down specific Source IPs from having access. In this example we will leave as All.

You will now choose ‘Custom‘ and then the Custom button

Now select Destination from the drop-down menu, most web based containers require TCP access but check the guide as it will show the port and protocol. Then add comma separated ports. Then press OK.

Click OK a couple of times to get back to the main screen. You will see by default the new rule is added to the bottom of the list. You must always have your Block All rule last in the list as the rules are applied top down so move your container up.

You have now completed the Firewall changes and can continue with the guide.

Jellyfin Initial Setup

After a few minutes you should be able to access the server and go through the initial Jellyfin setup by going to the IP of your NAS in your browser followed by port 8096.


When adding movies or shows they will be located in the /data/media folder.

How to enable Hardware Transcoding

The last steps for initial set up are to enable the hardware transcode features for your NAS.

On the main Jellyfin homescreen, click on the hamburger menu on the top left and then ‘Dashboard’ in the ‘Administration’ section

On the next screen select ‘Playback’ where you will now be able to select from the first drop-down from ‘None’ to ‘Intel QSV Video’

I have removed the video previously shown below and changed into a table – to take into account some feedback and testing completed in our Matrix/Discord server.

Below are the settings you would enable for a Gemini Lake based NAS such as the 920+/720+/420+/220+. You can cross-check between the Synology CPU list and the table on the QSV Wikipedia page as to the hardware functions your NAS supports.

Please note that I have included the items I changed from the default values – e.g. if the default item is turned off, and I turn it on then it appears in the table.

Setting changed from the default.Variable to use
HEVC 10bitTicked
VP9 10bitTicked
Allow Encoding in HEVC formatTicked
Enable VPP Tone MappingTicked
Enable Tone MappingUnticked

Once you have made the required change press ‘Save’ and you are now free to change any other settings you wish in relation to the server, make sure you check out the fantastic documentation from Jellyfin.

Remote Access

If you are going to be using your set-up outside your LAN you will also need to enable the following options to allow access and also to restrict bandwidth

Allow remote connections to this server


In order to limit upload bandwidth you can also set an overall limit for streams, this is useful if you or other users will be trying to play back files larger than your upload bandwidth can handle

Part 2 – DDNS, SSL and Reverse Proxy

Before we start, make sure you have registered for a Synology Account as we are going to be using their DDNS service.

In order to successfully use the reverse proxy you will also need to forward port 443 to you NAS IP. (You will need to check how to do this on your own router) This port is used for secure web traffic.

DDNS (Dynamic Domain Name System)

A DDNS address allows you to get external access to Jellyfin via a subdomain provided by Synology, this is useful on home internet connections where your ISP will change your IP address on a regular basis. (If you already have this set up via another guide you can skip to the Reverse Proxy section)

Note: If you want to access DSM via this new address you will either need to create an additional Reverse Proxy for it or open port 5001 on your router.

In the DSM Control panel go to ‘External Access’ and then to the ‘DDNS’ tab

Click on ‘Add’, then fill out the following sections.

Service ProviderSynology
HostnameThis can be anything it will be used to access your NAS externally
Email:Log into your Synology account
External Address (IPv4)This should be filled in automatically
External Address (IPv6)This should be filled in automatically if your ISP is using IPv6
Get a Cert from Let’s EncryptTick this box
Enable HeartbeatTick this box

Now press OK, DSM will apply your settings. It can take a few moments to set up and the DSM interface will refresh. You will likely receive a certificate error which you will need to accept to get back into DSM.

You should now test that you can access your Diskstation via the hostname you requested and not receive any SSL errors.

Reverse Proxy

So you don’t have to open up additional ports on your router for Jellyfin we are going to set up a reverse proxy subdomain. This means you and your users can access Jellyfin without using a port number as it will route all traffic through the secure 443 port.

Go back into the Control Panel and access the ‘Login Portal’ then in the ‘Advanced’ tab click ‘Reverse Proxy’ and then click on ‘Create’.

We are now going to enter some rules, so when you or your users access the URL specified the request will automatically be sent to the Jellyfin web UI.

Use the settings below, you will need to amend the Hostname sections in line with the hostname you registered earlier, and the IP of your NAS.

Reverse Proxy Name:jellyfin
Protocol:HTTPS (change the part after ‘jellyfin.’ to your own hostname you registered earlier.
Hostname:Your NAS IP
example settings

On the second tab ‘Custom Header’ click on Create then WebSocket, this will add two entries which will force a https connection if you ever try to connect over http, you can now press save.

You should now be able to access the Jellyfin login screen to https://jellyfin.yourhostname it will be a secure connection, and you should have no SSL errors.

You can now log in with the username and password you created earlier, the same address is used in the Android and iPhone apps.

Buy Me a Coffee or a Beer

If you have found my site useful please consider pinging me a tip as it helps cover the cost of running things or just lets me get the odd beverage. Plus 10% goes to the devs of the apps I do guides for every year.

Published inJellyfin 7.2


  1. Wanted to point out that I ended up switching over to Linuxserver because of all the HT issues.

    Used your process and such and everything went through without a hitch. HT works as expected.

    I would still really love to switch back to jellyfin/jellyfin release as I believe that their releases are much more consistent and should be the latest. But, for now . . . LS image will have to do.

    Do you have any other tips on this process?

    • Dr_Frankenstein Dr_Frankenstein

      Hey glad it is working, not sure what was happening with your issues with the Jellyfin official container, but there is nothing wrong with the LinuxServer releases they are kept up to date, hardware side works perfectly.

  2. Justas Justas


    after deploying jellyfin in Synology DS918+ and adding folders i fail to see any media pop up there after scanning. Plex was finding fine. I tried following the 1-2-3 steps guides as well for permission adding. but no luck. Do you have any tips what else could help me in my case?

    • Dr_Frankenstein Dr_Frankenstein

      Hey, odd that Plex can see and Jellyfin can’t triple check that the UID/GID are the correct way around

      – PUID=1234 (4 digits)
      – PGID=12345 (3 or 5 digits)

      If you are still struggling let me know and I will ping you a direct email.

  3. Aaron Aaron

    Rebuilt from this guide (i was using the syno-comunity store build, but it doesn’t support hardware trans-coding)
    Runs awesome, Thanks for the help.

    I do have a question though – An update is now available for Jellyfin. (through Container Manager, Images)
    Will it be safe to perform this update without loosing any data?
    I know the video files will be safe obviously, and /config is configured under one of the NAS’s normal volumes.
    Just wanted to ask for advice before i do it.

    • Dr_Frankenstein Dr_Frankenstein

      100% safe to do, see the left menu for instructions on the order of steps. Glad you got setup

  4. Santhoshi Santhoshi

    need help with that YAML bro .
    spent hours on “cannot build project jellyfin”
    i think you should attach a real example format .

    • Dr_Frankenstein Dr_Frankenstein

      Hey, what part is it not working with, the error should say what it wrong if you scroll right in the window.

  5. Matt Riechmann Matt Riechmann

    Ok, I love your site. Its on point and a GREAT reference to a lot of information that helps MANY!!

    I wanted to ask . .

    I have jellyfin setup with the jellyfin/jellyfin latest image, and transcoding worked great until recently. Looks like someone else in your comments also pointed out that the Jellyfin docker image is now requiring a Render group to be identified in the ENV variables.

    I wanted to ask if you know more around this and if you might be able to create another guide using the jellyfin docker image instead of the linuxserver image? I have been using the jellyfin image without issue for some time now but never needed HT until recently.

    I was also wondering . . if I were to switch over to the Linuxserver image . . would I have to start over from scratch? Or, could I simply kill my current container, update the compose file to be your own and replace all the media pointers and such? I tried doing this quickly, but found that I got server errors when trying to connect up.

    Any help would be greatly appreciated. I haven’t gotten very far and am hoping you can point me i nthe right direction because my family would like to watch my 4K movies, but requires HT in order for that to happen.

    • Dr_Frankenstein Dr_Frankenstein

      Hey – So I spun up a Jellyfin/Jellyfin image to compare the folder layout to the Linuxserver version and as you can see from the attached they are similar but not identical on first start up.

      However, your issue should be easy to fix looking at the documentation.

      SSH into your NAS and run

      sudo ls -l /dev/dri

      Output should look like this, meaning in this example the group we add is 226

      total 0
      drwxr-xr-x 2 root root 120 Mar 5 05:15 by-path
      crw-rw—-+ 1 root video 226, 0 Mar 5 05:15 card0
      crw-rw—-+ 1 root video 226, 1 Mar 5 05:15 card1
      crw-rw—-+ 1 root render 226, 128 Mar 5 05:15 renderD128

      Then in your compose file add the group add lines as shown below and fire it back up. Formatting is lost in comments so also a paste with the correct format

      image: jellyfin/jellyfin
      user: 1000:1000
      – “226” # Change this to match your “render” host group id and remove this comment

      Hope that helps.

      • Globalrebel Globalrebel

        I wish that had worked 🙁

        I ran the command and got the ouput for the render group ID

        Killed the container and edited to compose file to add the ID line and number to my list

        I also switch the Devices to the following . . .

        – /dev/dri/renderD128:/dev/dri/renderD128

        But, when testing, it still is erroring out. Should I have left the devices to the prefvious setup . .

        – /dev/dri:/dev/dri


        Might just switch over to Linux server image to get around this.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed. – writing Synology Docker Guides since 2016 – Join My Discord!