How Many Gigabytes Make A Terabyte

You buy a 2 TB external drive. Plug it in. Plus, windows says 1. Because of that, 81 TB. Your heart sinks — did you get scammed?

Short answer: no. Long answer: it's complicated. And understanding why saves you from a lot of confusion down the road.

What Is a Terabyte Anyway

A terabyte is a unit of digital storage. Also, the prefix "tera" comes from the Greek word for monster — fitting, given how much data we shove into these things now. Think about it: one terabyte equals one trillion bytes in the decimal system. That's 1,000,000,000,000 bytes. Written out, it looks absurd.

But here's where it gets messy. So while the packaging on your drive uses decimal math (base 10), your operating system uses binary math (base 2). Powers of two. Also, computers don't count in tens. Binary. They count in twos. Same number, different language.

The Decimal Definition

Drive manufacturers use the International System of Units (SI). In that system:

• 1 kilobyte = 1,000 bytes
• 1 megabyte = 1,000 kilobytes
• 1 gigabyte = 1,000 megabytes
• 1 terabyte = 1,000 gigabytes

Clean. Round. Easy for marketing. Think about it: a 2 TB drive has 2,000,000,000,000 bytes. That's the number printed on the box.

The Binary Definition

Your OS — Windows, mostly — uses the older binary convention:

• 1 kibibyte (KiB) = 1,024 bytes
• 1 mebibyte (MiB) = 1,024 KiB
• 1 gibibyte (GiB) = 1,024 MiB
• 1 tebibyte (TiB) = 1,024 GiB

Notice the "bi" in there? Kibi, mebi, gibi, tebi. Those are the official binary prefixes, standardized by the IEC back in 1998. Almost nobody uses them in daily conversation. Windows still labels them KB, MB, GB, TB — which is technically wrong but practically universal.

So when Windows reads your 2,000,000,000,000-byte drive, it divides by 1,024 four times. The result: roughly 1.81 TiB. Because of that, displayed as "1. 81 TB.In real terms, " You didn't lose space. The ruler just changed.

Why It Matters / Why People Care

This isn't trivia. It affects real decisions.

Buying Storage

You're shopping for a NAS. If you buy four 4 TB drives in RAID 5, you get roughly 10.9 TiB usable. 9 TiB raw — about 9.You need 8 TB of usable space after RAID. But if you calculated in decimal, you'd expect 12 TB raw. That gap matters when you're budgeting for a small business.

Cloud Pricing

Cloud providers bill in GB. AWS S3, Google Cloud, Azure — they all use decimal gigabytes. Here's the thing — 1 GB = 1,000,000,000 bytes. But your local tools might report in GiB. If you're syncing 500 GiB of data, you're actually paying for ~537 GB. Over months, that adds up.

Backup Planning

You have 1.Windows shows 1.You buy a 2 TB backup drive. Consider this: 5 TB of photos. But your photo library grows. Now, six months later, the backup fails. You think you have 300 GB of headroom. 81 TB free. The "missing" 185 GB wasn't missing — it was never there in binary terms.

Gaming

Modern games hit 150 GB+. Call of Duty with all modes installed can exceed 250 GB. A 1 TB SSD sounds like room for six big games. In practice, after OS overhead and binary conversion, you get maybe four. Gamers learn this the hard way.

How It Works — The Math Behind the Confusion

Let's walk through it step by step. No calculator needed — just the logic.

Decimal Path (What the Box Says)

Start with bytes. Multiply by 1,000 each step up.

1 TB = 1,000 GB
= 1,000,000 MB
= 1,000,000,000 KB
= 1,000,000,000,000 bytes

That's it. Base 10. Human-friendly.

Binary Path (What Your Computer Sees)

Start with bytes. Multiply by 1,024 each step up.

1 TiB = 1,024 GiB
= 1,048,576 MiB
= 1,073,741,824 KiB
= 1,099,511,627,776 bytes

