Mbps to Gbps Converter
Convert Mbps to Gbps — a thousand to one, for broadband and network links.
Updated
Gbps
1.0000Gbps
1,000 Mbps = 1.0000 Gbps
In short
How many Mbps are in a Gbps?
1,000 Mbps. Divide megabits per second by 1,000 for gigabits, so 500 Mbps is 0.5 Gbps. Bit rates are always decimal — a megabit is a million bits everywhere, with none of the 1,024 ambiguity that surrounds the megabyte.
One thousand, no exceptions. This is the only page on the data shelf with a single unambiguous factor.
Mbps to Gbps — quick reference
| Mbps (Mbps) | Gbps (Gbps) |
|---|---|
| 100 Mbps | 0.1000 Gbps |
| 200 Mbps | 0.2000 Gbps |
| 300 Mbps | 0.3000 Gbps |
| 500 Mbps | 0.5000 Gbps |
| 940 Mbps | 0.9400 Gbps |
| 1,000 Mbps | 1.0000 Gbps |
| 2,000 Mbps | 2.0000 Gbps |
| 10,000 Mbps | 10.0000 Gbps |
The formula, worked line by line
One division by a thousand, with no convention to choose. Bit rates are the one corner of this subject where the SI prefixes were never contested, so the only judgement left is about what the number describes rather than how it was computed.
“A line rate is what the wire signals. Throughput is what survives the framing. They are different numbers and both are honest.”
Keeping those apart removes most of the confusion about broadband performance. The advertised figure is a property of the link; the measured figure is a property of the link plus the protocol plus the path plus the far end. Neither is a lie, and they are not supposed to match.
gigabits per second = megabits per second / 1,000
megabytes per second = megabits per second / 8
1 Gbps = 10^9 bits per second = 125 MB/s
1000BASE-T line rate = 1,000 Mb/s exactly
Ethernet wire cycle = 1,500 + 14 + 4 + 8 + 12 = 1,538 bytes- Line rate
- 1,000 Mbps
- Ceiling in bytes
- 125 MB/s
- At 94 percent efficiency
- about 117.5 MB/s
- Over sixty seconds
- about 7 GB
- One minute
- roughly 7 gigabytes
The efficiency figure is the one to treat as approximate. It depends on the MTU, on whether IPv4 or IPv6 is in use, on TCP options, and on how much of the traffic is small packets rather than full frames — which is why the honest form of this answer is a range.
Why 1000BASE-T is exactly a billion bits
The standard that defines gigabit Ethernet over copper, published as IEEE 802.3ab in 1999 and later folded into 802.3, specifies a nominal data rate of 1,000 Mb/s. That is a decimal billion bits per second, not 2^30. Real hardware runs to an oscillator tolerance around that rated value, but the rating itself carries no binary interpretation.
The rates you will meet
- 100BASE-TX
- 100 Mbps = 0.1 Gbps
- 1000BASE-T
- 1,000 Mbps = 1 Gbps
- 2.5GBASE-T
- 2,500 Mbps = 2.5 Gbps
- 5GBASE-T
- 5,000 Mbps = 5 Gbps
- 10GBASE-T
- 10,000 Mbps = 10 Gbps
Each is a nominal line rate at the physical layer. What reaches an application is lower by the framing and protocol overhead described above, and the proportion lost is roughly the same at every rate.
One practical consequence: upgrading a link from one gigabit to two and a half does not make a single transfer two and a half times faster unless everything else in the path can keep up. Disk write speed, the far server, and the number of parallel connections all become the limit well before the wire does.
How to use the mbps to gbps converter
A gigabit per second is a thousand megabits per second. That is the entire conversion, and unusually for this subject there is no second answer waiting. In telecommunications the SI prefixes are used strictly: a kilobit is a thousand bits, a megabit a million, a gigabit a billion. No binary reading of a bit rate exists in any standard.
That makes rate conversions cleaner than storage conversions, and it is worth knowing why the two differ. Storage picked up binary units because memory is addressed in powers of two. A transmission line has no address space, so nothing ever pushed bit rates towards 1,024, and the decimal convention was never challenged.
1,000
Mbps in a Gbps
decimal, always
10^9
Bits per second in a Gbps
not 2^30
125
MB/s in a Gbps
divide by eight
The third figure is the one people actually want. A gigabit line carries at most 125 megabytes per second, because a byte is eight bits. That ceiling applies before any protocol overhead, and it is the honest upper bound on what a gigabit connection can deliver to a file being written to disk.
That range is worth stating as a range. The figure of 940 Mbps circulates as though it were a constant; it is a reasonable shorthand for one common configuration, and the FCC uses it in its broadband measurement work as the transport ceiling of a particular test device. It is not a property of Ethernet, and quoting it without its assumptions overstates how fixed it is.
- 100 Mbps
- 0.1 Gbps = 12.5 MB/s
- 500 Mbps
- 0.5 Gbps = 62.5 MB/s
- 1,000 Mbps
- 1 Gbps = 125 MB/s
- 2,500 Mbps
- 2.5 Gbps = 312.5 MB/s
- 10,000 Mbps
- 10 Gbps = 1,250 MB/s
The right-hand column is the theoretical byte-rate ceiling, obtained by dividing by eight. Real transfers land a few percent below it once framing and protocol headers are accounted for.
Turn a line speed into a download rate
Dividing by eight is what converts an advertised connection speed into the megabytes per second a file transfer will actually show. That page does it directly.
Open Mbps to MB/s →Megabits per second converted to gigabits per second, with the theoretical byte-rate ceiling that each line rate implies once divided by eight.
| Megabits per second | Gigabits per second | Ceiling in MB/s |
|---|---|---|
| 10 Mbps | 0.01 Gbps | 1.25 MB/s |
| 25 Mbps | 0.025 Gbps | 3.125 MB/s |
| 50 Mbps | 0.05 Gbps | 6.25 MB/s |
| 100 Mbps | 0.1 Gbps | 12.5 MB/s |
| 200 Mbps | 0.2 Gbps | 25 MB/s |
| 300 Mbps | 0.3 Gbps | 37.5 MB/s |
| 500 Mbps | 0.5 Gbps | 62.5 MB/s |
| 940 Mbps | 0.94 Gbps | 117.5 MB/s |
| 1,000 Mbps | 1 Gbps | 125 MB/s |
| 2,500 Mbps | 2.5 Gbps | 312.5 MB/s |
| 5,000 Mbps | 5 Gbps | 625 MB/s |
| 10,000 Mbps | 10 Gbps | 1,250 MB/s |
Where the missing sixty megabits go
The gap between a 1,000 Mbps line rate and the payload you can actually move is not waste; it is the machinery that makes the link work. Every Ethernet frame carries an eight-byte preamble, a fourteen-byte header, a four-byte checksum, and is followed by a twelve-byte interframe gap before the next one starts.
- Payload, standard MTU
- 1,500
- Ethernet header
- 14
- Frame check sequence
- 4
- Preamble
- 8
- Interframe gap
- 12
- Total wire cycle
- 1,538 byte-times
So 1,500 bytes of the 1,538 carried are payload, which is 97.5 percent efficiency at the Ethernet layer alone. IP and TCP headers then take 40 more bytes from inside the payload, and TCP options can take another dozen, which is what produces the 936 to 949 Mbps range.
Jumbo frames change the arithmetic in the other direction. Raising the MTU to 9,000 bytes leaves the same 38 bytes of framing around a payload six times larger, so the proportion lost falls sharply. That is why storage networks use them, and why a figure quoted for a standard MTU does not transfer to one that is not.
How regulators require speeds to be stated
The unit is not left to marketing departments in either the United States or the United Kingdom. The FCC requires broadband providers to display a consumer label giving typical download and upload speeds in Mbps, in force since 10 April 2024 for larger providers and 10 October 2024 for those with 100,000 or fewer subscriber lines.
In the United Kingdom, Ofcom uses Mbit/s in its broadband speed code of practice and much of its reporting, though not universally — some of its consumer guidance uses Mbps. Both notations mean the same thing, and both are bits rather than bytes, which is the distinction that matters when comparing a plan against a file size.
Do
- Divide by 1,000 for gigabits and by 8,000 for megabytes per second
- State the MTU and protocol version when quoting a throughput figure
- Expect a few percent below line rate on any real transfer
- Read Mbit/s and Mbps as the same unit
Don't
- Treat 940 Mbps as a fixed property of gigabit Ethernet
- Convert a bit rate using 1,024 — there is no binary megabit
- Compare an advertised Mbps figure against a file size in MB
- Assume a speed test measures the same thing your file transfer does
The last point deserves a sentence. A speed test measures a short burst against a nearby server under favourable conditions; a large file transfer measures a sustained stream against whatever server actually holds the file, over whatever path exists between you. Both are honest measurements and they routinely disagree.
Every Mbps value, worked out
111 common Mbps figures each get their own page, with the answer at full precision, the arithmetic, what rounding costs, and the nearest real-world reference point on the scale.
1 to 9 Mbps
100 to 999 Mbps
Questions people ask
Sources
Where the constants and formulas on this page come from. Each line names the figure it backs.
Broadband providers must display consumer labels stating typical download and upload speeds in Mbps, effective 10 April 2024 for larger providers and 10 October 2024 for those with 100,000 or fewer subscriber lines.
Broadband Consumer Labels — compliance dates, Public Notice DA 23-943 — Federal Communications Commission
IEEE 802.3ab specifies 1000BASE-T operation at a nominal 1,000 Mb/s over four-pair Category 5 cabling.
IEEE 802.3ab-1999 — Physical Layer Parameters for 1000 Mb/s Operation — IEEE Standards Association
Ethernet framing adds an 8-byte preamble, 14-byte header, 4-byte frame check sequence and a 12-byte interframe gap around each payload.
Encapsulation Overhead, IEEE 802.3 EFM task force materials — IEEE 802.3 Ethernet Working Group
SI prefixes are strictly powers of ten, so a kilobit is 1,000 bits rather than 1,024.
The International System of Units (SI) Brochure, 9th edition — Bureau International des Poids et Mesures
Related guides
How to Find the Volume of Hollow, Partial, and Composite Solids
A decomposition-first guide to pipes, frustums, domes, and partly filled tanks, with formulas and checks for avoiding geometric and unit errors.
August 12, 2026 · 12 min read
How to Compare Two Data Sets: Center, Spread, and Relative Difference
A practical workflow for deciding whether two sets are comparable, describing their typical values and variation, and reporting differences without overstating them.
August 11, 2026 · 10 min read
Putting JSON in a URL: Validate, Minify, Percent-Encode, or Base64url?
A decision guide for flattening, encoding, checking, and safely transporting JSON in a query string.
August 11, 2026 · 9 min read