How Much Data Does Cloudflare Speed Test Use and How Is the Server Location Chosen?

Cloudflare's Speed Test can consume up to 200MB of data in a single run, and the server location is selected automatically rather than manually. That combination matters most if you're on a metered or mobile connection, or if you're trying to figure out whether the result reflects your connection to a nearby edge or to a distant one.

Data consumption: up to 200MB per test

Cloudflare states directly that a speed test can consume up to 200MB of data. Treat that as a ceiling, not a fixed cost — the actual amount depends on how long the test runs and how fast your connection is, since a faster link moves more data in the same window.

Practical implications:

• Metered or mobile connections: one test can eat a meaningful slice of a limited data plan. If you're on a capped connection, run the test sparingly and avoid repeating it back-to-back.
• Multiple tests: the 200MB figure applies per test. Running the test several times to compare results multiplies the data used.
• Wi-Fi vs. cellular: on Wi-Fi the data usually doesn't count against a mobile allowance, but on cellular it does.

If you only need a rough sense of latency, note that latency, jitter, and packet loss are measured in milliseconds and don't require the same bulk transfer as the download and upload phases — but Cloudflare doesn't offer a latency-only mode, so any full test still carries the same up-to-200MB ceiling.

How the server location is chosen

The server location is selected automatically — there is no manual server picker described on the page. The page includes a "Server Location" heading, so the location used for your test is surfaced to you as part of the test experience.

The mechanism behind the automatic choice is geolocation. When you run the test, Cloudflare receives the IP address you use to connect and uses it to estimate your location at the country and city level, and to identify the Autonomous System Number (ASN) associated with your IP. That location estimate is what drives which nearby Cloudflare edge serves the test.

What this means in practice:

• You can't force the test to run against a specific city or region through the interface.
• The result reflects your connection to whichever edge Cloudflare deems closest based on your IP-derived location.
• If your IP geolocates incorrectly (common with VPNs, some ISPs, or corporate networks), the chosen server may not be the one physically nearest you, and the numbers can look worse than your real-world experience.

What Cloudflare receives and shares

Because server selection depends on your IP, it's worth knowing exactly what's collected:

Cloudflare states it does not share your IP address with measurement partners, and that it truncates the IP address it receives to /24 for IPv4 and /48 for IPv6 — meaning the last portion of the address is masked before storage.

Choosing whether to run it

Run the test when you want a real measurement of your connection's download, upload, latency, jitter, and packet loss, plus the Network Quality Score for streaming, gaming, and video calls. Skip it, or run it once and stop, when you're on a tight data allowance — the up-to-200MB cost per test is the deciding factor. If your results look unexpectedly poor, check whether a VPN or an unusual network setup is skewing the automatic server selection before concluding your connection is slow.