For more on this topic, read our article on which one of the following quantities is a vector quantity or check out what did the cathode ray tube discover.

The ratio between them: 1,099,511,627,776 ÷ 1,000,000,000,000 ≈ 1.Even so, 0995. So 1 TiB ≈ 1.0995 TB. On top of that, or flipped: 1 TB ≈ 0. 9095 TiB.

That 9% gap? That's where your "missing" space goes.

Why 1,024?

2^10 = 1,024. It's close to 1,000. Day to day, early computer engineers liked it because memory addressing works in powers of two. A 10-bit address bus gives you 1,024 locations. Natural fit. The "kilo" prefix got borrowed because it was close enough — and stuck for decades.

The IEC Standard That Nobody Uses

In 1998, the International Electrotechnical Commission said: stop. And almost entirely ignored by software makers. It was clean. Use kibi, mebi, gibi, tebi for binary. Day to day, keep kilo, mega, giga, tera for decimal. Practically speaking, 6) back in 2009. Logical. Because of that, windows, macOS (until recently), most Linux tools — they all still show "GB" when they mean "GiB. In practice, " macOS switched to decimal display in Snow Leopard (10. Windows never did.

So we live in a hybrid world. Drives in decimal. OS in binary. Labels wrong on both sides.

Common Mistakes / What Most People Get Wrong

"My Drive Is Defective"

It's not. The OS converts. The capacity is exactly what the box says — in decimal bytes. No bytes were harmed.

"The Manufacturer Lied"

They used the standard unit for their industry. It's like

buying a 2×4 at the lumber yard and complaining it's actually 1.Also, 5×3. 5 inches. Day to day, nominal vs. actual. Industry standard, not deception.

"Formatting Eats Space"

Formatting takes a few hundred MB for filesystem structures. Not 9%. So naturally, check raw block count: lsblk -b or diskutil list on macOS. The gap exists before you format. Practically speaking, matches the box. In practice, multiply blocks by block size. The "loss" is pure unit conversion.

"RAID / NAS Changes the Math"

It doesn't. So a 4-bay NAS with 4 TB drives (decimal) gives you 16 TB raw. Your OS sees ~14.5 TiB. RAID overhead (parity, mirrors) comes after* that conversion. Think about it: two different losses. Don't conflate them.

"Cloud Storage Is Different"

Mostly not. Which means your backup tool reports in GiB. Read the pricing page fine print. Same 7–9% bill surprise. On the flip side, aWS S3, Google Cloud, Backblaze B2 — they bill in decimal GB. It says "GB = 10^9 bytes.

What You Can Actually Do

Check Before You Buy

Multiply advertised TB by 0.Now, 909. That's your usable TiB.
4 TB drive → 3.Even so, 64 TiB. On the flip side, 8 TB drive → 7. 27 TiB.
But 12 TB drive → 10. So 9 TiB. Plan around the smaller* number.

Use Tools That Tell the Truth

Linux: df -H (decimal) vs df -h (binary).
macOS: Finder and df now agree — both decimal.
Think about it: windows: No built-in decimal view. Use third-party (WizTree, TreeSize) or mentally convert.

Label Your Drives

Sharpie on the label: "4 TB / 3.64 TiB." Future you won't panic.

Budget for the Gap

If you need 10 TiB usable, buy 11 TB decimal. Worth adding: not 10. The math is unforgiving.

The Bigger Picture

This isn't a bug. Still, it's a collision between two numbering systems that both made sense in their domain. Decimal for humans. Day to day, binary for silicon. The industry never agreed on a clean handoff. On top of that, the IEC standard exists. Almost no consumer software follows it.

So the gap persists. Every drive purchase. Now, every backup plan. Every "disk full" error that makes no sense until you remember: the box spoke decimal. The OS speaks binary. They weren't talking to each other.

Next time you see "931 GB free" on a 1 TB drive, don't rage. Which means do the math. In practice, the bytes are all there. They're just wearing a different label.