Internet speed test — download, upload and ping
What your connection can handle
Video streaming
Video calls
Online gaming
Live streaming
Test history
Your results will appear here. History is stored only in this browser.
History won't be saved: the browser has blocked storage (for example, in private mode).
| Date | Download, Mbps | Upload, Mbps | Ping, ms | Jitter, ms | Server | Of plan | Mode |
|---|
Frequently asked questions
Why do other speed tests show different results?
Each test measures to its own server. Many pick a server in your city, often inside your provider’s network: such a test checks only the stretch to the provider and usually shows more. We measure to the nearest Cloudflare node, along the same route many websites take to reach you. Its city and distance are shown next to the result; if the node is far away, this is your speed to the rest of the world. Speed also changes during the day, so compare results of the same test at different times — that’s what the history is for.
What is the difference between Mbps and MB/s?
Providers state speed in megabits, while browsers and torrent clients show megabytes. A byte has 8 bits, so 100 Mbps is about 12.5 MB/s, and in practice 10–11 MB/s because of protocol overhead.
Why is Wi-Fi slower than a cable?
Wi-Fi loses speed with distance, through walls and because of neighbouring networks, and older routers and the 2.4 GHz band hit their own ceiling. If the speed is below your plan, test from a computer connected by cable: that shows whether the provider or the Wi-Fi is to blame.
Where does the data go during the test?
Test data is downloaded from Cloudflare servers and sent back to them — random bytes, not your files. We don’t keep your results: the test history is stored only in this browser.
How much data does a test use?
The test stops on its own once the speed has settled, so data use depends on your speed: about 150 MB at 100 Mbps, up to 1.7 GB on a gigabit line. If the browser reports a mobile network or data saving, the test is shorter and uses no more than 170 MB. The amount used is shown under the result.
Why is there no packet loss?
Measuring packet loss honestly requires a separate server for real-time traffic, and a browser can’t do it without one. We chose not to show a made-up number. High jitter is an indirect sign of connection problems.
Where do the “can handle” thresholds come from?
From the requirements of the services themselves: Netflix needs 15 Mbps for 4K and YouTube 20 Mbps, Zoom needs 3.8 Mbps down and 3.0 Mbps up for a 1080p call, NVIDIA GeForce NOW needs a ping below 80 ms, and YouTube Live needs 12 Mbps of upload for a 1080p 60 fps stream. For 4K we use 25 Mbps to leave some headroom.
Why does the number rise smoothly while the chart jumps?
The big number is an estimate of the result: the average speed since the connection got up to speed. By the end of the test it settles and matches the result. The chart shows the speed every half second, so you can see how the network behaves: Wi-Fi and downloads on other devices cause dips and spikes.
Is it free?
Yes, it’s free, with no sign-up.