Best VPS for Jellyfin in 2026
Updated Oct 2026 · 8 plans compared
Jellyfin's sizing question is really two questions: will the server transcode, and how much video will it push out. Direct play to a modern client barely touches the CPU, but one incompatible client forces a software transcode that will saturate every core on a small VPS — and every stream is sustained outbound bandwidth, hour after hour.
- Transcoding is the whole CPU story. Software transcoding a single 1080p stream wants roughly 4 fast cores; 4K software transcoding is not realistic on a shared-CPU VPS at all. Plan to direct-play, and keep client compatibility in mind when you build your library.
- Bandwidth is the running cost. A 1080p stream is around 10–25 Mbit/s sustained — a couple of hours of evening viewing moves tens of gigabytes, so a provider with a large or unmetered traffic allowance matters more than raw specs.
- Disk decides what you can host. Media libraries dwarf every other self-hosted workload, so favour providers that let you attach or grow storage, and expect to keep the bulk of the library on cheap volume storage rather than the boot NVMe.
- Check the licensing and legal picture for your region and provider before uploading anything — hosting your own media off-site is a different situation from a box on your own LAN.
The picks
Custom sizing lets you buy fast cores for the occasional transcode without over-paying for RAM you won't use, and hourly billing makes it cheap to test whether your clients direct-play before committing to a plan.
The bandwidth pick: a CPX22 clears Jellyfin's floor and the generous included traffic allowance is what actually matters when every viewer is a sustained multi-megabit stream.
The most storage per dollar of the group — the practical way to keep a media library on the same box as the server, with unmetered traffic so a heavy viewing week doesn't turn into an overage bill.
Unlimited traffic and included anti-DDoS suit a service that streams for hours at a time, and its EU footprint keeps latency low and data local for European viewers.
The picks, side by side
Prices verified Oct 2026 · How we benchmark →
Common questions
How much CPU does Jellyfin need for transcoding?
For direct play, almost none — the server just streams the file. For software transcoding, budget roughly 4 fast cores per simultaneous 1080p stream, and treat 4K software transcoding as out of reach on a typical shared-CPU VPS. Matching your library's codecs to your clients is far cheaper than buying CPU.
How much bandwidth does a Jellyfin server use?
Roughly 10–25 Mbit/s per 1080p stream, sustained for as long as someone is watching. Two people watching a couple of hours each evening can move a terabyte or more a month, so read the provider's traffic allowance and overage price before the specs.
Is a VPS a good place to run Jellyfin?
It works well when your library is modest and you want access from anywhere without opening your home network. If the library runs to many terabytes, cloud storage costs quickly overtake a box at home — in that case a home server with a VPN or tunnel back to it is usually the better answer.