Every file you download, every photo you take, every video you stream involves data measured in specific size units. Yet most people don't fully understand the difference between a megabit and a megabyte, or why a 1 TB hard drive only shows 931 GB of usable space. This guide clears up the confusion around data size measurements, explains the competing standards, and shows you how to convert between units accurately.
Before discussing larger units, it's essential to understand the two smallest building blocks of digital data.
A bit (short for "binary digit") is the smallest unit of data in computing. It holds a single binary value: either 0 or 1. Every piece of digital information — from a text message to a 4K movie — is ultimately stored as a sequence of bits.
A byte consists of 8 bits. This grouping was standardized in the 1960s and became universal because 8 bits can represent 256 distinct values (2⁸), which is enough to encode the English alphabet, numbers, punctuation, and control characters in the ASCII standard.
The distinction between bits and bytes causes endless confusion in consumer technology. Internet service providers advertise speeds in megabits per second (Mbps), but web browsers and file managers display download progress in megabytes per second (MB/s). Since 1 byte = 8 bits, a 100 Mbps connection delivers roughly 12.5 MB/s of actual throughput. This isn't misleading — it's just two different units measuring the same data flow.
Data sizes scale using prefixes that multiply the base unit. The traditional (and still most commonly used) prefixes follow powers of 1,000 in decimal context:
| Unit | Abbreviation | Size in Bytes | Approximate Real-World Equivalent |
|---|---|---|---|
| Kilobyte | KB | 1,000 | A short email |
| Megabyte | MB | 1,000,000 | A medium-resolution photo |
| Gigabyte | GB | 1,000,000,000 | An hour of HD video |
| Terabyte | TB | 1,000,000,000,000 | 500 hours of HD video |
| Petabyte | PB | 10¹⁵ | All US academic research libraries |
| Exabyte | EB | 10¹⁸ | All data on the internet (2024) |
These prefixes — kilo, mega, giga, tera — are part of the International System of Units (SI) and use base-10 (powers of 1,000). However, computers operate in binary, and this creates a parallel system.
In binary computing, the natural progression uses powers of 2. The closest power of 2 to 1,000 is 1,024 (2¹⁰). For decades, the computing industry used the same prefix names (KB, MB, GB) to mean both 1,000 and 1,024, depending on context. This ambiguity caused real confusion.
To resolve this, the International Electrotechnical Commission (IEC) introduced new prefixes specifically for binary multiples:
| Binary Prefix | Symbol | Value | Decimal Prefix It Replaces |
|---|---|---|---|
| Kibibyte | KiB | 1,024 bytes | Kilobyte (KB) |
| Mebibyte | MiB | 1,048,576 bytes | Megabyte (MB) |
| Gibibyte | GiB | 1,073,741,824 bytes | Gigabyte (GB) |
| Tebibyte | TiB | 1,099,511,627,776 bytes | Terabyte (TB) |
In practice, the adoption of these binary prefixes has been uneven. Operating systems like Linux increasingly use KiB/MiB/GiB. macOS switched from MB to MiB in Snow Leopard (2009). Windows, however, still displays file sizes using binary multiples but labels them with decimal prefixes — so a 500 GB drive shows as "465 GB" in Windows Explorer, when it should say "465 GiB."
This is one of the most common complaints in consumer technology: "I bought a 1 TB hard drive, but my computer says it's only 931 GB!" Here's what's happening:
This isn't deceptive marketing. Storage manufacturers follow SI standards correctly: 1 TB = 10¹² bytes. The problem is that operating systems mislabel binary units with decimal names. As storage sizes grow, the gap widens:
| Advertised Size | Actual Bytes | What Windows Shows | Discrepancy |
|---|---|---|---|
| 256 GB | 256,000,000,000 | 238 GB | 7% |
| 1 TB | 1,000,000,000,000 | 931 GB | 9.1% |
| 2 TB | 2,000,000,000,000 | 1,862 GB | 9.1% |
| 4 TB | 4,000,000,000,000 | 3,725 GB | 9.1% |
Additionally, some space is reserved for the file system itself (NTFS, ext4, APFS each have overhead), partition tables, and on SSDs, over-provisioning for wear leveling. A small portion of your drive's capacity is always consumed by this infrastructure.
When shopping for internet service, you'll see speeds advertised in Mbps (megabits per second). When downloading files, your browser shows progress in MB/s (megabytes per second). The conversion is simple but often overlooked:
Speed in MB/s = Speed in Mbps ÷ 8
Examples:
100 Mbps connection → 12.5 MB/s maximum
500 Mbps connection → 62.5 MB/s maximum
1 Gbps connection → 125 MB/s maximum
Real-world speeds are typically 10–20% lower than theoretical maximums due to network overhead, protocol headers, and routing inefficiencies. A 100 Mbps plan realistically delivers around 10–11 MB/s for large downloads.
Historically, networking equipment measures data transfer at the physical layer in bits. Network interfaces, modems, and switches all report throughput in bits per second. Using the same unit in marketing keeps the numbers consistent with what the hardware actually delivers. The larger numbers don't hurt either — 1 Gbps sounds more impressive than 125 MB/s, even though they represent the same bandwidth.
Understanding data sizes becomes much more intuitive when you connect them to real files and activities:
Moving up the scale means multiplying by 1,000. Moving down means dividing by 1,000.
1 TB = 1,000 GB = 1,000,000 MB = 1,000,000,000 KB = 1,000,000,000,000 bytes
Examples:
2.5 TB × 1,000 = 2,500 GB
750 MB ÷ 1,000 = 0.75 GB
3,500 KB ÷ 1,000 = 3.5 MB
Moving up means multiplying by 1,024. Moving down means dividing by 1,024.
1 TiB = 1,024 GiB = 1,048,576 MiB = 1,073,741,824 KiB
Examples:
512 MiB × 1,024 = 524,288 KiB
2 GiB ÷ 1,024 = 0.00195 TiB
Always divide by 8 to convert bits to bytes, or multiply by 8 for the reverse.
100 Mbps × (1,000,000 / 8) = 12,500,000 bytes/s = 12.5 MB/s
A 50 MB file × 8 = 400 Mb
Understanding data sizes matters when choosing cloud storage plans or managing bandwidth caps. A typical household consumes 300–500 GB of internet data per month. Streaming services dominate this usage: Netflix at 1080p uses roughly 3 GB per hour, while 4K streaming consumes about 7 GB per hour.
Cloud storage pricing reflects the real cost of data at scale. Storing 1 TB of data on a major cloud provider costs roughly $20–25 per month. But downloading that data back to your machine can incur egress charges, and uploading 1 TB over a 50 Mbps connection takes about 46 hours — making data transfer speed a practical consideration alongside raw capacity.
Compression algorithms reduce file sizes by finding and eliminating redundancy. Lossless compression (ZIP, FLAC, PNG) preserves every bit of the original data. Lossy compression (JPEG, MP3, H.264) discards data that human perception barely notices, achieving much higher compression ratios.
Typical compression ratios vary widely: text files compress 60–80%, photos compress 30–50% losslessly but 90%+ lossily, and already-compressed video files barely compress further. Understanding these ratios helps estimate how much storage you actually need for your data.
Stop guessing and start converting accurately. Use our free Data Size Converter Tool to convert between bits, bytes, KB, MB, GB, TB, and more — with both decimal and binary prefix support. Instant results, no sign-up required.