Jellyfin Shows Duplicate or Empty Root Folders — Fixing the Wrong Media Path

You add a movie library in Jellyfin and it comes up empty, or you end up with two near-identical root folders that never fill in. The usual culprit isn't Jellyfin at all — it's a mismatch between the media path you typed and the path where your files actually live. Different docs used different spellings, and only one of them is correct.

Rather not hand-align paths? SparkBox registers one consistent media path across Jellyfin and its downloaders, so this contradiction can't happen in the first place. See the walkthrough →

What "root folder" means in Jellyfin

A root folder (also called a media folder or library path) is the directory Jellyfin scans to find your files. When you create a library — say "Movies" — you tell Jellyfin one or more folders to look inside. If that folder exists but contains nothing, the library shows up empty. If you point at the wrong spelling of a folder, Jellyfin may even create or reference a brand-new empty directory, which is where "duplicate root folders" come from.

The tricky part on a self-hosted setup is that several tools share the same disk. Your download and organizing tools (often called *arr apps) drop finished files into one path. Jellyfin needs to read from the exact same path. If those two disagree by even a single letter's case, Jellyfin sees nothing.

The real cause: three conflicting path conventions

This problem is almost always a documentation mismatch rather than a broken install. Three different path styles were floating around, and users followed whichever one they happened to read first:

• Capitalized, no /media/: /data/Movies, /data/TV, /data/Music
• Lowercase: /data/movies, /data/tv, /data/music
• With a media segment: /data/media/movies and similar

Only the first one is authoritative. The setup scripts register the capitalized paths, the finishing step creates those exact folders, and the shipped Jellyfin libraries point at them. The lowercase and /data/media/ spellings appeared in a couple of user-facing docs pages and caused the confusion — they were wrong.

Fix 1 — Point your libraries at the correct capitalized path

This is the fix for most people. Do not delete anything yet; just correct the path in place so you keep your library settings and watch state.

1. Open the Jellyfin web interface and go to Dashboard → Libraries.
2. Click the three-dot menu on your Movies library and choose Manage Library (or Edit).
3. Look at the folder(s) listed. If you see /data/movies (lowercase) or /data/media/movies, that's the problem.
4. Remove the wrong folder from the list and add /data/Movies instead — matching the capitalization exactly.
5. Repeat for TV (/data/TV) and Music (/data/Music).
6. Save, then go to Dashboard → Scheduled Tasks and run Scan All Libraries.

Within a minute or two the library should populate. If it stays empty, the files probably aren't in the capitalized folder yet — see Fix 3.

Fix 2 — Remove the duplicate empty library

If you ended up adding a second Movies library while troubleshooting, you'll now see two entries — one populated, one empty. Clean it up:

1. In Dashboard → Libraries, identify which library is empty (it will show 0 items).
2. Confirm the working library points at /data/Movies and actually lists your files.
3. Delete only the empty duplicate via its three-dot menu → Delete. Deleting a library does not delete the media files on disk.
4. Run Scan All Libraries again to refresh the home screen.

Fix 3 — Confirm where the files actually live

Jellyfin can only show what's on disk. If both the library path and the folder are correct but the library is still empty, the finishing/organizing step may have put files somewhere else — for example under a lowercase or /data/media/ tree created by following the wrong doc.

1. List what's under your data folder to see the real structure. From a shell on the host or inside the container:

   ls -la /data

2. You should see Movies, TV, and Music with capital letters. If you instead see lowercase movies or a media folder holding your files, that's where they went.
3. Move the files into the correct capitalized folders so everything shares one convention. Verify the target names first:

   ls -la /data/Movies

4. Once files sit under /data/Movies, /data/TV, and /data/Music, rescan in Jellyfin.

Going forward, make sure your downloader/organizer writes into these same capitalized paths. When Jellyfin and the *arr apps agree on one path, the duplicate/empty-folder problem disappears for good.

Fix 4 — Rule out a genuine permission problem

If the path is exactly right and the files are present but the library is still empty, Jellyfin may not be allowed to read the folder. A permission here means the operating-system rule that decides which user accounts can open a file or directory.

1. Check whether the folder is readable by the account Jellyfin runs as:

   ls -la /data/Movies

2. If the owner and group don't include the user Jellyfin runs under, Jellyfin can't scan it. Align ownership so Jellyfin and your downloader use the same user/group across the shared /data tree.
3. After adjusting ownership, rescan the library.

Frequently asked

What is the correct Jellyfin root folder path?

The authoritative convention is capitalized with no /media/ segment: /data/Movies, /data/TV, and /data/Music. That's what the setup scripts register and what your Jellyfin libraries should point at.

Why does Jellyfin show duplicate or empty root folders?

Because different docs used different spellings. Some pages said lowercase /data/movies or a /data/media/movies layout while the scripts actually created /data/Movies. Jellyfin then points at a folder with no files (empty), or you add both spellings and get duplicates.

Do file and folder names in Jellyfin paths need to match case exactly?

On Linux, yes. The filesystem is case-sensitive, so /data/Movies and /data/movies are different folders. Point Jellyfin at the exact capitalized path your files live in.

Will fixing the path lose my Jellyfin watch history?

Correcting the path on an existing library keeps your history. Deleting and re-adding a library can reset play state, so use Fix 1 to edit in place and only delete the empty duplicate.