Upload speed test
Press Start and the test uploads to our server in growing steps, then shows your upload speed and your ping while the upload runs. For a high-quality video call, about 4 Mbps up is enough. Cloud backups and live streaming need more. If ping jumps by 100 ms or more during the upload, every call and game will lag whenever something in the house is uploading.
The test needs JavaScript.
- Upload
- –
- Ping during upload
- –
- Ping at rest
- –
Upload vs download
Download speed is how fast data reaches you: web pages, streams, game downloads. Upload speed is how fast you send data out: your camera and voice on a call, a file going to the cloud, a video going to a platform. Both are measured in megabits per second (Mbps).
Most home plans advertise download first, and many cable plans upload at a small fraction of their download speed. That's fine for watching, but it can be the bottleneck the moment you start sending.
What needs upload
- Video calls. Your camera and microphone go out the whole time you're on a call. Microsoft Teams lists 4 Mbps each way as its "best performance" figure for video calls and meetings (Microsoft Teams bandwidth requirements). Our verdict uses that 4 Mbps for video calls. Two people on calls at once need twice that.
- Live streaming. Streaming a game or an event sends your video out continuously at the quality you choose. It needs steady upload with room to spare, because a dip shows up as buffering for every viewer. Check your platform's recommended settings against this result.
- Cloud backup and photo sync. Upload speed sets how long a backup takes. At 10 Mbps, 100 GB takes about 22 hours. At 40 Mbps it takes about 5.5 hours.
- Game uploads and clips. Sharing a recorded match, uploading a mod or saving to cloud storage all wait on upload.
- Gaming itself needs little upload, about 1 Mbps in our verdict. What hurts games is what happens to ping while something else uploads (below).
Why cable plans give so little upload
Cable internet runs over a shared coaxial network that sets aside most of its capacity for downloads, because that's what most people use most. CableLabs, which writes the cable industry's standards, says a typical customer's upstream use is only about 10% of their downstream use. Current DOCSIS 3.1 cable modems support up to 5 Gbps down but 1.5 Gbps up (CableLabs: DOCSIS 4.0). Providers then split that capacity into plans, and the upload side ends up much smaller.
CableLabs says the newer DOCSIS 4.0 standard supports up to 6 Gbps upstream, enough for symmetric multi-gigabit plans, but your plan's upload is whatever your provider sells. If upload is your bottleneck, compare plans by their upload figure, not the headline number.
How this upload test works
Your browser uploads blocks of random data to our server on Cloudflare's network, starting small and getting bigger: 100 kB, then 1 MB, 10 MB, 25 MB and 50 MB. It stops stepping up once a single upload takes more than a second, so slower lines finish early and use less data. Your speed is the 90th percentile of the measured uploads: faster than most of them, but not a single lucky peak.
While the uploads run, the test also sends a small ping every 400 milliseconds or so. That's your ping during upload, shown next to your idle ping.
Where it tops out. The largest upload is 50 MB (and downloads on the full test top out at 100 MB). That measures up to about 1 Gbps. Above about 950 Mbps, the result reads "at least 950 Mbps" rather than a number we can't stand behind. If you pay for multi-gigabit service, use the tool your provider recommends for the top end.
Pings are HTTP round trips to the nearest Cloudflare location, not ICMP. How it works has every detail.
Ping during upload: the number to watch
Upload is where bufferbloat usually hides. Because the upload side of most plans is small, it fills quickly, and the router's queue fills with it. A game or call packet then waits behind the upload.
A worked example:
| When | Ping |
|---|---|
| At rest | 16 ms |
| During upload | 210 ms |
| Rise | 194 ms |
That rise is a D on our bufferbloat scale (100 to 199 ms). In practice: every time a phone backs up its photos, everyone in the house lags. The upload speed itself might be fine. The fix is the router's queue, not a faster plan. Our guide to fixing bufferbloat covers it, and the bufferbloat test checks both directions at once.
Getting a fair result
- Pause cloud backup, photo sync and other uploads on every device. They compete with the test.
- Use a cable if you can. A weak Wi-Fi signal can hold upload below what your plan delivers (Wi-Fi vs Ethernet).
- Run it two or three times, and at different times of day. Shared networks get busier in the evening.
- Compare with your plan's upload figure, not its download figure. A 20 Mbps result on a "20 Mbps up" plan is working as sold.
Results differ between tests because each one uses its own servers, file sizes and math. Why results differ explains it, including how this test compares with Speedtest by Ookla.
Sources
- Microsoft Teams: prepare your network, bandwidth requirements: 4 Mbps up and down for best-performance video (checked November 2026)
- CableLabs: DOCSIS 4.0 technology: upstream use and modem capacities (checked November 2026)
- Cloudflare speed test engine (@cloudflare/speedtest), README: the 90th percentile and the one-second cutoff (checked November 2026)