Networking for Post-Production: 10GbE, VLANs, and Switch Configuration for Video Teams

Your post-production network is the invisible bottleneck that most teams never think about, until an editor complains that playback is stuttering, or a render that should take 20 minutes takes two hours. The storage might be fast, the workstations might be powerful, but if the network connecting them can't keep up, none of that matters.

This guide walks through networking for post-production: the bandwidth math, the hardware, and what we recommend for studios of every size.

Why Networking Matters in Post-Production

In a shared storage environment, every frame your editors play, every file they save, and every render they export travels over your network. A single 4K ProRes stream runs about 60–110 MB/s, and real timelines stack several: a two-camera interview, B-roll, graphics. That's why we budget 250–400 MB/s of sustained read traffic per editor. Add three more editors, a colorist pulling full-res clips, and someone exporting a final deliverable, and your network needs to handle well over 1,000 MB/s of simultaneous throughput without breaking a sweat.

Most office networks aren't built for this. Standard 1 Gigabit Ethernet (1GbE) maxes out at about 125 MB/s, and that's the theoretical maximum, not real-world. With protocol overhead, you're looking at 100-110 MB/s usable. That's barely enough for one editor in HD, let alone a team working in 4K.

The 10GbE Baseline

For any serious post-production environment, 10 Gigabit Ethernet (10GbE) is the minimum. At roughly 1,250 MB/s theoretical (1,000-1,100 MB/s real-world), every workstation should have its own 10GbE connection, and a single 10GbE link to your NAS carries three to four editors working in 4K ProRes at once. Past that, the NAS needs a faster uplink (more on that below).

What You Need for 10GbE

10GbE switch: A managed switch with enough 10GbE ports for all workstations plus your NAS. Budget $500-$2,000 depending on port count.
10GbE NICs: Each workstation needs a 10GbE network interface card. These run $100-$200 each for SFP+ or RJ45 models.
Cat6A or SFP+ cabling: Cat6A copper supports 10GbE up to 100 meters. SFP+ fiber is better for longer runs and lower latency.
NAS with 10GbE: Your storage needs to match. Most mid-range NAS units from TrueNAS, QNAP, and Synology offer 10GbE ports or expansion cards.

10GbE Cost Breakdown

For a 6-workstation post-production suite:

10GbE managed switch (8-port): $800-$1,500
10GbE NICs (6x): $600-$1,200
Cat6A cabling: $200-$500
Total network upgrade: $1,600-$3,200

That's a fraction of your NAS investment, but it's the difference between smooth 4K playback and constant buffering.

Beyond 10GbE: When You Need More

Larger facilities with 10+ editors or teams working in 8K and uncompressed formats may need to step up:

25GbE: The next practical step. 25GbE switches and NICs have come down in price and give you 2.5x the bandwidth of 10GbE. A good fit for facilities with 8-15 editors or mixed 4K/6K workflows.

100GbE: Enterprise-level networking for large post houses and broadcast facilities. Usually combined with SAN infrastructure. Overkill for most teams, but essential when you need 20+ simultaneous high-bandwidth streams.

Link aggregation (LACP): Bond multiple 10GbE connections together to get more throughput to your NAS. Two bonded 10GbE links give you 20 Gbps aggregate, though individual connections still max at 10 Gbps each.

Network Architecture for Post-Production

Keep Edit Traffic Separate

The most common networking mistake in post-production is running edit traffic on the same network as email, web browsing, and general office traffic. When an editor is streaming 4K media from the NAS and someone else starts a large file download, they're competing for the same bandwidth.

The fix is straightforward: dedicated edit network. Run a separate switch (or VLAN) for storage traffic between workstations and NAS. Office traffic stays on the standard 1GbE network. Your workstations get two network connections: one for storage, one for internet.

Setting Up a Dual-NIC Edit Network

Each workstation gets two network connections:

Storage network (10GbE or faster): connects only to the edit switch and the NAS. Give it a static IP on its own subnet (for example 10.10.10.x) and no default gateway, so the operating system never tries to send internet traffic over it.
Office network (1GbE or Wi-Fi): handles internet, email, Slack, and cloud apps as usual.

Mount the NAS by its storage-network IP address, not by its hostname. Otherwise the workstation may resolve the name to the office network address and quietly route all your media over the slow link. This one mistake accounts for a surprising share of the "we bought 10GbE and nothing got faster" calls we get.

If you'd rather run a single switch, a VLAN does the same job logically: storage traffic on one VLAN, office traffic on another, with the NAS only reachable on the storage VLAN.

Jumbo Frames: Worth It, If You Do It Everywhere

Jumbo frames (an MTU of 9000 instead of the standard 1500) reduce overhead on large sequential transfers, which is exactly what video playback is. On a 10GbE edit network they can add noticeable throughput and lower CPU load on the NAS.

The catch: every device on the storage network has to match. The NAS, the switch ports, and every workstation's storage NIC all need the same MTU. One mismatched device causes dropped or fragmented packets, and performance gets worse than if you'd never touched the setting. Keep jumbo frames on the dedicated storage network only, never on the office side.

SMB, NFS, and AFP: Choosing a File Protocol

