Plex VPS Hosting

Plex hosting means running Plex Media Server on a VPS, so your library stays reachable with no computer switched on at home. Every viewer counts as remote, because the server is in a data center outside your home network. A VPS has no GPU, so every transcode runs on the CPU cores. GreenGeeks gives you root access to install Plex from its package and choose its libraries and settings. Plex expects servers to run at home and says hosted ones may not work with every provider, so test yours early.

Plex itself needs an Intel Core i3 or equivalent, and Plex says 4 GB of RAM is typically more than enough. Plex publishes RPM packages for Fedora and CentOS-style systems, and they install on AlmaLinux 9, the OS on GreenGeeks VPS. Plex bundles its own transcoder, so you don't need FFmpeg. The bigger needs come from your viewers. Each 1080p H.264 transcode needs a PassMark CPU score of about 2,000, and HEVC or 10-bit video needs a lot more. Storage depends on your library. A 2-hour 1080p movie takes about 9 GB.

Plan on two bills, one for the server and one for remote streaming. A direct-play library fits GreenGeeks' 4 GB plan at $9.99 a month, renewing at $19.99. Plex Media Server itself is free, but every stream from a VPS counts as remote, so somebody has to pay for remote playback. The server admin's Plex Pass covers everyone they share with. It costs $6.99 a month, $69.99 a year or $749.99 for lifetime. Without it, each viewer needs their own Remote Watch Pass at $2.99 a month. The admin's pass also unlocks Plex Dash, an app for keeping an eye on the server.

The Plex data folder is the part to protect, since it keeps your watch states, metadata and server settings. It lives at /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/, and GreenGeeks leaves backups on a self-managed VPS to you. A weekly cron job can do the work. It stops Plex, archives that folder with tar while skipping Cache, starts Plex again and copies the archive off the server. Leave Plex's built-in database backup on too. It only keeps 3 copies of the database, so it isn't a full backup.

A move comes down to copying the Plex data folder to the new server. On the old server, turn off "Empty trash automatically after every scan" and stop Plex. Install Plex on the VPS and leave it stopped, then copy the data directory in and set plex:plex ownership. Upload the media, add the new folder paths to each library, scan and remove the old paths. Plex only supports moves between servers on the same operating system, so some Windows or macOS settings may not carry over. Check that your library fits the plan's disk before you start.

Running Plex on a VPS is legal, and what matters is the content you put on it. Plex's terms, revised October 30, 2025, grant a personal, non-commercial license. They ban sharing or distributing content without permission, and they ban selling access to Plex. Plex can suspend or disable accounts that break those terms, and your host's terms apply too. Plex has acted against a whole provider before. It blocked servers hosted at Hetzner starting October 12, 2023, citing large-scale violations from that provider.

Pick by transcodes and library size, since RAM rarely limits Plex. The 4 GB plan has 2 vCPU cores and 80 GB of SSD storage, enough for direct play and about one 1080p transcode. The 8 GB plan has 4 vCPU cores and 160 GB, for about 1 to 2 transcodes. The 16 GB plan has 8 vCPU cores and 320 GB, for about 3 transcodes and a bigger library. A 2-hour 1080p movie at 10 Mbps is about 9 GB, and 4K runs 36 to 45 GB. Even 320 GB fits only a small library.

Install it from Plex's own RPM repository. Add the repo.plex.tv RPM source and Plex's signing key, then run dnf install plexmediaserver. After that, normal system updates keep Plex current. A headless server has no browser for the first-time setup, so open an SSH tunnel with ssh -L 32400:localhost:32400 and go to localhost:32400/web on your own computer. Plex only offers first-time setup to a local connection, and the tunnel counts as one. Sign in there and claim the server.

Yes, on the CPU. The physical server under a VPS doesn't pass its video hardware through to the virtual machines on it, so hardware transcoding isn't possible. Software transcoding still works on a VPS, and on GreenGeeks it runs on the plan's 2 to 16 vCPU cores. Plex budgets about 2,000 PassMark per 1080p H.264 transcode, 12,000 for 4K SDR and 17,000 for 4K HDR. Cut transcodes where you can. Use files your devices can direct play, and watch for burned-in subtitles and low remote bandwidth, which often force Plex to transcode.

You run Plex and its libraries, settings and streams. GreenGeeks looks after the hardware and network, and on a self-managed VPS the operating system and anything you install on top are yours to look after. The two jobs that come up most are disk space and stream limits. Keep an eye on free space, since all your media is on the plan's SSD. Set limits on upload speed and on how many transcodes run at once, so one viewer can't slow down the rest. Most of those limits need Plex Pass. Plex Dash, another Plex Pass feature, shows the server and its streams.