Audited 31 Jul 2026·Last updated 28 Oct 2026·5 citations·Tier 1·0 uses

Mbps Converter — Megabits to Megabytes per Second

Convert data rates between bps, kbps, Mbps, Gbps and B/s, kB/s, MB/s, GB/s, with 8 bits to the byte and decimal prefixes: 300 Mbps is 37.5 MB/s.

Mbps Converter

Enter a non-negative rate. Every unit in this calculator means per second.
From
To
Converted rate
37.5
The entered rate expressed in the unit chosen under To, on the decimal scale where kilo is 1,000.
Bits per second
300,000,000 bps
Kilobits per second
300,000 kbps
Megabits per second
300 Mbps
Gigabits per second
0.3 Gbps
Bytes per second
37,500,000 B/s
Kilobytes per second
37,500 kB/s
Megabytes per second
37.5 MB/s
Gigabytes per second
0.0375 GB/s

Background.

A broadband plan sold as 300 Mbps, and a game launcher that never climbs past about 35 MB/s. It looks as if the provider is delivering a tenth of what you pay for, but nearly all of the gap is notation. The lowercase b in Mbps stands for bits, the capital B in MB/s for bytes, and a byte is eight bits, so 300 Mbps can never show as more than 37.5 MB/s. Software that counts megabytes in steps of 1,024 rather than 1,000 shaves the display to 35.76, and the headers that travel with every packet take a few percent more. The line may be working perfectly.

Network speeds have been quoted in bits per second since the telephone network went digital, when one voice channel carried 8,000 samples a second of 8 bits each: 64 kbps. Files, disks and download counters work in bytes, because that is how data is stored. Each time a speed crosses from one world to the other, someone has to divide or multiply by eight, and the two abbreviations differ only in the case of a single letter.

The converter takes a rate in any of eight units, bits or bytes per second at the plain, kilo, mega or giga scale, and gives it in the unit you choose, with all eight versions listed underneath. The prefixes are the decimal ones the BIPM defines for the SI: kilo is 1,000, mega 1,000,000 and giga 1,000,000,000. Every advertised line rate uses them, so 1 Gbps is exactly 1,000 Mbps and 1 MB/s is exactly 8 Mbps.

What comes out is a change of units, not a speed test. It tells you what a stated rate means in another unit; it cannot tell you how fast a real transfer will run once Wi-Fi conditions, congestion, a slow server or a busy disk join in. For the time a particular file will take, the download-time calculator lets you add an allowance for overhead.

What is mbps converter?

A data rate is an amount of information moved per second. The smallest unit is the bit, a single binary digit; the byte is a group of eight bits, the size NIST describes as the contemporary standard and the unit in which files and memory are counted. Rates are therefore written two ways, in bits per second (bps, kbps, Mbps, Gbps) or bytes per second (B/s, kB/s, MB/s, GB/s), and at the same prefix the byte figure is one eighth of the bit figure. A rate is different from a quantity: 500 MB is a file, 500 MB/s is a speed, and you need a time to get from one to the other. It also helps to separate bandwidth, the capacity a link is sold or signalled at, from throughput, the useful data that actually arrives. Converting units works the same for both but does not close the gap between them.

Which figure you start from changes what the conversion tells you. A plan speed is a sold capacity. A speed-test result is measured delivery, so converting it gives a realistic file rate. The link speed a laptop or phone reports for its Wi-Fi connection is the radio's negotiated signalling rate between device and router; it says nothing about the internet connection behind the router, and the data that actually gets through is well below it.

How to use this calculator.

  1. Type the rate into Transfer rate exactly as your plan, router, speed test or app shows it. Every unit offered is already per second.
  2. Set From to the unit the figure came in, checking the case of the b: Mbps, Mb/s and Mbit/s are megabits per second, while MBps and MB/s are megabytes per second.
  3. Set To to the unit you want to compare against, usually MB/s if you are matching a download counter or Mbps if you are matching an internet plan.
  4. Read the converted rate, then the list of all eight units below it if you need a different scale, such as Gbps for a network card or kB/s for a slow link.
  5. If your computer reports sizes in units of 1,024, multiply its MB/s reading by 1.048576 before entering it, because the From options here are decimal.

The formula.

target = value × bitsPerSecond(from) ÷ bitsPerSecond(to)

Every unit has a fixed size in bits per second. The bit units are 1 for bps, 1,000 for kbps, 1,000,000 for Mbps and 1,000,000,000 for Gbps. The byte units are eight times larger at each step: 8 for B/s, 8,000 for kB/s, 8,000,000 for MB/s and 8,000,000,000 for GB/s. A conversion multiplies the entered value by the size of the source unit to get bits per second, then divides by the size of the target unit:

result = value × size(from) ÷ size(to)

Going from Mbps to MB/s, that ratio is 1,000,000 ÷ 8,000,000, so you divide by 8. Going from GB/s to Mbps it is 8,000,000,000 ÷ 1,000,000, so 1 GB/s is 8,000 Mbps. Moving between prefixes in the same family changes the figure by a power of 1,000; moving between bits and bytes changes it by 8.

All of these factors are exact by definition, so a value converted out and back returns unchanged. There is no 1,024 anywhere in them. The powers of two belong to the IEC binary prefixes, kibi, mebi and gibi (Ki, Mi, Gi), which NIST recommends for memory-style quantities. One mebibyte per second is 1,048,576 bytes a second, or exactly 8.388608 Mbps, about 4.9% more than a decimal megabyte per second. None of the units offered uses binary prefixes, so a binary reading needs that 1.048576 correction before it goes in.

