Why Your Office WiFi Slows Down When Transferring Files
A large file transfer suddenly makes everyone's internet feel sluggish. This is a specific, solvable problem. Here is exactly why it happens and how to fix it.
The Symptom
Someone in the office starts copying a large file to a shared folder. Immediately, three things happen: the office WiFi feels slower for everyone, video calls get choppy, and someone complains that websites are loading slowly.
Then the transfer finishes and everything returns to normal.
This is not a coincidence. It is a predictable consequence of how WiFi works and how most office networks are configured.
Root Cause 1 — WiFi Is a Shared Medium
The most important thing to understand about WiFi is that all devices on the same access point share a single radio channel. No device transmits simultaneously with another — they take turns, managed by a protocol called CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance).
When a file transfer saturates the channel — maxing out available bandwidth — it consumes a disproportionate share of the available transmission time. Other devices get their turns, but less frequently, because the transferring machine is occupying the channel for longer continuous periods.
The result: video calls that need a consistent stream of small packets start getting delayed because the channel is congested with large file transfer packets.
Root Cause 2 — No QoS (Quality of Service) Configuration
QoS is a router/access point feature that prioritises certain types of traffic over others. If configured correctly, it would deprioritize large bulk transfers and prioritise real-time traffic (voice calls, video conferencing) to prevent exactly this symptom.
Most office routers and access points ship with QoS disabled or misconfigured. Without it, all traffic is treated equally: a 100MB file transfer packet gets the same priority as a Teams video frame.
The fix: Enable QoS on your router or access point. Set video conferencing applications (Teams, Zoom, Meet) to highest priority. Set bulk file transfers to low/best-effort priority. The exact setting location varies by router model — look for "QoS" or "Traffic Control" in the admin panel.
Root Cause 3 — Uploading Fills the Upload Pipe
If the file transfer is going to cloud storage (Dropbox, Google Drive, OneDrive) rather than a local machine, there is a second mechanism:
Cloud upload saturates your internet connection's upload bandwidth. When upload is maxed out, TCP acknowledgements for incoming traffic (video call data being received) get queued, causing the incoming stream to slow too — a phenomenon called buffer bloat.
The fix: Rate-limit cloud upload clients. In Dropbox settings, for example, you can set a maximum upload rate. Setting it to 70–80% of your total upload bandwidth leaves headroom for other traffic.
Root Cause 4 — Large Packets Cause Bufferbloat
Bufferbloat is a networking pathology caused by excessive packet buffering in routers and network equipment. When large file transfers fill the router's packet buffer, small latency-sensitive packets (for video calls, VoIP) get stuck behind large file transfer packets — adding 50–500ms of latency that makes calls sound choppy.
The fix: Enable Smart Queue Management (SQM) or FQ-CoDel on your router if it supports it. OpenWrt, pfSense, and some consumer routers (Netgear Nighthawk with DD-WRT, Asus with Merlin firmware) support this. Standard ISP-provided routers typically do not.
Why Same-Office Local Transfers Do Not Affect the Internet
This is the key distinction: file transfers between two machines on the same local network (a NAS to a workstation, or machine-to-machine via a LAN tool) do not touch your internet connection at all. They travel through the office switch or access point directly.
The WiFi contention issue still applies within the local network — a large local transfer will still congest the WiFi channel — but it does not affect your internet bandwidth, Zoom video quality, or web browsing in the way a cloud upload does.
For teams that frequently transfer large files internally, moving those transfers from cloud-routed to local LAN:
- Eliminates the internet bandwidth consumption entirely
- Is typically 5–20x faster
- Reduces the congestion burden on the WiFi channel (though does not eliminate it)
Diagnosing WiFi Slowdown During Transfers
Step 1 — Identify whether it is local or cloud: Open Task Manager on the machine doing the transfer → Performance tab → Ethernet or WiFi. If upload is near the maximum of your internet connection, it is cloud-bound. If transfer speed matches LAN speeds (~100 MB/s) with minimal internet upload, it is local.
Step 2 — Measure WiFi channel utilisation: Install a WiFi analyser (inSSIDer on Windows, WiFi Explorer on Mac) to see channel saturation. If your channel is shared with multiple other networks in your building, you may be better served by switching to a less congested channel.
Step 3 — Test with and without QoS: Enable QoS on your router, move video conferencing to highest priority, and repeat the scenario. If the problem resolves, QoS configuration solves it.
On Mac
macOS handles WiFi file transfers the same way at the network layer. The symptoms and causes are identical.
One MacOS-specific note: iCloud Drive and Photos library syncing can also trigger upload saturation without an obvious visible progress indicator. If your Mac owner is connected and iCloud has queued a large library sync, the effect is identical to a manual upload. Check System Settings → Apple ID → iCloud → Manage to see what is syncing.
Frequently Asked Questions
Will upgrading to a WiFi 6 router fix this? WiFi 6 improves efficiency (better multi-device handling via OFDMA) but does not eliminate the shared medium problem. Large file transfers on WiFi 6 will still congest the channel; they just do so more efficiently. A WiFi 6 upgrade helps more when many devices are competing simultaneously. For improving transfer speeds, wired ethernet remains more effective.
Does using 5GHz vs 2.4GHz help? 5GHz provides more available channels and less neighbourhood interference, which reduces base congestion. All else being equal, a 5GHz connection during file transfers will perform better than 2.4GHz. However, 5GHz has shorter range and less wall penetration. For performance-critical transfers, wired 5GHz (via access point to switch to machine) is better than either WiFi band.
Can scheduling large file transfers to off-hours help? Yes. Scheduling cloud uploads for overnight or lunch hours when the office is less active prevents the symptom from affecting work. Many cloud storage clients support upload scheduling.
Our internet feels slow even during local transfers. Why? If local transfers (between two office machines) are causing internet slowdown, either your network is misrouted (traffic that should stay local is being routed through a VPN exit node or proxy), or your router is CPU-bound by the NAT/routing load from the local transfer. Check your router's CPU utilisation during the transfer in its admin panel.
Done troubleshooting Windows?
Oxolan handles file sharing so you never have to think about this again.
Get Oxolan for Windows