← Blog
How to Reduce Plex Buffering: Every Cause and Fix
Buffering has multiple causes
Buffering is the most common Plex complaint, and it has at least six different causes. Most troubleshooting guides suggest checking your network and leave it at that. The reality is that each cause has a specific fix, and identifying the correct cause is more important than trying generic solutions.
Cause one: transcoding bottleneck
The most frequent cause of Plex buffering is a server that cannot transcode fast enough to maintain real-time playback. The symptom is buffering that starts after a few seconds of smooth playback, with the Plex dashboard showing high CPU usage and the transcode session falling behind real time.
How to fix it
- Enable hardware transcoding: a GPU with a hardware encoder handles transcoding far more efficiently than software encoding on the CPU. Even a budget GPU with a modern hardware encoder eliminates most transcoding bottlenecks
- Reduce the transcoding quality demand: lower the remote streaming quality setting in the client app. A lower resolution or bitrate requires less server processing power per stream
- Eliminate the transcode entirely: configure your media and client devices for direct play. If the client supports the source codec natively, no transcoding occurs and server load drops to near zero
Cause two: insufficient upload bandwidth
Remote streams consume your home internet upload bandwidth. If the combined bitrate of all active remote streams exceeds your available upload speed, every stream buffers. The symptom is buffering that correlates with the number of simultaneous remote users rather than server resource usage.
How to fix it
- Set remote quality limits: cap the maximum quality for remote streams to reduce bandwidth consumption per stream
- Upgrade your internet plan: if available, a plan with higher upload speeds directly increases the number of simultaneous remote streams your connection can sustain
- Enable bandwidth management: Quality of Service settings on your router prioritize Plex traffic and prevent other network activity from competing for upload bandwidth
Cause three: slow storage
If your media is stored on a slow disk, the server cannot read data fast enough to sustain playback, particularly when multiple streams read from the same drive simultaneously. The symptom is buffering that worsens as more streams become active, with the Plex dashboard showing low CPU and GPU usage but streams still falling behind.
How to fix it
- Check disk health: failing drives develop slow sectors that cause read delays. Monitor SMART data for signs of drive degradation
- Separate media and transcode directories: place the transcode temporary directory on a fast SSD while keeping media on bulk storage. This prevents transcode write operations from competing with media read operations on the same disk
- Upgrade to faster storage: SSDs eliminate mechanical seek times that cause read delays on spinning disks, particularly under concurrent multi-stream load
Cause four: client-side network issues
The client device network connection may be the bottleneck rather than the server. Wi-Fi interference, distance from the router, network congestion, and outdated wireless adapters all cause buffering that appears identical to a server-side problem.
How to fix it
- Use a wired connection: Ethernet eliminates wireless variables entirely. If the client device supports Ethernet, test with a wired connection to rule out Wi-Fi as the cause
- Reduce Wi-Fi interference: move the client closer to the router, switch to the 5 GHz band if available, and minimize competing devices on the same wireless channel
- Test with a different device: if buffering occurs on one client but not another on the same network, the issue is the client device or its network adapter rather than the server or internet connection
Cause five: Plex relay fallback
When your server cannot establish a direct connection to a remote client, Plex routes the stream through its relay servers. Relay connections are bandwidth-limited and produce significantly degraded playback quality. The symptom is consistently low quality and frequent buffering specifically for remote users, with the Plex dashboard indicating that the stream is using a relay connection.
How to fix it
- Configure port forwarding: forward the Plex media server port on your router to your server local IP address. This allows direct connections from remote clients without relay fallback
- Check your server remote access settings: verify that the Plex remote access indicator shows a successful connection rather than an error
- Contact your ISP about CGNAT: some ISPs use carrier-grade NAT that prevents port forwarding from working. If your ISP uses CGNAT, you may need to request a public IP address or use an alternative remote access method
Cause six: Plex server configuration
Several Plex server settings affect buffering behavior. The transcoder default throttle buffer setting controls how far ahead the server transcodes. Increasing this buffer allows the server to build a larger playback buffer that absorbs momentary processing slowdowns. The network buffer size in advanced settings affects how much data is held in memory during streaming. Default values work for most setups, but high-stream-count servers may benefit from tuning these settings.
Eliminate buffering with PlexBeam
PlexBeam removes the two most common buffering causes, transcoding bottlenecks and upload bandwidth limits, by handling remote transcoding and delivery on dedicated infrastructure with ample bandwidth and GPU capacity.