Article — Mbps Converter
Mbps converter: bits, bytes, and what your ISP is actually selling
An Mbps converter swaps megabits per second for megabytes per second, kilobits, gigabits, or larger units, with a single anchor: 1 byte = 8 bits. 100 Mbps equals 12.5 MB/s exactly. 1 Gbps equals 125 MB/s. ISPs advertise in Mbps because the number is eight times larger than the equivalent MB/s. File-transfer apps display MB/s because file sizes are measured in bytes. Both numbers describe the same speed, just in different units. Pick the target unit from the dropdown and the converter runs in both directions at any precision.
The default target is MB/s because that is what download progress bars show. Switch to Kbps for legacy dial-up or low-end DSL, Gbps for fiber tiers, KB/s for small transfers, or GB/s for backbone and datacenter links.
The Mbps converter formula
The two formulas that matter are Mbps divided by 8 = MB/s, and Mbps times 1000 = Kbps. Every other conversion in the dropdown derives from these. To get Gbps, divide Mbps by 1000. To get KB/s, take MB/s and multiply by 1000. To get GB/s, divide MB/s by 1000. The factor 8 is exact (1 byte = 8 bits), and the factor 1000 is decimal, not binary, per IEC 80000-13.
1 Mbps = 0.125 MB/s divide by 8100 Mbps = 12.5 MB/s standard cable1 Gbps = 1000 Mbps = 125 MB/s gigabit fiber10 Gbps = 1.25 GB/s 10G fiber1 Mbps = 1000 Kbps decimal multiplierfile MB ÷ speed MB/s = seconds transfer timeMbps converter vs MB/s
The single most common source of confusion in home networking is Mbps versus MB/s. A 100 Mbps cable plan does not download a 100 MB file in one second. It downloads it in eight seconds at theoretical line rate, because the line carries 100 megabits per second and the file is 100 megabytes (800 megabits). Divide the Mbps number by 8 to get the MB/s rate that file-transfer apps show.
The bit-versus-byte mismatch is not a marketing trick added later. IEEE 802.3, the Ethernet standard published in 1983, defined link speed in bits per second from day one. Routers, switches, and modems all count bits because that is what the physical layer sends. Files are measured in bytes because that is what filesystems store. The Mbps converter sits between the two.
Mbps to Gbps and beyond
1 Gbps equals 1000 Mbps, by IEC standard. That is decimal multiplication, not binary, so the conversion is exact and round. Gigabit fiber plans top out at 1 to 5 Gbps for consumers; multi-gigabit and 10 Gbps fiber are appearing in dense urban markets. Above Gbps, datacenter and backbone speeds enter Tbps territory: 1 Tbps = 1000 Gbps = 125 GB/s. A submarine cable typically carries 100 to 400 Tbps of capacity across multiple wavelengths on multiple fibers.
ISP tiers and Mbps numbers
US and European ISPs cluster their plans at standard tiers. Basic broadband is 25 Mbps, the FCC's current minimum threshold for "broadband." Mid-tier cable is 100 to 300 Mbps. Fiber plans start at 500 Mbps and climb to 1, 2, 5, and 10 Gbps. 5G fixed wireless tops out around 300 Mbps in most markets. The Mbps converter shows what each tier actually delivers in MB/s, which is the number that matters for file downloads.
Mbps for streaming and gaming
Netflix HD requires 5 Mbps; Netflix 4K requires 25 Mbps. YouTube 4K is 20 Mbps. Twitch 1080p is 6 Mbps. Cloud gaming (GeForce Now, Xbox Cloud) wants 25 to 35 Mbps for 1080p and 35 to 50 Mbps for 4K. A typical household with one 4K stream, two HD streams, and a gaming session needs 75 to 100 Mbps to run without buffering. That is why 100 Mbps is the standard home tier in most countries.
Video-call quality depends more on upload speed than download. Zoom 1080p needs 3 Mbps up; Google Meet wants 3.2 Mbps up. Asymmetric cable plans (100 Mbps down, 10 Mbps up) often hit upload ceilings during simultaneous calls. Fiber plans run symmetric and avoid this.
Real-world vs advertised Mbps
Speedtest.net typically shows 90 to 100 percent of advertised speed because it uses parallel streams to a nearby server. Real-world file transfers show 60 to 80 percent because the data has to traverse multiple ISPs, accept TCP windowing, and recover from packet loss. A 100 Mbps cable plan that benchmarks at 95 Mbps on Speedtest will transfer a 1 GB game patch in 100 to 130 seconds, not the theoretical 80 seconds.
If your phone shows 80 Mbps on a 1 Gbps fiber plan, the bottleneck is WiFi, not the ISP. WiFi 5 (802.11ac) tops out near 600 Mbps in practice; WiFi 6 (802.11ax) can reach 1 Gbps but only on a clean channel with a recent device. Wired Ethernet at 1 Gbps shows the actual line rate.
Mbps converter for download time
To estimate download time, convert Mbps to MB/s (divide by 8), then divide the file size in MB by the MB/s value. A 1 GB file (1000 MB) at 100 Mbps (12.5 MB/s) takes 80 seconds at line rate; add 20 to 40 percent overhead. A 15 GB 4K movie at 50 Mbps takes 40 minutes line-rate or about 50 minutes real-world. The Mbps converter handles the bit-to-byte step; the division by file size is straightforward from there.
Common Mbps converter mistakes
The first mistake is reading Mbps as MB/s. A 1 GB file on a 100 Mbps connection is not a 10 second download. It is 80 seconds at line rate, or 100 to 110 seconds in practice. The 8-times factor is the entire point of the conversion.
The second mistake is using 1024 instead of 1000 for the Kbps to Mbps step. Network units are decimal under IEC 80000-13: 1 Mbps = 1000 Kbps, not 1024. Binary (1024) multipliers apply only to memory (RAM, storage), where 1 KiB = 1024 bytes. For network speed, always use 1000.
The third mistake is treating peak speed as sustained. ISPs advertise burst speeds that hold for the first few seconds of a transfer; sustained speed over a long download settles to the line rate minus overhead. A 100 Mbps cable plan may peak at 110 Mbps for the first second of a Speedtest run and settle to 90 to 95 Mbps for the rest. Always evaluate sustained speed on a 30-second or longer transfer.