Why Does a 1 TB Drive Show as 931 GB? The Missing Capacity Explained
Not Lost Space, a Difference in Units
Short answer: no space is missing. When a manufacturer says 1 TB they mean 1,000,000,000,000 bytes; Windows divides that same number by 1024 and labels the result "931 GB". The roughly 7% difference comes entirely from that unit mismatch, and it is identical for every brand and model.
On top of that sit a few items that genuinely do consume space: a recovery partition, the EFI boot partition and the filesystem's own bookkeeping. This guide separates the part of the gap that is pure arithmetic from the part that is real — and explains when the gap is actually a sign of fraud.
Key Takeaways
- Manufacturers use decimal units: 1 TB = 1,000,000,000,000 bytes. Windows divides in binary (1024³) but still labels the result "GB".
- A 1 TB drive shows 931 GB, a 2 TB drive 1863 GB, a 500 GB drive 465 GB. The ratio is always the same.
- macOS has used decimal units since 10.6, so the same disk looks much closer to the label on a Mac.
- What genuinely consumes space: the recovery partition (500 MB-20 GB), the EFI partition (100-300 MB) and NTFS's Master File Table.
- If the gap exceeds 10% on a drive that is not new, look for a hidden manufacturer recovery partition or unallocated space.
- Far less space than expected — for example a "2 TB" drive corrupting data after 8 GB — is the signature of a fake-capacity drive.
The Real Cause: 1000 or 1024?
Hard drive and SSD manufacturers count capacity in decimal. To them a kilobyte is 1000 bytes, a megabyte 1,000,000 bytes and a terabyte 1,000,000,000,000 bytes. The "1 TB" on the label is exactly that, and it is not wrong; in the international system of units the prefix "tera" already means 10¹².
Windows divides the same bytes in binary: 1024, 1024², 1024³. The problem is not the division but the label — Windows writes the result as "GB" rather than "GiB" (gibibyte). Divide 1,000,000,000,000 bytes by 1024³ and you get 931.32, which appears on screen as "931 GB".
That is why the gap is always the same proportion: about 7.4%. A 500 GB drive shows 465 GB, 1 TB shows 931 GB, 2 TB shows 1863 GB and 4 TB shows 3725 GB. Buying a different brand changes nothing, because the arithmetic is identical on every disk.
Why Does a Mac Report It Differently?
Plug the same disk into a Mac and the capacity looks much closer to the label. The reason is simple: since 10.6 Snow Leopard, macOS reports storage sizes in decimal. Apple speaks the same language as the manufacturer.
That does not mean the Mac "gives you more space". Both operating systems see the same number of bytes; they just write it differently. The same file on the same disk can read as 4.66 GB in Windows and 5.0 GB on a Mac — the file did not change, the unit did.
Linux distributions use both. `df -h` reports in binary (GiB) while `df -H` reports in decimal, and many tools state the distinction explicitly by writing "GiB" and "GB". That is, in fact, what Windows ought to do too.
What Genuinely Takes Space
Beyond the unit difference, a few gigabytes really are gone. First, partitions. A modern Windows install carries at least two more partitions besides C:: a 100-300 MB EFI System Partition and a Recovery partition ranging from 500 MB to a few gigabytes. On pre-built machines the manufacturer adds a factory restore partition on top, which can be 10-20 GB.
Second, the filesystem's own structures. NTFS reserves space for the Master File Table, where it records every file on the disk, plus a journal and backup boot records. Typically that is under 1% of capacity, but it is not zero.
Third, the space Windows sets aside for itself. Since Windows 10 version 1903, the Reserved Storage feature holds back several gigabytes so updates can install without running out of room. That space does not show as used in Explorer but is not available either. `DISM /Online /Get-ReservedStorageState` shows its status.
When to Worry: Fake-Capacity Drives
Every difference described so far is predictable and normal. One situation, though, is genuinely a problem: USB sticks and memory cards with faked capacity. Their controller lies to the operating system — it reports itself as 1 TB while the chip inside holds only 8 or 16 GB.
The symptom is this: the drive looks normal, the first files copy fine, but once the real capacity is passed, everything written afterwards silently disappears or corrupts. The file stays in the listing and turns out to be broken when opened. This is the kind of problem you discover months later, when you need the backup.
The way to protect yourself is to fill a new drive to the end and read it back before you start relying on it. Only then do you know its capacity is genuinely what it claims. For unusually cheap, high-capacity sticks from unknown brands, that test is not optional — it is a required step.
Frequently Asked Questions
Will reformatting the drive get the missing space back?
No, not the part caused by units, because no space is actually missing. However, if there is an old recovery partition or unallocated space, merging partitions can recover a few gigabytes. Make sure you have recovery media before deleting a factory restore partition.
Is there a capacity difference between exFAT, NTFS and APFS?
A small one. Every filesystem reserves space for its own bookkeeping and uses different cluster sizes. With very many small files the difference grows, but on its own it does not account for several gigabytes.
Does SSD over-provisioning reduce capacity?
The area the controller reserves for wear levelling already sits outside the labelled capacity, so on a 1 TB SSD it is not carved out of the advertised 1 TB. Separately, leaving part of the drive free yourself acts as extra over-provisioning and helps performance.
Does my phone show the same difference?
Yes, the same arithmetic applies. On top of that, the operating system and preinstalled apps occupy internal storage, which is why a 128 GB phone typically shows around 105-112 GB usable.
Verdict
A 1 TB drive showing 931 GB is not a fault, it is the result of two different ways of counting. Add recovery partitions and filesystem bookkeeping and usable space on a typical Windows machine lands at roughly 90-92% of the label. That is entirely normal.
What matters is not how big the drive is but what is inside it. Disk Mop's Disk Analysis and Disk Treemap modules show folder by folder where the remaining space went; for most people, clearing 30-40 GB of genuine clutter beats worrying about the unit difference.
See what is really using space on your drive
One-time payment for lifetime access to all features. No subscription, no hidden fees.
Download Disk Mop Now