Capacity reporting can change while the byte count stays fixed
A drive advertises 500 GB and an application displays a number closer to 465.66. That difference can be a naming convention rather than lost data. Decimal gigabytes and binary gibibytes count different numbers of bytes per unit. The comparison becomes useful when the byte count, formatting overhead and current free space are kept separate.
A nominal 500 GB quantity contains 500,000,000,000 bytes under decimal prefixes. Dividing by 1,073,741,824 gives about 465.661287308 GiB. That numerical difference does not mean the conversion deleted data. It expresses the same byte count using different-sized units.
Available storage can be smaller for other reasons: partitions, filesystem structures, recovery areas and reserved capacity. Those effects should not be folded into the decimal-to-binary conversion. Compare the reported total byte count first, then examine which space is reserved or used. A display labelled GB may need documentation if it actually uses a binary divisor.
For a transfer estimate, file size must be compared with a rate using compatible bits or bytes. Multiply bytes by eight before dividing by bits per second, or translate the rate to bytes per second. Compressed archive size, expanded file size and allocated filesystem space can all differ. Name which quantity is being converted before reporting the equivalent.
500 GB = 500,000,000,000 bytes ≈ 465.661287308 GiB.
Data Storage units, side by side
The values below all describe 500 GB. They provide a comparison of unit sizes for data storage; they are not separate measurements. Read the complete symbol and convention before copying a number.
- BBytes
- 500,000,000,000 B
- bitBits
- 4,000,000,000,000 bit
- kBKilobytes (1000)
- 500,000,000 kB
- MBMegabytes (1000²)
- 500,000 MB
- GBGigabytes (1000³)
- 500 GB
- TBTerabytes (1000⁴)
- 0.5 TB
- KiBKibibytes (1024)
- 488,281,250 KiB
- MiBMebibytes (1024²)
- 476,837.158203 MiB
- GiBGibibytes (1024³)
- 465.661287308 GiB
Keep the original gigabytes (1000³) record alongside the converted gibibytes (1024³) display. The unit list uses up to twelve significant digits for arithmetic readability, while the measurement precision still comes from its source.
Separate capacity convention from usable space
When comparing storage devices, document their byte count or exact prefix convention. Keep advertised capacity, formatted capacity and current free space as separate figures.
The following inputs stay in gigabytes (1000³) and the results use gibibytes (1024³). They illustrate different magnitudes for this measurement. Retain the specific conditions described above when replacing an example with your own value.
| Starting value | Equivalent value |
|---|---|
| 256 GB | 238.418579102 GiB |
| 500 GB | 465.661287308 GiB |
| 1,000 GB | 931.322574615 GiB |
This data storage unit pair has a constant factor ratio. Changing the input changes the output by the same proportion. If a copied figure differs by an unexpected factor, review the full unit symbol before changing the source measurement. Compare the actual byte count and the filesystem’s reserved space separately.
Compare exact byte counts or explicitly labelled GB/GiB values, then examine reserved and used space as separate quantities.
One byte count, two prefix systems
Storage capacity measures a quantity of data. Use this converter to compare bits, bytes, decimal prefixes and binary prefixes. A disk advertised in gigabytes and an operating-system display in gibibytes can describe the same byte count using different numerical labels; that difference is separate from space reserved for formatting or system files.
One byte is eight bits. Decimal GB means 10⁹ bytes; binary GiB means 2³⁰ bytes. The prefixes must remain explicit. A value in bytes need not equal the available space shown after formatting because metadata, reserved partitions and files consume storage. Unit conversion accounts for naming conventions, not the layout of a filesystem.
A GB is one billion bytes, while a GiB is 1,073,741,824 bytes. The same physical byte count therefore has a smaller numerical label in GiB. Filesystem metadata, reserved partitions and stored files can reduce usable or free capacity further. An ambiguous application label cannot be repaired by guessing; confirm whether it uses decimal or binary scaling.
Compare exact byte counts or explicitly labelled GB/GiB values, then examine reserved and used space as separate quantities.
500 GB in gibibytes (1024³)
500 GB = 465.661287308 GiB
Output = input × source factor ÷ destination factor500 × 1,000,000,000 ÷ 1,073,741,824 = 465.661287308 GiB. The two factors express the source and destination relative to the same internal reference unit. Their ratio is the multiplier.
Both unit factors refer to the same internal reference for data storage. Multiplying by the source factor and dividing by the destination factor changes the numerical scale while retaining the quantity. The source definition still matters: Choose the prefix explicitly; 1 GB is approximately 0.931323 GiB.
Reversing the unrounded 465.661287308 GiB result returns 500 GB. Use this as a direction check. A consistent reverse calculation cannot resolve calling gb and gib identical or improve the original observation.
What this data storage comparison can tell you
Useful capabilities
Compare exact byte counts or explicitly labelled GB/GiB values, then examine reserved and used space as separate quantities.
The listed units express the same supplied data storage quantity. The 500 GB → 465.661287308 GiB example makes the selected convention visible before it is used in a longer calculation.
Important limits
Decimal and binary prefixes are explicit. Eight bits make one byte; storage overhead is not included.
Choose the prefix explicitly; 1 GB is approximately 0.931323 GiB. Compare the actual byte count and the filesystem’s reserved space separately.
| Possible mismatch | What resolves it |
|---|---|
| Calling GB and GiB identical | Choose the prefix explicitly; 1 GB is approximately 0.931323 GiB. |
| Assuming the conversion accounts for formatting losses | Compare the actual byte count and the filesystem’s reserved space separately. |
The decimal-to-binary prefix relationship does not describe filesystem overhead or reserved partitions. Check the underlying byte count before concluding that capacity is missing. File length and allocated space can also differ. A converted display should say GB or GiB accurately and retain whether the source describes total, available, allocated or compressed data. Those quantities need separate comparisons.
As a controlled uncertainty example, suppose the original 500 GB record had a stated ±1% input interval. Its endpoints would be 495 GB and 505 GB. Converting those endpoints gives an output interval from 461.004674435 GiB to 470.317900181 GiB. The interval scales with the same fixed unit ratio as the central value. This chosen interval illustrates the arithmetic and is not an accuracy claim for your measurement.
Before using this data storage result
- Use uppercase B for bytes and lowercase bit labels for bits.
- Identify decimal GB versus binary GiB before comparing numbers.
- Distinguish total capacity from free space and usable formatted capacity.
Keep the original data storage value, its unit and the relevant conditions in the record. A copied answer of 465.661287308 GiB is interpretable only when those details remain available. State which of the measurement checks above you verified before using the value in another calculation.
Questions about data storage
Why does a 500 GB drive show about 465.66 GiB?
A gibibyte contains more bytes than a gigabyte. The same 500 billion bytes therefore has a smaller number when expressed in GiB. Formatting overhead can reduce the usable amount further.
Can a fractional byte result be meaningful?
The arithmetic can express fractional equivalent units, but an actual count of stored bytes is discrete. Round according to the task and do not interpret a fractional byte as an addressable storage location.