GB and GiB use different bases
A gigabyte, abbreviated GB, is a decimal quantity of exactly 1,000,000,000 bytes, or 10⁹ bytes. A gibibyte, abbreviated GiB, is a binary quantity of exactly 1,073,741,824 bytes, or 2³⁰ bytes. They are both byte-based storage units, but they are not interchangeable labels.
The IEC binary prefix gibi was created to distinguish powers of 1,024 from SI decimal prefixes. Capitalization matters: uppercase B means byte, while lowercase b normally means bit. One byte contains eight bits, but GB-to-GiB conversion does not require multiplying or dividing by eight because both units already describe bytes.
At smaller scales, the matching definitions are 1 kB = 1,000 bytes and 1 KiB = 1,024 bytes; 1 MB = 1,000,000 bytes and 1 MiB = 1,048,576 bytes. The pattern continues consistently. Using explicit IEC names for binary quantities prevents a reader from having to guess whether a familiar decimal prefix was repurposed for a power of two.
How to convert GB to GiB
Start with bytes. Multiply GB by 1,000,000,000 bytes per GB, then divide by 1,073,741,824 bytes per GiB. The combined formula is GiB = GB × 1,000,000,000 ÷ 1,073,741,824. One GB is approximately 0.9313225746 GiB.
Reverse with GB = GiB × 1,073,741,824 ÷ 1,000,000,000. One GiB is exactly 1.073741824 GB. Because GiB is the larger unit, a fixed positive byte count has a smaller numeric value in GiB than in GB. This direction check catches the common mistake of treating the two prefixes as synonyms.
The percentage gap grows in its visible numeric effect at larger prefix levels. Decimal prefixes advance by factors of 1,000, while binary prefixes advance by factors of 1,024. One TB is about 0.9095 TiB, even though one GB is about 0.9313 GiB. This does not mean a different rule suddenly applies; repeated scaling makes the ratio between the corresponding decimal and binary units change at each prefix level.
Three storage-capacity examples
Input: 128 GB. Formula: GiB = GB × 1,000,000,000 ÷ 1,073,741,824. Calculation: 128 × 1,000,000,000 ÷ 1,073,741,824 = 119.20928955…. Result: about 119.21 GiB. Interpretation: both figures represent the same 128,000,000,000-byte quantity before other uses of space. Reverse check returns 128 GB.
Input: 500 GB. Formula: GiB = GB × 1,000,000,000 ÷ 1,073,741,824. Calculation: 500 × 1,000,000,000 ÷ 1,073,741,824 = 465.66128730…. Result: about 465.66 GiB. Interpretation: the smaller number comes from using a larger binary unit, not from bytes disappearing during conversion.
Input: 1 TiB. Formula: GiB = TiB × 1,024. Calculation: 1 × 1,024 = 1,024. Result: exactly 1,024 GiB, equal to 1,099.511627776 GB. Interpretation: binary units scale by 1,024 at each prefix step, while the decimal GB expression scales from bytes by powers of 1,000.
Why an advertised capacity may display differently
Storage products commonly state capacity with decimal units, while some operating systems or utilities calculate a binary-scaled quotient. If software divides 500,000,000,000 bytes by 2³⁰, it obtains about 465.66. Correct labeling would call that value GiB. Some interfaces historically display binary-scaled quantities with a GB label, which makes the comparison less transparent.
This numerical difference is explained by unit convention alone and does not establish that a seller removed capacity. Compare the underlying byte count and read the product's definition of GB. A clear interface should state whether it uses powers of 1,000 or 1,024 rather than relying on the prefix text without explanation.
When comparing products, use their declared byte capacity and definitions rather than converting a rounded number copied from an operating-system screen. Two devices both marketed at 1 TB can expose different available space because of system partitions or product configuration even though their unit convention is the same. Conversely, a display of about 931 GiB is the binary-unit expression of one trillion bytes before separate reserved-space effects are considered.
Formatting and system use are separate issues
Unit conversion explains only how the same raw byte count is expressed. A formatted device can also reserve space for file-system structures, recovery partitions, firmware, system files, over-provisioning, snapshots, or other functions. Those uses can reduce the space available for personal files beyond the GB-versus-GiB numerical difference.
The amount varies by device, operating system, file system, configuration, and manufacturer. A generic converter cannot predict it. Check the device and software documentation, disk-management view, and allocation details when reconciling a specific product. Do not subtract an assumed universal overhead percentage.
File-system metadata is useful data, not necessarily unexplained loss. Directories, allocation maps, journals, checksums, and recovery structures help the system organize or protect files. Manufacturers and operating systems may report raw, formatted, usable, and free capacity at different stages. A fair comparison states which quantity is being shown. The converter can normalize units only after the underlying quantity has been identified.
Files, allocated space, and transfer rates
A file's logical byte size can differ from space allocated on disk because storage is assigned in blocks or clusters. Many small files may occupy more allocated space than their summed logical sizes, while compression, sparse files, deduplication, or snapshots can alter other reported figures. GB-to-GiB arithmetic does not model those storage mechanisms.
Transfer speed introduces time and bits. A network rate such as 1 Gb/s uses lowercase b and describes one billion bits per second under its stated convention. Estimating transfer duration also requires protocol overhead, device performance, network conditions, and often conversion between bits and bytes. The Data Storage Converter intentionally handles byte quantities, not live throughput or completion time.
Cloud storage plans and backup systems can add further definitions, including account quotas, version history, trash retention, compression, deduplication, or billing measurements. A plan labeled with GB may describe a decimal quota, but the service's documentation controls. Locally displayed file totals may not predict billed usage. Check whether metadata, previous versions, shared files, or transmitted bytes are included before treating a difference as a conversion error.
Using the Data Storage Converter
Enter the capacity and choose GB or GiB explicitly. The converter translates through bytes and also supports B, kB, MB, TB, KiB, MiB, and TiB. It does not inspect a drive, measure free space, account for formatting, calculate compression, or forecast download time.
For very large exact byte counts, software should use integer or arbitrary-precision arithmetic because ordinary floating-point numbers cannot represent every integer beyond a limit. For everyday display, keep sufficient internal precision and round the final number sensibly. The conversion can clarify unit conventions, while product support or system documentation should resolve device-specific discrepancies.
A transparent capacity comparison can show three columns: the declared unit value, the exact byte count, and the converted value with its explicit unit. For example, 128 GB, 128,000,000,000 bytes, and about 119.21 GiB identify one quantity without suggesting that GB equals GiB. Keeping bytes as the common reference also makes it easier to audit formulas or compare software reports that use different prefixes clearly and accurately.