MB/s to Mbps Converter

Convert megabytes per second to megabits per second. Multiply by 8 to find the link capacity a measured transfer rate actually consumes.

From a measured rate to a link requirement

This direction is the one you use when planning rather than decoding. A backup window, a replication target or a measured copy rate all give you bytes per second, and the hardware you buy is specified in bits per second. Multiplying by 8 is the bridge.

Converting MB/s to Mbps

Mbps = MB/s × 8

  1.25 MB/s × 8 =   10 Mbps
  12.5 MB/s × 8 =  100 Mbps
    50 MB/s × 8 =  400 Mbps
   112 MB/s × 8 =  896 Mbps
   125 MB/s × 8 = 1,000 Mbps = 1 Gbps

The last line is the important one to memorise: 125 MB/s is exactly 1 Gbps. If a single stream reaches 112 MB/s it is using about 90% of a gigabit link, which is the realistic maximum once TCP/IP overhead is included.

Sizing a link from a throughput requirement

The conversion is the first step; the second is applying an efficiency factor so the plan reflects reality rather than the theoretical ceiling.

Example: sizing a replication link

Requirement: replicate 500 GB overnight in a 6-hour window. First convert the volume to bits: 500 GB is 500 × 8,000,000,000 = 4,000,000,000,000 bits. The window is 6 × 3,600 = 21,600 seconds. Required useful throughput is 4,000,000,000,000 ÷ 21,600 = 185.2 Mbps.

185.2 Mbps ÷ 0.94 efficiency = 197 Mbps of raw link capacity

A 250 Mbps circuit covers that with headroom; a 200 Mbps circuit does not, once the efficiency factor is included. Working in bytes instead: 500 GB ÷ 21,600 s = 23.1 MB/s, and 23.1 × 8 = 185 Mbps — the same answer by the shorter route.

The bandwidth calculator performs this in the other direction, taking a volume and a window and returning the required speed with the efficiency factor applied.

Unit spellings you will meet

Equivalent byte-rate unit spellings
Written as	Means	Bits per second
MB/s	Megabytes per second	8,000,000
MBps	Megabytes per second	8,000,000
MB/sec	Megabytes per second	8,000,000
MiB/s	Mebibytes per second (binary)	8,388,608
GB/s	Gigabytes per second	8,000,000,000
GiB/s	Gibibytes per second (binary)	8,589,934,592
KB/s	Kilobytes per second	8,000
KiB/s	Kibibytes per second (binary)	8,192

The 4.9% difference between MB and MiB compounds at higher prefixes: GB against GiB differs by the same 4.9%, while TB against TiB is also 4.9%. It does not accumulate with the prefix size, because each step applies the same single factor.

Common mistakes

Multiplying when you should divide. Going from bytes to bits multiplies; going from bits to bytes divides. Getting the direction wrong produces a planning error of 64×, not 8×, because it compounds.
Ignoring protocol efficiency. A calculated requirement of 185 Mbps does not fit in a 200 Mbps link reliably once TCP overhead is present. Provision at least 10% above the theoretical figure.
Planning for the sum of peak rates. Ten systems each replicating at 12.5 MB/s do not necessarily need a 1 Gbps link, but if their schedules overlap they do. Serialise the jobs or size for the overlap.
Forgetting the disk at the far end. A link faster than the destination storage can absorb is wasted capacity; the write path becomes the bottleneck.

Also: Mbps to MB/s Converter · Gbps to MB/s Converter · IP to Decimal Converter · IP to Hex Converter · IP to Binary Converter

Reference: throughput and link size

Common throughput figures and the link they require
Throughput	In Mbps	Link needed (at 94% efficiency)	Typical context
1 MB/s	8 Mbps	9 Mbps	Slow broadband
3 MB/s	24 Mbps	26 Mbps	HD video streaming
6.25 MB/s	50 Mbps	53 Mbps	Basic fibre
12.5 MB/s	100 Mbps	106 Mbps	Standard fibre
25 MB/s	200 Mbps	213 Mbps	Fast fibre
50 MB/s	400 Mbps	426 Mbps	High-end fibre
112 MB/s	896 Mbps	953 Mbps	Saturating 1 GbE
125 MB/s	1,000 Mbps	1,064 Mbps	Full 1 GbE line rate
312.5 MB/s	2,500 Mbps	2,660 Mbps	2.5 GbE
1,250 MB/s	10,000 Mbps	10,640 Mbps	10 GbE

Notice the last column in the middle rows: a 1 GbE link cannot quite deliver 125 MB/s of application throughput because the theoretical figure assumes zero overhead. The practical ceiling on a well-tuned 1 GbE path is about 118 MB/s.

Frequently asked questions

How do I convert MB/s to Mbps?

Multiply by 8. A transfer rate of 12.5 MB/s corresponds to 100 Mbps of link capacity, because each byte carries eight bits. The formula is Mbps = MB/s × 8.

Why multiply instead of divide?

Because bits are smaller than bytes, so the same transfer expressed in bits is a larger number. One megabyte per second moves 8 megabits every second, so the bit-rate figure is always eight times larger than the byte-rate figure for the same throughput.

What link speed do I need for 50 MB/s?

At least 400 Mbps, since 50 × 8 = 400. To account for protocol overhead you should provision more than that — at roughly 94% TCP efficiency you need about 425 Mbps of raw capacity, so a 500 Mbps or 1 Gbps link is the practical choice.

How do I size a backup link from a throughput requirement?

Convert the required throughput to Mbps, then divide by a realistic efficiency figure. For a nightly backup that must move 1 TB in 8 hours: 1 TB is 8,000,000 megabits, divided by 28,800 seconds gives 278 Mbps of useful throughput, and dividing by 0.94 gives about 296 Mbps of link capacity. A 500 Mbps link leaves comfortable headroom.

Is MB/s the same as MBps?

Yes. A forward slash and a capital P are both common ways of writing 'per', so MB/s, MBps and MB per second all mean megabytes per second. The important distinction is the capital B, which means bytes rather than bits.

Should I use MiB/s or MB/s for disk throughput?

Disk manufacturers and most benchmarking tools use decimal MB/s where 1 MB = 1,000,000 bytes, while some operating systems report MiB/s where 1 MiB = 1,048,576 bytes. The difference is 4.9%, so a drive quoted at 500 MB/s reads as about 477 MiB/s in a tool that uses binary units. Neither is wrong; they are different scales.