Setting up a NAS for team collaborative editing in a small studio
Network-attached storage has quietly become the backbone of many Australian creative agencies, post-production houses, and editorial teams who need a shared workspace that doesn't depend on a flaky cloud connection. When a project involves multiple editors, colourists, or writers working on the same footage, copy, or design files, a properly configured NAS can replace a tangle of external drives and messy Dropbox folders. The aim is to give every team member the same view of the project, with permissions that match their role, and with enough throughput to keep previews, proxy renders, and saves running without lockups.
Aussie teams often work across cities, with editors in Sydney, sound mixers in Melbourne, and a producer checking in from Brisbane. That geographic spread makes local infrastructure valuable, since round-tripping to a foreign cloud can add noticeable latency, especially on consumer-grade NBN plans. A well-tuned NAS sitting in the office, combined with a sensible remote-access layer, lets a Sydney editor stream dailies while a Melbourne colourist grades the same media minutes later. The right setup also respects how Australian studios actually bill, archive, and audit their work.
The hardware choices below are written for a small team of between four and twelve people, the size that most local boutique post houses and content agencies sit in. Larger facilities will need to scale the same principles upward, while a solo freelancer can strip things back further. The general approach stays the same: pick the chassis, choose the RAID profile, lock down the network, hand out the right credentials, install the sync layer, and protect everything with a backup routine that doesn't rely on a single drive.
Choosing the right hardware and disk layout
For a small editorial team, a four-bay or six-bay unit from QNAP or Synology is usually the sweet spot. Chassis in this range can be expanded later with a larger enclosure, which matters in Australia where shipping replacement parts from overseas can take a week. AMD Ryzen-based models handle several simultaneous video streams without choking, while Intel Celeron units are fine for document-heavy workflows such as script editing or transcription work.
Drives should be enterprise-grade NAS drives like Seagate IronWolf or WD Red Pro, matched in capacity for predictable performance. Mixing a 4 TB drive with an 8 TB drive wastes the larger disk and complicates future replacements. Plan for at least 20 to 30 percent spare capacity once RAID overhead is calculated, since editing projects balloon quickly, and leaving headroom keeps write speeds steady during the final mix-down.
| Platform | Best for editing teams | Typical CPU class | Expandable chassis | Built-in sync apps |
|---|---|---|---|---|
| Synology DS/SA series | Document and small video teams | Intel Celeron / AMD Ryzen | Yes, with DX expansion | Synology Drive, Hyper Backup |
| QNAP TVS series | Heavier video and colour work | Intel Core / AMD Ryzen | Yes, with TL expansion | Qsync, HybridMount |
| TrueNAS Scale | Linux-savvy IT staff | Xeon or Ryzen | Yes, flexible pools | Built-in SMB, NFS, S3 |
| Unraid | Mixed media archives | Variable, consumer boards | Yes, parity-based | Community apps |
RAID levels, SSD caching, and storage pools
RAID is not a backup, but it does keep the project moving when a single drive fails. RAID 5 is the most common choice for editorial pools under 20 TB because it balances usable space with one-drive fault tolerance. RAID 6 is wiser for pools above 20 TB, since the rebuild time on a large RAID 5 array can stretch over several days and a second failure during that window would be catastrophic. RAID 10 suits fast turn-around projects where raw write speed matters more than raw capacity, but the trade-off in lost space is real.
An SSD cache, often two mirrored SATA or NVMe drives, sits in front of the spinning pool and absorbs small random writes from project autosaves, thumbnail generation, and metadata churn. This dramatically reduces the stutter that editors see when scrubbing through a timeline, because the hot data lives on flash while the bulk media sits on the spinning array. Cache should never hold the only copy of a file; it is an accelerator, not a safety net.
For studios in Sydney or Melbourne that juggle both 4K rushes and finished deliverables, a two-pool setup is often sensible. One pool handles current projects with SSD caching, while a second pool mirrors completed work to slower, higher-capacity drives for archival. This mirrors how many Australian production houses keep "active" and "library" volumes, and it keeps the busy pool small enough to rebuild quickly when a disk eventually fails.
Network configuration for fast shared access
A gigabit switch is the bare minimum, and 2.5 GbE or 10 GbE becomes worthwhile once a team regularly moves uncompressed 4K or 8K media. Cat 6A cabling is cheap insurance for any Australian office re-fit, because a single run to a noisy kitchen or across a long warehouse floor can otherwise cripple throughput. Bonded NICs on the NAS provide redundancy, and the SMB 3 multichannel feature on newer Synology and QNAP units spreads traffic across two cables automatically.
The NBN in Australia delivers asymmetric speeds that can throttle uploads to under 20 Mbps on a standard FTTN plan, which is why remote editors on the road benefit from a separate protocol for off-site access. WebDAV, Tailscale, or a VPN into the office keeps file locking honest, while a cloud mirror through Backblaze B2, Wasabi, or a local provider such as Vault Cloud provides a second copy outside the studio. The aim is to keep the editing experience fast on the LAN and merely usable on the road, rather than forcing everyone to work the way the slowest connection behaves.
Static IPs or DHCP reservations stop chaos when the NAS reboots. The same applies to the workstation side, where the studio router should reserve addresses for each Mac, PC, or Linux box. Australian studios that share premises with a sub-letter or operate out of a co-working space in Brisbane or Perth often run their own small router for exactly this reason, isolating the editorial VLAN from the rest of the building.
Users, groups, and permission structures
Granular permissions matter as soon as a project has a producer, a lead editor, an assistant, and a freelance colourist. Most modern NAS operating systems support Active Directory or LDAP integration, so the team can manage logins from one place rather than maintaining separate accounts on every device. Smaller studios without a domain controller can use the built-in local user system, which still supports per-folder read, write, and owner rights.
A practical structure for a small editorial team looks like this. A top-level shared folder called "Projects" contains one subfolder per client or job, with permissions set so the producer can read and write, the lead editor can read, write, and delete, and the assistant can read and write but not delete. A separate "Rushes" folder holds raw footage with read-only access for most users, while "Output" is open to anyone in the studio for review. This shape prevents the classic Australian problem of a freelancer accidentally trashing a graded master at 4 pm on a Friday.
For mixed-platform studios, configuring both SMB for Windows and AFP or SMB for macOS ensures that FileVault-protected MacBooks can mount the share without losing keychain credentials. ACLs applied through the NAS interface travel with the files, so a project moved to a portable drive retains its permission structure.
Sync, locking, and collaborative editing tools
True real-time collaborative editing on shared media still leans on specific applications, and the NAS plays a supporting role. Adobe Premiere Pro and DaVinci Resolve both read from a shared storage location and rely on consistent file locking to stop two editors from overwriting the same project file. The NAS must enable SMB oplocks and honour POSIX file locks, otherwise timelines will silently corrupt.
For document work, tools such as Synology Drive, Nextcloud, or Qsync give Google-Docs-style co-editing on top of the file system, with version history kept on the local appliance. Australian legal and publishing teams often prefer this arrangement because the data stays on a server in their own office, satisfying client confidentiality clauses. The sync clients run on macOS, Windows, and Linux, which covers the typical mix found in a Melbourne or Adelaide agency.
Versioning deserves a separate mention. Enable snapshot replication on the NAS so that every change to a project folder is captured hourly or daily, depending on the project pace. Editors who regret a cut can roll back a single file without bothering the IT person, which keeps Friday-afternoon panic out of the support queue.
Backup routines and disaster recovery
A NAS is a single point of failure unless something else holds a copy. The standard local practice is the 3-2-1 rule: three copies of every project, on two different media types, with one copy off-site. A second NAS in another office, a hot-spare USB drive rotated weekly, or a low-cost object storage bucket all qualify. Many Australian studios send a backup drive home with the senior editor each Friday and bring it back Monday, which is low-tech but surprisingly effective.
Snapshots on the NAS protect against accidental deletion and ransomware-style encryption, but they do not protect against the building itself flooding or burning. A cloud target through the NAS's built-in backup app adds geographic separation without forcing editors to manage another login. The bandwidth in regional Australia is often limited, so seeding the first backup on a physical drive shipped to the cloud provider is a common workaround.
Testing matters more than configuration. Schedule a quarterly restore drill where a project is pulled back from the cloud copy and verified on a stand-alone workstation. The fifteen minutes spent on this exercise catches silent credential expiry, broken snapshots, and misaligned schedules long before a real incident reveals them.
Practical checklist for a smooth rollout
- Label every drive bay and keep a printed chassis map inside the rack for quick replacement during an after-hours failure.
- Document the RAID level, cache configuration, and pool layout in a one-page runbook that any editor can read.
- Standardise on a single shared folder structure across projects so freelancers can find files without a verbal walkthrough.
- Schedule a weekly scrub and a monthly SMART test to catch drive degradation before it costs a project.
- Use UPS battery backup rated for at least fifteen minutes so the NAS can shut down cleanly during a Sydney or regional outage.
- Keep the NAS firmware current, but stagger updates by at least a week after release to avoid the early bugs that hit production environments first.
- Write a one-page recovery procedure naming who holds the off-site drive, who knows the cloud credentials, and who calls the insurer.
Talk to a WhichNAS specialist about matching these settings to the specific editors, codecs, and deadlines in your studio. The right combination of hardware, network, and workflow turns a NAS from a generic file server into the heart of a productive, audit-friendly creative operation that can scale as the team grows.