Why Does My 1TB Hard Drive Show Only 931GB? The Real Reason

Your 1 TB drive shows 931 GB because drive makers count a terabyte as 1,000,000,000,000 bytes (decimal), while Windows counts a 'GB' as 1,073,741,824 bytes (binary gibibytes). Divide 10^12 by 2^30 and you get 931.32 — that's exactly what Windows reports. No space is missing; the two sides just use different definitions of 'giga.' Check any data size in our gigabytes to megabytes converter; the full explanation is below.

The 30-second answer: 10^12 ÷ 2^30 = 931.32

There are two different 'gigabytes' in play, and your drive and your operating system picked different ones. Drive manufacturers use the decimal (SI) definition: 1 TB = 1,000,000,000,000 bytes = 10^12 bytes. Windows uses the binary definition: 1 'GB' = 1,073,741,824 bytes = 2^30 bytes. So Windows takes the drive's 1,000,000,000,000 bytes and divides by 1,073,741,824 — and 1,000,000,000,000 ÷ 1,073,741,824 = 931.32. That is the entire mystery: the drive holds every byte it promised, and Windows reports every byte it received — they just disagree on what to call a gigabyte. Nothing is broken, nothing was stolen, and no space is hiding. It is the same phenomenon as buying a '2×4' plank of lumber that actually measures 1.5 × 3.5 inches: the label follows one convention, the ruler follows another, and both are 'correct' within their own system.

TB vs TiB: the two definitions of 'tera'

To end the confusion, engineers created distinct names in 1998 (IEC 60027-2): decimal prefixes (KB, MB, GB, TB — powers of 10) and binary prefixes (KiB, MiB, GiB, TiB — powers of 2). Under this system your drive is exactly 1 TB and exactly 931.32 GiB — both statements are true, like saying a distance is both 1 mile and 1.609 km. Drive makers, network speeds, and USB specs use decimal; Windows, RAM sizing, and most software use binary. The industry shorthand got lazy: Windows labels its binary gibibytes 'GB', which is technically wrong but thirty years entrenched. macOS switched to decimal labels in 2009, which is why the same drive shows ~1 TB on a Mac and 931 GB on a PC. Linux tools vary by program. The honest fix would be for Windows to label the number '931 GiB' — and some utilities already do — but the 'GB' label persists. Whenever storage numbers look wrong, translate both sides into raw bytes first; bytes never lie.

The same math on every drive size

The labeling gap scales with size — roughly 7% at every step, because 2^30 is about 7.4% larger than 10^9. Here is what Windows reports for common drive sizes: 256 GB SSD → 238.4 GB. 500 GB drive → 465.7 GB. 1 TB drive → 931.3 GB. 2 TB drive → 1.82 TB. 4 TB drive → 3.64 TB. 8 TB drive → 7.28 TB. The pattern: take the advertised size, multiply by 0.9313, and you get the Windows number. (Above 1,024 binary gigabytes Windows switches the label to TB, so a 2 TB drive reads '1.81 TB' — itself a mix of decimal marketing and binary reporting.) The same gap hits USB sticks, SD cards, and phones: a '128 GB' phone shows about 119 GB before the OS and apps take their share. None of this is formatting overhead — formatting costs megabytes, as the next sections show. If your drive shows less than these numbers, something else is consuming space: recovery partitions, preinstalled software, or a disk that needs checking.

Why is my SSD smaller than advertised?

SSDs show the same binary-decimal gap as hard drives — a '1 TB' SSD also reports 931 GB — plus one extra invisible slice: over-provisioning. SSD controllers permanently reserve roughly 7% of the flash for wear leveling, bad-block replacement, and garbage collection, and this space is hidden from the operating system entirely. So a 1 TB SSD gives Windows 931 GiB of addressable space, of which a further hidden reserve never appears anywhere. This is by design and it extends the drive's life enormously: the controller needs spare blocks to shuffle data around as cells wear out. It is not space you can reclaim, and no formatter or partition tool will reveal it. The practical upshot: budget SSD capacity at about 86–87% of the box number for usable space (931 GiB minus the reserve), and leave 10–20% of an SSD unfilled in daily use — SSDs slow down and wear faster when packed to the brim. Our gigabytes to megabytes converter keeps the decimal/binary math straight when you are comparing specs.

