Data Transfer Speed Converter

Convert between bps, Mbps, Gbps, MB/s, and GB/s — and finally see why a 100 Mbps connection downloads at about 12.5 MB/s.

Data Transfer Speed

Mbps, MB/s, Gbps

From
Result
0.125

1 bps = 0.125 B/s

Popular conversions

What Is a Data Transfer Speed Converter?

A data transfer speed converter translates network and transfer rates between units — megabits per second to megabytes per second, gigabits per second to MB/s. The central confusion is bits versus bytes: internet speeds are quoted in bits per second (Mbps, lowercase b), while file downloads and disk speeds are shown in bytes per second (MB/s, capital B). Since a byte is 8 bits, the two differ by a factor of 8.

This converter routes through bits per second and keeps the bit/byte distinction explicit. It's the reason a '100 Mbps' broadband plan downloads a file at roughly 12.5 MB/s, not 100 — the speed is the same, but bits-per-second and bytes-per-second are eight times apart. The tool also handles the metric prefixes (kilo, mega, giga) that scale rates by 1,000.

This is one category of the full Unit Converter — pair it with our percentage calculator or scientific calculator for related everyday maths.

How Transfer Speed Conversion Works

Everything routes through bits per second

Each unit has a fixed bps factor. The converter normalises to bits per second, then projects to byte-based and prefixed units.

8 bits per byte

Mbps (megabits/s) ÷ 8 = MB/s (megabytes/s). This factor of 8 is why download speeds look far smaller than the advertised plan.

Prefixes scale by 1,000

1 Mbps = 1,000 kbps; 1 Gbps = 1,000 Mbps. Network rates use decimal (SI) prefixes, not binary.

Speed vs total data

A rate (Mbps) times a duration gives total data transferred. Divide a file size by the rate to estimate download time.

Core Transfer Speed Conversion Factors

Divide by 8 to go from bits to bytes; multiply prefixes by 1,000.

Mbps → MB/s

÷ 8

Megabits per second divided by 8 gives megabytes per second. 100 Mbps = 12.5 MB/s.

Gbps → Mbps

× 1000

One gigabit per second is 1,000 Mbps — the scale of fibre and data-centre links.

Download time

t = size / rate

File size divided by transfer rate gives the time, once units match (both bits or both bytes).

How to Use the Transfer Speed Converter

  1. 1

    Enter the speed value

    Type the rate you want to convert — a broadband speed, a transfer rate, a link capacity.

  2. 2

    Choose the 'from' unit

    Pick bps, kbps, Mbps, Gbps (bits) or KB/s, MB/s, GB/s (bytes). Mind bits vs bytes.

  3. 3

    Choose the 'to' unit

    Select the target unit, or swap the two to reverse direction.

  4. 4

    Read every unit at once

    The all-units table shows the rate in both bit-based and byte-based units, exposing the factor of 8.

Key Transfer Speed Concepts

Bits per second

The standard for network and internet speeds (bps, Mbps, Gbps). Lowercase 'b'. A 100 Mbps plan moves 100 million bits each second.

Bytes per second

The standard for file downloads and disk transfers (B/s, MB/s). Capital 'B'. Equals the bit rate divided by 8.

The factor of 8

8 bits per byte. Forgetting it makes downloads seem eight times slower than the plan — the most common bandwidth confusion.

Decimal prefixes

Network rates use SI prefixes (×1,000), so 1 Gbps is 1,000 Mbps. Storage may use binary, but transfer rates are decimal.

Real-World Transfer Speed Conversions

🌐

Broadband plans

A 100 Mbps plan downloads at about 12.5 MB/s. The factor of 8 explains why the file-manager figure looks smaller.

📥

Download time

A 1 GB file over 100 Mbps takes ~80 seconds (1,000 MB ÷ 12.5 MB/s). Converting rate to MB/s makes ETA math easy.

🚀

Fibre and gigabit

A 1 Gbps fibre link is 125 MB/s. Gigabit internet quotes bits; your transfers show bytes.

📡

Wi-Fi

A Wi-Fi link negotiated at 866 Mbps tops out near 108 MB/s of throughput before overhead. Bits advertised, bytes delivered.

💽

SSD speeds

