Guides
What Is Mbps?
Mbps means megabits per second. Learn how it differs from MB/s and MiB/s, calculate transfer time and compare measurements under matching conditions.
Mbps means megabits per second: 1 Mbps is 1,000,000 bits per second. It measures a data transfer rate, rather than file size or a monthly data allowance. Download and upload are separate directions. Latency, often measured in milliseconds (ms), describes time rather than throughput.
Bits, bytes and prefixes
One byte (B) contains eight bits. A megabyte (MB) is 1,000,000 bytes; a mebibyte (MiB) is 1,048,576 bytes. MB/s and MiB/s therefore differ. Check the application’s label and documentation if its meaning is unclear. These conversions exclude protocol overhead; approximate values below are rounded.
- 1 Mbps = 0.125 MB/s. This is a unit conversion, rather than an application performance guarantee.
- 80 Mbps = 10 MB/s. Multiply decimal MB/s by eight to obtain Mbps.
- 100 Mbps = 12.5 MB/s, approximately 11.92 MiB/s. Multiply MiB/s by 8.388608 to obtain Mbps.
- 1 Gbps = 1,000 Mbps = 125 MB/s. The unit alone does not identify the connection technology.
A transfer-time calculation
For an illustrative calculation, assume a constant useful-data rate of 500 Mbps, or 62.5 MB/s. A 5 GB (5,000 MB) file then takes an ideal 5,000 / 62.5 = 80 seconds. A larger 5 GiB file takes approximately 85.90 seconds at that rate. This is neither a measurement of your connection nor a time guarantee for a 500 Mbps plan. Protocol overhead, varying throughput, server limits and device processing can change actual time. A game update may also include waiting, unpacking and installation after transfer.
What VMAXCHECK measures
VMAXCHECK uses M-Lab NDT to measure download and upload over a single TCP stream to a measurement server, and displays a server-reported estimate of TCP round-trip time. Rates appear in Mbps, or Gbps from 1,000 Mbps. Results describe that path, device, method and moment. They do not establish every application’s speed, a separate jitter value or the performance of the contracted access line alone. Run load-generating tests outside important calls.
Why link rate and throughput differ
A link’s transmission rate and useful data delivered by an application describe different layers. Protocol information and retransmissions consume capacity; the server, path, competing traffic and device may also limit throughput. There is no universal few-percent gap or rule that Wi-Fi must be slower than Ethernet. A device’s wireless link rate is not an internet throughput measurement. Check how your own contract defines download and upload speeds before comparing; providers’ terms differ.
Four comparisons before drawing conclusions
- Record the application, server, time, direction, file size and exact rate unit. Distinguish active data transfer from waiting or installation. Save results and relevant device or router events before restarting.
- Compare Wi-Fi with supported Ethernet on the same device, application or measurement server and method at nearby times. Treat a position change as a separate comparison. Improvement indicates changed conditions; it does not prove a particular fault.
- Record other traffic and compare without your own transfer, then with one permitted download or upload. Pause only traffic you are authorized to stop, record the direction and change one factor at a time. Keep load tests outside important calls.
- Compare another time or another permitted device one factor at a time, then recheck the actual application. Repeated differences can be investigated with dated method and condition records through private support. Keep protections and managed-network rules in place.
More than a speed number
Consider download, upload and latency alongside the actual application’s behavior. A higher Mbps value does not guarantee stable games or calls. If your traffic fills the available capacity, extra capacity may reduce queuing, but it does not automatically change distance or routing. Use current application requirements, simultaneous use and measurement conditions instead of treating 100 Mbps as a universal quality guarantee.
Common questions
- Is 12.5 MB/s equal to 100 Mbps? Yes, if MB means decimal megabytes. At 12.5 MiB/s the rate is approximately 104.86 Mbps. Converting units alone does not measure the actual speed of your contracted line.
- Is Mbps a data allowance? No, it is a rate. GB or GiB can describe data amounts or file sizes; check which definition is used.
- Does a smaller download-app number prove a connection fault? No. Check units, direction, server, transfer phase and other traffic first. Comparable measurements and actual application behavior are more useful than one number.