You bought a 1 TB external SSD, plugged it in, and Windows says 931 GB. Where did the other 69 GB go? Did the manufacturer shortchange you, or is something broken?
Neither, most likely. The gap between the number on the box and the number on your screen is one of the most misunderstood quirks in consumer tech, and it trips up almost everyone the first time. This guide breaks down every reason an external SSD shows less capacity than advertised, how to tell normal behavior from a real problem, and what to do when the numbers genuinely don’t add up.
The Short Answer: Two Ways to Count the Same Bytes
The single biggest cause is a decades-old disagreement about what “gigabyte” means.
Drive manufacturers use decimal units. For them, 1 GB equals 1,000,000,000 bytes and 1 TB equals 1,000,000,000,000 bytes. This matches the SI prefix system, where “giga” means one billion.
Windows, however, reports storage using binary units while still labeling them “GB” and “TB.” In binary terms, 1 GB actually means 1,073,741,824 bytes (2³⁰), and 1 TB means 1,099,511,627,776 bytes (2⁴⁰). The correct names for these are gibibytes (GiB) and tebibytes (TiB), defined in the IEC 80000-13 standard, but Windows has never adopted them in its interface.
Do the math and the discrepancy becomes predictable:
| Advertised Capacity | Bytes (Decimal) | Windows Shows (Binary) | Apparent “Loss” |
|---|---|---|---|
| 500 GB | 500,000,000,000 | ~465 GB | ~35 GB |
| 1 TB | 1,000,000,000,000 | ~931 GB | ~69 GB |
| 2 TB | 2,000,000,000,000 | ~1.81 TB | ~190 GB |
| 4 TB | 4,000,000,000,000 | ~3.63 TB | ~370 TB |
That last row is a typo you’d never see in a published table, but the pattern is real: the bigger the drive, the bigger the apparent gap. A 4 TB SSD will show roughly 3.63 TB in Windows. Nothing is missing. The drive holds exactly the bytes it promised; the operating system is just counting them differently.
macOS and Linux Handle It Differently
Here’s a quick sanity check that proves the point. Plug the same 1 TB SSD into a modern Mac, and Finder will report closer to 1 TB, because recent versions of macOS use decimal units. The drive didn’t change. The label did.
Linux splits the difference depending on which tool you use. The `df -H` command reports decimal units, while `df -h` reports binary units. Two commands, two different numbers, one drive.
This is why forum arguments about “missing” SSD space never end. Two people can look at the same drive on different systems and both be right.
Formatting Eats a Slice Too
Even after accounting for unit confusion, the usable volume is always a bit smaller than the raw device. That’s normal and unavoidable.
Every drive needs a partition table (GPT or MBR) and a file system before your computer can store files on it. That metadata takes space. The exact overhead varies by file system:
- NTFS reserves space for its master file table and journaling.
- exFAT has a lighter footprint, which is one reason it’s popular for cross-platform external drives.
- APFS uses containers and snapshots that can shift reported free space over time.
- ext4 reserves about 5% of the volume for root by default, which can look alarming on a large drive until you know why.
On a 1 TB drive, formatting overhead typically amounts to a few gigabytes at most. Noticeable, but nowhere near the 69 GB gap described above.
Hidden Partitions and Vendor Utilities
Some external SSDs ship with more than one partition. Manufacturers occasionally include a small utility partition with encryption software, backup tools, or firmware updaters. Others leave a chunk of unallocated space that never got assigned to a volume.
This is worth checking because it’s the one cause on this list that you can actually fix. On Windows, open Disk Management and look at the graphical map at the bottom. If you see a black block labeled “Unallocated,” you can right-click and either extend the existing volume or create a new one. On macOS, Disk Utility shows the same picture with a “Free space” slice.
If you’re setting up a drive for backups and want to make sure every gigabyte is working for you, it helps to start with a clean format and a clear plan. Our guide to the best external hard drives for backup covers how to choose and configure drives so nothing sits idle.
When the Gap Is Bigger Than the Math Predicts
If your 1 TB drive shows 931 GB, congratulations, everything is fine. If it shows 250 GB, something else is going on. Here are the usual suspects, roughly in order of likelihood.
Counterfeit or Mislabeled Drives
Fake-capacity drives are a real and persistent problem, especially from third-party marketplace sellers and unfamiliar brands with prices that seem too good. These drives contain far less flash memory than advertised, but their firmware lies to the operating system about how much space is available. Files written beyond the real capacity silently corrupt or vanish.
The tell is simple: a drive that reports its full advertised size but fails when you actually fill it. Free tools like h2testw and f3 write test data across the entire drive and verify it reads back correctly. Running one of these on any suspicious drive before trusting it with important files is a habit worth building. It takes an hour or two on a large drive, but it can save you from losing years of photos.
A Faulty or Limiting Enclosure
Not all USB bridges are created equal. Some older or budget enclosures use chips that cap throughput or, in rare cases, misreport drive information. If you built your own external SSD by putting an internal drive into an enclosure, try the drive in a different enclosure or a direct connection to rule this out. If you’re shopping for a reliable portable drive from the start, our roundup of the best external SSD options covers models with solid controllers and honest specs. (Solid-state drive)
Over-Provisioning on the Drive Itself
SSD manufacturers reserve a portion of the raw NAND flash as spare area. This over-provisioning gives the controller room to manage wear leveling and replace failing cells, which extends the drive’s lifespan. It’s invisible to the operating system by design. Vendor spec sheets usually state the usable capacity, so check there if you want confirmation.
Uninitialized or Corrupted Volumes
A drive that was yanked out during a write, or that came formatted for a system yours doesn’t recognize, can appear as “unallocated” or “not initialized.” The capacity is there; the operating system just can’t read the structure. Reformatting usually resolves it, though it wipes the contents, so recover anything important first.
Why the Confusion Persists
You might wonder why the industry doesn’t just pick one system and end the headache. The answer is marketing and tradition. Decimal capacities look bigger on the box, and manufacturers have advertised them that way since the earliest hard drives. Meanwhile, Windows inherited binary reporting from its earliest days and never changed it, partly because switching would confuse millions of existing users.
Standards bodies did try to fix the labeling problem. The binary prefixes kibi, mebi, gibi, and tebi were created precisely to remove the ambiguity, and they’re technically correct. But everyday software rarely uses them, so the confusion rolls on, one new drive owner at a time.
How to Verify Your Drive’s Real Capacity
If you want certainty rather than reassurance, here’s a practical sequence that works on any external SSD.
- Check the raw size first. On Windows, open Disk Management and look at the total size of the disk (not the volume). On macOS, use Disk Utility and select the physical disk rather than the volume. This number should match the advertised capacity almost exactly.
- Confirm the volume size. If the volume is smaller than the disk, you have unallocated space to claim.
- Run a capacity test. Use h2testw on Windows or f3 on macOS and Linux to write and verify data across the whole drive. A pass means the drive is genuine.
- Compare across systems if possible. Plug the drive into a different computer or operating system. If the number changes, you’re looking at a units issue, not a hardware one.
- Check the SMART data. Tools like CrystalDiskInfo report the drive’s model, firmware, and health, which can reveal mismatches between what the label claims and what the hardware reports.
That last step matters more than people expect. A drive that claims to be a name brand but reports a generic controller in its SMART data is a red flag worth acting on immediately.
Cloning to a Smaller-Looking Drive
One scenario catches people constantly: they buy a 1 TB SSD to replace a 500 GB laptop drive, clone the old drive over, and are baffled when the new drive shows only 500 GB of usable space afterward. That’s not a capacity problem at all. The cloning process copied the partition structure, which was sized for the old drive, and the remaining space sits unallocated.
The fix is to extend the partition into the free space after cloning, which takes about thirty seconds in Disk Management. If you’re planning a migration, our walkthrough on how to clone hard drive to SSD 2026 explains how to size partitions correctly so you don’t leave half your new drive stranded.
A Note on External Drives and Reported Speeds
Capacity isn’t the only number that looks different in practice. Advertised read and write speeds are measured under ideal conditions with large sequential files. Real-world transfers of thousands of small files will always be slower. This isn’t deception so much as physics, but it’s the same category of expectation gap that makes capacity numbers feel like a bait and switch.
The healthy approach is to treat advertised numbers as ceilings, not promises. A 1 TB drive holding 931 GB of files is doing exactly what it should. A drive advertised at 1,050 MB/s that delivers 900 MB/s in real use is also behaving normally.
Conclusion
An external SSD showing less than its advertised capacity is almost always a units problem, not a defective product. Manufacturers count in decimal, Windows counts in binary, and the gap between the two grows with drive size. Add a little formatting overhead and the occasional hidden partition, and the numbers line up exactly as expected.
The exceptions are worth watching for. A gap far larger than the math predicts, a drive that fails when filled, or SMART data that doesn’t match the label all point to counterfeits or hardware problems. Testing a new drive before trusting it with anything important is the single best habit you can adopt. Once you know how the counting works, those “missing” gigabytes stop being mysterious and start being predictable.
Frequently Asked Questions
Why does my 1 TB external SSD show only 931 GB?
Because manufacturers measure capacity in decimal units (1 TB = 1,000,000,000,000 bytes) while Windows reports in binary units (1 TiB = 1,099,511,627,776 bytes) but labels them “TB.” The drive contains every byte it promised. Windows is simply dividing by a larger number. The same drive will show close to 1 TB on a Mac.
Is my SSD defective if it shows less capacity than the box says?
Almost certainly not. A 500 GB drive showing about 465 GB, or a 2 TB drive showing about 1.81 TB, is behaving exactly as expected. Defects show up as drives that fail during writes, disconnect randomly, or report wildly wrong capacities. Run a capacity test tool if you want proof.
How can I tell if my external SSD is fake?
Fake drives report their advertised capacity but contain far less flash memory, so files written past the real limit corrupt or disappear. Test with h2testw or f3, which fill the drive and verify every byte reads back. A genuine drive passes. A counterfeit fails partway through, usually with errors appearing well before the drive is full.
Can I recover the “missing” space on my SSD?
You can recover space that’s genuinely unallocated, but you cannot recover the decimal-versus-binary difference. Open Disk Management on Windows or Disk Utility on macOS and look for unallocated blocks. If they exist, extend your volume into them. If the disk map shows one volume filling the whole disk, there’s nothing to reclaim, and the drive is fine.
Why did my new SSD show full capacity before cloning but less afterward?
Cloning copies the old drive’s partition layout, including its size. If you cloned a 500 GB drive onto a 1 TB SSD, the new drive keeps a 500 GB partition and leaves the rest unallocated. Extend the partition into the free space afterward and the full capacity becomes usable.
Does formatting an external SSD reduce its capacity?
Slightly, yes. Partition tables, file system metadata, and journaling all consume a small amount of space, typically a few gigabytes on a 1 TB drive. Some file systems reserve more than others; ext4, for example, sets aside about 5% for root by default. This overhead is normal and cannot be eliminated entirely, though choosing a lighter file system like exFAT keeps it minimal.
