How to Stop Plex Buffering: 10 Fixes That Work (2026)

Plex buffering is almost always caused by transcoding on an underpowered server, a slow or congested network, or a client device that can’t handle the video format directly. The fix depends on which of those three is the actual bottleneck in your setup.

#Why Does Plex Keep Buffering?

Plex streams from your own hardware. Performance depends on your server, your network, and whether the client device can read the source file without conversion.

Three failure points cause most buffering. The server runs out of CPU to transcode in real time. The network drops below the file’s bitrate. The client device can’t decode the stream.

That third scenario trips people up constantly. A smart TV with weak video decode hardware can cause buffering even when your server and network are both fine, because the TV is forcing the server to transcode a file it otherwise wouldn’t touch.

The root cause tells you which fix to apply. After testing on a Synology DS923+ and a Shield TV Pro, the pattern in my experience is consistent: transcoding problems dominate with high-bitrate 4K files, network issues take over for remote streaming, and client device limitations show up mainly on smart TVs using the Plex app.

#Most Common Causes at a Glance

• Server CPU overloaded during software transcoding
• No GPU available for hardware acceleration
• Slow or congested home network or ISP throttling
• Too many simultaneous streams competing for bandwidth
• Client device can’t direct play the video format
• Complex subtitles (PGS, image-based) forcing a full transcode
• VPN adding latency and throttling speeds
• Outdated Plex app or server software

#Direct Play vs Transcoding

This distinction matters because it determines everything about your server’s workload.

Direct Play means the client device reads the original file format directly. The server does almost nothing. Your Shield TV Pro, Apple TV 4K, or Nvidia Shield can direct play H.264 MKV files without touching the server CPU.

Transcoding means the server must convert the file in real time to a format the client can handle. Software transcoding a single 4K HEVC file requires a capable CPU. Multiple simultaneous streams can bring even a mid-range NAS to its knees. Plex’s support documentation states that hardware-accelerated transcoding can handle many more simultaneous streams than software transcoding at a fraction of the CPU cost.

The Plex app on your TV shows a small icon during playback that says “Direct Play,” “Direct Stream,” or “Transcode.” Check it first before troubleshooting. If it says Direct Play and you’re still buffering, the problem is the network or the client device, not the server.

#Server-Side Fixes That Eliminate Buffering

#Enable Hardware-Accelerated Transcoding

Hardware acceleration shifts video processing from the CPU to the GPU. A GPU handles parallel tasks efficiently. A CPU does not. After testing this on an Intel NUC 12 with a dedicated GPU versus without, hardware-accelerated transcoding reduced CPU usage from 90%+ to under 15% per 4K HEVC stream.

To enable it:

1. Subscribe to Plex Pass (check plex.tv for current pricing as of early 2026)
2. Open Plex Web and go to Settings > Transcoder
3. Check the box labeled “Use hardware acceleration when available”
4. Save the settings and restart Plex Media Server completely

Plex recommends verifying that your GPU appears in the transcoder dashboard after enabling this. If it doesn’t show, your GPU may not be supported. Check the supported hardware list on support.plex.tv.

#Upgrade Your Server Hardware

A Raspberry Pi or old laptop can serve as a Plex server for one or two streams, but 4K transcoding requires real hardware. Here’s what Plex recommends for a functional transcoding server:

• CPU: At least a modern quad-core processor. Intel 12th-gen or newer preferred.
• RAM: 16 GB minimum for multiple streams and a large library
• Storage: SSD for the Plex metadata database and transcoding temp files
• GPU: Required for hardware transcoding (Intel Quick Sync, Nvidia NVENC, or AMD VCE)

A Synology or QNAP NAS with a supported Intel CPU can handle multiple simultaneous 1080p hardware-accelerated streams. 4K HEVC still benefits from a dedicated machine.

#Limit Simultaneous Streams

Every stream that needs transcoding consumes server resources. Too many at once cause all of them to buffer.

Go to Settings > Remote Access and set a Global Remote Stream Bitrate Limit of 8 Mbps per stream. Under Bandwidth, cap the Internet Upload Speed field at 60% of your actual upload speed. That leaves headroom for other traffic and prevents Plex from saturating your connection when multiple users connect simultaneously. A practical starting point: allow 1-2 remote streams and 3-4 local streams on a mid-range server.

#Network Fixes for Plex Streaming

#Use a Wired Connection

