Data Storage Converter

Share:

Convert between bits, bytes, and full SI/IEC ladder. Bridges the bit-vs-byte gap; bandwidth context output.

RT-CNV-008 · Converters & Units
Your browser is too old for this tool’s interactive features. Please update to Safari 13.1, Chrome or Edge 80, Firefox 74 or newer.

Data Storage Converter

Advertisement
After results · AD-W1 Responsive · Post-tool — peak engagement

How to use the data storage converter

Enter the value

Type any positive number. The result panels update on every keystroke.

Pick the source unit

Three optgroups separate Bits (lowercase b — for network speeds), Bytes SI (uppercase B with 1000-based prefixes — for drive sizes), and Bytes IEC (KiB / MiB / GiB — for OS-displayed file sizes).

Read all conversions side-by-side

Five card groups show the input value in every unit family. Useful when comparing what your ISP advertises (Mbps), what your OS reports (MiB), and what your drive label says (GB) — three different unit systems describing related quantities.

Transfer time

Whatever you enter, the dark card below shows how long that much data takes to move across a fixed ladder of link rates, from a 56k modem to a 10 Gbps datacentre link — at line rate, and again once TCP/IP framing is taken off. The ladder never changes with your input, so the rows are comparable.

Advertisement
After how-to · AD-W2 Responsive

Bits vs bytes — why your 100 Mbps internet downloads at 12 MB/s

The most common confusion in network and storage units is the distinction between bits (lowercase b) and bytes (uppercase B). Eight bits make one byte. Networking conventions use bits-per-second (Mbps, Gbps); storage conventions use bytes (KB, MB, GB). Internet service providers advertise speeds in bits to make them sound bigger — "1 Gbps" sounds more impressive than "125 MB/s", even though they're the same speed measured differently. This tool exists to make the conversion trivial: pick your input unit, see the equivalent in every other common unit, plus a real-world transfer-time estimate.

The historical split

The split came from different industry origins. Telecommunications (the source of "bandwidth" as a concept) measured signals in bits per second because circuits carry bits — 64 kbps was the original digitised voice channel (8000 samples/sec × 8 bits/sample). Computer storage measured everything in bytes because that's what addressable memory addressing demanded. When telcos started selling internet service, they kept their unit convention; when drive manufacturers started selling consumer hardware, they kept theirs. The two industries never reconciled and we live with it.

Practical conversions

Divide Mbps by 8 to get approximate MB/s of file transfer, so 100 Mbps ≈ 12.5 MB/s and a 1 GB file takes about 80 seconds at line rate. Framing takes a fixed bite out of that: a full-size TCP/IPv4 segment carries 1,460 bytes of payload for 1,538 bytes on the wire once you count the IP and TCP headers, the Ethernet header and checksum, the preamble and the interframe gap — 94.93% efficient, so the 80 seconds becomes about 84. Everything past that is contention rather than protocol: congestion at peak hour, Wi-Fi retransmission, ISP shaping, and a source server that will not send any faster. Those are real and often larger than the framing cost, but none of them can be derived from a file size and a plan rate, so this tool does not pretend to predict them.

APAC bandwidth landscape

What a plan is sold as and what a region actually gets apart widely across APAC, and the gap is why the bit-versus-byte confusion bites here. Singapore sells 1 Gbps as an ordinary residential tier and 10 Gbps in some buildings; Hong Kong, South Korea, Japan and Taiwan sit in the same bracket. Malaysia's Unifi and Maxis tiers run from the low hundreds of Mbps upward. Indonesia, the Philippines and Vietnam are all climbing quickly from a lower base, and India spans the widest range of any market in the region, from urban fibre to single-digit Mbps in remote areas.

Deliberately, none of that is given as a number here. Median national speeds move every month, and this page used to carry a set of them that disagreed with the figures on our own file size converter and image format converter — three snapshots taken at three different times, each of them stale within a quarter. For a current figure, read it from the source: Ookla's Speedtest Global Index publishes median fixed-broadband and mobile speeds by country and updates them monthly. What does not move is the arithmetic above, which is what this converter is for. One regional constant worth planning around: mobile data caps remain real across ASEAN, so "how big is this video" stays a practical question long after "how fast is my line" stops being one.

When the difference matters

For everyday consumer use, the bit-vs-byte gap is annoying but trivial. For network engineers, video streaming providers, cloud architects, and game devs sizing CDN capacity, the difference between "10 Mbps user link" and "10 MB/s transfer" is critical — you can carry 8× more data when bits and bytes are confused in the favourable direction. ISP marketing benefits from the confusion; technical work needs the converter. SaaS pricing typically uses bytes (GB transferred per month). CDN pricing typically uses bits (Mbps committed rate, occasionally with per-GB overage). Storage pricing always uses bytes. So a single application's monthly bill might quote three different unit systems — all describing related things.

A byte was not always eight bits, and your ISP counts in the other one

01

