Bandwidth management determines how much of your internet connection Plex uses when streaming to remote users and how much of your local network it consumes for local playback. Without management, a few simultaneous streams can saturate your connection — causing buffering for everyone including non-Plex traffic. This guide covers bandwidth control at every level.
Understanding Plex Bandwidth Usage
Direct Play
When a client direct plays a file, Plex streams it at the file's native bitrate. A 4K HDR Blu-ray remux at 60-80 Mbps consumes that full bandwidth between the server and client. For local playback this is usually fine. For remote streaming, it may exceed both your upload bandwidth and the remote user's download bandwidth.
Transcoding
When Plex transcodes, it re-encodes the video at a lower bitrate. The output bitrate is determined by the quality setting. Transcoding gives you control over bandwidth per stream but costs CPU or GPU resources on the server.
Server-Level Bandwidth Controls
Remote Streaming Quality
Set a maximum quality for remote streams:
Go to Settings then Remote Access.
Set the Internet upload speed to match your actual upload bandwidth.
Plex uses this value to determine how much bandwidth is available for remote streams.
Per-User Limits
Set maximum streaming quality per user in their sharing settings. This caps the bitrate they can request:
Low bandwidth users: Limit to 4-8 Mbps. Suitable for mobile viewing or slow connections.
Medium bandwidth users: Limit to 10-20 Mbps. Good quality on most displays.
High bandwidth users: Set to Maximum or Original for direct play when their connection supports it.
Client-Side Quality Settings
Each Plex client has quality settings that the user controls:
Remote streaming quality: Limits the stream quality when watching away from the local network.
Home streaming quality: Usually set to Maximum for local playback.
Mobile data quality: Limits quality when on cellular data to conserve data usage.
Educate users about these settings. Many remote streaming issues are caused by clients requesting Original quality over connections that cannot sustain it.
Bitrate Reference
Quality Level
Approximate Bitrate
Best For
720p 2 Mbps
2 Mbps
Phones, very slow connections
720p 4 Mbps
4 Mbps
Tablets, moderate connections
1080p 8 Mbps
8 Mbps
Laptops, good connections
1080p 12 Mbps
12 Mbps
TVs, fast connections
1080p 20 Mbps
20 Mbps
High quality remote streaming
Original
Varies (10-80+ Mbps)
Direct play, local network
Upload Bandwidth Planning
Calculating Requirements
Estimate your upload bandwidth needs based on expected simultaneous streams:
Each remote stream at 1080p 8 Mbps uses approximately 8-10 Mbps of upload (video plus overhead).
Three simultaneous streams at 8 Mbps need approximately 25-30 Mbps upload.
Reserve 20-30% of total upload for non-Plex traffic (video calls, cloud sync, general browsing).
When Upload Is Limited
If your upload bandwidth is limited (10-20 Mbps is common for residential connections):
Limit the number of simultaneous remote streams in Plex settings.
Set per-user bitrate limits to lower values so more users can stream simultaneously.
Encourage users to set their remote quality to 4-8 Mbps rather than Original.
Router QoS
Quality of Service (QoS) on your router prioritizes traffic types. Configure QoS to prioritize Plex traffic:
Assign the Plex server's IP address high priority for outbound traffic.
Prioritize traffic on port 32400 (Plex's default port).
This ensures Plex streams remain smooth even when other devices are using bandwidth.
Alternatively, use QoS to limit Plex's bandwidth to prevent it from consuming your entire upload:
Cap Plex traffic at 70-80% of your upload speed.
The remaining bandwidth stays available for other uses.
Local Network Bandwidth
Wired vs Wireless
Gigabit Ethernet: 1 Gbps is sufficient for even the highest bitrate content. Multiple simultaneous 4K streams have no bandwidth issues on wired connections.
Wi-Fi 5 (802.11ac): Delivers 200-400 Mbps in practice. Adequate for most content but may struggle with multiple simultaneous 4K remux streams.
Wi-Fi 6 (802.11ax): Improved throughput and better handling of multiple devices. Suitable for all Plex use cases.
NAS Bandwidth
If media is stored on a NAS, the connection between the Plex server and NAS is a potential bottleneck:
Use Gigabit Ethernet or faster between the server and NAS.
A single 4K remux stream needs 60-80 Mbps. Gigabit Ethernet handles about 10 simultaneous streams at this bitrate.
Link aggregation (LACP) doubles the available bandwidth with two Ethernet connections.
Plex Relay
When direct connections between the Plex server and remote clients are not possible (double NAT, CGNAT, restrictive firewall), Plex uses its relay service. The relay is limited to 2 Mbps for non-Plex Pass subscribers and 10 Mbps for Plex Pass. This is significantly lower than direct streaming.
To avoid relay limitations, configure port forwarding on your router so remote clients can connect directly to your server.
Monitoring Bandwidth Usage
Plex Dashboard
The Plex dashboard shows active streams with their current bitrate and whether they are direct play or transcode. Monitor this during peak usage to understand your bandwidth consumption.
Tautulli
Tautulli provides detailed bandwidth history:
Peak concurrent streams and their total bandwidth.
Per-user bandwidth consumption over time.
Trends showing whether your bandwidth needs are growing.
Troubleshooting
Remote Users Buffering
Check if the stream exceeds the user's download bandwidth. Reduce their quality limit.
Verify your upload bandwidth is not saturated. Check the Plex dashboard for total active stream bitrate.
Test whether Plex is using relay (limited bandwidth). Configure port forwarding for direct connections.
Local Playback Buffering
Check the network connection between client and server. Use a wired connection for 4K content.
If media is on a NAS, verify the NAS connection speed. Test with iperf.
Check server disk I/O. Slow storage can cause buffering even with sufficient network bandwidth.