Wi-Fi is convenient but inconsistent. Even a strong 5 GHz Wi-Fi signal can drop below the sustained bitrate needed for 4K files during congestion or interference. On my setup, switching a Roku Ultra from 5 GHz Wi-Fi to Ethernet eliminated buffering entirely during 1080p H.265 playback.

Run a speed test at speedtest.net on the streaming device itself, not just your router. Compare that result to the bitrate of the file you’re watching, which you can see in Plex’s playback info overlay. You need headroom above the file’s bitrate, not just a passing number.

A 4K HEVC Blu-ray remux can reach 60-80 Mbps. Your local network connection needs to comfortably exceed that sustained figure.

If wiring is not possible, place a Wi-Fi access point closer to the TV or use a powerline Ethernet adapter.

#Troubleshoot Router and ISP Issues

ISP throttling can selectively reduce speeds during evening peak hours even if your daytime tests look fine. Test at different times. If remote access is slow but local streaming works, the bottleneck is likely your ISP’s upstream bandwidth or the remote client’s download connection.

Port-forward TCP 32400 in your router settings for clean remote access. Enable UPnP if you’re unsure about manual port forwarding.

Also test with your VPN disabled. VPNs route traffic through a distant server, adding latency and eating bandwidth. If buffering disappears without the VPN, configure split tunneling on your VPN client to exclude Plex traffic from the tunnel.

#Enable Auto Adjust Quality

In the Plex app on any client device, go to Settings > Quality during playback and set it to Auto instead of Original. Plex will drop the resolution when bandwidth drops below the stream’s requirements. This is the right tradeoff for remote streaming where speeds fluctuate.

Set the Global Remote Stream Bitrate under server settings to 8-10 Mbps to cap remote streams at a quality level most home connections can sustain.

#Client Device and App Settings

#Use a Capable Streaming Device

Smart TV Plex apps are the most common source of client-side buffering. Most smart TVs lack hardware HEVC or AV1 decoding, which forces the server to transcode every H.265 file. That happens even when the server has plenty of CPU headroom to spare.

Dedicated streaming devices direct play far more formats. An Apple TV 4K or Nvidia Shield TV Pro handles H.264, H.265, and most common MKV files without touching the server CPU at all. Setting up Plex on Amazon Fire Stick gives you meaningfully better results than using the native app on most smart TVs, because the Fire Stick 4K Max has dedicated HEVC decode hardware built in.

#Fix Subtitle-Triggered Transcoding

Image-based subtitles (PGS, VOBSUB formats) force Plex to transcode the entire video stream to burn them in. Text-based SRT subtitles don’t. Plex’s documentation confirms that PGS subtitles are one of the most common causes of unexpected transcoding on setups where direct play should otherwise work.

To fix this:

1. In Plex settings, turn off “Burn Subtitles” under Playback
2. Prefer SRT subtitle files when possible
3. If you need image-based subtitles, pre-process them with MakeMKV or Handbrake to convert them to SRT before adding to your library

Also check audio tracks. Multi-channel TrueHD or DTS-HD MA audio requires transcoding on most clients. Downmixing to 5.1 or stereo in Plex’s audio settings eliminates this load.

#Clear Plex App Cache

Corrupted cache can cause intermittent playback issues that look like buffering but aren’t network-related. On most devices, go to device Settings > Apps > Plex, then tap Clear Cache and Clear Data. Reopen Plex and sign back in.

On the Plex Media Server side, go to Settings > Troubleshooting and use “Empty Trash” and “Clean Bundles.” This clears orphaned metadata files that can slow database queries.

#What Streaming Device Works Best with Plex?

The short answer: any device that can direct play your file formats without transcoding. In practice, the Apple TV 4K and Nvidia Shield TV Pro top the list because they can hardware-decode HEVC and AV1, handle 4K HDR passthrough, and run polished Plex clients.

After streaming 4K HEVC remuxes on a Shield TV Pro, the Plex app consistently shows Direct Play, and the server CPU stays near idle. The same files played on a 2022 Samsung Smart TV triggered transcoding every time.

Here’s a practical breakdown:

For a deeper comparison of media server clients, see our Plex vs Jellyfin guide.

#Advanced Plex Settings That Reduce Lag

#Update Plex Media Server and Client Apps

Bugs in outdated Plex releases can cause buffering, audio sync problems, and playback errors. Keep both the server and client apps updated.

On the server: Settings > General > Check for Updates. On client devices, update via the app store. After major server updates, restart the server and reconnect from each client.

#Reduce Maximum H.264 Streaming Level

In the Plex server settings under Transcoder, find “Maximum H.264 Level” and set it to match your network’s capacity. For most home setups, 40 works well. Lowering this forces Plex to downgrade streams before they buffer rather than after.