SMB is the default for almost every mixed Mac and Windows post environment, and it's what most media NAS vendors tune for. Use SMB3.
NFS works well for Linux render nodes, some Resolve setups, and pipeline automation, but permissions and file locking take more care in mixed environments.
AFP has been deprecated by Apple. Don't build a new workflow on it, and plan to move any existing AFP shares to SMB.

On Macs, SMB performance depends heavily on client settings. Disabling SMB packet signing on edit workstations (where your security policy allows it) and turning off .DS_Store creation on network volumes are two common, measurable improvements. Check with your NAS vendor's guide for the recommended nsmb.conf settings for your macOS version.

Choosing a Switch for Post-Production

The switch is the center of the edit network, and cheap consumer or basic office switches are where a lot of studios cut corners they regret later. What to look for:

Line-rate (non-blocking) switching. The switch must be able to run every port at full speed at the same time.
Port mix. 10GbE for workstations, plus 25GbE (SFP28) or faster uplinks for the NAS once you're past three or four editors.
SFP+ vs 10GBASE-T (RJ45). SFP+ with short DAC cables or fiber runs cooler, uses less power, and has lower latency. RJ45 is convenient when you're reusing existing Cat6A runs to edit suites. Many teams use both.
Buffers. Larger packet buffers help when several editors pull from the NAS at once.
Noise and heat. If the switch lives in an edit suite instead of a server closet, check the fan noise.

For small and mid-size studios, UniFi is a popular choice because one dashboard manages switches, Wi-Fi, firewall, and VPN together, which keeps day-to-day administration simple for teams without dedicated IT. Its aggregation switches cover 10GbE and 25GbE. MikroTik offers very fast, inexpensive switches but expects more networking knowledge to configure. Netgear's M4350 line is common in AV-heavy facilities, and enterprise lines from Aruba, Cisco, and Juniper make sense for larger facilities with IT staff.

Laptops, Thunderbolt, and Multi-Gig

Not every editor sits at a tower with a PCIe slot. Thunderbolt 10GbE adapters from Sonnet, OWC, and ATTO give laptops and Mac minis a full 10GbE storage connection, and ATTO's ThunderLink models go to 25GbE and beyond. Mac Studio includes 10GbE built in.

2.5GbE and 5GbE (multi-gig) ports are now common on newer machines and switches. They're a reasonable step up for proxy editing and HD work, but they won't carry 4K camera originals for a busy editor.

Why Wi-Fi Doesn't Work for Editing

Even Wi-Fi 6E and Wi-Fi 7 deliver far less than their headline speeds once walls, distance, and other users are involved, and the connection is shared by everyone on that access point. The bigger problem for editing is inconsistency: latency spikes and throughput drops cause dropped frames and beach-balling. Wi-Fi is fine for proxies and review. Camera originals need a cable.

Your Internet Connection and Cloud Workflows

If your team uses cloud storage, streaming filesystems, or remote editors, the internet uplink becomes part of your post-production network. Upload speed matters as much as download, because every shoot day has to get into the cloud before anyone remote can cut it. For cloud-heavy teams, symmetrical business fiber (1 Gbps or faster) is worth far more than a faster asymmetric cable plan.

Put the internet connection on the office network, not the storage network, and use a firewall that can handle full line rate with VPN and security features turned on. See our guides to post-production in the cloud and remote video editing workflows for how this fits into a hybrid setup.

Network Sizing by Team Size

Using a planning budget of 250–400 MB/s per editor for 4K ProRes work (see our shared storage guide for how we get there):

1–3 editors: 10GbE to every workstation and a 10GbE NAS. One 10GbE link to the NAS carries about 1,100 MB/s in practice, which covers three editors.
4–8 editors: 10GbE to workstations, with a 25GbE (or two bonded 25GbE) link to the NAS. A switch with SFP28 uplinks makes this simple.
8–15 editors: 25GbE to finishing and heavy-multicam seats, and a 100GbE link to the storage.
15+ editors or 8K/uncompressed: a 100GbE core, often with SAN infrastructure. At this size you want a proper network design, not a pile of switches.

The pattern: every workstation needs its own fast link, but the NAS uplink is the shared bottleneck, so it should be at least one step faster than the workstations.

Troubleshooting Slow Playback on a Shared Network

When editors report stuttering or dropped frames, work through it in this order:

Check the negotiated link speed. A bad cable or port can silently fall back to 1GbE. Look at the NIC status on the workstation and the port on the switch.
Test the network on its own. Run iperf3 between a workstation and the NAS. A healthy 10GbE link should show roughly 9 Gbps or more.
Test the storage over the network. Run AJA System Test or Blackmagic Disk Speed Test against the mounted share with a file size and codec similar to your real media.
Confirm the route. Make sure the share is mounted on the storage-network IP, not through the office network.
Check MTU consistency if you've enabled jumbo frames anywhere.
Look at the NAS itself. CPU, RAM, cache hit rate, and how many users are actually connected. Sometimes the network is fine and the array is the bottleneck.

If those all check out and playback still struggles, the issue is usually the codec or the project (long-GOP camera files, heavy effects, or too many layers), not the network.

Get Your Network Right Once

Networking is one of the cheapest parts of a post-production setup and one of the most expensive to get wrong, because bad networking makes your storage, your workstations, and your editors look slow. We design edit networks alongside the storage they serve. Learn more about our post-production storage consulting and support services, or book a free 30-minute call to talk through your setup.