TL;DR / Summary: IEC binary prefixes (KiB, MiB, GiB) use powers of two—1 KiB = 2^10 bytes—while SI decimal prefixes (KB, MB, GB) often mean powers of ten in storage marketing. The mismatch explains why a 1 TB drive shows ~931 GiB in your OS. Clarify any conversion with our free power of 2 calculator.
Two prefix systems, one confusion
In computing, binary prefixes count by doublings: kibi (Ki) = 2^10, mebi (Mi) = 2^20, gibi (Gi) = 2^30. Decimal prefixes in SI count by thousands: kilo = 10^3, mega = 10^6, giga = 10^9. Hard-drive manufacturers historically labeled capacity with decimal gigabytes while operating systems report gibibytes—same bytes, different labels.
Exact definitions
- 1 KiB (kibibyte) = 2^10 = 1,024 bytes
- 1 MiB (mebibyte) = 2^20 = 1,048,576 bytes
- 1 GiB (gibibyte) = 2^30 = 1,073,741,824 bytes
- 1 TiB (tebibyte) = 2^40 bytes
Compare to decimal: 1 GB (decimal gigabyte) = 10^9 = 1,000,000,000 bytes. The ~7% gap at gigabyte scale widens at terabyte scale—enough to spawn decades of forum arguments.
Why IEC introduced KiB/MiB/GiB
Standards bodies needed unambiguous terms. Before 1998 recommendations, “kilobyte” might mean 1024 or 1000 depending on context. IEC 60027 and later ISO/IEC 80000-13 defined KiB explicitly as 2^10. Linux and macOS increasingly show GiB in disk utilities; Windows often still prints “GB” while using 1024-based math internally for some dialogs—a mixed UX landscape.
Quick conversion mental math
Decimal GB to binary GiB: divide by ~1.074. Example: 500 GB × 10^9 bytes / 2^30 ≈ 465.66 GiB. Reverse: multiply GiB by 1.074 for approximate decimal GB marketing labels.
RAM versus HDD labeling
RAM sticks labeled 16 GB almost always mean 16 × 2^30 bytes (16 GiB worth of cells). SSDs sold as 1 TB usually mean 10^12 bytes. Benchmarks comparing “gigabytes per second” may mix bases in throughput (decimal) versus buffer sizes (binary)—read footnotes carefully.
Programming implications
Constants like 1024 appear as 2^10 in code. Some languages offer units: Rust’s KiB macros, .NET’s binary prefixes in APIs. Using 1000 where 1024 is intended causes off-by-2.4% errors at kilo scale—acceptable in UX copy, disastrous in memory allocators.
Network speeds add a third layer
Megabits per second (Mbps) for broadband uses decimal mega = 10^6 bits per second, not 2^20. Converting download ETA requires dividing file size in bytes by (Mbps × 10^6 / 8). Three bases—decimal bits, decimal bytes, binary bytes—trip up students and professionals alike.
Documentation best practices
Write “512 MiB” in technical docs when you mean 512 × 2^20 bytes. Write “500 GB (decimal)” on consumer packaging if legally required. Internal tools should display both during transition periods. Never assume readers know which kilo you mean without a suffix.
Practice conversion
How many bytes in 3 MiB? 3 × 2^20 = 3,145,728. How many 2^10-byte pages fit? 3 × 2^20 / 2^10 = 3 × 2^10 = 3072 pages. Use our free power of 2 calculator for 2^20 and 2^30 refreshes when writing storage calculators or unit tests.
Legal and regulatory labeling
Consumer protection rules in some jurisdictions require storage devices to disclose decimal capacity on packaging while software may use binary counting internally. Support teams trained only in one system escalate “false advertising” tickets that are actually prefix education opportunities—document scripts explaining 10^12 versus 2^40 with empathy, not jargon.
Enterprise procurement contracts specifying “1 TB RAM” should clarify whether vendors mean 10^12 bytes or 2^40 bytes—differences at terabyte scale affect database licensing tied to memory tiers.
Database and analytics sizing
Columnar databases quote block sizes in MiB; ETL pipelines reading “100 MB” CSV exports from third parties may be decimal. Pipeline failures at row 104857600 bytes often trace to assuming decimal MB when vendor used binary. Normalize in ingestion metadata: store byte_count_int64 always.
Benchmark papers comparing systems must footnote whether throughput is measured per decimal megabit wire speed or per mebibyte processed—mixing units invalidates cross-paper comparisons students cite in literature reviews.
Teaching SI versus IEC in one lesson
Present both columns simultaneously early in CS curricula. Quiz with deliberate traps: “How many bytes in 2 GiB?” versus “How many bytes in 2 GB decimal?” Immediate feedback prevents years of professional confusion. Provide printable conversion card with 2^10, 2^20, 2^30 highlighted.
Mobile app store and CDN labeling
App store download sizes frequently use decimal megabytes while in-app cache reports binary on Android internal stats screens. Product managers comparing competitor APK sizes must normalize units before concluding one team ships smaller code. CDN billing per decimal gigabyte egress while origin storage counts binary mebibytes creates finance spreadsheets that only reconcile when someone documents both columns explicitly.
Technical writers preparing user-facing storage FAQs should include one worked example showing why a 1 TB drive displays about 931 GiB, with an authoritative IEC explanation, reducing support load more than adding verbose legal disclaimers alone.
Carry this into tomorrow: kiB, MiB, GiB vs KB, MB, GB
KiB, MiB, and GiB anchor to powers of two; KB, MB, and GB in marketing often anchor to powers of ten. The difference explains storage discrepancies and network math surprises. Label clearly, convert with 2^10 steps, and verify exponents online when building user-facing size formatters.
