Data Units: Decimal vs Binary (GB vs GiB)
ME
Morgan Ellis
Technical Writer & Measurement Specialist · Updated March 2026
Storage makers use decimal prefixes, while many operating systems show binary prefixes. That gap explains why your “512 GB” drive looks smaller on your computer.
Two systems on purpose
- Decimal (SI): 1 kB = 1000 bytes; 1 MB = 1000 kB; 1 GB = 1000 MB.
- Binary (IEC): 1 KiB = 1024 bytes; 1 MiB = 1024 KiB; 1 GiB = 1024 MiB.
Both are correct; they answer different questions. Networking gear and marketing often use decimal because it aligns with signals and standards; operating systems historically used binary to match memory addressing.
Why the numbers don’t match
512 GB (decimal) equals about 476.84 GiB (binary) because 1000³/1024³ ≈ 0.931. Your device isn’t missing space; it is measuring with a different yardstick.
Converting between the two
- Pick a direction (GB→GiB or GiB→GB).
- Use the exact power-of-two ratio (1024) or power-of-ten ratio (1000).
- Keep full precision internally; round the display based on context.
Updated {today}
Practical tips
- When comparing storage devices, convert both numbers to the same system first.
- For network throughput, assume decimal unless the documentation explicitly shows binary prefixes.
- When filing a support ticket, state which system you used so your math is reproducible.
Deeper Context for “Data Units: Decimal vs Binary (GB vs GiB)”
Focus: GB vs GiB and where each appears. This section goes beyond the basics with practical choices you can apply immediately.
Rule of thumb: verify unfamiliar numbers by converting there-and-back (forward unit then inverse). If you get close to your start value, your magnitude is sound.
Updated October 08, 2025
Quick Checklist
- Confirm the exact units in play (variants noted on our converters).
- Enter numbers with the fewest necessary decimals; let the tool handle precision.
- Run the inverse conversion to sanity-check magnitude.
- Round at the end for reports; keep full precision while calculating.
- Document constants used if the result will be shared.
Common Pitfalls & How to Avoid Them
- Mixing variants (e.g., US vs Imperial gallons) without realizing it.
- Rounding too early—use full precision until your final display.
- Copying a number without its unit symbol; always keep units attached.
- Interpreting temperature as pure scale (°C↔°F needs the offset).
- Assuming decimal vs binary data units are interchangeable—they aren’t.
Worked Examples
Worked numeric examples using the same logic as our calculators.
- 4 GB (decimal) ≈ 3.725 GiB
- 27 GiB ≈ 28.991 GB
Values rounded for readability; our tools compute with full precision.
FAQs
How do you guarantee accuracy?
We use exact constants when they exist and clearly label variants (e.g., US vs Imperial). Calculations run client-side with full precision; rounding is only for display.
Why don’t my numbers match a label I saw?
Some packaging uses rounded or conventional values. Use back-conversion to sanity-check and confirm the variant on the page.
Can I cite your converters?
Yes—include the unit pair and the constant shown on the page. If your field requires specific standards, list them in your report.
Deepen Your Understanding
Why GB ≠ GiB on your screen: Device boxes use decimal prefixes (1 GB = 10^9 bytes). Operating systems often report binary prefixes (1 GiB = 2^30 bytes). 512 GB ≈ 476.84 GiB.
Quick conversions
- GB → GiB: value × (1000^3 / 1024^3) ≈ value × 0.931323.
- GiB → GB: value × (1024^3 / 1000^3) ≈ value × 1.073742.
Practical advice
When comparing drives, convert both specs to the same system. For network rates (e.g., Mbps), assume decimal unless the documentation says otherwise.
Updated October 08, 2025
Throughput vs Capacity
Throughput (MB/s) may be reported in decimal while your OS shows file sizes in binary. Convert both to one system when comparing copy speeds to expectations.
Filesystem Overhead
Capacity reported by the OS also subtracts filesystem overhead. The GB↔GiB conversion explains most of the difference; overhead explains the rest.
Benchmark Recipe
- Create a large test file.
- Time the copy and compute MB/s in a single unit system.
- Compare to the device spec after converting it to the same system.
Updated October 08, 2025
Key Takeaways — Data Units: Decimal vs Binary (GB vs GiB)
- GB vs GiB: convert to one system before comparing specs.
- Throughput (MB/s) may be decimal while files show binary; normalize before judging speed.
- Filesystem overhead reduces available space beyond the GB↔GiB difference.
Practice Problems
- 512 GB to GiB; 256 GiB to GB.
- Copy test: 12 GB file transfers in 90 s — compute MB/s in decimal and binary.
- RAID shows 3.63 TiB — convert to TB (decimal).
Updated October 08, 2025
Putting This Guide Into Practice
Reading about conversions is helpful, but the real shift comes when you apply the ideas to a specific job, recipe, trip, or project.
- Identify one place in your week where the ideas from “Data Units: Decimal vs Binary (GB vs GiB)” can remove confusion or re-work.
- Write down the key constants or rules from this article in the units you actually encounter.
- Test the new approach on a small, low-risk task first to build confidence.
- Update your notes with what worked so future you doesn't have to re-learn it from scratch.
When a guide leaves you with a concrete change in how you handle units, it's done its job.
Reflecting After You Use These Ideas
- Note one friction point that this article helped remove in your real workflow.
- Record any new numbers or constants you want to reuse next time you face a similar task.
- Share a short summary of “what worked” with someone who tackles the same kind of conversions.
- Decide when to revisit “Data Units: Decimal vs Binary (GB vs GiB)” so the insights stay fresh.
Small moments of reflection turn one-time tips into lasting improvements in how you handle units.
Next Steps After “Data Units: Decimal vs Binary (GB vs GiB)”
- Summarize the article in three sentences in your own words and save it near your project notes.
- Create a tiny reference card with the most important constants or rules and keep it visible.
- Share one insight with someone who doesn't enjoy working with units as much as you do.
- Schedule a quick reread before your next big task that involves the same type of conversion.
You know an article was worth your time when it changes how you handle the next real-world problem.
Discussing “Data Units: Decimal vs Binary (GB vs GiB)” With Others
- Share one example from the article with a friend, colleague, or student.
- Ask how they currently handle the type of unit problem the article describes.
- Compare notes on which tips feel realistic in your specific settings.
- Update your own approach with anything useful that comes out of that conversation.
Talking through ideas out loud often reveals which parts really make sense for your life.
Writing a Personal Note After “Data Units: Decimal vs Binary (GB vs GiB)”
- Write a few sentences about how this article connects to your own projects or studies.
- Record any new terms or unit relationships you want to remember.
- Note one thing you disagreed with or would adapt for your situation.
- Store that note somewhere you actually check, like a project notebook or notes app.
Personal reflections turn general advice into something tailored to you.
Turning “Data Units: Decimal vs Binary (GB vs GiB)” Into a Mini Project
- Identify one small task where you can apply the ideas from this article within a week.
- Write down the before-and-after of how you handle units for that task.
- Note any obstacles you hit while applying the guidance.
- Decide what you'd keep and what you'd tweak next time.
When an article becomes a concrete experiment, its lessons tend to stick.
Decimal vs Binary Prefix Reference
| Decimal Prefix | Bytes | Binary Prefix | Bytes | Difference |
|---|
| Kilo (K) | 1,000 | Kibi (Ki) | 1,024 | +2.4% |
| Mega (M) | 1,000,000 | Mebi (Mi) | 1,048,576 | +4.9% |
| Giga (G) | 1,000,000,000 | Gibi (Gi) | 1,073,741,824 | +7.4% |
| Tera (T) | 1,000,000,000,000 | Tebi (Ti) | 1,099,511,627,776 | +10.0% |
| Peta (P) | 10¹⁵ | Pebi (Pi) | 2⁵⁰ | +12.6% |
Common Storage Device: Labeled vs Reported
| Labeled Capacity | Actual Bytes | Windows Reports | Apparent Difference |
|---|
| 256 GB SSD | 256,000,000,000 B | 238.4 GiB | 17.6 GB "lost" |
| 512 GB SSD | 512,000,000,000 B | 476.8 GiB | 35.2 GB "lost" |
| 1 TB HDD | 1,000,000,000,000 B | 931.3 GiB | 68.7 GB "lost" |
| 2 TB HDD | 2,000,000,000,000 B | 1,862.6 GiB | 137.4 GB "lost" |
| 4 TB HDD | 4,000,000,000,000 B | 3,725.3 GiB | 274.7 GB "lost" |
Frequently Asked Questions
Why does my 1 TB hard drive show less than 1 TB in Windows?
Drive manufacturers use decimal prefixes (1 TB = 1,000,000,000,000 bytes). Windows reports in binary (1 TB binary = 1,099,511,627,776 bytes). A "1 TB" drive contains 1,000,000,000,000 bytes, which Windows divides by 1,099,511,627,776 and displays as 931 GB. No storage is missing — it is a units labeling difference.
What is the difference between GB and GiB?
1 GB (gigabyte, decimal) = 1,000,000,000 bytes exactly. 1 GiB (gibibyte, binary) = 1,073,741,824 bytes (2³⁰). The difference is about 7.4%. The IEC defined the binary prefixes (KiB, MiB, GiB, TiB) in 1998 to resolve this ambiguity, but the industry has been slow to adopt them consistently.
Does internet speed use decimal or binary?
Internet speeds (Mbps, Gbps) always use decimal: 1 Mbps = 1,000,000 bits per second. File sizes on your computer are often shown in binary units. This creates a second confusion: a 100 Mbps connection downloads at 100,000,000 bits/sec = 12,500,000 bytes/sec ≈ 11.92 MiB/sec (binary), which is why a "100 Mbps" connection shows ~12 MB/s in download managers.
What is a kibibyte?
1 KiB (kibibyte) = 1,024 bytes exactly (2¹⁰). Compare to 1 KB (kilobyte, decimal) = 1,000 bytes. The difference is 2.4%. Historically "KB" was used to mean 1,024 bytes in computing, which caused the confusion. The IEC binary prefixes (KiB, MiB, GiB) were created to make the distinction unambiguous.
How much smaller does a 512 GB SSD appear in Windows?
512 GB (decimal) = 512,000,000,000 bytes. Divided by 1,073,741,824 (bytes per GiB) = 476.8 GiB, which Windows displays as 476 GB using binary math but the wrong label. You appear to "lose" about 35 GB — all of which is a labeling issue, not missing storage.
