Data Transfer Converter

A data transfer converter rescales a rate, an amount of data per second, between bit-based and byte-based units and between the decimal and binary prefix systems. Network links, internet plans, and serial ports are rated in bits per second, while file managers, browsers, and disk benchmarks usually report bytes per second, so the same link speed appears as two numbers that differ by a factor of eight.

The rate can be written as a decimal, a fraction such as 3/4, a mixed number such as 1 1/2, or scientific notation such as 1.5e3. A lowercase b in a symbol means bits and an uppercase B means bytes: Mbps is megabits per second and MBps is megabytes per second. SI rates (kbps, Mbps, Gbps) step by 1,000, the convention networking standards use, so a gigabit link carries 1,000,000,000 bits each second. IEC binary rates (Kibps, Mibps, Gibps) step by 1,024 and appear mainly in system tools that count in binary units; they are listed as separate units so a reading of 100 Mibps is never mistaken for 100 Mbps.

Every conversion passes through bits per second. The value is multiplied by the bits per second in one source unit and divided by the bits per second in one target unit: 1,000 for kbps, 8,000 for kBps, 1,048,576 for Mibps (1,024 squared), 8,000,000 for MBps, and 1,000,000,000 for Gbps. One shared base keeps all 26 units consistent with each other. Settings holds the number of decimal places (four by default), a step-by-step view of both operations, and a list of the same rate expressed in every unit.

A converted rate is a ceiling, not a forecast. A link rated at 1 Gbps moves at most 125 MBps of raw bits, and the payload a file copy sees is lower once Ethernet framing, IP and TCP headers, and acknowledgements take their share. Serial links lose more: an asynchronous frame with one start bit, eight data bits, and one stop bit spends ten bits on every byte, so 115,200 bps carries 11,520 bytes per second rather than the 14,400 that dividing by eight suggests. A rate too small for the chosen precision is written in scientific notation instead of being rounded to zero.

100 Mbps is 100 x 1,000,000 = 100,000,000 bits per second, and dividing by the 8,000,000 bits per second in one MBps gives 12.5 MBps. At that rate a 25 GB file, which is 25,000 MB, takes 25,000 / 12.5 = 2,000 seconds, about 33 minutes, before any protocol overhead.

Differences between bit-based and byte-based rate notation cause frequent confusion when comparing advertised speeds, real throughput, and hardware specifications. The following scenarios show where a precise rate conversion prevents a miscalculation.

• ISP plan comparison: An internet plan advertised at 500 Mbps tops out at 62.5 MBps, the most a browser or download manager can report for a single file before protocol overhead.
• File transfer estimation: Gigabit Ethernet carries 1 Gbps, which is 125 MBps, so a 25 GB disc image of 25,000 MB needs at least 200 seconds to copy across it.
• Cloud migration planning: A corporate uplink rated at 10 Gbps moves 1.25 GBps, so migrating 50 TB (50,000 GB) to a cloud provider takes at least 40,000 seconds, a little over 11 hours of sustained transfer, and longer when the link is shared.
• Video streaming requirements: A 25 Mbps video stream consumes 3.125 MBps, or 11.25 GB for each hour of viewing, a figure that sizes both a monthly data cap and a recording drive.
• SAN and NAS configuration: A PCIe 3.0 NVMe drive reading at about 3.5 GBps produces 28 Gbps, more than a 25 Gbps network port can carry, so the network fabric rather than the drive sets the ceiling.
• Wireless standard evaluation: The 9.6 Gbps headline rate of Wi-Fi 6 and 6E equals 1.2 GBps, a theoretical aggregate across every spatial stream that a single client device rarely approaches.
• Embedded telemetry design: A 115,200 bps serial bus converts to 14.4 kBps of raw bits, and framing overhead brings the usable figure to 11,520 bytes per second, which decides whether a sensor payload fits within each sampling interval.
• Academic networking labs: Students studying protocol overhead can step through the exact multiplier chain from Mbps to Bps, reinforcing the eight-to-one bit-byte ratio and the distinction between decimal and binary prefixes.