Why is My Upload Speed So Slow?

If you create content, run live streams, upload large project files, or join video meetings, upload speed is the metric that determines whether your workflow feels instant—or painfully slow. Upload speed is simply how fast your device can send data to the internet (cloud drives, YouTube/Twitch, Zoom/Teams, backups, etc.).

Two important realities:

• Your ISP plan sets the ceiling (especially on cable/DSL/5G where upload is often capped).
• Your network setup determines how close you get to that ceiling (Wi-Fi quality, router capacity, bufferbloat, background sync, destination region, protocol).

This guide focuses on fixes that actually move the needle. Start with a baseline test, then apply the highest-impact changes first.

0. Before You Change Anything: Identify the Bottleneck

Most people guess. Power users measure.

1. Test wired first (Ethernet to router). If wired is slow, Wi-Fi isn’t the problem.
2. Run a bufferbloat / “latency under load” test. If ping spikes when uploading, your router needs SQM (CAKE/fq_codel) or better QoS.
3. Test to the real destination (Google Drive/OneDrive/S3/YouTube). Speedtest servers may look fine while cloud uploads crawl due to peering or region selection.

1. Increase Upload Speed

1.1 Get wired (for Wi-Fi users)

Wi-Fi is convenient, but it’s also the most common reason uploads underperform. Upload throughput is sensitive to interference, signal quality (RSSI/SNR), retransmissions, and channel contention—especially in apartments or offices.

If you can, connect your computer to the router with Ethernet. A wired link removes RF noise from the equation and usually gives you the closest result to what your ISP actually delivers.

Technical tips for wired: use Cat5e or Cat6 cabling (Cat5e is fine up to 1 Gbps at typical lengths), ensure the NIC link is 1.0 Gbps full-duplex (check adapter status), avoid powerline unless it’s a high-quality AV2 MIMO model, and plug into the router—not an old 100 Mbps switch. If your ISP plan is >1 Gbps and your router supports 2.5G WAN/LAN, a 2.5G USB adapter can materially improve headroom for uploads.

1.2 Adjust antennas and reposition the router

Router placement directly affects uplink stability. Many consumer antennas radiate best with a vertical orientation, so mixing antenna angles (some vertical, some slightly tilted) can improve coverage across floors and rooms.

Keep the router:

• High and central (not on the floor)
• In the open (not inside cabinets)
• Away from interference (microwaves, baby monitors, thick concrete walls, metal shelves)

RF engineering tips: aim for RSSI between –35 to –65 dBm at the workstation; SNR > 25 dB is ideal for high MCS rates (which drive uplink throughput). On 5 GHz, prefer 80 MHz channels if the spectrum isn’t crowded; in busy apartments, 40 MHz with lower interference can outperform a noisy 80 MHz. 2.4 GHz travels farther but is congested; keep it for low-bandwidth IoT. If you have Wi-Fi 6/6E, 6 GHz can be superb for short-range uploads with very low contention.

1.3 Check the internet plan (and access technology)

If wired upload speed is consistently below what you need, it may not be “your setup”—it may be the plan or the access technology.

What to ask your ISP: upstream technology and profile (e.g., DOCSIS 3.1 vs 3.0; GPON vs XGS-PON; 5G fixed-wireless uplink limits), upstream channel bonding (for cable), whether your modem supports your plan’s upstream profile, and whether upstream shaping/policing is applied.

Reality check: many cable plans have excellent download but limited upload. If you routinely push large files, a symmetric fiber plan (where available) is the biggest upgrade you can make.

1.4 Change the DNS server (helps “where” you upload, not raw Mbps)

DNS translates domain names into IP addresses. It usually doesn’t increase raw throughput, but it can affect which region or endpoint you hit—especially with CDNs and cloud services. A closer endpoint often means lower RTT, fewer retries, and better real-world upload goodput.

Popular DNS servers

Note: DNS doesn’t increase raw throughput, but it affects path selection. Faster/more local upload targets reduce RTT and congestion, enabling higher TCP/QUIC goodput and fewer timeouts on large uploads.

Here is how you can change DNS on major platforms. The primary DNS server can fail in rare cases, which is why you should set a secondary as backup.

Change DNS on Windows 10

1. Head to the Network & Internet settings from the taskbar through the right-click menu.
   
2. Click Change adapter options under Advanced network settings.
   
3. Right-click your Ethernet (or Wi-Fi) adapter → Properties.
   
4. Select Internet Protocol Version 4 (TCP/IPv4) → Properties.
   
5. Tick Use the following DNS server addresses and enter primary + secondary DNS.
   
6. Tick Validate settings upon exit → OK.

Change DNS on macOS

1. Apple Menu → System Preferences.
   
2. Open Network.
   
3. Select Wi-Fi → Advanced.
   
4. DNS tab → click + to add primary and secondary.
   
5. Click OK → Apply.

1.5 Check the router’s firmware and performance features

Firmware updates matter for both security and performance. Routers handle NAT, Wi-Fi scheduling, traffic shaping, and sometimes even intrusion prevention—features that can cap uplink if the router CPU is weak or the firmware is outdated.

Router performance features that improve uploads: enable Smart Queue Management (SQM) / fq_codel / CAKE if available to reduce bufferbloat (upload spikes causing latency). Set the upstream shaper slightly below your plan (e.g., 90–95%) for best stability under load.

1.6 Update network drivers (and verify NIC settings)

Outdated or buggy drivers can reduce throughput, especially on Wi-Fi (rate control) and on multi-gig adapters.

1. Search Device Manager → open it.

1. Expand Network adapters.
2. Right-click your adapter → Update driver → Search automatically.
   

