Understanding GB and GiB in Storage Sizes

Two storage labels can describe the same number of bytes and still show different numbers. A manufacturer may state capacity in gigabytes, while an operating system or utility may display the same bytes using binary-sized units. Nothing necessarily disappeared. The scale used to divide the byte count changed.

The distinction matters when you compare a drive label, a file browser, a cloud storage allowance, a backup estimate, or a download size. “GB” and “GiB” are close enough to look interchangeable at small sizes, but the gap grows with capacity.

Decimal units and binary units start from different steps

Decimal storage units grow in powers of 1,000:

• 1 kilobyte (kB) = 1,000 bytes
• 1 megabyte (MB) = 1,000,000 bytes
• 1 gigabyte (GB) = 1,000,000,000 bytes
• 1 terabyte (TB) = 1,000,000,000,000 bytes

Binary storage units grow in powers of 1,024:

• 1 kibibyte (KiB) = 1,024 bytes
• 1 mebibyte (MiB) = 1,048,576 bytes
• 1 gibibyte (GiB) = 1,073,741,824 bytes
• 1 tebibyte (TiB) = 1,099,511,627,776 bytes

These are not two estimates. They are two precisely defined unit families. The National Institute of Standards and Technology explains the binary prefixes and gives the same byte relationships.

Why a labelled capacity can look smaller

Suppose a drive is labelled 500 GB. In decimal units, that means:

500 × 1,000,000,000 = 500,000,000,000 bytes

Express the same byte count in GiB:

500,000,000,000 ÷ 1,073,741,824 ≈ 465.66 GiB

The drive has not lost about 34 billion bytes during conversion. The displayed number is smaller because each GiB is larger than each GB. It is the same reason 1 metre and about 3.28 feet describe one length with different numbers—except the storage labels have historically been used less consistently.

The Data Storage Converter keeps decimal and binary choices explicit — each prefixed unit is labelled (decimal) or (binary) in the menu. Bits and bytes carry no suffix because they take no prefix, so neither family applies to them. Select the unit written beside the original figure rather than choosing the one whose number looks familiar. It reports up to twelve significant digits, so this conversion appears there as 465.661287308 GiB rather than the two-decimal figure rounded above.

A label saying “GB” may still need investigation

Correct symbols make the distinction clear: GB is decimal and GiB is binary. Real software does not always follow that convention. Some interfaces calculate with powers of 1,024 but display “GB”; others use decimal units throughout. A screenshot containing only a number and “GB” may therefore be ambiguous.

When accuracy matters, look for one of these:

1. A byte count, which is the common denominator.
2. A definition in the product or service documentation.
3. An explicit KiB, MiB, GiB, or TiB symbol.
4. A known example that reveals whether the next step is 1,000 or 1,024.

Do not “correct” a value by multiplying or dividing by 1.024 without knowing its starting and target units. GB-to-GiB conversion depends on the full byte definitions, and the ratio changes by scale: the difference between kB and KiB is not the same percentage as the difference between TB and TiB.

Unit conversion is not the only capacity difference

Even after converting correctly, usable space can be lower than a labelled raw capacity. Possible reasons include:

• filesystem structures that organize files and directories;
• recovery, system, or vendor partitions;
• reserved space used by a device or service;
• redundancy or snapshots;
• a storage pool that reports usable rather than raw capacity;
• rounding in a product label or interface.

Those are separate from GB-versus-GiB conversion. The converter answers “what is this quantity in another unit?” It cannot inspect a device, identify its partitions, or explain every byte that is reserved. If the converted figure and the displayed usable figure still differ, review the device or service’s own storage breakdown.

Bits and bytes are another separate distinction

Lowercase b means bit; uppercase B means byte. One byte contains eight bits. Network speeds are often stated in bits per second, while file sizes are commonly stated in bytes. A 100 megabit-per-second connection is not a promise to transfer a 100-megabyte file in one second.

First match the quantity type, then match the prefix family. Converting GiB to GB does not also convert bytes to bits unless you explicitly choose the bit unit. Our converter offers a single plain Bits unit rather than kilobits or megabits, so a megabit-per-second figure has to be scaled by hand before it can be compared with a file size.

Compare storage claims in a fixed order

For a clean comparison:

1. Record the exact number and symbol from each source.
2. Determine whether each prefix is decimal or binary.
3. Confirm whether the quantity is in bits or bytes.
4. Convert both figures to bytes or to one shared unit.
5. Keep enough decimal places to see the difference before rounding.
6. Separate conversion differences from reserved or unavailable capacity.

If you want to describe the remaining difference as a percentage, calculate it only after both capacities use the same unit. The Percentage Calculator can compare two normalized figures, but the base you choose still determines what the percentage means.

What the result can and cannot establish

A correct conversion can establish that two unit-labelled quantities represent the same or different byte counts. It cannot establish why a device, operating system, provider, or file format uses space. Nor can it tell you whether a product description, screenshot, or interface has used its symbols correctly.

Keep the original labels with your notes. A bare number such as “465.66” loses the information needed to interpret it later. “465.66 GiB converted from 500 GB” preserves both the result and its meaning.

Storage planning needs a margin for change

A capacity conversion describes a quantity at one moment. It does not forecast how quickly files, backups, applications, snapshots, or system updates will grow. If you are deciding whether storage is large enough, keep that planning question separate from the conversion. Measure the current byte total, identify what is likely to change, and leave an explicit margin rather than treating every advertised byte as permanently available working space.

Repeated conversions can also magnify rounding confusion. Keep the byte count or the highest-precision source figure, and convert from that original value each time. Converting a rounded GiB result back to GB may not reproduce the label exactly even when both calculations are correct.