Skip to main content
Media

Self-host Jellyfin (Docker) on a VPS

Containerised Jellyfin for easy updates.

Run Jellyfin as a container so upgrades and rollbacks are trivial and your media stays separate.

Start freeSee VPS plans

Why self-host Jellyfin (Docker)?

The container route keeps Jellyfin’s config isolated, making version changes and backups simple.

How to install Jellyfin (Docker)

  1. 1

    Provision a VPS

    Choose a plan with room for your data as well as the app.

  2. 2

    Install the stack

    Install Docker + media volume.

  3. 3

    Deploy the application

    Follow the project’s official install guide for your distribution.

  4. 4

    Enable HTTPS

    Serve it on your own domain behind a reverse proxy with a certificate.

  5. 5

    Back it up

    Schedule a database dump plus a copy of any uploaded files to an off-box location.

Practical tips

  • Give Jellyfin (Docker) its own database user with rights only on its own schema.
  • Reverse-proxy Jellyfin (Docker) and terminate TLS at the proxy so certificates are managed in one place.
  • Take a VPS snapshot before major upgrades so you can roll back cleanly.
  • Keep Jellyfin (Docker) patched — most self-hosting incidents are unpatched software.

Frequently asked questions

How much RAM does Jellyfin (Docker) need?
Plan on 2–4 GB for typical use; add headroom if you expect many concurrent users.
What stack does Jellyfin (Docker) run on?
Docker + media volume.
Can I run other things on the same VPS?
Yes — size the plan so Jellyfin (Docker) plus your other workloads fit in RAM with room to spare.

Looking for something else? Popular alternatives include Plex, Emby, Jellyfin (native) — browse all app guides.

About Jellyfin (Docker)

Jellyfin (Docker) is open-source software released under the GPL-2.0 licence. HostingSwift does not maintain, sell or support Jellyfin (Docker) itself — you install and run it on your own VPS. These are the official links to the project:

Read the project's own documentation before deploying. We credit upstream projects because we genuinely run and recommend them — see our full open-source directory.