Driver/NIC tips: ensure Speed & Duplex is “Auto Negotiation,” and watch for legacy VPN/filter drivers that intercept packets even when “off.” If you see high CPU usage during uploads on an older machine, try a different adapter or disable heavyweight security filtering temporarily.

1.7 Check for malware and background uploaders

Malware can consume upstream bandwidth (exfiltration, botnet traffic) or add latency through proxying and DNS hijacking. Even without malware, background services frequently saturate upload:

• Cloud backup and sync (OneDrive/Dropbox/Drive)
• OS delivery optimization / peer updates
• Game launchers and auto-updaters

Also audit background sync: pause cloud backup tools during mission-critical uploads. In Windows, disable Delivery Optimization (Settings → Windows Update → Advanced) to prevent peer uploads.

1.8 Use a VPN (only when it fixes peering/throttling)

A VPN can help in specific scenarios: poor ISP peering to your cloud destination, throttling on certain services, or unstable routing. But a VPN can also reduce throughput due to encryption overhead.

Reality check: a VPN can increase upload speed only when your ISP path to the destination is congested/throttled or when the VPN’s peering to the target region is superior. Otherwise, the crypto overhead can reduce throughput. Try multiple VPN protocols (WireGuard-style protocols are typically fastest) and choose an exit node close to the upload target’s region.

1.9 Stop programs hogging bandwidth (Windows Resource Monitor)

1. Press Windows + R → type resmon.exe → Enter.
2. Open the Network tab and identify high-traffic processes.
3. End only non-critical tasks you recognize (updaters/sync tools).
   

Advanced shaping: on capable routers, create QoS rules that prioritize video conferencing and creator tools while capping bulk sync during work hours.

1.10 Replace the router (when hardware is the limit)

If you’ve confirmed the ISP uplink is fine on wired tests but performance collapses under load (video calls stutter during uploads, uploads fluctuate wildly), your router may lack CPU or modern traffic management.

Router specs that matter for uploads: multi-core CPU (>1 GHz), at least 512 MB RAM, SQM support (CAKE/fq_codel), Wi-Fi 6/6E with uplink OFDMA, and 2.5G WAN/LAN if your plan/LAN requires it. For mesh systems, prefer Ethernet backhaul; Wi-Fi backhaul often halves effective throughput.

1.11 Conclusion

Start with a wired baseline. If wired is fast but Wi-Fi isn’t, fix RF: placement, band selection (5/6 GHz), channel width, and interference. If wired is also slow, look at your plan, modem/access tech, router CPU, and background sync. The highest ROI changes for most people are: Ethernet for critical uploads, SQM/CAKE to eliminate bufferbloat, and stopping competing uploaders.

2. Advanced Techniques for Power Users

2.1 Validate the bottleneck (don’t guess)

• Latency under load: If uploads make calls lag, you have bufferbloat → enable SQM/CAKE and shape upstream at ~90–95%.
• Destination testing: speedtest ≠ cloud upload. Test to your real platform (S3/Drive/OneDrive/YouTube).
• Regional endpoints: confirm your bucket/tenant region is local (EU vs US region mismatches can crush goodput).

2.2 MTU/MSS tuning (especially on VPN/PPPoE/cellular)

Wrong MTU can cause fragmentation and retries. On VPNs, effective MTU often drops to ~1420–1450. If your router supports it, TCP MSS clamping can stabilize uploads by preventing fragmentation.

2.3 Upload tools and protocol behavior

• Use clients that support multipart uploads (parallel chunking saturates uplink better).
• Prefer desktop/CLI tools for large jobs (resume support, retries, parallel threads).
• QUIC/HTTP/3 can be smoother on lossy links due to faster recovery.

2.4 Access technology specifics

• DOCSIS cable: upstream is sensitive to signal quality; poor coax/splitters hurt uploads.
• Fiber: check your router WAN port speed (avoid 100 Mbps gear); disable heavy DPI/IDS if it caps throughput.
• 5G/LTE FWA: placement matters; external MIMO antennas can materially improve uplink stability.

2.5 Router CPU saturation

If uploads plateau and router CPU hits 90–100%, disable heavyweight features (deep packet inspection, IDS/IPS, excessive logging) or upgrade hardware. Many consumer routers can’t sustain high uplink rates with advanced features enabled.

3. Quick Diagnostic Checklist

1. Wired baseline (Ethernet): slow → ISP/plan/modem/router or background processes.
2. Bufferbloat test: high latency under upload → enable SQM/CAKE and set upstream to ~90–95%.
3. Destination/region: verify nearest region endpoint and use multipart-capable clients.
4. Kill competing uploads: pause sync/updates; confirm in Resource Monitor.
5. Fix Wi-Fi: 5/6 GHz, better SNR, less interference, sensible channel width.
6. Upgrade router if CPU/QoS features can’t sustain your uplink.

4. FAQs

Does changing DNS increase upload speed? Not raw Mbps. But it can route you to closer endpoints, lowering latency and increasing real-world goodput.

Can a VPN improve upload speed? Sometimes—when it fixes poor peering or throttling. Otherwise, encryption overhead can reduce throughput.

Why do video calls lag when I upload? Bufferbloat. Fix it with SQM/CAKE and proper upstream shaping.

What Wi-Fi band is best for uploads? 5 GHz (or 6 GHz at short range). 2.4 GHz is usually congested and slower.

5. A final word

Upload performance is a chain: app behavior (multipart uploads), OS/NIC (drivers, MTU), LAN (Wi-Fi engineering vs Ethernet), router (SQM, CPU), access tech (DOCSIS/fiber/5G), and destination region. Measure first, then fix the highest-impact link. For most creators and remote workers, the biggest wins come from Ethernet for critical uploads, SQM/CAKE to eliminate bufferbloat, and removing competing background uploaders.