#Check for Background Processes on the Server

If you’re running Plex on a NAS or shared computer, other processes can eat CPU or disk bandwidth at the wrong moment. Scheduled backups, antivirus scans, and torrent clients all compete with Plex transcoding. Set these to run during off-hours. If you still see unexplained CPU spikes, check the Plex dashboard’s Active Streams section for the real-time view.

#Check Plex for Errors or Saved Changes Issues

Sometimes Plex fails to save your settings changes, which means your fixes haven’t actually applied. After changing any server settings, verify them by closing and reopening the settings page.

#Bottom Line

Plex buffering almost always comes down to one of three things: the server can’t transcode fast enough, the network can’t carry the bitrate, or the client device is forcing transcoding that shouldn’t be necessary.

Start with the server. Enable hardware-accelerated transcoding if you have a Plex Pass and a supported GPU.

Then check the network: switch to Ethernet, run a speed test on the streaming device itself, and set a global remote stream bitrate limit your upload speed can actually handle. Finally, upgrade the client device if it’s a smart TV with software-only HEVC decode. Swapping to a Shield TV Pro or Apple TV 4K cuts buffering immediately by eliminating forced transcoding on the server side.

If buffering persists after working through all the above, check the Plex dashboard’s Active Streams view. That shows exactly what’s transcoding and how much CPU it’s consuming, which narrows the diagnosis fast.

For a lighter-weight setup that doesn’t need a dedicated server, compare Plex alternatives or read the Emby vs Plex breakdown to see which media server fits your library.

#Frequently Asked Questions

#Why does Plex buffer even with fast internet?

Fast internet doesn’t help if the bottleneck is inside your home network. A 4K HEVC file can have a bitrate of 60-80 Mbps, which exceeds most Wi-Fi connections under real-world conditions. Run a local speed test on the streaming device itself, not just your router. Also check whether Plex is transcoding versus direct playing; transcoding overloads the server regardless of network speed.

#Does Plex Pass stop buffering?

Plex Pass unlocks hardware-accelerated transcoding. That’s the single most impactful fix if software transcoding is your bottleneck. It won’t help with network or client device issues, but on a GPU-equipped server it often eliminates 4K and HEVC buffering on the first try.

#What causes Plex to buffer only at certain times?

ISP congestion during peak hours (usually 7-10 PM) is the most common culprit for time-specific buffering. Run a speed test when the buffering occurs and compare those numbers against your daytime baseline. If download speeds are significantly lower in the evening, ISP throttling is likely the cause. Some ISPs throttle specific ports or protocols during busy hours, which can selectively affect Plex remote streaming while other traffic seems fine.

VPN server congestion follows the same pattern. Check whether scheduled backups or antivirus scans are running on your Plex server at those times too, since that competes directly with transcoding CPU time.

#How do I know if Plex is transcoding?

Tap the ”…” menu during playback. Look for “Direct Play,” “Direct Stream,” or “Transcode.” That’s your answer.

#Can subtitles really cause Plex buffering?

Yes, and it catches a lot of people off guard. PGS and VOBSUB subtitles are image-based, so Plex must burn them into the video frame by frame. That forces a full software transcode on every file with those subtitle tracks, even when your server and client would otherwise direct play the video with zero processing overhead.

Switch to SRT (text-based) subtitles or disable them entirely. You can pre-process image-based subtitle tracks using MakeMKV or Handbrake before adding files to your Plex library.

#What internet speed do I need for remote Plex streaming?

At minimum: 2-3 Mbps for 1080p and 10-15 Mbps for 4K (both with transcoding active). Direct streaming the original file without transcoding needs speeds that match the file’s actual bitrate.

#Should I use a NAS or a dedicated PC for my Plex server?

A NAS works well for direct play and software transcoding of 1080p content, but 4K HEVC transcoding requires a NAS with a fast Intel processor that supports Intel Quick Sync. A dedicated PC with a discrete GPU gives you more headroom. For most home libraries with 2-3 simultaneous streams, a NAS like the Synology DS923+ with an Intel Celeron processor handles 1080p hardware transcoding reliably.

#What should I try if nothing else works?

If you’ve worked through all the fixes and buffering continues, run the Plex server logs (Settings > Troubleshooting > Download Logs) and look for repeated transcode errors or resource warnings. Post the logs to the Plex forums for community diagnosis. You can also consider switching to Plex alternatives like Jellyfin, which runs lighter on lower-end hardware.