Plex on a NAS: Fix Playback, Buffering, Transcoding

The spinning buffer wheel is the single most common complaint I get from people who just set up Plex on their NAS. They loaded a beautiful 4K movie, hit play from the couch, and got three seconds of video followed by thirty seconds of nothing.

Here is the part that surprises them: the file is fine, the NAS is fine, and the network is usually fine too. The problem is almost always a mismatch between what your box can do and what Plex is being asked to do in that moment.

So let us work through it in order, the same way I would if I were sitting next to your NAS with a coffee.

Step 1: Figure out if Plex is transcoding at all

Before you touch a single setting, you need to know what is actually happening during playback. Start a video that stutters, then open the Plex web dashboard on another device and go to the Activity screen.

Look at the "Now Playing" tile. It will say one of three things next to the stream: Direct Play, Direct Stream, or Transcode.

• Direct Play means the file is sent as-is. This uses almost no CPU and rarely buffers.
• Direct Stream means the video is untouched but the container or audio is being rewritten. Light load.
• Transcode means your NAS is rebuilding the video in real time. This is the load that kills cheap NAS boxes.

Step 2: Understand why your NAS is transcoding

The first time I hit this, I assumed my Synology DS220+ was just weak. It was not. The real issue was that my TV app could not play the specific audio track, so Plex transcoded the entire movie just to fix the sound.

Transcoding gets triggered by a handful of predictable things. The video codec is too new for the client (HEVC or H.265 on an older Roku). The audio format is unsupported (TrueHD or DTS-HD on many TVs). The player is set to a lower quality than the file. Or subtitles are burned in, which forces a full video re-encode every time.

Each of those is fixable, and none of them require a new NAS.

The subtitle trap

Image-based subtitles like PGS, the kind in most Blu-ray rips, cannot be overlaid without redrawing the video. So Plex transcodes. Switch to a text-based subtitle track (SRT) or turn subtitles off and watch the load vanish.

Step 3: Match the file to the client

The cheapest fix is to stop asking your NAS to transcode in the first place. If your files are H.264 with AAC or AC3 audio in an MP4 or MKV container, almost every modern client will Direct Play them.

Here is a rough guide to what plays without help on common devices.

The pattern is clear. A cheap streaming stick or a browser tab forces transcoding constantly. A dedicated player like an Apple TV 4K (around 150 dollars) or an Nvidia Shield removes most of the workload before it ever reaches your NAS.

Step 4: Turn on hardware transcoding if you can

Some transcoding is unavoidable, especially when you stream away from home. This is where hardware acceleration earns its keep.

If your NAS has an Intel CPU with Quick Sync (most Synology "plus" models and many QNAP units), a single machine can transcode several 1080p streams at once instead of choking on one. You enable it in Settings, Transcoder, Use hardware acceleration when available.

A mistake I see constantly: people buy a barebones ARM NAS for 200 dollars, then wonder why it cannot transcode a single stream. The CPU matters far more than the drives for Plex.

Step 5: Rule out the network

If the dashboard says Direct Play and you are still buffering, the file is not the problem. The pipe is.

A 4K remux can run at 60 to 80 Mbps. Over gigabit wired Ethernet that is nothing. Over shaky Wi-Fi, or a NAS plugged into a 100 Mbps port on an old switch, it stalls immediately.

• Confirm the NAS shows a 1000 Mbps link in its network settings, not 100.
• Test the same file on a wired device to isolate Wi-Fi issues.
• For remote streaming, check your home upload speed. Many home connections upload at only 10 to 20 Mbps, which cannot carry a 4K stream out to the internet.

Step 6: Check the transcoder temp folder

When Plex transcodes, it writes temporary files to a scratch directory. If that folder sits on a slow or nearly full drive, playback hitches even when the CPU has headroom.

Point it at your fastest storage. On a NAS with an SSD cache or an M.2 slot, use that. Set it under Settings, Transcoder, Transcoder temporary directory. I moved mine off a full volume once and a 20-second startup delay dropped to about 3 seconds instantly.

Give the folder some breathing room too. A single 4K transcode can write 5 to 10 GB of temporary data, and if the drive fills mid-movie, playback simply stops without warning.

Step 7: Confirm the library and files are healthy

Occasionally the culprit is the media itself. A file with a broken index, a variable frame rate, or a corrupt download will stutter no matter how strong your hardware is.

Play the same file directly on the NAS or copy it to a laptop with VLC media player. If it stutters there too, re-download or re-rip the file. If it plays cleanly in VLC but not through Plex, you are back to a transcoding or network issue, not a bad file.

For the official settings reference, the Plex transcoding documentation is worth a bookmark.

A realistic setup that just works

After years of fiddling, my advice for most homes is simple. Put an Intel-based NAS with Quick Sync in the closet, buy an Apple TV 4K or Nvidia Shield for the main TV, and keep your files as H.264 or H.265 in MKV with AC3 audio.

Do that and the vast majority of playback will Direct Play, your NAS will sit near idle, and the buffer wheel becomes a rare visitor instead of a nightly guest.

Related reading: NAS Apps Eating RAM: How to Find the Culprit, Plex Won't Detect Hardware Transcoding: Checklist and QNAP Container Station: Update Docker Containers.

Start at Step 1, read what the dashboard is telling you, and fix the one thing it names. That single habit turns Plex from a frustrating puzzle into the reliable movie library you wanted in the first place.