Control Plex Streaming Quality and Throttling
Published 2026-10-16 · PlexBeam
Plex gives you multiple layers of control over streaming quality. Server-side throttling sets the maximum bandwidth any stream can consume. Per-user limits cap individual viewers. Client-side settings let users adjust their own quality. Understanding how these layers interact helps you balance bandwidth usage with the viewing experience your users expect.
Server-Side Quality Controls
Upload Speed Setting
The primary server-side throttle is the upload speed setting:
- Go to Settings then Remote Access.
- Set the Internet upload speed to match your actual measured upload bandwidth.
Plex uses this value to calculate how much bandwidth is available for all remote streams combined. When total demand approaches this limit, Plex restricts the quality offered to new streams. Setting this accurately prevents Plex from overcommitting bandwidth and causing buffering across all streams.
Maximum Remote Stream Quality
Under the same Remote Access settings, you can set a maximum quality for remote streams. This caps the quality Plex will ever deliver to a remote client, regardless of that client's settings or available bandwidth:
- Original: No server-side cap. Clients can request any quality up to the original file bitrate.
- Specific quality levels (720p 4 Mbps, 1080p 8 Mbps, etc.): Hard caps the maximum bitrate for all remote streams.
Setting a specific cap is useful when your upload bandwidth cannot support original quality for multiple users simultaneously.
Per-User Quality Limits
Set individual quality limits for each shared user:
- Go to Settings then Manage Library Access (or the sharing/friends settings).
- Select a user.
- Set their maximum streaming quality.
Per-user limits override the user's own client settings if the user requests higher quality than allowed. Use these to manage bandwidth fairly across your user base:
- Casual viewers on slow connections: 720p 4 Mbps keeps streams smooth on limited bandwidth.
- Regular viewers on broadband: 1080p 8-12 Mbps provides good quality without excessive bandwidth.
- Power users on fast connections: 1080p 20 Mbps or Maximum for the best quality your library can deliver.
Bandwidth Fairness
Without per-user limits, one user streaming 4K at 60 Mbps can consume your entire upload capacity, leaving nothing for other remote viewers. Per-user caps distribute bandwidth more evenly. If you have 50 Mbps upload and want to support 4 simultaneous users, capping each at 1080p 10 Mbps (about 12 Mbps with overhead) fits within your budget.
Client-Side Quality Settings
Each Plex client has its own quality settings that the viewer controls:
Remote Streaming Quality
The maximum quality the client requests when watching from outside the local network. Options range from 720p 2 Mbps up to Original. If set higher than the server or per-user limit, the server limit takes precedence.
Home Streaming Quality
Quality for playback on the local network. Usually set to Maximum since LAN bandwidth is not a constraint. Setting this lower than Maximum forces unnecessary transcoding for local playback.
Mobile Data Quality
Quality when streaming over cellular data. Lower settings conserve mobile data allowances. This only applies when the client detects it is on a cellular connection.
Automatic Quality
Some Plex clients have an Automatic quality option that lets the client and server negotiate the best quality based on measured bandwidth. This generally works well but can cause brief quality drops during network fluctuations. Setting a specific quality avoids the adjustment periods.
How Quality Layers Interact
When a stream starts, Plex evaluates quality limits from most restrictive to least:
- Server upload speed budget: If the total bandwidth of all active streams plus this new one would exceed the configured upload speed, Plex limits the quality.
- Server maximum remote quality: If set, this caps the quality regardless of available bandwidth.
- Per-user limit: If set for this user, their stream cannot exceed this quality.
- Client setting: The client's own quality preference applies if it is more restrictive than the above.
The most restrictive setting always wins. A user with a per-user cap of 1080p 8 Mbps cannot stream at higher quality even if the server has available bandwidth and their client is set to Original.
Transcoding and Quality
When Plex limits quality below the original file's bitrate, it transcodes the stream in real time:
- The server re-encodes the video at the target bitrate.
- This consumes CPU or GPU resources on the server.
- Transcode quality is generally good but slightly below what an offline encode at the same bitrate would produce, since real-time encoding has less time for optimization.
Direct play (original quality with no server processing) always provides the best quality and uses the least server resources. Throttling is a tradeoff: lower bandwidth usage in exchange for some quality reduction and server processing cost.
Quality Settings for Common Scenarios
Limited Upload (10-20 Mbps)
- Server max remote quality: 1080p 8 Mbps.
- Per-user caps: 720p 4 Mbps for most users.
- Expected simultaneous streams: 2-3 at 720p, 1-2 at 1080p.
Moderate Upload (30-50 Mbps)
- Server max remote quality: 1080p 20 Mbps.
- Per-user caps: 1080p 8 Mbps for standard users, 1080p 20 Mbps for premium users.
- Expected simultaneous streams: 3-5 at mixed quality.
High Upload (100+ Mbps)
- Server max remote quality: Original.
- Per-user caps: 1080p 20 Mbps standard, Maximum for trusted users.
- 4K direct play becomes viable for select users.
Monitoring Quality Settings in Action
Use Tautulli to verify your quality settings work as intended:
- Check actual stream bitrates against your per-user limits. If users consistently hit their cap, the limit is effective.
- Monitor transcode percentage. High throttling with many transcodes means your server is working hard to enforce quality limits.
- Track user complaints. If users report poor quality, their limits may be too aggressive for their content preferences.
Troubleshooting
User Gets Lower Quality Than Their Limit
- The server's total bandwidth budget may be exhausted by other streams. Check total active stream bandwidth.
- The user's own client quality setting may be more restrictive than their server-side limit.
- Network conditions between server and client may not support the allowed quality. Check for relay usage.
Quality Limit Not Being Enforced
- Verify the per-user limit is set on the correct user account. Managed users and regular Plex accounts have separate settings.
- Local network playback bypasses remote quality limits. If the user is on the same network, home streaming quality applies instead.
All Streams Dropping to Low Quality
- The upload speed setting may be too low. Verify it matches your actual measured upload bandwidth.
- Your actual upload bandwidth may be lower than expected. Run a speed test during the problem period.
- Non-Plex traffic may be consuming upload bandwidth. Check total network usage.