How much space does formatting actually take?

Far less than the labeling gap — formatting overhead is a rounding error next to it. When you format a 1 TB drive as NTFS, the file system writes its bookkeeping structures (the Master File Table, bitmap, journal): roughly tens to low hundreds of megabytes, depending on the allocation unit (cluster) size you choose. That is under 0.05% of the drive — invisible against the 69 GB decimal/binary difference. exFAT, the usual choice for USB sticks and SD cards, is even leaner. The cluster-size choice matters only at the margins: tiny 4 KB clusters waste less space on small files but grow the file table; 64 KB clusters suit drives holding mostly large videos. None of these choices will turn 931 GB into 1,000 GB, because the gap was never about formatting. If a freshly formatted drive shows meaningfully less than 931 GB per advertised terabyte, look for hidden recovery partitions or a failing drive — not the file system.

Why your Mac shows the full 1 TB

Plug the same drive into a Mac and Finder cheerfully reports about 1 TB — because since Mac OS X 10.6 (Snow Leopard, 2009), Apple counts storage in decimal, matching the drive makers. Same bytes, different ruler, no contradiction. This creates its own confusion in reverse: files copied from a Windows PC 'grow' slightly when viewed on a Mac, and download progress bars disagree between the two systems. Neither is wrong; they are just labeling the same 1,000,000,000,000 bytes differently. Windows, as of current versions, still reports binary-style sizes under the 'GB' label — the 931 GB figure is the giveaway. When comparing drives across systems, or checking whether a backup actually fits, convert both sides to bytes first. And when a spec sheet says 'GB' without qualification, assume decimal from a manufacturer and binary from an operating system — that assumption resolves nearly every storage-size argument on the internet.

Recovery partitions: space that really is gone

Beyond the labeling gap, some space genuinely disappears — and it belongs to recovery and system partitions. Windows typically reserves a few hundred megabytes for its recovery environment plus a 100+ MB EFI partition; manufacturer PCs add their own restore images, often 10–30 GB, which is why a '512 GB' laptop may show only ~440 GB usable. Phones are worse: the OS, preinstalled apps, and system reserves can eat 15–30 GB of a 128 GB phone before you install anything. To see where it went on Windows, open Disk Management: it lists every partition, including the hidden ones, in megabytes — the numbers add up to the drive's full binary capacity. On a Mac, Disk Utility's partition view does the same. This reserved space is real and (mostly) intentional: it holds the tools that reinstall your system when everything breaks. The labeling gap explains the 931; partitions explain anything below it.

How to check a drive's true capacity

Stop arguing with labels and measure in bytes. On Windows, right-click the drive → Properties: the 'Capacity' line shows the size in bytes alongside the GB figure — compare that byte count to the manufacturer's spec (1,000,000,000,000 for a 1 TB drive) and they will match. In Disk Management, all partitions' sizes sum to the full capacity. On a Mac, Disk Utility → Info shows both decimal and binary figures. For a second opinion, the drive maker's own diagnostic tool (Samsung Magician, WD Dashboard, Crucial Storage Executive) reports raw capacity and health. Two red flags that mean something is actually wrong: capacity in bytes far below spec (failing flash or a counterfeit drive — '2 TB' USB sticks that are really 32 GB are a classic scam), or capacity that shrinks over time (failing sectors being retired). A stable 931,322,000,000-ish bytes on a 1 TB drive is perfectly healthy — it is just 931.32 GiB wearing a 'GB' nametag.

Data sizes, converted exactly

The decimal/binary split follows you into every storage calculation — video file sizes, backup planning, cloud tiers — so keep a converter handy. Our gigabytes to megabytes converter runs the exact factors, and the free unit converter covers every data unit from bits to terabytes. Start from the ToolNest homepage for all 130+ free tools. Related guides: converting text to binary by hand (how bits become bytes), decoding Base64 (why encoded files run ~33% larger), and Unix timestamps in Excel.