The answer depends on which gigabyte you mean: under the binary definition used by Windows and most RAM, 1 GB equals 1,024 MB, while under the decimal definition used by drive makers and the SI system, 1 GB equals 1,000 MB. That 24 MB gap looks small at the single-gigabyte level, but it compounds into a 74 MB difference at 10 GB and a 7.4 GB apparent shortfall on a 100 GB drive. Knowing which standard a device or label uses prevents you from thinking a healthy drive has shrunk or that a file transferred incompletely.
Where the 1,024 figure comes from
The number 1,024 is not arbitrary. It is 2 to the tenth power, the exact count of distinct values ten binary switches can hold, which is why every binary prefix in computing steps by 1,024 rather than 1,000. A byte has 8 bits, a kilobyte under the binary reading has 1,024 bytes, a megabyte has 1,024 kilobytes, and a gigabyte has 1,024 megabytes. The multiplier is uniform at every rung.
That uniformity is the reason the ladder feels clean to engineers and awkward to shoppers. Memory addresses map to powers of two, so a 4 GB stick of RAM physically contains 4,096 MB organized in addressable blocks. Operating systems report storage in this binary scale by default. When Windows shows a folder as 2.4 GB, it is summing binary units internally even though the label says "GB."
The terminology itself is contested. The International Electrotechnical Commission introduced "gibibyte" and the symbol GiB in 1998 to name the 1,024-based quantity unambiguously, so that 1 GiB means exactly 1,024 MiB. Under that convention, "gigabyte" proper means 1,000 megabytes. The IEC standard is technically current, but the market never fully adopted the gibibyte suffix, which is why a single label can mean two different sizes.
Apple has nudged the other way. Since OS X Snow Leopard in 2009, macOS reports drive capacity in decimal units, so a 500 GB Mac drive shows roughly 500 GB rather than the ~465 GB Windows would display. Two machines with identical physical storage can therefore report different "GB" totals purely because of the base each counts in.
Why drive manufacturers count 1,000 MB as one GB
Drive makers use the decimal definition because it matches the SI prefix system and because the resulting numbers are larger and simpler to market. A manufacturer sells you a "1 TB" SSD that contains 1,000,000,000,000 bytes by design, not a defective product masking a shortfall. Seagate, Western Digital, and Samsung all state the decimal basis in their capacity notes.
The arithmetic consequence is a consistent ratio, not a random loss. Decimal capacity divided by binary capacity equals 1,000 divided by 1,024, roughly 0.9766 per step. For a single unit the shortfall is about 2.34 percent. Stack the steps to terabytes and the compounding grows, which is why a 1 TB drive shows close to 931 GB in Windows file listings rather than 1,024 GB.
Drive makers are not the only decimal users. Networking gear and telecom billing often count decimal, so a "1 Gbps" connection means 1,000,000,000 bits per second. SSD controllers and flash firmware also work in decimal or mixed units internally, which is why some utilities report a drive's raw size one way and the OS another.
None of this changes the drive's physical capacity. The bytes are all there. The label and the readout simply speak different dialects, and the missing "GB" exist only in the translation.
The full unit table from bytes to terabytes
Seeing every rung side by side makes the divergence easier to track. The table below shows the binary value, the decimal value, and the gap at each level, using figures derived from the 1,024 and 1,000 multipliers.
| Unit | Binary value (IEC name) | Decimal value (SI) | Gap in bytes |
|---|---|---|---|
| 1 KB | 1,024 bytes (1 KiB) | 1,000 bytes | 24 |
| 1 MB | 1,024 KB = 1,048,576 bytes (1 MiB) | 1,000 KB = 1,000,000 bytes | 48,576 |
| 1 GB | 1,024 MB = 1,073,741,824 bytes (1 GiB) | 1,000 MB = 1,000,000,000 bytes | 73,741,824 |
| 1 TB | 1,024 GB = 1,099,511,627,776 bytes (1 TiB) | 1,000 GB = 1,000,000,000,000 bytes | 99,511,627,776 |
The binary GB is about 7.37 percent larger than the decimal GB. That percentage stays fixed across the boundary between MB and GB, which means every conversion you do has the same relative distortion whether you are working in megabytes or terabytes.
For quick mental math, treat a binary GB as roughly 1.07 decimal GB and a decimal GB as roughly 0.93 binary GB. Those approximations land within a fraction of a percent for most everyday estimates.
Windows, macOS, and Android each label the same disk differently
The operating system decides which number you see, and the big three do not agree. Windows Explorer and the Windows disk management tools report binary units under the "GB" label, so a 256 GB drive reads as roughly 238 GB. macOS reports decimal units under the same label, so the same drive reads as roughly 256 GB. Android's settings app also leans decimal for storage totals.
The table below compares a 256 GB and a 1 TB drive as each platform would display it, using the 0.9766 binary-to-decimal ratio and rounding to whole gigabytes.
| Drive label | Windows (binary GB) | macOS / Android (decimal GB) | Difference |
|---|---|---|---|
| 256 GB | ~238 GB | ~256 GB | ~18 GB |
| 512 GB | ~477 GB | ~512 GB | ~35 GB |
| 1 TB | ~931 GB | ~1,000 GB | ~69 GB |
The lesson for anyone comparing a Windows laptop to a MacBook is to normalize before judging. A 512 GB Windows machine showing 477 GB free of the marketing label is not worse built than a Mac showing 512 GB; both contain the same physical flash, and the difference is purely the display base. Check the "bytes" figure in the OS's disk properties or in System Information if you need the exact number.
File transfer apps can muddy this further. Some show speed or file size in binary MB while the operating system shows decimal GB, and a single copy operation can display a "GB" figure on one side and a different "GB" figure on the other. Both are correct within their own convention.
Worked example: converting 5,000 MB to GB in both systems
Take a 5,000 MB file, a common size for a 4K video export or a compressed archive. The conversion you get depends entirely on the base you divide by, and the difference is large enough to matter for planning.
Under the binary rule, divide 5,000 by 1,024 to get 4.88 GB. Under the decimal rule, divide 5,000 by 1,000 to get 5.00 GB. The gap is about 0.12 GB, or roughly 120 MB, which is enough to change whether the file fits on a remaining-space reading.
Now reverse it. A file advertised as 5 GB is 5,120 MB in binary terms and 5,000 MB in decimal terms, a 120 MB shortfall if you budgeted by the decimal number. For a stack of files, multiply the gap by the count: ten 5 GB files drift by about 1.2 GB between the two systems, which is the equivalent of a small application install.
Run the same arithmetic on a drive purchase. A 2 TB drive is 2,000,000 MB in decimal and about 1,862,645 MB in binary, so the binary MB total looks roughly 137 GB smaller than the decimal GB total suggests. That computation is how you predict the "missing" space before you open the box, rather than after.
When the 1,024 conversion leads to a bad decision
The most expensive misreading happens in cloud billing and backup quotas. Bucket storage is usually priced per decimal gigabyte-month, but customers plan by copying binary figures from their own systems. A 100 GB backup job that reads as 100 GB in Windows is roughly 107.4 decimal GB when the provider counts bytes, which inflates the bill by about 7 percent if you estimate purely from the OS reading.
The second failure case is transfer verification. A file copy tool may report completion at "4.88 GB" using binary units while a sync client reports "5.0 GB" using decimal ones. Neither tool is wrong, and both describe the same 5,000 MB of data. Users who assume one tool is lying sometimes re-copy a perfectly intact file or reformat a drive unnecessarily, wasting hours.
A third edge case involves flash drives sold as "32 GB" that display around 29.8 GB in Windows. The drive contains about 32,000,000,000 bytes, which is 32 decimal GB and about 29.8 binary GB, and the vendor is within specification. Counterfeit drives that contain less than the stated bytes are a separate problem, and the only reliable test is writing known files and confirming a readback hash matches.
How to convert any MB-to-GB figure in three steps
If you need a reliable conversion on the spot rather than a rough estimate, this sequence works for any file, drive, or plan. It assumes you have the number in megabytes and need the answer in gigabytes under a specific standard.
1: Decide which base applies: binary for Windows, RAM, and most operating system readouts; decimal for drive labels, macOS, and cloud billing figures. Ask the source of the MB number first. 2: Divide the megabytes by 1,024 for the binary answer, or by 1,000 for the decimal answer. Use a calculator rather than estimating when the result drives a purchase or a quota decision. 3: Sanity-check against a known ratio: the binary result should be about 97.7 percent of the decimal result, and each additional gigabyte of binary storage should show roughly 24 megabytes less than the decimal equivalent.
Common mistakes are mixing bases in the same calculation, such as dividing decimal megabytes by 1,024 or the reverse, and trusting a single tool's "GB" readout without confirming which base it counts in. If a conversion looks off by a round number like 7 percent, you almost certainly crossed the boundary between the two systems. Write the base in your notes when you record the result so a later reader does not repeat the divide.
A simpler guardrail is to state results as both, for example "5,000 MB is 4.88 GiB, the binary reading, and 5.0 GB, the decimal reading." Two labels remove the ambiguity that a single ambiguous number creates.
Why gibibytes never caught on in marketing
The IEC's gibibyte was supposed to end the confusion, but it lost the marketing war. Drive makers had no incentive to label a 500 GB drive as 465 GiB, and operating systems had decades of internal code built around binary prefixes. The result is a durable split where the same three-letter abbreviation can mean two different sizes, and the only fix is to read the context.
Regulators have occasionally stepped in. Some consumer protection bodies in Europe have pressed manufacturers to state capacity in decimal terms explicitly, while others have asked operating systems to adopt decimal labels, both of which are slow-moving changes. The IEC standard remains the closest thing to an authority for what "GB" technically means, even though most devices ignore it.
Practically, this means no single answer to "how many MB in a GB" is correct in every setting. The unit conversion table above shows both values, and the correct pick is whichever base the reader's device or label uses. The safest habit is to ask which definition applies before doing arithmetic, because the choice changes the number by about 7.37 percent.
FAQ
Is a GB 1,000 MB or 1,024 MB?
Both are valid, and the split is the source of the whole confusion. Under the SI and IEC prefixes, 1 GB equals 1,000 MB and 1 GiB equals 1,024 MiB. Under the older binary usage that most operating systems and memory vendors still follow, 1 GB equals 1,024 MB. The base determines the answer, not the label.
Why does Windows show 1 TB drives as only 931 GB?
Windows counts binary terabytes, so 1 TB of decimal storage equals about 931 GiB, which the OS labels as GB. The drive has 1,000,000,000,000 decimal bytes and roughly 1,099,511,627,776 binary bytes, and the difference is the base conversion. The physical storage is present, and the OS just counts it in units of 1,024.
Do SSD makers short-change you when they sell "500 GB"?
No, if the drive contains 500,000,000,000 bytes as advertised. That decimal capacity becomes roughly 465 GiB in binary readouts, and the 35 GB gap is the ratio, not a shortfall. Genuine short-changing happens with counterfeit drives that physically contain less flash, and the only reliable test is writing files and verifying the readback.
What is the difference between a gigabyte and a gibibyte?
A gigabyte is 1,000,000,000 bytes in the SI convention, while a gibibyte is 1,073,741,824 bytes in the IEC convention. The IEC introduced the gibibyte in 1998 to separate the two stems, and the pronunciation is "gib-ih-bite." The term is standard in technical documentation but rarely appears in consumer product labels.
How many megabytes are in a terabyte?
A decimal terabyte is 1,000,000 MB, and a binary terabyte is 1,048,576 MB under the 1,024 ladder. The same 7.37 percent gap applies between the two totals. Windows showing a 1 TB drive as 931 GB is the binary reading, and the decimal equivalent is 1 TB.
Does a USB drive with less than advertised capacity have a virus?
Usually not. Genuine brand drives at 32 GB or 64 GB show lower binary readings and are within spec, and the apparent loss is the unit convention. A counterfeit drive that shows a capacity far below the label, or that corrupts files past a certain point, is a different case, and the write-verify test above distinguishes the two.
Can I change which unit Windows reports?
Yes, Windows supports decimal display in some newer builds and through registry settings, and macOS reports decimal by default. The setting changes the label, not the physical bytes, and two machines with the same setting will agree on the display but not on the underlying count. Confirm the current option in the OS's documentation before changing it.
This is general educational information about unit conversion, not a diagnosis, treatment plan, or professional advice. Storage accounting can affect billing quotas and backup planning, so verify figures against the provider's documented unit convention and consult a qualified professional for decisions with contractual or financial consequences.