Data Transfer Rate Conversions

Your internet provider advertises "300 Mbps." You run a speed test and see 280 Mbps. You start downloading a large file and watch it transfer at 35 megabytes per second. All three numbers are consistent with each other, but the units make them look contradictory. The "Mbps" in the advertisement is megabits per second. The download speed shown by your browser is megabytes per second. Since there are 8 bits in a byte, 280 megabits divided by 8 equals 35 megabytes. This 8:1 ratio between bits and bytes is the single most common source of confusion in data transfer speed discussions.

The convention exists for historical reasons. Telecommunication networks have always measured line speed in bits per second because data travels one bit at a time across a wire or fiber. When Claude Shannon published his foundational information theory paper in 1948, he measured channel capacity in bits. Modems, Ethernet standards, and ISP plans followed that convention. Meanwhile, file systems and application software measure data in bytes because a byte (8 bits) is the smallest addressable unit of storage. The result is that network engineers think in bits while software developers and end users think in bytes, and the two groups regularly talk past each other.

Real-world throughput is always lower than the advertised link speed. Protocol overhead (TCP/IP headers, Ethernet framing) typically consumes 5-10% of raw bandwidth. A 1 Gbps (gigabit per second) Ethernet link delivers roughly 940 Mbps of usable data, or about 117.5 MB/s of file transfer speed. For Wi-Fi, the gap widens: a router advertising 1,200 Mbps will deliver 400-600 Mbps in practice due to contention, interference, and protocol overhead.

At the enterprise level, data center interconnects now operate at 100 Gbps and 400 Gbps, with 800 Gbps links entering production. Converting between these rates matters for capacity planning: a 400 Gbps link can transfer 50 gigabytes per second, meaning a 1 TB database backup takes about 20 seconds over that link.

Video streaming is the heaviest consumer of bandwidth for most households. A 4K Netflix stream requires about 25 Mbps sustained, or 3.125 MB/s. A family running two simultaneous 4K streams plus a video call needs 60+ Mbps of available bandwidth. Knowing how to convert between bits and bytes per second allows you to verify whether your internet plan actually supports your household's usage pattern.

For backup and disaster recovery planning, transfer speed determines recovery time. Restoring a 10 TB dataset over a 1 Gbps link takes approximately 22.2 hours at full theoretical speed, or closer to 24-26 hours accounting for protocol overhead. A 10 Gbps link reduces that to about 2.5 hours. These calculations require converting between TB (storage) and Gbps (transfer rate), bridging the bit/byte divide.

This converter supports 8 data transfer units: bit per second, kilobit per second (kbps), megabit per second (Mbps), gigabit per second (Gbps), and terabit per second (Tbps) on the bit side; kilobyte per second (kB/s), megabyte per second (MB/s), and gigabyte per second (GB/s) on the byte side. All conversions use the standard SI decimal definitions (1 kbps = 1,000 bps, not 1,024), consistent with IEEE and ITU-T standards.