Plex "Playback Error" or video won't play? How to tell a server problem from a broken file

By the FixMP4 engineering team · · 9 min read

A Plex error at the moment you press play is frustrating because the message rarely says which part failed. Plex involves several moving parts: the server that reads the file, the transcoder that may convert it, the network, and the client app that decodes it. Any of them can fail. Sometimes, though, the file is the problem, especially home videos copied from phones, cameras and screen recorders. This guide helps you work out which part is responsible and fix it.

Test the file outside Plex first

The most useful single check takes a minute: copy the file from the server to a computer and play it in VLC.

  • It plays to the end: the file is healthy. The issue lies with Plex, the client or the network, covered in the next sections.
  • It does not open, shows 0:00 or stops early: the file is damaged. Plex cannot play what is not there; go to "Fixing files that are genuinely damaged".

While you are at it, compare the duration VLC shows with what Plex shows in the item's details. A big mismatch often points at a file whose index is wrong or incomplete.

"Please check that the file exists and the necessary drive is mounted"

This message means the server cannot reach the file at the path it stored. Typical reasons:

  • An external or network drive is disconnected or mounted under a different path after a restart.
  • The file was moved or renamed outside Plex and the library has not been rescanned.
  • The account that runs Plex Media Server lacks read permission for the folder.

Reconnect the drive, rescan the library and check folder permissions for the Plex service account. On Linux servers and NAS devices, permission changes after copying new files are a frequent cause.

Direct play versus transcoding

Plex prefers to send the file to the client unchanged, which is direct play. If the client cannot handle the video codec, audio codec, container or subtitle format, the server transcodes it on the fly. Transcoding is where many errors start.

Open Settings > Dashboard on the server while a video is playing. It shows whether the stream is direct play, direct stream (container change only) or transcode, and why. Common triggers:

  • HEVC or high-bit-depth video on a client that only decodes H.264;
  • Audio formats such as DTS or TrueHD on a client without support, which forces an audio transcode;
  • Image-based subtitles that must be burned into the picture;
  • A quality setting in the client that is lower than the file, which forces a video transcode.

"Server is not powerful enough to convert video"

This appears when a transcode cannot keep up in real time, often with 4K HEVC on a modest CPU. Options, from easiest:

  1. Set the client's playback quality to original or maximum so it attempts direct play.
  2. Use a client app that supports the file's codecs; dedicated TV apps and streaming boxes generally decode more formats than web browsers.
  3. Turn off subtitles or switch to text subtitles to avoid burning them in.
  4. Enable hardware-accelerated transcoding if your server hardware and Plex plan support it.
  5. Use Optimize on the item to create a more compatible version ahead of time, or convert the file yourself to H.264 and AAC.

Files that stop or freeze at the same point

If a video always stops at the same timestamp in every client, test that spot in VLC. A file that also freezes there has damaged or missing data from that point; videos that freeze halfway through explains the usual causes and what can be saved. If VLC plays straight through, try Analyze on the item in Plex so the server re-reads the file's details, and check the server log around the time of the failure.

Fixing files that are genuinely damaged

Home video libraries collect files with problems that commercial media rarely has: recordings cut off by a dead battery, phone videos that were still being written when copied, screen captures from apps that crashed, and clips rescued from failing cards. Many of these MP4 and MOV files have their frames intact but are missing the index that players rely on.

To repair one:

  1. Find a short clip recorded on the same device with the same settings to use as a reference.
  2. Open the FixMP4 repair tool and add the damaged file and the reference.
  3. FixMP4 rebuilds the index locally in your browser, so a private family video never leaves your computer.
  4. Check the free preview, save the repaired file, and replace the broken copy in your Plex library folder. Then refresh the item's metadata.

You can check several files quickly with the MP4 file checker before deciding which need repair. If a file plays but has no sound in Plex only, the issue is more likely the audio codec than damage; see MP4 with no sound.

Network and client issues

When healthy files direct play but still buffer or stop, look at the connection. Wi-Fi between a server and a 4K TV is a common bottleneck; a wired connection usually solves it. Remote streaming depends on your upload speed, which is often much lower than download. Lowering the remote quality setting, or downloading items to the device for offline viewing where your plan allows, avoids interruptions.

For files played straight from a USB drive on a TV rather than through a server, see MP4 won't play on TV.

Summary

Start by playing the file in VLC outside Plex. If it fails there, it is damaged, and rebuilding the index in FixMP4 with a reference clip usually brings it back. If it plays, use the Plex dashboard to see whether transcoding is involved, then adjust the client, quality or file format so it can direct play.

Frequently asked questions

What does "An error occurred trying to play" mean in Plex?

It is a general message that playback could not start. The cause can be the server being unable to read the file, a transcoding failure, a client that cannot decode the format, or a damaged file. The server's dashboard and logs show which part failed.

Why does Plex say the server is not powerful enough to convert the video?

The client cannot play the file directly, so the server tried to transcode it in real time and could not keep up. This is common with 4K HEVC files on low-power servers. Use a client that can direct play the format, lower the quality setting, or create an optimized version in advance.

How can I tell if the video file itself is broken?

Copy the file from the server and open it in VLC on a computer. If it fails there too, shows the wrong duration or stops at the same place, the file is damaged. If it plays perfectly, the problem is in the server, the client or the network.

Does the same advice apply to Jellyfin and Emby?

Mostly, yes. They also choose between direct play and transcoding, and they also show errors for unreadable or damaged files. The menu names differ, but testing the file outside the server is the same first step.

Have a broken recording right now?

Diagnose it and hear or watch a free repaired preview. Nothing is uploaded.

Open the repair tool
  • Plex
  • Jellyfin
  • media server
  • transcoding
  • MP4