GB vs GiB — Why Your Hard Drive Shows Less Space Than the Box Says
Plug a drive labeled "500GB" into your computer, and its properties window shows a number closer to 465GB. That's not a defect and it's not false advertising — the GB the manufacturer prints on the box and the GB your operating system displays simply aren't the same unit to begin with. This guide walks through where that gap comes from, and checks the actual source code of the unit converter to see which of the two standards it uses.
1. Same "GB," Two Different Ways to Calculate It
Byte-size prefixes were originally borrowed straight from the decimal SI prefixes (kilo = 1,000, mega = 1,000,000, and so on). But since computer memory physically operates in powers of two, the computing world started calling 1,024 (2¹⁰) — the power of two closest to 1,000 — "kilo" as a convenient shorthand. The problem is that this habit stuck, and as a result the same label "KB" can mean either 1,000 bytes or 1,024 bytes depending on context. Storage device manufacturers (hard drive, SSD, and USB makers) label capacity in decimal per the international standard (1GB = 1,000,000,000 bytes), while most operating systems still calculate and display file sizes in binary (base 1,024). The gap between the two values comes out to roughly 7.4%.
2. Why the IEC Created GiB and MiB
To clear up this confusion, the International Electrotechnical Commission (IEC) standardized binary prefixes in 1998. Under this standard, 1,024 bytes is called "KiB" (kibibyte), 1,024² bytes is "MiB" (mebibyte), and 1,024³ bytes is "GiB" (gibibyte) — while the existing KB, MB, and GB were meant to go back to their original decimal (base-1,000) meaning. The problem is that, more than twenty years later, this distinction has barely caught on in everyday use. Most software and users still compute a binary value and slap the label "GB" on it. In other words, you can't tell from the label alone whether a "GB" on screen is a true decimal GB or is actually a GiB in disguise — you have to check the program's actual calculation logic to know for sure.
3. Different Operating Systems, Different Display Conventions
Companies handle this differently. Windows Explorer still computes on a base-1,024 basis and labels the result "GB" (it's effectively GiB being called GB). macOS switched its storage display to decimal (true GB, matching manufacturer labels) starting with Snow Leopard in 2009. So the same 500GB drive shows up as "465GB" on Windows but as a number close to "500GB" on a recent macOS. On Linux, it can even come down to which command-line flag you use: df -h shows binary (labeling GiB as GB), while df -H shows decimal.
4. The Actual Gap, in Numbers
Converting the manufacturer's decimal-labeled capacity into actual bytes, then re-dividing that by the OS's binary (base-1,024) convention, gives the following:
| Manufacturer label | Actual bytes | OS display (binary, GiB) | Difference |
|---|---|---|---|
| 500 GB | 500,000,000,000 | ≈ 465.66 GiB | −6.9% |
| 1 TB | 1,000,000,000,000 | ≈ 931.32 GiB | −6.9% |
| 256 GB (SSD) | 256,000,000,000 | ≈ 238.42 GiB | −6.9% |
5. Which Convention Does MODOO HUB's Unit Converter Use?
Checking the actual source code of the data-size category in the unit converter, the multipliers for Byte, KB, MB, GB, TB, and PB are all defined as 1, 1024, 1048576 (1024²), 1073741824 (1024³)… — in other words, every single unit is built entirely on powers of 1,024. That means this tool's "GB" is labeled GB but calculated as GiB (binary). There's no separate option to select decimal (manufacturer-standard) GB. So if you type your hard drive spec sheet's "500GB" directly into this tool to convert it to MB or KB, keep in mind the result won't match the manufacturer's raw billion-byte figure — it'll match the same figure your operating system shows on screen (binary basis). Put the other way around, that also makes it exactly the right tool for answering "how many KB is the size Explorer is showing me?"
6. Practical Tip: Which Number Should You Trust, and When
- Comparing specs before you buy (comparing manufacturer-announced capacities against each other) works fine with plain decimal numbers. The actual ratio between 500GB and 1TB is exactly 2×.
- Checking how much space is actually left on your machine should go by the OS's displayed value (binary), but keep in mind that if you use both macOS and Windows, the same file can show different numbers on each.
- Network speed (throughput per second, Mbps/MB/s) is conventionally measured in decimal in most cases, which is a whole separate convention from storage labeling and easy to mix up with it.
Frequently Asked Questions
Q. Why does my 500GB hard drive show up as 465GB?
Manufacturers label 1GB as 1 billion bytes (decimal), but most operating systems calculate and display 1GB as effectively 1GiB (binary, 1,073,741,824 bytes). Dividing 500,000,000,000 bytes by the binary convention gives approximately 465.66.
Q. Can MODOO HUB's unit converter accurately convert manufacturer-labeled GB?
This tool calculates every data-size unit on a base-1,024 (binary) basis. If you enter a decimal manufacturer-labeled figure as-is, the result will match "what the operating system displays" rather than the manufacturer's exact billion-byte figure — the two can differ by roughly 7.4%.
Q. When was the GiB unit introduced?
The International Electrotechnical Commission (IEC) standardized binary prefixes (KiB, MiB, GiB, etc.) in 1998. In practice, though, most of the software industry still calculates in binary while calling the result "GB," so the distinction never really caught on widely.
Q. Why is the gap always around 7.4%?
1,024 (2¹⁰) is 2.4% larger than 1,000 (10³). Because the GB unit compounds that ratio three times (kilo → mega → giga), it grows to (1.024)³ ≈ 1.0737 — about a 7.4% difference. Go up to TB (a fourth power), and the gap widens further.