How to Set Up a Home NAS and Get the Fastest Local Transfer Speeds
A home NAS turns a box of hard drives into a private, always-on file server for backups, media, and shared documents. Getting fast local transfers, though, is less about buying the biggest drives and more about making sure every link in the chain — disk, network card, switch, cable, and protocol — can keep up. This guide walks through setup and the practical limits that decide how quickly files actually move.
What a NAS is and what people use it for
A NAS (network-attached storage) is a small computer dedicated to storing files and serving them to other devices over your local network. Instead of plugging a drive into one PC, you plug the NAS into your router or switch and every device in the house can reach it. Popular ready-made units come from Synology, QNAP, TerraMaster, and Asustor, but plenty of people build their own with TrueNAS or Unraid on old PC hardware.
The three most common jobs are:
- Backups. A central target for Time Machine, File History, or scheduled backups from every computer, plus a copy of phone photos.
- Media. A library for Plex, Jellyfin, or Emby that streams movies and music to TVs and phones.
- Files and projects. Shared folders for documents, photo/video editing scratch space, or a place to offload a laptop's crowded SSD.
Note: A NAS is not by itself a backup. RAID protects against a drive dying, not against ransomware, accidental deletion, or a fire. Keep at least one copy of anything irreplaceable somewhere else — another drive or a cloud service.
Choosing drives: HDD vs SSD and RAID basics
For bulk storage, spinning hard drives (HDDs) still win on cost per terabyte, and for media libraries or backups their speed is rarely the bottleneck. Look for drives rated for NAS or 24/7 duty — WD Red Plus/Pro, Seagate IronWolf, and Toshiba N300 are common choices. A single modern NAS HDD sustains roughly 150–250 MB/s on large sequential files, which is already faster than a gigabit network can carry.
SSDs make sense when you need low latency and high speed for many small files or for editing directly off the NAS — but to feel that speed you also need a network faster than gigabit, or the network simply caps you. Many NAS units accept NVMe SSDs as a read/write cache, which can help with frequently accessed data without paying to make the whole array flash.
RAID combines multiple drives for redundancy, capacity, or both:
- RAID 1 mirrors two drives — you lose half your raw capacity but survive one drive failure. Simple and safe for a two-bay unit.
- RAID 5 (or Synology's SHR) spreads data and parity across three or more drives, surviving one failure while keeping most of your capacity.
- RAID 6 survives two simultaneous failures, worth it on larger arrays where rebuilds take a long time.
RAID adds read throughput on large sequential transfers because data comes off several spindles at once, but write speed on parity RAID can dip during rebuilds or when the array is nearly full.
The network side: NIC, switch, and how you connect
This is where most home setups quietly lose speed. A gigabit (1 GbE) link tops out around 1,000 megabits per second, which in real files means roughly 110–118 MB/s after overhead. That is a hard ceiling no matter how fast your drives are. If your NAS holds a fast SSD array or several HDDs in RAID, gigabit becomes the limiting factor.
Stepping up means multi-gig networking, and every device in the path has to agree on the speed:
- A NAS with a 2.5 GbE or 10 GbE network port (built in or via an add-in card / USB adapter).
- A switch with ports at the same speed — a plain gigabit switch will negotiate the link down to 1 GbE.
- A client PC with a matching fast NIC.
- Cabling rated for the speed and length (more on that below).
Wired beats Wi-Fi for NAS work every time. Even a strong Wi-Fi 6 connection is shared, variable, and usually delivers a fraction of its headline rate in real transfers, while a wired link is steady and full-duplex. If a device must use Wi-Fi, expect that link — not the NAS — to be the limit. For the trade-offs, see our guide on Ethernet vs Wi-Fi speed.
Cabling matters more than people expect at higher speeds. Cat5e handles gigabit easily and can carry 2.5 GbE over typical home runs; 10 GbE wants Cat6 for short runs and Cat6a for longer ones. Our Ethernet cable categories guide breaks down which cable does what.
Why real transfer speed is limited by the slowest link
A file copy is only as fast as the weakest component it passes through. You can have 10-gig cards on both ends, but a single old HDD, a gigabit switch in the middle, or a damaged cable will set the ceiling. The table below shows rough real-world ceilings for common components — actual numbers vary with hardware, file sizes, and configuration.
| Component | Typical real-world ceiling | Notes |
|---|---|---|
| Single 7200-rpm NAS HDD | ~150–250 MB/s sequential | Much lower for many small files |
| SATA SSD | ~450–550 MB/s | Needs faster-than-gigabit network to show |
| NVMe SSD | ~1,000–3,500+ MB/s | Almost always network-limited on a LAN |
| 1 GbE network link | ~110–118 MB/s | The common home ceiling |
| 2.5 GbE network link | ~280–295 MB/s | Cat5e usually fine on home runs |
| 10 GbE network link | ~1,100+ MB/s | Needs Cat6/6a and fast storage to fill |
| Wi-Fi 6 (5 GHz, real) | ~40–120 MB/s, variable | Shared, distance- and interference-dependent |
Protocol tuning: SMB and the jumbo frames question
The file-sharing protocol adds its own overhead. Most Windows and macOS clients use SMB, which is fine for large files but slows dramatically on directories full of tiny files because each file involves round-trips. That is normal behavior, not a fault — a 50 GB video will copy near your link ceiling while 50 GB of small photos may crawl.
A few practical tuning notes:
- Prefer SMB3 (modern Windows, macOS, and NAS firmware all support it). It is faster and more secure than the ancient SMB1, which you should leave disabled.
- Jumbo frames (raising the MTU to ~9000) can shave CPU overhead on 10-gig links, but they must be enabled identically on the NAS, the switch, and every client on that segment. A mismatch causes mysterious slowdowns or dropped connections. On gigabit the benefit is usually tiny, so most homes should leave the default 1500 MTU alone unless every device supports jumbo and you can verify it.
- Disable real-time antivirus scanning of the mounted NAS share on the client if copies of many files stall — the scanner, not the network, is often the culprit.
Tip: Change one thing at a time and re-measure. Flipping jumbo frames, cache settings, and RAID levels all at once makes it impossible to know what actually helped — or broke.
How to verify you're getting expected speed
Don't guess — measure. Start by confirming the negotiated link speed at both ends: Windows shows it in Network Connection Status, macOS in System Settings > Network, and the NAS in its control panel. If you paid for 2.5G and see 1.0 Gbps, you have found your problem before copying a single file.
Next, separate the network from the disk. A raw LAN speed test — or a memory-to-memory tool a LAN speed test like PulseLAN — measures the path without disk involvement, so if that hits your link ceiling but real file copies don't, the storage is the limit. Then copy a single large file to gauge sequential speed and a folder of small files to see protocol overhead. Compare the numbers against the table above.
If the results fall short of what your hardware should deliver, our companion guide on the slow NAS transfer diagnostic walks through isolating the cause step by step, and the multi-gig home networking guide covers what it takes to move past the gigabit ceiling for good.
Build the NAS around the job it will do, wire it up with matching speeds end to end, and verify with real measurements rather than assumptions. Do that and your transfers will land where the hardware says they should — no mystery slowdowns, no wasted spending on a fast component that a slower one downstream was never going to let shine.