TL;DR / Summary: File sizes that “do not add up” usually mix decimal KB (1000 bytes) with binary KiB (1024 bytes) or confuse bits with bytes. Normalize to one system before comparing totals. Confirm power-of-two byte counts with our free power of 2 calculator.
Symptom: missing gigabytes
A 500 GB drive reports 465 GB free in OS. Users suspect failure; actually 500 × 10^9 / 2^30 ≈ 465.66 GiB—expected conversion, not lost sectors (excluding formatting overhead separately).
Symptom: upload size mismatch
Host limits “10 MB” upload as 10 × 1000 × 1000 bytes while local script counts 10 × 1024 × 1024. File at 10,485,760 bytes exceeds decimal 10 MB cap by 4.86%. Read API docs for which base.
Symptom: bandwidth versus size
Download speed 100 Mbps (decimal megabits) divides by 8 for bytes, then divides file bytes—mixing three conventions if file labeled in MiB. Build spreadsheet with explicit columns: bits, decimal bytes, binary bytes.
Diagnostic steps
- Identify unit label: KB vs KiB vs kb (kilobit!).
- Convert everything to raw byte integers.
- Compare sums in same base.
- Account filesystem block size (often 4096 = 2^12 bytes) rounding file allocation up.
Tools reporting differently
Windows Explorer historically labeled GiB as GB. Linux du -h uses 1024. Cloud S3 bills decimal GB-month. Git objects measure bytes exactly—no prefix games. npm package size badges vary by script.
Fix for developers
Display both units in UI for transparency: “1.0 MB (1,048,576 bytes).” Use IEC labels in internal metrics. Document API limits in bytes integer to avoid ambiguity.
Quick conversion formulas
Binary bytes = decimal bytes × 1000 / 1024 per “kilo” step (approximate per step). Exact: multiply decimal GB by 10^9 / 2^30 for GiB. For repeated steps, raise conversion factors to power of number of prefixes (k, M, G).
When exponent math gets messy, compute 2^30 once exactly: use our free power of 2 calculator and store constant in code comments.
Network versus storage
1 Gbps link ≠ 1 GiB/s. 1 Gbps = 10^9 bits/s ≈ 119.2 MiB/s theoretical max. Real-world less— but order-of-magnitude checks prevent expecting 1 GB file in 1 second on “gigabit” line without math.
Support script for users
Explain: manufacturers count decimal; operating systems count binary. Provide calculator link and table. Reduces refund requests on “missing” terabytes.
Backup and sync tools
Cloud sync clients reporting “10 GB uploaded” may count decimal while local du -sh reports binary GiB—progress bars stall visually near 93% when bases differ though transfer complete. UX writers should footnote unit in tooltip.
Compression ratio reporting
Compression tools quote “50% reduction” on decimal-labeled files while internal buffers use 2^n block sizes—support tickets alleging wrong compression often need unit normalization not algorithm fix.
Enterprise monitoring dashboards
Grafana panels mixing prometheus metrics (often decimal SI) with node_exporter disk (binary) on same chart without axis labels confuse SRE oncall. Standardize one base per dashboard row; annotate conversion in panel description referencing 2^30 versus 10^9 explicitly.
Photography and creative pro workflows
Photographers archiving RAW batches estimate storage with decimal TB drives but Lightroom internal cache counts binary—project managers planning 500 GB shoot need both numbers in spreadsheet row to avoid stopping session early when card fills at 465 GiB effective.
Video editors rendering ProRes at roughly 2^30 bytes per minute order-of-magnitude still multiply decimal duration minutes—hybrid math errors cause overnight render jobs missing deadline by one misunderstood prefix.
Customer support macro
Pre-write empathetic reply explaining decimal versus binary with analogy: kilometers versus miles— different units, same road. Link authoritative blog section anchor; reduce handle time and escalation to engineering.
Measure ticket volume before and after macro— leadership funds documentation when data proves ROI in support hours saved monthly.
Legal discovery exports
Litigation support vendors quote collection size decimal; e-discovery platform indexes binary—discrepancy triggers opposing counsel accusation of spoliation until units clarified in meet-and-confer.
Release notes clarity
When shipping app update, state install size in both MiB and decimal MB footnote—transparency reduces one-star reviews claiming false advertising when users compare to last phone model reporting differently.
DevOps runbook snippet
Include conversion table in on-call runbook appendix for disk-full alerts—engineer at 2 AM compares df output to vendor ticket without re-deriving 2^30 arithmetic under incident stress.
Inventory spreadsheet column
Add raw byte column alongside human labels in asset inventory—sorting and summing without unit ambiguity simplifies annual capacity planning meetings with finance and infrastructure teams together.
Add unit suffix to every size column in internal dashboards by default so newcomers never guess which kilo you mean.
Train support staff on prefix difference quarterly; new hires otherwise relearn same ticket patterns from scratch every rotation season.
Bookmark this tip: confusing KB with KiB
KB versus KiB discrepancies trace to decimal versus binary prefixes and bit/byte confusion. Normalize to bytes, label clearly in software, and educate users on storage marketing. Exact 2^n byte values clarify tests when building upload validators or disk quota features.
