Why Wi-Fi Is the Wrong Tool for Video Editing

Editors ask whether they can cut straight from the NAS over Wi-Fi. For a quick review of a short clip, sometimes. For real editing, it is the wrong tool, and the reasons come from how wireless works, not from one brand of router. This article explains the limits in plain terms, what to use instead, and how to move someone onto a wired connection.

The quickest first thing to try

Plug the computer into the network with a cable and turn Wi-Fi off. If the problem goes away, you have your answer. If both are active at once, it gets harder to tell which path the traffic is using, so turn Wi-Fi off for the test. This matters on a Mac in particular. Apple documents that with more than one network available, macOS favors the network that advertises the highest speed, and that some Wi-Fi networks advertise faster speeds than a wired connection. Apple provides a setting, mc_prefer_wired in nsmb.conf, that keeps SMB Multichannel on but treats Wi-Fi as a failover path. See Apple Support article 102010. Turning off Wi-Fi is the simpler test.

Why Wi-Fi struggles with editing

• Shared airtime. Wi-Fi devices on the same channel take turns using the air. Every laptop, phone and tablet nearby shares it. A cable gives each computer its own path to the switch.
• Advertised speeds are theoretical. The big numbers on a router box are the best-case rate under ideal conditions, shared between all devices. They are not the speed an editor will see while others are online.
• Variable latency. Editing needs steady delivery of data. Wireless links change with distance, walls, interference and other networks. A playhead needs frames on time every time, and a link that is fast most of the time but pauses now and then still drops frames.
• Interference. Microwaves, neighboring networks and building materials affect the signal, and these change during the day.
• Roaming and sleep. A laptop that moves between access points, or sleeps and wakes, can drop its SMB connection to the NAS. Premiere then reports offline media, as we explain in our article on relinking after moving drives.
• Uploads suffer too. Frame.io's own help center advises using a wired connection when possible if uploads are slow, and lists public Wi-Fi as a likely cause.

None of this means Wi-Fi is bad. It is good at what it was built for: email, chat, web pages, review links, and moving small files.

What to use instead

1. 1Wired Ethernet to the desk. For the edit bay, run Ethernet to every workstation. The speed you need depends on the footage. Adobe lists 1 Gbps per workstation as the minimum for Productions and recommends 10 Gbps or faster for frame sizes larger than HD, larger Productions or multiple editors. See Thunderbolt versus 10GbE for how to connect laptops and desktops.
2. 2A wired adapter for laptops. A laptop with no Ethernet port can use a Thunderbolt or USB-C Ethernet adapter. Check the adapter's rated speed and its reviews for your operating system, since cheap adapters can vary.
3. 3Proxies and local caches for people who must work wirelessly. Cut with small proxy files stored on the laptop, and relink to the originals later. See our article on proxy workflows.
4. 4Cloud review for remote people. Use a review platform with browser playback, instead of mounting the studio NAS over the internet. See our Frame.io remote editing setup.
5. 5A separate Wi-Fi network for guests and phones. Keep it apart from the edit network so casual use does not interfere.

Step by step: move an editor from Wi-Fi to wired

1. 1Find where the nearest switch port is, and how far the run would be. Cat6a handles the full 100 m for copper 10GBASE-T, while shorter runs are safer on lower-rated cable.
2. 2Label the wall port and the switch port, so the link is easy to trace later.
3. 3Connect the workstation, and confirm the link speed reported by the operating system.
4. 4Turn off Wi-Fi on the workstation, or on a Mac set the wired service to the top of the Network service order.
5. 5Remount the NAS share by its SMB address, then reopen the project.
6. 6Run an iperf3 test from the workstation to a machine near the NAS. See our 10GbE troubleshooting guide for the commands.
7. 7Play the heaviest timeline for several minutes and watch the dropped frame indicator.

What not to do

• Do not buy a more expensive router and expect it to fix editing over Wi-Fi. A faster router helps everything else but does not change how airtime is shared.
• Do not run an Ethernet cable across a walkway or through a door gap. A damaged cable gives problems that look like network faults.
• Do not leave both Wi-Fi and Ethernet active on an editing machine without checking which one carries the NAS traffic.
• Do not mount the studio NAS to a remote editor over a home router and a VPN, and expect it to play like the edit bay.

When it is time to call someone

Call for help if you cannot run cable to every editing position, if the building makes wiring hard, or if the studio is growing past the point where a consumer router can cope. A proper switch, wiring plan and separate networks fix this at the source. The same applies when remote editors need to work on the studio footage and you want to do it securely.

Want a person to look at it?

This is the kind of problem our production consulting team handles: planning cabling, switches and the separation of the edit network from everything else. See our network setup service, or tell us what is happening in your edit bay and a real person on our team will reply.