Lowercase b = bit, uppercase B = byte. ISPs use bits because the numbers look bigger; storage uses bytes because computers are byte-addressed.

02

One byte = 8 bits has been standard since IBM System/360 (1964). Earlier mainframes used 6, 7, 9, or 12-bit bytes — the term "byte" wasn't even consistent.

03

56k dial-up modems (1996) ran at 56,000 bits/second = 7 KB/s of usable throughput. A modern 1 Gbps connection is ~17,857× faster.

04

Singapore's Next Gen Nationwide Broadband Network reached effectively every home and business by around 2013, built by OpenNet under the Infocomm Development Authority. IMDA, usually credited with it, did not exist until IDA and MDA merged in October 2016.

05

The PCI Express 5.0 lane runs at 32 Gbps; a 16-lane GPU slot is 512 Gbps aggregate. Internet downloads will be the bottleneck for the foreseeable future.

06

HDMI 2.1 (2017) added 48 Gbps of bandwidth — enough for 4K at 120 Hz with full chroma. The HDMI 2.0 it replaced topped out at 18 Gbps.

07

Japan's NICT pushed 1.02 petabits per second over 1,808 km of 19-core fibre in May 2025 — through a strand the same 0.125 mm diameter as the fibre already in the ground. That is roughly a petabyte every eight seconds.

08

Australia's NBN was originally promised at 1 Gbps fiber-to-the-home in 2009. Cost overruns and a political pivot to fixed-wireless / FTTN reduced that to ~100 Mbps for most premises until 2024.

09

India's broadband subscriber base crossed one billion in November 2025, TRAI reported — 100.37 crore, up from 13.15 crore ten years earlier. It is the world's second-largest market after China.

10

The IEC binary prefixes (kibi, mebi, gibi) were standardised in 1998 to disambiguate "K" — 1000 or 1024? Adoption has been patchy: Linux uses them, Windows doesn't.

Frequently asked questions

Because Mbps is megabits per second, not megabytes. Divide by 8 to convert: 100 Mbps = 12.5 MB/s theoretical, ~10-11 MB/s in practice after TCP overhead. ISPs use bits because the bigger number sounds better.
Networking → bits per second (Mbps, Gbps). Storage → bytes (KB, MB, GB). When in doubt, look for the lowercase b (bits) vs uppercase B (bytes). RAM and OS file sizes use IEC binary units (KiB, MiB) even if they're labelled "KB", "MB".
1 petabit = 10^15 bits = 1,000 terabits. Used mostly in submarine cable capacity and large-scale data center networking.
Internally uses JavaScript numbers (double precision). Above ~9 PB you may see ~1 byte rounding errors at the extreme end. For everyday values (TB and below) conversions are exact.
GiB = gibibyte = 2^30 bytes = 1,073,741,824 bytes. The IEC adopted "kibi/mebi/gibi" prefixes in 1998 to disambiguate the 1024-based units from the 1000-based SI ones. Outside Linux few systems use the new spellings, but the units are still useful for precise communication.
When your input value falls in the typical bandwidth range, the tool shows the closest representative real-world speed (dial-up, broadband, fiber) and how long that speed takes to transfer your value. Useful for sanity-checking "how long will downloading X take?"
One part of it is computable and the rest is not. Protocol framing costs 5.07%: a full TCP/IPv4 segment on Ethernet carries 1,460 payload bytes per 1,538 bytes on the wire. On top of that sit shared capacity at your ISP, Wi-Fi retransmission between your router and your device, and throttling at the source server — all variable, none predictable from your plan rate, and together usually larger than the framing. That is why this tool shows the line-rate time and the framed time and stops there.
In theory yes — 5G NR achieves 1-2 Gbps peak. In practice, depending on cell capacity and signal quality, real-world 5G typically delivers 100-500 Mbps. Wired fiber is more consistent.
The lowercase k is correct (SI standard). Uppercase K appears in older texts and is technically wrong, but both mean kilobits per second = 1000 bits/second. Some publications write "Kbps" capitalised; we use lowercase here.
Use a speed-test service (fast.com, speedtest.net) — most measure both download and upload in Mbps. Run multiple tests at different times of day; results vary by 10-30% depending on contention.

Method & sources

How it computes

Bits and bytes differ by 8; decimal byte units are powers of 1000 and IEC units powers of 1024. Transfer time = bytes ÷ (link bits per second ÷ 8), shown at line rate and again after framing, where a full TCP/IPv4 segment carries 1 460 payload bytes per 1 538 bytes on the wire (94.93%).

What this tool implements

  • IEC binary prefixes and SI decimal prefixes distinguish KiB from kB (NIST).
  • A maximum-size Ethernet-framed TCP/IPv4 segment: 1 460 payload + 20 TCP + 20 IPv4 + 18 Ethernet header and FCS + 8 preamble/SFD + 12 interframe gap = 1 538 bytes, so line rate × 0.9493 is the usable ceiling before congestion.

Sources

Advertisement
Pre-footer · AD-W3 728 × 90