Choosing a Host for Jellyfin: Five Questions That Decide It

Jellyfin makes the host matter more than Plex does

Plex quietly does three jobs for you. It hands your server an HTTPS address on plex.direct, it keeps a relay in reserve for when your connection will not cooperate, and it does sharing through accounts so nobody you invite ever sees an IP address. Jellyfin does none of that, on purpose. It is your server, on your address, with your certificate, and it does not phone home to anybody.

That is the right trade for a lot of people, and it is why Jellyfin keeps winning converts. It also means the box you put it on decides more than it would for Plex. Here are the five questions worth asking before you pay anybody, and what our own answers are.

1. Does the host hand you a working HTTPS address?

This is the big one and almost nobody writes about it.

Rent a bare VPS and install Jellyfin yourself and remote access becomes a small project: buy a domain, point an A record at the box, put a reverse proxy in front, get a certificate from Let's Encrypt, keep it renewing, and do it again the next time you rebuild. Until all of that is finished you are typing an IP and a port into your TV, and your browser is calling the page insecure. Some Jellyfin clients on current mobile systems will not talk to a plain HTTP server at all.

A managed host should have done that work once, for everybody. On a Bytesized Appbox, Jellyfin comes up at https://yourname.yourserver.bysh.me/jellyfin. Apache sits in front of it, the certificate is ours, and there is no port to forward and no DNS to edit. If you would rather use your own domain you still can, but you do not have to, and nothing is broken until you get round to it.

One catch is worth knowing before it bites you. Jellyfin is served under a path, not at the root: its base URL is /jellyfin. Anything you hand Jellyfin's address to has to carry that path. Point Jellyseerr or a TV client at the bare hostname and you get a redirect that looks like it worked, while every API call quietly comes back as a web page instead of data. Include the /jellyfin.

2. How many transcodes does the plan allow, and is there a GPU behind it?

Jellyfin's hardware acceleration is free. There is no Plex Pass equivalent to buy, and people read that and assume it is switched on. Free software does not conjure a GPU into a machine. Hardware transcoding needs the host to give your server a video device, and most shared seedboxes do not.

So ask two things, in this order:

• Does the plan I am buying give my media server access to a GPU?
• How many concurrent transcodes does this plan allow?

The second number is the one to get in writing, because it is the one you actually hit on a Sunday evening. Ours is published per plan on the plans page: 2 on Appbox Lite at EUR 5 for 500 GB, 3 on the 1 TB plan at EUR 11, and up the ladder to 10 on the 18 TB plan at EUR 96. A host that will not give you a number for this is telling you something.

Then the part that saves you the whole argument: the cheapest transcode is the one that never runs. A client that direct-plays the file costs the server almost nothing, and most buffering blamed on weak hardware is really a server transcoding when it did not need to. We wrote that up in do you need a GPU for Jellyfin, and the same logic in 4K is in 4K transcoding on a seedbox. Sort direct play out first and the transcode number stops mattering nearly as much.

3. Who decides when Jellyfin gets a major upgrade, and how do you go back?

Jellyfin moves fast, and 2026 is the year that stopped being free. Version 12.0 shipped on 8 September 2026 and 12.1 a week later on the 15th, both published as stable releases, both a major step off the 10.x line that most libraries were running.

A major is not a drop-in. A 10.x database meeting a 12.x schema is how people lose watch history, and plugins go quiet until their authors catch up. So whatever you rent, know the answer to two questions: who decides when your server moves to a new major, and what does going back look like.

On a VPS that is entirely you, which is fine if you enjoy it and grim at 11pm. On an Appbox the upgrade is a button in the panel, so the timing is yours rather than something that happens to you overnight.

Either way, one habit is worth more than any answer a host gives you. Before an upgrade, take a copy of the Jellyfin data folder:

cp -a ~/.local/share/jellyfin/data ~/jellyfin-data-backup

That folder holds your users, your watch state and your library database. It is small. Copying it costs you nothing and it is the difference between a bad evening and a lost library.

4. Is your media on the same disk as your downloader, at the same path?

Jellyfin scans a filesystem path. Everything good about it depends on that path being local and fast. If your downloader lives on one box and Jellyfin on another with a cloud mount bridging them, scans crawl, artwork times out, and playback stops at the worst possible moment.

On an appbox the whole stack sits on one machine and one disk. Sonarr and Radarr sort finished downloads into ~/media/TV Shows/ and ~/media/Movies/, which are the two libraries Jellyfin is pointed at the moment it is installed. Nothing is mounted, nothing is synced, and the file Jellyfin is playing is the same file your torrent client is still seeding.

Worth asking any host: are the media server and the download client on the same machine, and do they see the same paths? On some providers they do not, and you find out after you have paid.

5. Can the rest of the stack live next to it?

Jellyfin on its own is a player. The setup people actually want is Jellyfin plus something to ask for films, something to fetch them, and something to fix the subtitles. Check the host installs those too, on the same box, without you building containers by hand.

• Seerr so people can request things without messaging you
• Bazarr for subtitles that turn up on their own
• The full arr stack for the fetching

The five-minute test for any host

Before you pay, ask:

1. What URL does a fresh Jellyfin install get? If the answer is an IP and a port, remote access is your project, not theirs.
2. How many concurrent transcodes does this plan allow?
3. Does my media server get a GPU on this plan?
4. Who triggers a Jellyfin major upgrade, and how do I roll back?
5. Do Sonarr, Radarr, Jellyseerr and Bazarr run on the same box and see the same paths?

Five answers, five minutes, and you will know more than any ranked list can tell you.

When a managed host is the wrong answer

If you want to compile your own ffmpeg, pass through a GPU you chose yourself, or run Jellyfin behind your own domain with proxy rules you wrote, rent a dedicated server or a VPS and enjoy it. You will spend a weekend on remote access and you will own every upgrade after that, and for some people that is the good part. We priced that trade honestly in seedbox or a VPS.

If you would rather the address, the certificate and the wiring were already done, that is what we sell. Start at our Jellyfin hosting page, or go straight to setting it up. Still deciding between the two big media servers? We compared them without picking a winner in Plex vs Jellyfin.