Data Transfer Speed Converter

Convert between data transfer speed units like Mbps, Gbps, KB/s, and MB/s. Includes download time estimates for common file sizes to help you understand real-world performance.

Convert Speed

Result
12.5
100 Megabit/s (Mbps) = 12.5 Megabyte/s (MB/s)

Conversion Details

Input Speed100 Megabit/s (Mbps)
Speed in bps100,000,000 bps
Speed in Bytes/s12,500,000 B/s

Quick Reference — 100 Megabit/s (Mbps) in All Units

bit/s (bps)100,000,000
Kilobit/s (Kbps)100,000
Megabit/s (Mbps)100
Gigabit/s (Gbps)0.1
Terabit/s (Tbps)0.0001
Byte/s (B/s)12,500,000
Kilobyte/s (KB/s)12,500
Megabyte/s (MB/s)12.5
Gigabyte/s (GB/s)0.0125

Download Time Estimates at 100 Megabit/s (Mbps)

Theoretical minimums — real-world speeds may vary due to overhead, latency, and throttling.

Photo(1 MB)
80 ms
Song (MP3)(5 MB)
400 ms
CD Image(700 MB)
56.0 sec
DVD Image(4.7 GB)
6 min 16 sec
Blu-ray Image(25 GB)
33 min 20 sec
Game Download(50 GB)
1 hr 7 min

How to Use This Tool

  1. Enter the speed value you want to convert.
  2. Select the unit you are converting from in the "From" dropdown (e.g. Mbps).
  3. Select the unit you want to convert to in the "To" dropdown (e.g. MB/s).
  4. Read the converted result, plus the equivalent speed in bps and Bytes/s.
  5. Scan the Quick Reference table to see the same speed expressed in every supported unit.
  6. Check the Download Time Estimates card to see how long common file sizes would take at that speed.

Formula & How It Works

Speed Conversion Formula

result = (value × fromFactor) ÷ toFactor

All speeds are normalized to bits per second (bps) first — the value is multiplied by its unit's bps factor — then divided by the target unit's bps factor to get the final result.

Bits to Bytes

Bytes/s = bps ÷ 8

Byte-based units (B/s, KB/s, MB/s, GB/s) are derived by dividing the bit rate by 8, since 1 byte equals 8 bits. Networking speeds use decimal multiples of 1000 (1 Kbps = 1,000 bps, 1 Mbps = 1,000,000 bps).

Download Time Estimate

time (seconds) = file size (bytes) ÷ speed (bytes/second)

Dividing a file's size in bytes by the connection's speed in bytes per second gives the theoretical minimum download time, before accounting for overhead.

Practical Examples & Common Use Cases

Converting a 100 Mbps connection to MB/s

100 Mbps = 100,000,000 bps. Dividing by 8 gives 12,500,000 bytes/s, which is 12.5 MB/s — the real-world maximum transfer rate for a file download tool showing bytes.

Converting 1 Gbps fiber to KB/s

1 Gbps = 1,000,000,000 bps ÷ 8 = 125,000,000 bytes/s = 125,000 KB/s.

Estimating download time for a 4.7 GB DVD image

At 12.5 MB/s (a 100 Mbps connection), time = 4,700,000,000 bytes ÷ 12,500,000 bytes/s ≈ 376 seconds, or about 6 minutes 16 seconds under ideal conditions.

Frequently Asked Questions

Internet plans are advertised in megabits per second (Mbps), while download managers show megabytes per second (MB/s). Since 1 byte = 8 bits, you need to divide Mbps by 8 to get MB/s. A 100 Mbps plan can theoretically download at 12.5 MB/s. In practice it will be slightly less due to protocol overhead and network conditions.

The capitalization matters significantly. Mbps (lowercase b) means megabits per second — this is how ISPs measure internet speed. MBps or MB/s (uppercase B) means megabytes per second — this is how file transfers are typically measured. Since 1 byte = 8 bits, 1 MB/s = 8 Mbps. Always check whether the "b" is uppercase or lowercase when comparing speeds.

Networking and data transfer speeds universally use decimal (SI) multipliers: 1 Kbps = 1000 bps, 1 Mbps = 1,000,000 bps. This is different from file sizes, which sometimes use binary multipliers (1 KiB = 1024 bytes). The networking industry standardized on decimal multipliers long before the binary vs. decimal distinction became a common concern in storage.

Calculated download times represent the theoretical minimum based on raw bandwidth. Real-world downloads are slower because of TCP/IP protocol overhead (headers, acknowledgments), network latency and congestion, server-side speed limits, ISP throttling, Wi-Fi signal degradation, and TCP slow-start behavior at the beginning of transfers. A good rule of thumb is to expect 60-80% of the theoretical maximum in practice.

Related Tools