Here is a fact-based summary of the story contents:You plug in a brand-new 1TB hard drive. Windows pops up with the good news: 931GB available. You do the math, and that's 69 gigabytes that appear to have evaporated somewhere between the factory and your USB port. No warning, no receipt, no explanation. Just fewer gigabytes than you paid for, staring back at you from the taskbar. For some, the immediate fear is that they've been scammed, leading them to look for ways to test real drive capacity and spot a fake before they even copy their first file.The part that might annoy you more than the missing space itself is that nobody is wrong here. Not the manufacturer, not your operating system, and not even the box the drive came in. The number you were promised and the number you got are, technically, the same number. So what happened here?Your drive has every byte it promisedYour OS is just measuring them with a longer ruler Hard drive manufacturers stick to the decimal system, the same base 10 logic we use in everyday measurements. So when they say 1TB, they mean exactly 1,000,000,000,000 bytes. One trillion, nice, clean, and no tricks there.The confusion creeps in when your operating system gets involved. Windows measures storage capacity using the binary (base-2) system, which lines up better with how a computer's architecture actually works. The catch is, it still labels everything using the familiar decimal terms. So when Windows encounters your trillion bytes, it doesn't divide by 1,000 to get gigabytes. Rather, it divides by 1,024 because, in binary, the nearest tidy power of two to 1,000 is 1,024. Then it does that again, and again, and once more for good measure. By the end of it, your 1TB drive shows up as roughly 931GB.https://www.makeuseof.com/author/oluwademilade-afolabi/
A simple way to picture it is this: the manufacturer measured your drive in kilometers. Windows came along and measured that same distance in miles. Nothing physically changed, but the number you see did. Or if you want a slightly nerdier version: the drive maker uses a ruler where 1TB equals exactly 1,000,000,000,000 bytes. Windows uses a longer ruler, one where "1TB" stretches to 1,099,511,627,776 bytes. On that scale, your drive does not quite make it to the end, even though nothing is actually missing. Here is where this story gets a little absurd. The naming confusion has, on paper at least, already been solved. Back in the late 1990s, the International Electrotechnical Commission introduced a new set of units for binary measurements in IEC 60027‑2, later consolidated in the IEC 80000‑13 standard used today. Under that system, a kilobyte stays at a clean 1,000 bytes; no confusion there. But 1,024 bytes gets a new name: a kibibyte. And from there it scales up: mebibytes, gibibytes, tebibytes. Slightly awkward names, actually, but very precise.A gibibyte, or GiB, is the one that matters here. It is what Windows has effectively been showing you this whole time. The system measures storage in binary units (gibibytes) but labels it as gigabytes, which is where that hard drive uncertainty sneaks in. That small "i" in the middle carries about a 7% difference in meaning, and Windows just... leaves it out.
>>108415712>>108415716this is a fucking technology board, everyone on the board already knowsif not, /g/ has truly fallen
There is even a formal standard, called IEC 80000-13 (2025 edition), that explicitly defines these decimal and binary prefixes. A gigabyte is one billion bytes. A gibibyte is the binary counterpart. If Windows labeled things properly and wrote "GiB" instead of "GB," most of this confusion would disappear overnight. But it doesn't. Instead, it borrows the decimal label and applies it to a binary measurement, and has done so for long enough that most people assume the confusion is the truth.Despite these IEC measurements having existed for more than two decades, most people have never heard of them, myself included, until a few moments ago, when I started writing this. Because they remain some of the most commonly confused tech terms, and there are no hard-and-fast rules governing which measurement a company can or should use, the standoff continues indefinitely.The gap keeps widening with one OS already switched sidesAnd some manufacturers were actually sued over thisThe mac storage panel.At the kilobyte level, the difference between decimal and binary is less than 2.4%. By the time you reach terabytes, that gap has grown to about 10%. A 2TB drive shows up as roughly 1.81TB, a 5TB drive as around 4.54TB, and an 18TB drive as about 16.4TB in Windows. The nothing gets bigger every time you upgrade to a larger hard drive.
Not everyone went along with this approach. When macOS X 10.6 Snow Leopard came out, Apple made a low-key but meaningful switch. It started reporting storage using the decimal system. So a 1TB drive shows up as… well, 1TB. Meanwhile, Windows still reports that same drive as 931GB. Both are technically correct. They're just speaking different dialects of the same language.The confusion hasn't just lived in forums and comment sections either. It's made its way into courtrooms. Companies like Western Digital and Seagate have faced legal challenges over this exact issue. Both ended up settling and now include disclaimers explaining that usable capacity may differ from what's printed on the box. There's no admission of wrongdoing, but an acknowledgment that the gap between what a box says and what a computer reads is real enough to require a disclaimer.Interestingly, there is one place in Windows where this whole decimal-versus-binary debate does not really exist: RAM. Memory has always been measured in binary because that's how it's addressed at the hardware level. So 8GB, 16GB, 32GB, those are really 8, 16, 32 gibibytes. And in this one case, the number you see lines up perfectly with reality.Your terabyte is fineSo, now you see that the 69GB that seems to vanish every time you buy a terabyte drive isn't actually missing. It never existed in the form you expected it to. You bought a trillion bytes, you have a trillion bytes, but your operating system is showing you those bytes measured with a slightly oversized ruler it hasn't bothered to relabel in thirty years.The storage is all there. It always was. The only thing still up for debate, oddly enough, is what we should call it.
>>108415712>No warning, no receipt, no explanation.except for the fact that this is common practice and has been for decades>For some, the immediate fear is that they've been scammed, leading them to look for ways to test real drive capacity and spot a fake before they even copy their first file.a fake would report high capacity and then fail when you try to actually store dataor just be a legit smaller disk sold as bigger and therefore report much less than 1024*1024*1024*1024 bytes rather than just modestly lesswhy did you post this here again?
