Nothing is more deflating than watching that little scan spinner finish, waiting for the poster wall to fill in, and getting a blank grey page instead. Your files are right there. You can see them in File Station or a network share. Plex just refuses to admit they exist.
The first time I hit this, I had 340 movies sitting on a Synology DS920+ and Plex showed exactly zero of them after a full scan. I spent an hour convinced the drives were dying. They were fine. The fault was one wrong character in a folder path.
This is a Q&A, so I have laid it out as the questions I actually ask, in the order I ask them, when someone sends me a screenshot of an empty library. Work through them top to bottom and you will almost certainly find the culprit before the third one.
Did Plex actually scan the folder you think it did?
Nine times out of ten, the answer is no. The library is pointed at a path that does not contain your media, or contains an empty version of it.
On a NAS this happens because Plex runs in a container or a package, and the path inside Plex is not the same as the path you browse in File Station. A share you see as /volume1/Media/Movies might be mounted inside the Plex container as /data/Movies or not mounted at all.
To check, open the library, go to Edit Library, and look at the exact folder it lists. Then, on the NAS itself, browse to that precise path and confirm your files are sitting directly inside it. If Plex lists /movies but your Docker mapping only exposes /data, that is your whole problem right there.
Are the files buried one folder too deep?
Plex expects a specific shape. For movies, each film should sit in its own folder, and that folder should be directly under the library root.
A structure like Movies/Heat (1995)/Heat (1995).mkv scans perfectly. A structure like Movies/Downloads/Complete/Heat.1995.1080p/Heat.mkv often does not, because people accidentally point the library at Movies when the real content lives three levels down, or the top folder has junk that confuses the matcher.
A mistake I see constantly: someone copies a whole download folder in, complete with sample clips, .txt files, and a nested season folder, then wonders why nothing matches.
The clean test is to open the exact library folder and count how many levels down your first video file sits. If it is more than one folder deep for a movie, either flatten it or point the library at the correct parent. Moving one film up two levels and rescanning is often all it takes to confirm the depth was the issue.
Is this a permissions problem?
If the path is right and the shape is right, permissions are the next suspect. Plex runs as a specific user, and that user has to be allowed to read the files.
On Synology, the Plex Media Server package runs as the user PlexMediaServer. On a Docker setup you usually set this yourself with the PUID and PGID environment variables. If those do not match the owner of your media files, Plex sees the folder but cannot open what is inside, so it reports empty.
For a Docker install, the fast test is to SSH in and run ls -la on the folder, note the numeric owner, and make your PUID and PGID match it. If your files are owned by user 1026 and group 100, set PUID=1026 and PGID=100, recreate the container, and rescan.
There is a subtler version of this too. Sometimes the top folder is readable but a subfolder inside it was created by a different app, say a download client running as root, and only that folder comes back empty. If half your library shows and half does not, compare the owner and permission bits on a working folder against a broken one. They will almost never match.
Could hidden files or the wrong share type be hiding everything?
Two sneaky ones live here. First, macOS and some backup tools scatter hidden files like .DS_Store and ._filename across shares, and while these rarely block a scan outright, a folder full of only hidden or partial files reads as empty to Plex.
Second, and more common on NAS boxes, the media lives on an external USB drive or a share that was not indexed. If you moved files onto the NAS over SMB and the destination was actually a different volume than the one Plex is mapped to, the library sits empty.
Here is a quick reference for what "empty" usually means depending on your setup.
| Symptom | Most likely cause | First thing to check |
|---|---|---|
| Docker Plex, scan finds nothing | Volume not mapped | docker-compose volume binds |
| Synology package, empty after scan | Plex user lacks read access | Shared Folder permissions |
| Files show but posters are blank | Naming or match failure | Folder and filename format |
| Some titles missing, not all | Deep or messy folder structure | One file per folder, no junk |
Is the naming so far off that Plex refuses to match?
A library can be genuinely empty because Plex scanned real files but could not turn any of them into a recognised title. This is closer to a matching failure than a scanning failure, but it looks identical from the poster wall.
Follow the official naming pattern. Movies want Title (Year).ext, and TV wants Show/Season 01/Show - s01e01.ext. Plex publishes its exact requirements, and it is worth reading the Plex media naming guide once so you never guess again.
What is the fastest way to force a clean rescan?
Once you have fixed the underlying cause, do not trust a normal scan to notice. Plex caches aggressively.
- Open the library, click the three-dot menu, and choose Scan Library Files.
- If that fails, go to Settings, then Library, and enable thorough scanning options temporarily.
- Still empty? Remove the library entirely, confirm the path in the add dialog by browsing to it live, then re-add it. The add dialog only lets you pick folders Plex can actually see, which instantly proves whether your mapping is correct.
That last step is the single most useful diagnostic in this whole article. If the folder you expect does not even appear in the browse tree when adding a library, you have your answer: Plex cannot see that path, and no amount of rescanning will change that.
When it still shows nothing
If you have confirmed the path, the shape, the permissions, and the naming and the wall is still blank, look at the Plex logs. On most systems they live under the Plug-in Support or Logs folder, and the scanner log will literally tell you how many files it found and why it skipped them.
I have fixed hundreds of these, and I have never once found a case where the media was truly gone. It is always hiding behind a mapping, a permission bit, or a folder one level too deep. Start at the top of this list, resist the urge to reinstall Plex, and you will find yours faster than you expect.
Frequently asked questions
Why does Plex say scan complete but show no movies?
The scan finished but found zero readable media at the mapped path. This is usually a wrong or unmapped folder, or the Plex user lacking read permission on the share. Check the exact path listed in Edit Library and confirm your files sit directly inside it on the NAS.
How do I fix Plex permissions on a Synology NAS?
Open Control Panel, go to Shared Folder, edit your media share, and on the Permissions tab grant the PlexMediaServer user at least Read access. Apply it, then run Scan Library Files again. This resolves a large share of empty-library cases on Synology.
Do I need to name files a certain way for Plex to find them?
Yes. Movies should follow Title (Year).ext with each film in its own folder, and TV should use Show/Season 01/Show - s01e01.ext. Bad naming usually produces grey placeholder entries rather than a fully empty library, but it is still worth getting right.
Why is my Plex Docker library empty when the files are clearly on the NAS?
Plex in Docker only sees folders you bind as volumes. If the library points at a path that was never mapped into the container, it scans and finds nothing with no error. Check your docker-compose volume binds and make sure the library path matches a mapped folder.
Can hidden files make a Plex folder look empty?
They can contribute. Folders containing only hidden files like .DS_Store or partial downloads can read as empty. More often though, the real cause is that the media landed on a different volume or share than the one Plex is actually mapped to.
