You buy a brand new 1 TB external hard drive, plug it into your computer, and the operating system reports only 931 GB of available space. Where did the other 69 GB go? This is not a defect, and the manufacturer is not cheating you. The discrepancy comes from two different ways of defining what a "gigabyte" means. This issue affects every storage device — hard drives, SSDs, USB flash drives, and SD cards. The larger the drive, the bigger the apparent discrepancy. A 4 TB drive shows as approximately 3.63 TB, and a 16 TB drive appears as about 14.55 TB. Understanding why this happens is essential knowledge for IT professionals who regularly work with storage systems.

Storage device manufacturers use the International System of Units (SI), also known as decimal or base-10 units. In this system, each unit is exactly 1,000 times the previous one: • 1 Kilobyte (KB) = 1,000 bytes • 1 Megabyte (MB) = 1,000 KB = 1,000,000 bytes • 1 Gigabyte (GB) = 1,000 MB = 1,000,000,000 bytes • 1 Terabyte (TB) = 1,000 GB = 1,000,000,000,000 bytes When a manufacturer labels a drive as "1 TB," they mean it contains exactly 1,000,000,000,000 bytes of storage capacity. This is technically correct and follows the SI standard that is used across all scientific disciplines.

Computers operate in binary (base-2), and historically, operating systems have used powers of 2 to define storage units. The International Electrotechnical Commission (IEC) formalized these as binary units with distinct names: • 1 Kibibyte (KiB) = 1,024 bytes • 1 Mebibyte (MiB) = 1,024 KiB = 1,048,576 bytes • 1 Gibibyte (GiB) = 1,024 MiB = 1,073,741,824 bytes • 1 Tebibyte (TiB) = 1,024 GiB = 1,099,511,627,776 bytes The problem is that most operating systems (including Windows) display these binary values but label them with decimal unit names. Windows shows "931 GB" when it actually means 931 GiB. macOS since version 10.6 (Snow Leopard) switched to using decimal units, so a 1 TB drive correctly shows as approximately 1 TB on a Mac.

Let us walk through the calculation for a 1 TB drive: The drive contains 1,000,000,000,000 bytes (1 TB in decimal). When Windows calculates the size in "GB" (actually GiB), it divides by 1,073,741,824: 1,000,000,000,000 ÷ 1,073,741,824 = 931.32 GiB Windows displays this as "931 GB," creating the appearance that 69 GB is missing. The discrepancy percentage grows with each unit level: • At the KB level: 1,000 vs 1,024 = 2.4% difference • At the MB level: 1,000,000 vs 1,048,576 = 4.6% difference • At the GB level: 1,000,000,000 vs 1,073,741,824 = 6.9% difference • At the TB level: 1,000,000,000,000 vs 1,099,511,627,776 = 9.1% difference This is why the "missing" space seems to grow with larger drives — the percentage difference compounds at each unit level.

Understanding this distinction is critical in several IT scenarios: Server storage planning: When provisioning storage for servers, you need to account for the decimal-to-binary difference. If an application requires 500 GiB of storage, you need to purchase at least a 537 GB drive (500 × 1.073741824 = 536.87 GB in decimal terms). RAID calculations: RAID arrays compound the confusion because you lose capacity to parity or mirroring, and the remaining usable space is displayed in binary units. A RAID 5 array with four 4 TB drives provides approximately 10.91 TiB (displayed as "10.91 TB" in Windows), not 12 TB. Cloud storage: Cloud providers typically use decimal units (GB/TB) for billing, but your operating system may display usage in binary units. This can cause confusion when monitoring storage quotas. Backup planning: When calculating backup storage requirements, ensure you are consistent in your unit usage. A 500 GiB database backup requires approximately 537 GB of cloud storage space when the cloud provider uses decimal units. Network file transfers: When estimating transfer times, remember that a "1 GB" file on Windows is actually 1 GiB (1,073,741,824 bytes), which is about 7.4% larger than 1 decimal GB. This affects your download time calculations.

Different operating systems handle the decimal vs binary display differently: Windows (all versions) uses binary calculations but displays decimal unit labels (GB, TB). This is the primary source of confusion for most users. A file that is 1,073,741,824 bytes is shown as "1.00 GB" in Windows. macOS (10.6 and later) switched to decimal calculations with decimal labels. A file that is 1,000,000,000 bytes is shown as "1.00 GB." This matches what manufacturers advertise. Linux varies by distribution and file manager. The command-line tool "ls -l" shows exact byte counts, "ls -lh" uses binary units with decimal labels (like Windows), and some modern file managers offer options for both. For IT professionals, the safest approach is to work in exact byte counts when precision matters, and to always clarify which unit system you are using in documentation and communications.