Storage Math That Actually Matters
A terabyte is either 1,000,000 megabytes or roughly 953,674 megabytes, depending on which system your equipment uses. The confusion exists because two completely different standards are being applied to the same unit names, and neither side admits the other is wrong. Storage manufacturers use base-10. Operating systems like Windows use base-2. Both are correct within their own frameworks, which makes troubleshooting compatibility issues unnecessarily painful. The base-10 answer is straightforward: 1 TB = 1,000,000 MB. The calculation is 1,000 times 1,000 times 1,000. Every term adds three zeros. This is what the SI system defines, and it is what Seagate, Western Digital, and Samsung use when they label their drives. A 1 TB hard drive from any major manufacturer contains exactly 1,000,000,000,000 bytes of raw storage capacity. The base-2 answer comes from how computers actually address memory and storage. Here, a terabyte is technically a tebibyte (TiB), and a megabyte is technically a mebibyte (MiB). Under this system, 1 TB = 1,024 GB, and 1 GB = 1,024 MB, which gives you approximately 1,073,741,824 megabytes. When Windows shows you that your 1 TB drive has only about 931 GB of free space, that is this system at work. The drive has not shrunk. The naming convention has shifted.
I ran into a real mess with this a few years back when a client ordered five 4 TB NAS drives for a media archive project. The manufacturer specs listed a total of 20 TB raw storage. After formatting and the base-2 conversion, the system reported roughly 18.18 TiB available. The client thought we had lost nearly 2 TB of capacity to some kind of hardware defect. We spent an entire afternoon pulling drives, running diagnostics, and checking SMART data before anyone admitted the math didn't match the expectation. The workaround was simple: calculate usable capacity using the binary conversion from day one, not after the drives are already racked and cabled. SSDs add another layer that most people skip over. When a manufacturer says a 1 TB SSD holds 1 TB, they are selling you 1,000,000,000,000 bytes of NAND. But a significant portion of that space is reserved for wear leveling, over-provisioning, and controller operations. A Kingston or Samsung 1 TB SSD might only offer around 930 GB to the operating system after factory overhead is accounted for. That is not a bug. It is the price of longevity. The practical impact shows up most when you are migrating data. If you have 800 GB of files and you try to move them onto a drive that looks big enough on paper, you might find yourself stuck at 97% because the destination drive is measured in base-10 and your source is counted by the OS in base-2. I usually just multiply my source data by 1.1 as a buffer, which covers the conversion gap and leaves room for metadata without second-guessing every drive label.
Another thing that trips people up is that not all operating systems convert the same way. macOS reported storage differently for years, and even Linux gives you options depending on whether you are using df, lsblk, or a GUI tool. If you are building a server and you need to know exactly how many megabytes fit in your volume, always check the actual byte count rather than trusting the pretty-printed display. For everyday purposes, memorizing the base-10 figure is fine. 1 TB equals 1 million MB. When you are buying drives, planning capacity, or doing migrations, knowing the base-2 discrepancy prevents panic and wasted hours. The drives are not broken. The math is just wearing two different hats.
Get the Full Details
