anas101siddiqui
10-10-2026, 03:14 AM
I see the same questions come up again and again: "Why does my Plex buffer when I am away from home?" and "What server specs do I need for remote streaming?" So here is a short breakdown of the numbers worth knowing before you plan a remote setup, whether at home or on a VPS.
1. Bandwidth: the number most people forget is upload speed
When you stream remotely, your server's upload speed is the limit, not your download speed. Data use per hour depends on bitrate:
4 Mbps (720p) = about 1.8 GB per hour
8 Mbps (1080p) = about 3.6 GB per hour
20 Mbps (high quality 1080p) = about 9 GB per hour
40 Mbps (4K) = about 18 GB per hour
60 Mbps (4K remux) = about 27 GB per hour
Three viewers at 8 Mbps need about 24 Mbps of upload at the same moment. Many home connections offer far less upload than download, which is the real cause of a lot of remote buffering.
2. CPU: direct play is cheap, transcoding is not
If the client plays your file as it is (direct play), CPU use is tiny. When Plex has to convert the video (transcoding), it gets heavy. Plex's own guidance for ONE transcoding stream, in PassMark points:
720p, 4 Mbps, H.264: about 1,500
1080p, 10 Mbps, H.264: about 2,000
4K SDR, 40 Mbps, HEVC: about 12,000
4K HDR, 50 Mbps, HEVC: about 17,000
These are per stream, so three simultaneous 1080p transcodes need roughly three times the budget. Single thread speed matters too, not only core count.
3. Why remote streams transcode more often than local ones
The viewer's app or connection forces a lower bitrate
The client cannot decode the codec (HEVC and AV1 on older devices)
Image based subtitles (PGS) get burned into the video
HDR content shown on a non-HDR screen needs tone mapping
Quick fixes: keep clients on original quality where possible, use H.264/AAC for wide compatibility, prefer SRT subtitles, and keep a 1080p copy of your biggest 4K files.
4. Storage: do the math before you buy
A 1080p movie is often 5 to 15 GB, and a 4K remux can pass 50 GB. A 200 GB drive holds a curated library, not a huge archive. For large collections, a hybrid works well: bulk storage at home, and a smaller always on server for the library you actually share.
5. Home server vs VPS: honest pros and cons
Home server: cheap bulk storage, but limited upload, a dynamic IP, and it depends on your power and router.
VPS: fast network port, fixed IP, 24/7 uptime and no noise or power bill at home. But storage per dollar is lower, bandwidth usually has a monthly quota, and there is normally no GPU, so transcoding runs on the CPU.
6. Heads up on Plex's remote streaming rules
Plex has tightened remote streaming. Since March 23, 2026, remote streaming of personal media on its smart TV apps requires either the server owner to have a Plex Pass or the viewer to have a Remote Watch Pass. Check Plex's plans page for the current details, because it affects any offsite server.
7. A VPS option (disclosure)
Disclosure: I run QloudHost, which recently launched a Plex VPS service. It uses KVM with NVMe storage and dedicated AMD EPYC vCPU cores, a 1 Gbps+ port and a dedicated IPv4, hosted in Amsterdam, with plans from 2 vCPU/4 GB to 8 vCPU/16 GB and a 14 day money-back guarantee. Details here: https://qloudhost.com/offshore-vps-hosting/plex
Any provider with a refund period works for testing, so my real advice is to test your actual files and clients for a few days before committing. And only host media you own or have the rights to stream.
What is your biggest remote streaming bottleneck right now: upload speed, CPU, or storage?
1. Bandwidth: the number most people forget is upload speed
When you stream remotely, your server's upload speed is the limit, not your download speed. Data use per hour depends on bitrate:
4 Mbps (720p) = about 1.8 GB per hour
8 Mbps (1080p) = about 3.6 GB per hour
20 Mbps (high quality 1080p) = about 9 GB per hour
40 Mbps (4K) = about 18 GB per hour
60 Mbps (4K remux) = about 27 GB per hour
Three viewers at 8 Mbps need about 24 Mbps of upload at the same moment. Many home connections offer far less upload than download, which is the real cause of a lot of remote buffering.
2. CPU: direct play is cheap, transcoding is not
If the client plays your file as it is (direct play), CPU use is tiny. When Plex has to convert the video (transcoding), it gets heavy. Plex's own guidance for ONE transcoding stream, in PassMark points:
720p, 4 Mbps, H.264: about 1,500
1080p, 10 Mbps, H.264: about 2,000
4K SDR, 40 Mbps, HEVC: about 12,000
4K HDR, 50 Mbps, HEVC: about 17,000
These are per stream, so three simultaneous 1080p transcodes need roughly three times the budget. Single thread speed matters too, not only core count.
3. Why remote streams transcode more often than local ones
The viewer's app or connection forces a lower bitrate
The client cannot decode the codec (HEVC and AV1 on older devices)
Image based subtitles (PGS) get burned into the video
HDR content shown on a non-HDR screen needs tone mapping
Quick fixes: keep clients on original quality where possible, use H.264/AAC for wide compatibility, prefer SRT subtitles, and keep a 1080p copy of your biggest 4K files.
4. Storage: do the math before you buy
A 1080p movie is often 5 to 15 GB, and a 4K remux can pass 50 GB. A 200 GB drive holds a curated library, not a huge archive. For large collections, a hybrid works well: bulk storage at home, and a smaller always on server for the library you actually share.
5. Home server vs VPS: honest pros and cons
Home server: cheap bulk storage, but limited upload, a dynamic IP, and it depends on your power and router.
VPS: fast network port, fixed IP, 24/7 uptime and no noise or power bill at home. But storage per dollar is lower, bandwidth usually has a monthly quota, and there is normally no GPU, so transcoding runs on the CPU.
6. Heads up on Plex's remote streaming rules
Plex has tightened remote streaming. Since March 23, 2026, remote streaming of personal media on its smart TV apps requires either the server owner to have a Plex Pass or the viewer to have a Remote Watch Pass. Check Plex's plans page for the current details, because it affects any offsite server.
7. A VPS option (disclosure)
Disclosure: I run QloudHost, which recently launched a Plex VPS service. It uses KVM with NVMe storage and dedicated AMD EPYC vCPU cores, a 1 Gbps+ port and a dedicated IPv4, hosted in Amsterdam, with plans from 2 vCPU/4 GB to 8 vCPU/16 GB and a 14 day money-back guarantee. Details here: https://qloudhost.com/offshore-vps-hosting/plex
Any provider with a refund period works for testing, so my real advice is to test your actual files and clients for a few days before committing. And only host media you own or have the rights to stream.
What is your biggest remote streaming bottleneck right now: upload speed, CPU, or storage?