Links checked 2026-10-14
Self-hosting Jellyfin
The self-hosted route instead of Plex, streaming subscriptions.
Running the container is simple. Making it pleasant — hardware acceleration, remote access, a library that is backed up — is where the time goes.
What it is
A media server for films, television, music and photos, with clients for televisions, phones, browsers and set-top boxes. It catalogs a library you already own and streams it to your devices.
What you actually need
This is the reader's own hardware and configuration, not a price. We describe what a job needs; we do not put a figure on what self-hosting costs, because that depends on the provider, the term and the disk you choose.
- The server
- The software is not the expensive part; the disks are. What the server needs depends on whether it transcodes video or just serves files your clients can already play.
- How it installs
- The official container images, run directly or with Compose, or a package for your distribution.
- Data store
- An embedded database inside the configuration directory.
- What grows
- The library decides everything. Films and television are measured in terabytes, and the configuration directory holds the metadata and watch state you would rather not rebuild.
Before it is safe to expose
- Hardware acceleration for transcoding, or clients that can play your files directly
- The configuration and cache directories on persistent storage
- A reverse proxy and TLS if it is reachable from outside your network
- A backup of the configuration directory so users, library and metadata survive
The trade-offs, specifically for Jellyfin
- Storage is the real cost of this entry: the application is free to run and the disks are not.
- Transcoding is processor work. Without hardware acceleration, one remote viewer can occupy a small VPS, and the documentation's container guidance is written with that in mind.
- The project's container documentation states plainly that running Jellyfin in a container on platforms other than Linux will not receive support and that some features are known to be broken there.
- Remote access means exposing a service that streams your own library; authentication, TLS and who gets an account are yours to decide.
And the six things you own from now on
These are true of every tool in this section, including Jellyfin. They are also the reason to decide against self-hosting, which is a legitimate decision.
- You own the updates. Security releases have to be applied by you, on your schedule, and a project that stops publishing releases becomes your problem to notice.
- You own the backups, and a backup is not a backup until you have restored from it once.
- You own the uptime. There is no status page to watch and no support line to call when it stops answering.
- You own the security patches, the TLS certificate, the reverse proxy and the firewall in front of it.
- You are the on-call rota. The failure mode nobody plans for is being the only person who knows how the thing was set up.
- The hardware has a running cost and a lifetime. Disks fail, and the replacement is on you.
What you give up
- A commercial streaming service's licensed catalogue and its zero maintenance
- The polish of a hosted media platform's remote access and apps
What you gain
- Your own library, your own metadata, no vendor account in the middle
- Clients on most platforms, with no subscription attached to the server software
The box it runs on
The software is not the expensive part; the disks are. What the server needs depends on whether it transcodes video or just serves files your clients can already play. That machine is the purchase this page is really about, and it is the one number we will not invent for you: the right size depends on the provider, the term and the disk, so check it on the provider's own page.
Hostinger
Hostinger's VPS product is the closest fit to a self-hosted application: its own page advertises root access, Docker and NVMe storage, with data centres in several regions.
See Hostinger's plansRead Hostinger's published pricing ↗DigitalOcean
Virtual machines billed as you use them, with separate volumes, snapshots and object storage for the parts you want to keep outside the server.
See DigitalOcean's plansRead DigitalOcean's published pricing ↗Hetzner
Cloud instances and dedicated servers with rates published per instance size, so the cost of a bigger box is visible before you move.
See Hetzner's plansRead Hetzner's published pricing ↗What to check before you buy
- A virtual machine you have root on, not a website plan with a control panel bolted on top.
- Snapshots or automated backups, and where those backups are stored.
- Block storage or object storage for the data that will outgrow the server's own disk.
- What the monthly rate renews at, rather than the first-term rate on the signup page.
- Where the data centre is, if the data has a jurisdiction attached to it.
The “See plans” links go through our own /go/ redirect and some are affiliate links, which pay us if you sign up. The descriptions and trade-offs on this page are written from the project's own documentation and are unaffected. The plain pricing link under each provider is not an affiliate link. See our disclosure.
Frequently asked questions about self-hosting Jellyfin
Answers restate the notes on this page or point at the project's own documentation. Self-hosting moves work to you rather than removing it, and these answers say so.
What is Jellyfin?
A media server for films, television, music and photos, with clients for televisions, phones, browsers and set-top boxes. We cover it as a replacement for Plex, streaming subscriptions.
What do you need to run Jellyfin yourself?
The official container images, run directly or with Compose, or a package for your distribution. The requirements table on this page lists the server, the data store, what grows and what else to arrange first. Setup steps are at Jellyfin's container installation guide.
How hard is Jellyfin to run yourself?
We rate it Moderate. Running the container is simple. Making it pleasant — hardware acceleration, remote access, a library that is backed up — is where the time goes.
What are the trade-offs of self-hosting Jellyfin?
Our notes list these costs. Storage is the real cost of this entry: the application is free to run and the disks are not. Transcoding is processor work. Without hardware acceleration, one remote viewer can occupy a small VPS, and the documentation's container guidance is written with that in mind.
What do you give up by running Jellyfin yourself?
You take on what Plex, streaming subscriptions used to do for you. A commercial streaming service's licensed catalogue and its zero maintenance. The polish of a hosted media platform's remote access and apps. Self-hosting moves that work to you rather than removing it.
What do you gain by running Jellyfin yourself?
Our notes list these. Your own library, your own metadata, no vendor account in the middle. Clients on most platforms, with no subscription attached to the server software.