MB/s to Mbps Converter

The Direction People Get Backwards

This is the mirror of the ÷8 conversion — here you multiply by 8 to go from MB/s to Mbps — and it is the direction most people actually need: your provider sold you megabits per second, but the download dialog counts megabytes per second, so the number you see will always be about one eighth of the number you were sold.

The other classic trap: uppercase B versus lowercase b. MB is megabytes (storage), Mb is megabits (speed). A "600 Mb connection" delivering "75 MB/s" is not underperforming — it is exact.

When the requirement starts in MB/s

Most bandwidth requirements are written the other way around — an ISP plan or a circuit is quoted in Mbps, and you work out what that gives you in MB/s. This converter answers the reverse question, which is the one infrastructure decisions actually start from: a storage, backup, or media workflow specifies a sustained transfer rate in MB/s, and you need to know what link speed has to be provisioned to deliver it.

• NAS and SAN planning — a backup window of 30 minutes for a 120 GB share defines a required average rate, and therefore a required link.
• WAN and ISP sizing — comparing a quoted circuit (e.g. 500 Mbps) against the MB/s a file migration actually needs.
• Cloud and egress limits — provider throughput is often metered per second, so MB/s targets map directly onto instance or volume limits.
• Stream and capture pipelines — recording or relaying a sustained MB/s feed without dropping frames.

Worked example: sizing a link for a backup window

A nightly job must move 120 GB in 30 minutes. That is 120,000 MB ÷ 1,800 s = 66.7 MB/s sustained, and 66.7 × 8 = 533 Mbps of required throughput. A 1 Gbps link clears it with margin; a 500 Mbps link does not, even though "500 Mbps" and "66.7 MB/s" look comparable at a glance.

Because the figure is a sustained average, provision headroom rather than the exact number: protocol overhead, retransmits, and the storage device itself typically consume 5–15% of the nominal rate. In practice that means sizing the link one step above the calculated value — 533 Mbps becomes a 1 Gbps port.

Limitations

• The result is a required line rate, not a guarantee of end-to-end speed: the slowest device in the path (disk, NAS controller, switch port) sets the real ceiling.
• Common practical ceilings for reference: 1 Gbps Ethernet ≈ 125 MB/s theoretical (≈112–119 MB/s real), SATA SSD ≈ 550 MB/s, mechanical HDD ≈ 150–200 MB/s sequential.
• Wi-Fi and shared links sustain far less than their rated speed, so treat any calculation on a wireless path as a best case.
• Conversions are exact; what they cannot model is how consistently your specific link will hold its rated speed.

The Factor of Eight Behind Every Download Estimate

File sizes are counted in bytes and line speeds in bits, and one byte is eight bits. A transfer of 25 MB per second therefore needs a link of 200 Mbps, and a 100 Mbps connection tops out near 12.5 MB per second before any overhead.

Real transfers land a little below the theoretical figure. Ethernet, IP and TCP headers consume roughly 5 to 10 percent of the raw rate, and Wi-Fi adds contention on top of that. When sizing a backup window or a camera uplink, convert with this tool and then keep about 10 percent of headroom rather than planning to the last megabit.