What it is and the problem it solves
The gigabyte is a unit of digital information that solves the problem of expressing large byte counts — but its dual definitions create mismatched expectations between marketing, engineering, and end-user interfaces.
How it works
The gigabyte is defined in two ways: as 10^9 bytes (decimal, SI-aligned) for storage and transmission, and as 2^30 bytes (binary) for RAM sizing. The IEC 80000-13 standard (1998) mandates GB = 10^9 bytes and introduces GiB = 2^30 bytes to resolve ambiguity.
What works
The decimal definition works for storage, transmission, and commerce: it aligns with SI, international standards (IEC, IEEE, EU, NIST), and US federal law. The binary definition works for RAM addressing — where powers of two match hardware architecture.
What does not
The binary definition does not apply to storage devices in legal or standards-compliant contexts. It persists only in legacy OS behaviour (e.g., Windows file managers) and RAM specifications — not in SSDs, HDDs, or network throughput.
What it changes
It changes how capacity claims are legally enforceable, technically precise, and interoperably interpreted. Adoption of GiB/GiB-aware tools forces explicit distinction between base-10 and base-2 scaling — shifting responsibility from users to implementers.
Is it worth your time
Yes — if you specify, sell, test, or document digital capacity. Ambiguity still causes real discrepancies: a 500 GB drive shows ~465 GB in Windows. You must choose which definition applies — and why — every time you use the unit.