An SSD rated 550 MB/s is byte-based already (4,400 Mbps). Drives use MB/s; networks use Mbps.

🎮

Game downloads

A 50 GB game on a 200 Mbps line takes ~33 minutes (25 MB/s). The conversion turns the plan speed into a real ETA.

Best Practices for Transfer Speed Conversion

  • Divide Mbps by 8 for MB/s. Internet speeds are bits; downloads are bytes. The factor of 8 is the single most important transfer-speed conversion.
  • Watch capital B vs lowercase b. Mbps (megabits) and MB/s (megabytes) differ 8×. The case of the 'B' tells you which — and it's easy to misread.
  • Use decimal prefixes for rates. Network speeds scale by 1,000 (Gbps = 1,000 Mbps). Unlike storage capacity, transfer rates don't use binary prefixes.
  • Account for overhead. Real throughput is below the advertised rate due to protocol overhead. The unit conversion gives the ceiling, not the guaranteed speed.
  • Match units before computing time. To estimate download time, put file size and rate in the same base (both bytes or both bits) before dividing.

Common Transfer Speed Conversion Mistakes

Confusing Mbps with MB/s

They differ by 8×. Expecting a 100 Mbps plan to download at 100 MB/s ignores the bits-to-bytes conversion.

Misreading the B's case

Lowercase b is bits, capital B is bytes. A single case slip changes the value eightfold.

Using binary prefixes for rates

Transfer speeds are decimal (1 Gbps = 1,000 Mbps), not 1,024-based. Applying binary scaling misstates the rate.

Ignoring overhead in estimates

Treating the advertised rate as guaranteed throughput overestimates real-world download speed, which sits below the ceiling.

Why Transfer Speed Conversion Matters

Data transfer speed is where the bit-versus-byte split bites hardest: broadband is sold in megabits per second, but every download manager reports megabytes per second, leaving users convinced their connection is eight times slower than promised. Converting correctly — dividing by 8 — turns an advertised plan into a realistic download speed and ETA.

As gigabit fibre, fast Wi-Fi, and large game and media files become routine, fluent conversion between Mbps, MB/s, and Gbps is essential for setting expectations and diagnosing connections. A converter that routes through bits per second and shows bit- and byte-based units together makes the factor of 8 obvious and download-time math trivial.

Built for anyone comparing internet plans, estimating download times, or sizing network links — converting between Mbps, MB/s, and Gbps.

Linear unit factors follow the BIPM SI brochure, the NIST Guide to the SI, and ISO 80000. Currency rates load live from open.er-api.com; crypto prices from CoinGecko. See our methodology and editorial policy. Educational only — not certified for regulated trading, settlement, medical, or aerospace use.

Data Transfer Speed Converter FAQs

Because internet speeds are quoted in megabits per second (Mbps) while downloads are shown in megabytes per second (MB/s), and a byte is 8 bits. Dividing 100 Mbps by 8 gives 12.5 MB/s — that's the expected maximum download speed, and it's working as intended, not a slow connection.

Mbps is megabits per second (lowercase b), used for network and internet speeds. MB/s is megabytes per second (capital B), used for file transfers and disk speeds. Since one byte equals 8 bits, MB/s = Mbps ÷ 8. The case of the 'B' is the key signal for which one you're looking at.

Divide the file size by the transfer rate, with both in the same base. For a 1 GB (1,000 MB) file on a 100 Mbps connection: 100 Mbps ÷ 8 = 12.5 MB/s, then 1,000 ÷ 12.5 = 80 seconds. Real time is a bit longer due to protocol overhead.

One gigabit per second equals 1,000 megabits per second, since transfer rates use decimal (SI) prefixes that scale by 1,000. In byte terms, 1 Gbps is 125 MB/s. So gigabit fibre can move data at up to about 125 megabytes per second before overhead.

Decimal. Network and transfer rates scale by 1,000 (1 Mbps = 1,000 kbps, 1 Gbps = 1,000 Mbps), unlike storage capacity where binary (1,024-based) units are common. So a gigabit is exactly 1,000 megabits, not 1,024.

It uses exact definitions (8 bits per byte, decimal prefix steps of 1,000) and routes every conversion through bits per second at full precision, so the result is exact — it gives the theoretical maximum rate, before real-world protocol overhead.