How to Fix Jellyfin Not Detecting New Movies Added to Your Library Folder

You copy a new film into your movies folder, open Jellyfin, and… nothing. The library looks exactly as it did yesterday. Refreshing the page does not help, and restarting the app feels like a gamble. This is one of the most common Jellyfin complaints, and the good news is that it is almost never a mystery. Jellyfin did not see the file, could not read the file, or saw it and failed to match it. Each cause has a clear fix.

Quick Answer

Jellyfin usually misses new movies because the library scan has not run, the jellyfin user does not have permission to read the new files, or the file and folder names do not follow Jellyfin’s naming rules. Fix it by running Scan Library from the Dashboard, correcting folder permissions so Jellyfin can read the media, and renaming files to the pattern Movie Name (Year). Then refresh metadata on the library.

How Jellyfin Detects New Media

Jellyfin discovers files in two ways. First, it can watch library folders in real time if real-time monitoring is enabled, reacting when files appear. Second, it runs scheduled or manual library scans that walk the folders and add anything new. During a scan it also tries to identify each item and download artwork and descriptions from metadata providers.

A failure can happen at any stage. The scan may never run. The scanner may find the folder but lack permission to open it. Or it may add the file but match it to nothing, leaving it hidden, merged wrongly, or buried under a strange title. Working out which stage failed saves a lot of random clicking, and our wider Jellyfin home media server troubleshooting guide covers the other faults you may meet later.

Fix 1: Run a Manual Library Scan

1. Open Jellyfin as an administrator and go to the Dashboard.
2. Under Libraries, find the Scan All Libraries button, or open the specific library and choose its scan option.
3. Wait for the scan to finish. A progress indicator shows while it runs. Large libraries can take several minutes.
4. Return to the library view and check whether the movie appeared.

If manual scans always work but automatic detection does not, your problem is real-time monitoring or the schedule, covered in Fix 4.

Fix 2: Check File and Folder Permissions

This is the most common real cause, especially when files arrive from another computer, a download tool, or a USB drive. Jellyfin runs as the jellyfin user, and that user needs read and execute permission on every folder in the path, plus read permission on the files themselves.

1. On the server, test what Jellyfin can see: sudo -u jellyfin ls /media/movies. An error here proves a permission problem.
2. Make folders traversable and files readable: sudo chmod -R a+rX /media/movies.
3. If the drive uses restrictive ownership, give Jellyfin ownership of a dedicated media tree instead: sudo chown -R jellyfin:jellyfin /media/movies.
4. Check parent folders too. A private home directory can block access to everything beneath it, even when the media folder itself looks open.
5. Re-run the library scan and confirm the movie appears.

The official Jellyfin movies documentation also stresses clean folder structure, which leads directly to the next fix.

Fix 3: Fix File and Folder Naming

Jellyfin identifies movies mainly by folder and file names. Messy names copied from downloads confuse it badly. Follow the standard pattern:

• One folder per movie: /media/movies/Movie Name (2021)/
• The file inside uses the same name: Movie Name (2021).mkv
• Always include the year. It separates remakes and stops wrong matches.
• Remove release-group tags, quality strings, and extra words from the name itself. Keep editions in the approved extra format if you need them.
• Keep each movie’s extra files, like subtitles, sharing the same base name as the video file.

After renaming, scan again, and if an older wrong entry exists, remove the bad match by identifying the item manually from its library page.

Fix 4: Turn On Real-Time Monitoring and Check Scheduled Scans

1. Go to Dashboard, then Libraries, and edit the affected library.
2. Enable Real-time monitoring if it is off, and save.
3. Under Dashboard, Scheduled Tasks, confirm the Scan Media Library task is enabled and note when it last ran and whether it reported an error.
4. Be aware that network shares and some merged or remote filesystems do not deliver file-change events reliably. On such setups, real-time monitoring may simply never fire, and a frequent scheduled scan is the dependable answer.

Fix 5: Read the Server Log

When the cause is still unclear, stop guessing and read the evidence. Open Dashboard, then Logs, and open the main server log around the time of your last scan. Look for the new file’s name, and for lines mentioning permission denied, failed identification, or skipped paths. You can also follow the log live from the terminal while a scan runs:

sudo journalctl -u jellyfin -f

A single clear error line usually points straight at the real problem, whether it is a locked folder, an unsupported structure, or a metadata provider timing out.

Fix 6: Check the Library Settings and Filters

• Confirm the folder you copied into is actually one of the paths listed in that library. Files in a neighbouring folder are invisible to it.
• Make sure the library type is Movies, not Mixed Content, for a pure film collection. Mixed libraries identify items far less reliably.
• Check that no parental control or user library access setting is hiding new, unrated items from the account you are browsing with.
• Look inside the library sorted by Date Added. A badly matched movie sometimes appears under an unexpected title rather than not appearing at all.

Common Mistakes and Useful Tips

• Copying files as root: Files created by root-owned tools often land with permissions Jellyfin cannot read. Fix permissions after every bulk copy.
• Dumping hundreds of films into one flat folder: It can work, but one folder per movie with the year is far more reliable for matching.
• Scanning before the copy finishes: A half-copied file may be skipped or flagged. Copy fully, then scan.
• Confusing a matching failure with a detection failure: Search the library by year or browse by folder view to see whether the item exists under a wrong name.
• Forgetting external drives unmount: If the media drive was not mounted when Jellyfin scanned, items can vanish or fail to update. Mount it permanently in /etc/fstab.

Conclusion

When Jellyfin does not detect new movies, work the problem in order: scan manually, prove the jellyfin user can read the files, clean the names into the Movie Name (Year) pattern, and check monitoring and scheduled tasks. Finish by reading the log if anything still refuses to appear. In almost every home setup, one of those steps — most often permissions or naming — is the whole story, and once corrected, new films show up within moments of being added.

Frequently Asked Questions

Why does Jellyfin find some new movies but not others?

Selective failures usually mean naming or permission differences on the missing items. Compare a working file with a missing one: check its folder name, year, and permissions side by side.

How long should a library scan take?

A small library scans in under a minute. Thousands of items with fresh metadata downloads can take much longer. Later scans are faster because only changes are processed.

Does Jellyfin detect files on a network share automatically?

Not always. Real-time monitoring depends on the filesystem reporting changes, and network shares often do not. Use scheduled scans at a sensible interval for network storage.

My movie appears but with the wrong title and artwork. How do I fix it?

Open the item, choose Identify from its menu, and select the correct match. Then improve the folder and file name so future scans match it correctly the first time.

Can I force Jellyfin to re-scan one folder only?

Scanning works at library level rather than single-folder level. For a small library that is fine; for huge ones, tidy naming and working real-time monitoring reduce the need for full rescans.