NAS for Plex: Setup, Performance, and Best Practices
A NAS (Network Attached Storage) is a dedicated storage device on your network that serves files to other machines. For Plex, a NAS stores your media library — movies, TV shows, music — and either runs the Plex server itself or provides storage to a separate server over the network. The right NAS setup gives you expandable storage, data protection, and clean separation between your media files and your Plex server hardware.
NAS as storage vs NAS as server
The first decision is whether the NAS runs Plex or just stores files for a separate Plex server:
- NAS as storage only (recommended): Your Plex server runs on a separate machine (a PC, a mini PC, a VM) and mounts the NAS as a network drive. The server handles all Plex processing — transcoding, metadata, database, streaming — while the NAS just serves files. This gives you the best performance because you can choose powerful server hardware independently of your storage device
- NAS as Plex server: The NAS runs Plex Media Server directly. Synology, QNAP, and Asustor NAS devices support running Plex as a package. This is simpler (one device does everything) but limits your transcoding capability because NAS processors are designed for file serving, not video encoding. Only higher-end NAS models with Intel CPUs support hardware transcoding
- When NAS-as-server works: If your users mostly direct play and you rarely need to transcode, a mid-range Synology or QNAP NAS handles Plex adequately. For 1-3 direct play streams with occasional audio-only transcodes, a NAS is sufficient. For regular video transcoding or more than a few simultaneous users, a separate server is strongly recommended
Connecting a NAS to your Plex server
When using a NAS as storage for a separate Plex server, you need to mount the NAS shares on the server. The protocol you use affects performance:
- NFS (Linux servers): NFS is the preferred protocol for Linux-based Plex servers. It has lower overhead than SMB, supports proper Unix permissions, and handles large file streaming efficiently. Mount the NAS share in /etc/fstab with options like
nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600for optimal performance - SMB/CIFS (Windows servers): SMB is the standard protocol for Windows. Map the NAS share as a network drive or mount it in a folder. Use SMB version 3 for the best performance and security. SMB works well for Plex — the overhead compared to NFS is minimal for media streaming workloads
- iSCSI (advanced): iSCSI presents NAS storage as a local block device rather than a network share. This gives the best raw performance and allows the server to format the storage with its own filesystem. The downside is that only one server can access an iSCSI target at a time, and setup is more complex. Useful for dedicated Plex servers that do not need to share the storage with other devices
- Persistent mounts: Configure mounts to reconnect automatically after a reboot. On Linux, use /etc/fstab with the
_netdevoption so the mount waits for the network to be available. On Windows, use a startup script or the Credential Manager to reconnect mapped drives. If the NAS share is unavailable when Plex starts, Plex shows empty libraries until the mount reconnects
Performance considerations
Network storage adds latency compared to local drives. Here is how to minimize the impact on Plex:
- Gigabit is the minimum: A single 4K HDR remux can sustain 80 Mbps or more. On a gigabit network (theoretical 1000 Mbps, practical ~900 Mbps), you can serve roughly 10 high-bitrate 4K streams simultaneously. For most home Plex setups, gigabit Ethernet is sufficient
- 10 GbE for large setups: If you have many concurrent users or your library exceeds 100 TB with frequent full-library operations (scans, metadata refreshes), 10 GbE between the NAS and server eliminates the network as a bottleneck. Many NAS devices now include 10 GbE ports or support add-in cards
- WiFi is not acceptable: Never connect a NAS or Plex server via WiFi. The latency, throughput variability, and packet loss of WiFi cause buffering during playback. Both the NAS and server must be on wired Ethernet
- Keep Plex database local: Even when media is on the NAS, keep the Plex database, metadata, and thumbnail cache on a local SSD on the server. The database generates many small random reads and writes during library browsing — a local SSD handles this in milliseconds, while a network-mounted database adds noticeable latency to every library page load
- Transcode temp on local SSD: Set the Plex transcode temporary directory to a local SSD, not the NAS. Transcoding writes many temporary segments that are read shortly after — local SSD eliminates the network round trip for these temporary files
NAS recommendations for Plex
These NAS devices are commonly used with Plex in 2026:
- Synology DS923+ or DS1522+: AMD Ryzen-based NAS with 4 or 5 bays. Fast for file serving, adequate for direct-play Plex server duty. No hardware transcoding (AMD, not Intel). Best used as storage for a separate Plex server. Synology's DSM software is polished and reliable
- Synology DS723+ or DS224+: Compact 2-bay models good for smaller libraries. The DS224+ uses an Intel Celeron with Quick Sync, enabling hardware transcoding for Plex Pass users running Plex on the NAS. Limited to 2 drives, so storage expansion requires upgrading or adding a DX517 expansion unit
- QNAP TS-464: Intel Celeron with Quick Sync, 4 bays, dual M.2 SSD slots for caching. Supports hardware transcoding if running Plex on the NAS. QNAP's software is functional but less polished than Synology's
- TrueNAS (DIY): Open-source NAS operating system running on your own hardware. ZFS filesystem provides enterprise-grade data integrity. Requires more hardware knowledge to set up but offers the most flexibility and performance. No hardware limitations beyond what you build — add as many drives and as much RAM as you want
- Budget option: A used Dell PowerEdge T340 or HP ProLiant MicroServer with 4-8 drive bays running TrueNAS. These enterprise servers are designed for 24/7 operation, have ECC memory, and can be found used for $200-400. Add your own drives for a powerful and affordable NAS
Data protection
A NAS should protect your media from drive failures:
- RAID or equivalent: Use RAID 1 (mirror, 2 drives), RAID 5 (single parity, 3+ drives), or RAID 6 (double parity, 4+ drives). Synology's SHR (Synology Hybrid RAID) automatically selects the best RAID level for your drives and allows mixed drive sizes. RAID protects against a drive failure — if one drive dies, your data survives while you replace it
- RAID is not backup: RAID protects against hardware failure, not against accidental deletion, ransomware, or NAS failure. For irreplaceable media (home videos, personal recordings), maintain a separate backup on a different device or cloud storage. Replaceable media (movies, TV shows that can be re-downloaded) often does not need a separate backup
- Scrubbing: Enable periodic data scrubs (also called integrity checks). The NAS reads all data and verifies checksums to detect and repair bit rot before it causes data loss. ZFS and Btrfs filesystems do this natively. Run scrubs monthly for the best protection
Troubleshooting
- Plex shows empty library after reboot: The NAS mount was not established before Plex started. Configure mount ordering so the network share is available before the Plex service starts. On Linux, use
systemctl edit plexmediaserverto addRequiresMountsFor=/path/to/media - Buffering on NAS-hosted content: Check network throughput between the NAS and server with iperf3. If throughput is below 500 Mbps, check cable quality, switch ports, and network configuration. A bad Ethernet cable or a 100 Mbps port on the switch can silently bottleneck your connection
- Permission denied on NAS shares: NFS and SMB use different permission models. On NFS, ensure the UID/GID of the Plex user on the server matches the permissions on the NAS share. On SMB, verify the credentials used to mount the share have read access to the media directories
- Slow library scans: Library scans on NAS-mounted media are slower than local drives because every file stat and metadata read goes over the network. This is normal. Run initial scans during off-hours and configure automatic scans to run during low-usage periods