The conversion also leaves out everything that is not a unit change: the packet headers, error correction, retransmissions and line coding that sit between a link's rated speed and the data you receive. Those are real losses, but they depend on the technology, so no single percentage would be right everywhere.

A worked example.

Example

Take a 300 Mbps internet plan and convert it to MB/s. First into plain bits: 300 × 1,000,000 = 300,000,000 bits per second. Eight bits make a byte, so 300,000,000 ÷ 8 = 37,500,000 bytes per second. Dividing by 1,000,000 for the mega prefix gives 37.5 MB/s. The list below the result shows the same rate at every scale: 300,000 kbps, 0.3 Gbps, 37,500 kB/s and 0.0375 GB/s. What does 37.5 MB/s buy? A 50 GB game is 50,000 MB, and 50,000 ÷ 37.5 = 1,333.3 seconds, a little over 22 minutes, if the line ran at its full rated speed with nothing else on it. Running flat out for an hour, the same connection could move 37.5 × 3,600 = 135,000 MB, or 135 GB. A real download will take somewhat longer, because packet headers and any competing traffic share those 300 megabits. The conversion also runs the other way. Suppose a download counter that counts in 1,024s reads 11.5 MB/s. Multiplying by 1.048576 turns that into 12.0586 decimal MB/s, and entering 12.0586 MB/s with Mbps as the target gives about 96.47 Mbps: a reasonable showing for a 100 Mbps plan once headers are paid for.

to UnitMBps
value300
from UnitMbps

Frequently asked questions.

How many MB/s is 100 Mbps?
12.5 MB/s: divide by eight because a byte holds eight bits. If your computer counts megabytes as 1,048,576 bytes, the same rate appears as about 11.92 MB/s on its display. Either way that is the ceiling before overhead, so a real download over a 100 Mbps line settles somewhat below it.
What download speed should a 1 Gbps connection reach?
The unit conversion says 125 MB/s. Over wired Ethernet with standard 1,500-byte packets, each frame spends 1,538 byte-times on the wire to carry 1,460 bytes of TCP data when no TCP options are in use, about 94.9% efficiency, so the practical ceiling is near 949 Mbps or 118.7 MB/s. Software counting in 1,024s shows that as roughly 113 MB/s.
Is Mbps the same as MB/s?
No. Mbps, Mb/s and Mbit/s mean megabits per second; MBps, MB/s and Mbyte/s mean megabytes per second, eight times as much. Strictly, a lowercase m is the SI symbol for milli, so mbps would mean millibits per second; in practice it almost always means megabits, but check the source when the case matters.
Why do network speeds count in 1,000s rather than 1,024s?
A link sends a fixed number of bits every second, and telecommunications has always counted them in decimal: a digital telephone channel carries 64,000 bits per second, and a gigabit Ethernet link one billion. Powers of 1,024 come from memory addressing and are properly written with the binary prefixes Ki, Mi and Gi. Drive makers use decimal as well, which is why a 1 TB drive, 1,000,000,000,000 bytes, shows up in Windows as about 931 GB.
Why does my computer show a lower MB/s than this converter?
Often because it divides by 1,048,576 rather than 1,000,000 but still labels the result MB. Windows File Explorer reports sizes that way, for example. A perfect 300 Mbps transfer is 37.5 decimal MB/s but about 35.76 in binary megabytes, a 4.6% difference that has nothing to do with the network.
How long will a file take to download at a given speed?
Convert both to the same family, then divide size by rate. A 1 GB file is 8,000 megabits, so at 10 Mbps it needs at least 800 seconds, 13 minutes 20 seconds. Real transfers run slower than that ideal figure, which is why the download-time calculator includes an overhead allowance. The wait scales inversely with speed: at 300 Mbps the same 8,000 megabits need about 26.67 seconds.
How much data can a connection use in an hour?
Multiply the rate in MB/s by 3,600. A stream running steadily at 10 Mbps is 1.25 MB/s, which comes to 4,500 MB, or 4.5 GB, every hour. That arithmetic is useful against a mobile data bundle or a capped plan, where the limit is a quantity and the activity is a rate.
Why aren't USB and SATA speeds simply divided by eight?
Some links spend part of their signalling rate on line coding. SATA at 6 Gbps and first-generation USB 3 at 5 Gbps use 8b/10b coding, sending ten bits on the wire for every eight bits of data, so their byte ceilings are 600 MB/s and 500 MB/s, not 750 and 625. USB 2.0 at 480 Mbps is 60 MB/s before its own protocol overhead.
Can I convert a file size in MB straight into Mbps?
Not without a time, because one is a quantity and the other a rate. If a 600 MB file arrived in two minutes, the average rate was 600 ÷ 120 = 5 MB/s, and the converter turns that into 40 Mbps. That is a handy way to check what speed a past download really achieved.
Why can a fast connection still download slowly from a distant server?
TCP can only send a limited amount of data before waiting for an acknowledgement, so throughput is capped at the window size divided by the round-trip time. Without window scaling, a 65,535-byte window over a 100 ms round trip limits a single connection to about 5.24 Mbps, however fast the line. Current operating systems negotiate window scaling, so the cap is far higher today, but packet loss on a long path can still hold a single connection well below the line rate. The bandwidth-delay product calculator works through the window limit.

How this page was produced

Published by
Quanta Calculator
Primary sources
5 cited below
Method
target = value × bitsPerSecond(from) ÷ bitsPerSecond(to)
Published
Last verified

Built with AI assistance and verified by automated tests against the cited sources — every worked example on this page is computed by the same code that runs the calculator. How we build and check calculators.

In this category

Embed

Quanta Pro

Paid features are coming later.

  • All 1560 calculators remain free
  • No billing is enabled
Coming soon