Slow upload speed on Windows 11 is frustrating when you need to send large files, join video calls, or back up to the cloud. The good news: Windows-side upload throttling is a real and fixable thing — and several Windows settings actively limit upload speed without obvious indication they’re doing so. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
Run an upload speed test first to establish a baseline: go to fast.com or speedtest.net, click “Show more info” to see upload speed separately. Do this test on your Windows machine and simultaneously on a phone using the same Wi-Fi. If both show similar speeds: the network connection is the bottleneck. If the phone is significantly faster: Windows is doing something to limit the upload.
The hidden upload thief: Windows Update Delivery Optimization
Windows 11’s Delivery Optimization uploads portions of Windows Updates to other PCs across the internet — a peer-to-peer sharing system. By default this can consume upload bandwidth continuously in the background, without any indication in the taskbar.
Settings → Windows Update → Advanced options → Delivery Optimization → “Allow downloads from other PCs” → if it’s set to “Devices on my local network and the internet”: Windows is uploading to strangers’ machines. Change to “Devices on my local network only” or turn it off entirely. Also check the bandwidth settings below — “Upload settings” → limit the upload bandwidth to a specific percentage or value.
This is often the single biggest Windows-side upload speed improvement you can make.
Background applications consuming upload bandwidth
Task Manager → Performance → the Wi-Fi or Ethernet tab → look at the “Send” column in real time. If it’s consistently non-zero even when you’re not actively uploading: background apps are consuming the bandwidth. Switch to the Processes tab → sort by Network → identify which process is sending data.
Common background upload consumers:
- OneDrive, Google Drive, Dropbox: syncing files continuously in background
- Windows Update: downloading updates (which also triggers Delivery Optimization uploads)
- Steam, Epic Games, Xbox: updating games
- Antivirus cloud scanning: uploading suspicious files for analysis
- Backup software: running cloud backup jobs
Closing or pausing these applications during upload-intensive tasks makes the full upload bandwidth available.
Network adapter settings for upload performance
Several NIC (network interface card) settings affect upload speed specifically. Device Manager → Network Adapters → right-click your adapter → Properties → Advanced tab:
- Large Send Offload v2 (IPv4 and IPv6): should be Enabled — offloads packet segmentation to the NIC hardware, reducing CPU overhead during large uploads
- Transmit Buffers: increase to the maximum available value (512 or 1024) — larger buffers prevent the NIC from having to wait for the CPU between burst uploads
- Speed and Duplex: confirm Auto Negotiation — a duplex mismatch cuts effective upload speed dramatically
- Flow Control: try Disabled if uploads are hitting a ceiling below the expected speed — some switches and routers don’t handle flow control well and it creates artificial upload pauses
Upload speed on Wi-Fi vs Ethernet
Wi-Fi upload speeds are fundamentally more variable than Ethernet. The asymmetry matters: most home Wi-Fi routers prioritise download over upload traffic — your download speed may be 300 Mbps but upload only reaches 100 Mbps on the same Wi-Fi connection. This is a router/Wi-Fi specification, not a Windows issue.
If upload speed is critical (video production, large file transfers, cloud backups): Ethernet almost always provides higher and more consistent upload speeds than Wi-Fi. A Gigabit Ethernet connection sustains much closer to the ISP’s actual upload capacity than Wi-Fi on the same plan.
QoS router configuration
Router Quality of Service (QoS) rules that prioritise download traffic over upload can artificially cap upload speeds to give downloads more bandwidth. If your router has QoS configured: check whether upload traffic is being deprioritised. Router admin panel → QoS → look for upload bandwidth allocation or application-specific rules that limit upload for certain traffic types.
ISP upload throttling
Most residential internet plans are asymmetric: much more download bandwidth than upload. Common plan examples: 500 Mbps down / 20 Mbps up. Upload speed that seems slow may just be the plan’s actual upload limit. Check your ISP plan’s stated upload speed and compare to your speed test results. If you’re achieving the plan’s upload speed but it’s still not fast enough: upgrading to a plan with higher upload capacity or switching to a symmetric plan (fibre plans often offer equal upload and download) is the solution.
For specific use cases like streaming on Twitch or YouTube, consistent video calls, or frequent large file uploads: ISP-level upload capacity is often the real bottleneck, not Windows configuration.
TCP/IP tuning for upload
Windows’ auto-tuning should optimise TCP for your connection automatically, but it can be manually checked. Administrator Command Prompt:
netsh int tcp show globalConfirm “Receive Window Auto-Tuning Level” is set to “normal.” If it’s “disabled”: run netsh int tcp set global autotuninglevel=normal. Also check “Initial RTO” — if very high (5000+), reducing it improves upload responsiveness. For most connections the defaults are good, but these commands let you confirm Windows isn’t in a degraded TCP state.
Our guide on general internet speed covers the broader network performance diagnostics including download speed and DNS configuration. For upload issues specific to cloud storage applications, our OneDrive upload guide covers the application-level throttling and bandwidth settings. Microsoft’s network performance documentation covers the Windows Performance Monitor counters for tracking network interface utilisation in detail, and the PowerShell commands for reviewing all active network adapters and their statistics.
Upload speed during specific applications vs general
If upload speed is slow only in one application (Teams, Zoom, a specific FTP client) but fast in a general speed test: the application has its own upload limits or is using a suboptimal upload path.
- Video call apps: Zoom and Teams have configurable video upload bitrates in their settings. Higher quality video uses more upload bandwidth — but many apps cap upload quality automatically based on available bandwidth. Check the apps’ quality settings for upload resolution and bitrate options
- FTP clients: check whether the client has a bandwidth throttle setting (many do, for polite server access)
- Web browsers: uploading through a browser (Google Drive, Dropbox web) is typically slower than using the desktop sync client, due to HTTP overhead versus the sync client’s optimised protocol
Half-duplex network conditions
On older networks or certain switches: full-duplex negotiation fails and the connection operates in half-duplex mode — meaning it can only send or receive at any given moment, not both simultaneously. Half-duplex dramatically reduces effective throughput, especially for upload.
Device Manager → your network adapter → Advanced → Speed and Duplex → if it shows “Half Duplex”: the negotiation failed. Change to “1.0 Gbps Full Duplex” if you know your cable and switch support Gigabit, or “Auto Negotiation” to let the devices negotiate properly. Check the switch/router side as well — a mismatch where one end is set to full and the other to half also causes performance problems.
DPC latency affecting upload consistency
High DPC (Deferred Procedure Call) latency from buggy device drivers causes upload inconsistency — the upload speed varies wildly or stutters rather than maintaining a steady rate. This appears as erratic upload performance rather than consistently slow upload.
LatencyMon (free from resplendence.com) measures DPC latency and identifies which drivers are causing long DPC times. Run it during an upload test and look for drivers with high DPC counts. The most common high-DPC offenders for upload performance: some USB 3.0 host controller drivers, certain audio drivers, and older wireless NIC drivers. Updating the specific high-DPC driver often stabilises upload performance noticeably.
VPN overhead on upload
VPN connections add encryption overhead to every packet, including uploads. The overhead is fixed per packet — small packets are proportionally more affected than large ones. On a fast connection, VPN overhead may reduce effective upload by 10-30%. On a connection already near its upload limit, VPN overhead can reduce usable upload speed significantly more.
Test upload speed with VPN connected and disconnected. If there’s a meaningful difference: the VPN is the overhead source. Options: use WireGuard protocol instead of OpenVPN (WireGuard has lower overhead), enable split tunneling so only work traffic goes through VPN while uploads to cloud storage or video calls go direct, or accept the speed reduction as the cost of VPN security for that traffic.
Upload speed test accuracy
Speed tests measure upload by sending data from your machine to the test server. The test server’s location and capacity affect results: a test server in your city gives more accurate local upload results than one in another country. Use multiple test services (speedtest.net, fast.com, testmy.net) and compare — they use different test servers and methods. Consistent results across multiple tests give a better picture of actual upload capacity than a single test from one service.
Also: test upload speed at different times of day. Cable internet has shared upstream capacity — evening peak hours can show 40-50% lower upload speeds compared to off-peak times on congested infrastructure. If your upload speed varies by time of day in a consistent pattern: ISP congestion is the cause, not Windows.
Diagnostic summary: slow upload
| Test result | Cause | Fix |
| Phone upload faster than Windows on same Wi-Fi | Windows-side background traffic or NIC settings | Check Delivery Optimization; Task Manager network |
| Both devices slow on same network | ISP or router bottleneck | Check router QoS; contact ISP |
| Slow at peak hours, fast in morning | ISP congestion | Schedule uploads for off-peak; consider ISP upgrade |
| Upload erratic, not just slow | DPC latency or Wi-Fi interference | LatencyMon test; try Ethernet |
| Slow only with VPN connected | VPN encryption overhead | Switch to WireGuard; use split tunneling |
| Slow in specific app only | App-level throttle or protocol overhead | Check app bandwidth settings |
Slow upload on Windows 11 is most commonly fixed by checking Delivery Optimization and Task Manager for background apps consuming bandwidth. These two checks take five minutes and address the majority of Windows-side upload slowdowns. The NIC settings optimisations, TCP tuning, and DPC latency analysis are for cases where background traffic isn’t the cause and you need to extract the last bit of upload performance from the connection.
One practical tip for content creators and remote workers who regularly need high upload speeds: schedule large uploads (video files, cloud backups, software deployments) for off-peak hours using Windows Task Scheduler or the scheduling features built into cloud backup applications. Combining off-peak scheduling with pausing Delivery Optimization and other background sync during work hours maintains more upload bandwidth for interactive tasks like video calls during the day, while large transfers complete overnight without competing for bandwidth.
Router upload buffer bloat
Buffer bloat is a lesser-known upload problem: your router has a large buffer that fills up during heavy uploads, causing all other traffic (including video calls and gaming) to get stuck waiting behind the upload queue. The result: upload tests show decent speed, but everything else becomes unusably laggy during uploads.
Test for buffer bloat at waveform.com/tools/bufferbloat — it measures latency under load. A score of A or B is good; C or worse indicates buffer bloat. The fix is typically enabling Smart Queue Management (SQM) or similar features in your router — many modern routers have this as an option in their advanced WAN settings under names like “QoS,” “SQM,” or “CAKE.” Enabling it regulates the upload queue so large transfers don’t starve other traffic.
Checking upload capacity through command-line tools
For a precise view of what’s using upload bandwidth: open an administrator PowerShell and run:
Get-NetAdapterStatistics | Select Name, SentBytes, ReceivedBytes
Run it twice a few seconds apart and compare SentBytes — the difference divided by the time interval gives you the current upload rate per adapter. This is more precise than Task Manager for identifying which physical adapter is handling upload traffic, particularly useful when multiple adapters are active (VPN + Ethernet + Wi-Fi).
For ongoing upload monitoring: netstat -e in Command Prompt shows cumulative bytes sent and received since the last boot. Watching this counter over a period and noting which processes have active connections during high upload periods (from netstat -b) identifies the sending processes more precisely than Task Manager’s momentary view. Our guide on VPN Slowing Internet Speed covers an adjacent issue.
Understanding whether slow upload is a Windows issue, a network hardware issue, or an ISP capacity issue is the key to not wasting time on the wrong fixes. The dual speed test (Windows and phone simultaneously) answers this in 2 minutes. Task Manager shows whether Windows itself is consuming the bandwidth. Everything after that is about optimising what’s already working or escalating to the ISP for capacity issues. See also Windows 11 Slow Startup for a related case.
For users on fixed wireless internet (5G home internet, LTE home internet): upload speeds are significantly more variable than fibre or cable. These connections share cell tower capacity with nearby users, and upload speed can vary 10x depending on network load and signal conditions. Running upload tests at different times of day and from different locations in the home (signal strength varies room to room) provides a realistic picture of what’s achievable and whether Windows optimisation will make a meaningful difference or whether the connection type itself is the limiting factor. You might also run into Ethernet Slow on Windows 11.
