You can use one set of media files for both Plex and Jellyfin. Mount the NAS share on each server’s host, give each application read access to it, and add that path to each server’s library. If a server runs in a container, bind-mount the host path into that container and configure the library with the path as seen inside it. Keep the media files shared, but keep Plex and Jellyfin’s application data and databases separate.
How the shared-library setup works
The NAS holds one canonical copy of your movies and TV episodes. Plex and Jellyfin each read that same directory, but maintain their own library indexes, metadata, settings, and application data. They do not need to share a database.
As an Amazon Associate I earn from qualifying purchases.
A container adds a path translation: a host directory such as /mnt/nas/media can appear inside a container as /media. Plex and Jellyfin may use different in-container paths; what matters is that both paths point back to the same host directory. See Plex’s installation guidance and Jellyfin’s container guide.
Set up the NAS path and permissions
- Choose one organized media directory. Put your media in a consistent folder structure suitable for the library types you plan to create, such as separate locations for movies and television. Follow the naming guidance for each application.
- Allow both server identities to read it. Confirm the NAS share and filesystem permissions allow the actual Plex and Jellyfin service users to traverse directories and read files. Plex requires its server account to have at least read and execute access; the identity varies by installation, especially with NAS packages and containers. See Plex’s permissions troubleshooting guide.
- Mount the SMB/CIFS or NFS share on each host. Jellyfin’s general guidance says network storage should first be mounted to the operating system. If Plex runs directly on a NAS that stores the files, follow the manufacturer’s package and permissions procedure instead. See Jellyfin’s storage guidance.
- Pass the mounted folder into each container, if applicable. Bind the host mount into a stable path inside the container. Jellyfin documents a bind-mount form such as
--mount type=bind,source=/path/to/media,target=/media. Use the same host source for both services, even if their target paths differ. Add each container’s target path—not the host path—to that application’s library settings. - Keep application data separate and local where required. Do not point one server at the other’s configuration or database directory. Jellyfin specifically says its database should be on local storage rather than a network storage device.
- Test a small folder before scanning everything. Check that the host mount exists, that the path is visible inside each container, and that each service identity can list and read a sample file. Then add the library and scan it.
Choose read-only access when possible
If Plex and Jellyfin only need to play and catalog the media, make their media mounts read-only. Jellyfin’s container guide shows read-only bind-mount options, including readonly and ro=true. This reduces the chance that a server process can alter or delete source files. If a particular file-management or metadata workflow needs write access, grant only the required access and verify its effect first.
#1 Best Overall
- IronWolf internal hard drives are the ideal solution for up to 8-bay, multi-user NAS environments craving powerhouse performance
- Store more and work faster with a NAS-optimized hard drive providing ultra-high capacity up to 16TB and cache of up to 256MB
- Purpose built for NAS enclosures, IronWolf delivers less wear and tear, little to no noise/vibration, no lags or down time, increased file-sharing performance, and much more
- Easily monitor the health of drives using the integrated IronWolf Health Management system and enjoy long-term reliability with 1M hours MTBF
- Three-year limited warranty protection plan included and three year Rescue Data Recovery Services included
Choose a mount method that fits your platform
Host mount with a container bind mount
This follows Jellyfin’s documented general pattern: mount the NAS share on the host, then pass that host directory into the container. It gives the container a stable local path to use, while the files remain on the NAS. Use this approach for Docker or Podman deployments unless your platform’s documented method differs.
SMB/CIFS or NFS
The available documentation does not establish one protocol as the universal best choice for a mixed Plex and Jellyfin setup. Choose based on NAS and host support, the permission model you can manage reliably, and the behavior documented for your platform. A specific exception applies to the Jellyfin app on TrueNAS SCALE: its guide, scoped to SCALE 24.10.0 (Electric Eel) or higher, says SMB additional-storage mounts do not support Jellyfin real-time media scanning; use a Host Path if that feature is needed. This limitation is specific to that documented app setup, not every SMB mount. See Jellyfin’s TrueNAS SCALE guide.
Rank #2
- Store more, compute faster, and do it confidently with the proven reliability of BarraCuda internal hard drives
- Build a power house gaming computer or desktop setup with a variety of capacities and form factors
- The go to SATA hard drive solution for nearly every PC application from music to video to photo editing to PC gaming. Ax. Sustained transfer rate OD: 190MB/s
- Confidently rely on internal hard drive technology backed by 20 years of innovation
- Frustration Free Packaging - This is just an anti-static bag. No cables, no box.
NAS package or separate server
You do not have to run both media servers on the NAS. A separate computer can mount the NAS share and run either or both applications. Native NAS packages can be convenient, but installation steps and service identities vary by manufacturer and model; Plex advises following the NAS manufacturer’s procedure. Compare platform support, maintenance, path handling, permissions, and your hardware needs rather than assuming one deployment type is required.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Keep Jellyfin’s database off the NAS and protect against outages
Jellyfin states that its database should remain on local storage. Its application files also perform random access, and its hardware guidance recommends SSD storage for those files; media can remain on network storage. See Jellyfin’s hardware selection guidance.
Rank #3
- IronWolf internal hard drives are the ideal solution for up to 8-bay, multi-user NAS environments craving powerhouse performance.date transfer rate:6.0 gigabits_per_second
- Store more and work faster with a NAS-optimized hard drive providing 8TB and cache of up to 256MB
- Purpose built for NAS enclosures, IronWolf delivers less wear and tear, little to no noise/vibration, no lags or down time, increased file-sharing performance, and much more
- Easily monitor the health of drives using the integrated IronWolf Health Management system and enjoy long-term reliability with 1M hours MTBF
- Three-year limited product warranty protection plan and three year Rescue Data Recovery Services included
Keep the NAS mount available during Jellyfin maintenance tasks. Jellyfin warns that scheduled maintenance can remove library items if the media storage is unavailable when a task runs. Confirm the mount is reliable and available to the service before enabling scans or maintenance that rely on it.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Keep NAS sharing separate from remote access
Mounting a NAS share for a server is a local storage arrangement; it does not require exposing SMB or NFS to the public internet. For remote access to Jellyfin, plan a secure network setup such as a VPN or reverse proxy. Jellyfin’s networking guidance says opening a port directly to the internet is insecure and not recommended: Jellyfin networking documentation.
Quick Recap
Rank #4
- Available in capacities ranging from 2 to 22TB(1) | (1) 1GB = 1 billion bytes and 1TB = 1 trillion bytes. Actual user capacity may be less depending on operating environment.
- For RAID-optimized NAS systems with unlimited number of bays
- Rated for 550TB/yr workload rate(2) | (2) Annualized Workload Rate = TB transferred x (8760 / recorded power-on hours). The maximum rated workload is specified for operating at typical temperature of 40C. Workload Rate will vary depending on your hardware and software components and configurations.
- Designed to handle the demands of high-intensity 24x7 multi-user NAS environments
- Western Digital partners with a wide range of NAS system vendors for extensive testing to ensure compatibility with most NAS enclosures
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors
