Why a 1TB Drive Shows About 931GB in Windows

A drive sold as 1TB commonly appears as about 931GB in Windows because the label and the display use different size units. One trillion bytes equals 1,000 decimal gigabytes, or about 931.32 binary gibibytes.

That conversion does not consume any storage. However, it does not explain every capacity difference. A small partition, unallocated space, recovery partitions, and existing files can change the volume or free-space figure you are looking at.

Start by comparing the same bytes at the same storage layer.

The calculation behind 931

Drive manufacturers generally use decimal capacity:

• 1 GB = 1,000,000,000 bytes.
• 1 TB = 1,000,000,000,000 bytes.

A binary gibibyte, written GiB, is 1,073,741,824 bytes. Familiar Windows capacity displays can use that binary calculation while labeling the result “GB.”

For an illustrative drive containing exactly one trillion bytes:

Decimal GB = 1,000,000,000,000 / 1,000,000,000
           = 1,000 GB

Binary GiB = 1,000,000,000,000 / 1,073,741,824
           ≈ 931.32 GiB

Both results describe the same amount of storage. Subtracting 931 from 1,000 does not calculate bytes lost because the two numbers use different units.

An actual model may expose a byte count slightly different from the round number used here. Formatting, partition boundaries, and the display’s rounding also affect the final figure. “About 931” is an expectation, not an exact specification for every 1TB product.

Check whether you are looking at capacity or free space

In File Explorer, right-click the drive and open Properties. Compare the labels next to the numbers, including the byte values when shown.

Figure	What it describes
Whole-disk size	Capacity of the disk object presented to Windows
Partition size	A region assigned within that disk
Volume capacity	Capacity of a particular file-system volume
Free space	Space currently available within that volume

For example, a C: volume with about 300GB free is not a 300GB disk. The rest of that volume may be in use, and the same physical disk may also contain other partitions.

Likewise, a disk near 931GiB can contain a much smaller C: partition. Converting units again will not expand that partition.

Inspect the layout before changing anything

Open Disk Management from the Start button’s right-click menu. Find the correct disk and review its entire horizontal layout, including partitions without drive letters and any unallocated region.

Check the model and capacity where available. Do not assume Disk 0 is the drive you just installed, and do not use an old disk number after reconnecting hardware.

For a careful device match, see Which Drive Is Disk 0 in Windows?.

Use this first inspection to answer three questions:

1. Does the whole disk have approximately the expected capacity?
2. Is the volume you are examining only part of that disk?
3. Is the apparent difference used by other partitions, left unallocated, or simply reported as used space inside the volume?

Do not delete EFI, recovery, or other unfamiliar partitions to reclaim the apparent decimal-to-binary difference. They have a separate purpose, and deleting them does not change the unit conversion.

Compare the raw byte counts in PowerShell

For a more precise inventory, open Windows PowerShell as administrator and run this query. It uses the Windows Storage module, reads reported properties, and does not modify disk contents.

Get-Disk |
    Select-Object Number, FriendlyName, SerialNumber,
        @{Name='Bytes';Expression={$_.Size}},
        @{Name='DecimalGB';Expression={
            [math]::Round($_.Size / 1000000000, 2)
        }},
        @{Name='GiB';Expression={
            [math]::Round($_.Size / 1073741824, 2)
        }} |
    Format-List

The explicit divisors make the two units visible. In PowerShell, the literal 1GB means 1,073,741,824, so using it as the divisor calculates GiB despite the letters in the literal.

After confirming the current disk number, inspect its partitions. Replace 2 below with the intended disk’s number; 2 is only an example.

Get-Partition -DiskNumber 2 |
    Select-Object PartitionNumber, DriveLetter, Type,
        @{Name='OffsetBytes';Expression={$_.Offset}},
        @{Name='SizeBytes';Expression={$_.Size}} |
    Format-Table -AutoSize

An empty DriveLetter field does not mean a partition has no purpose. Also, these Storage-module queries are not a complete inventory of every dynamic-disk or hardware-RAID configuration.

When the difference needs more investigation

Finding	Interpretation and next step
Whole disk is near one trillion bytes	The roughly 931GiB result is consistent with unit conversion
Whole disk is expected size but the volume is smaller	Inspect partition layout and unallocated space
Volume capacity is expected but free space is low	Review files and Windows storage usage
Whole-disk byte count is far below the model’s specification	Verify the device identity, enclosure/controller limits, and product configuration

If cloning left a smaller partition on a larger disk, extending it may be a separate task. Whether that is possible depends on the layout, file system, and adjacent space. Back up first and assess those conditions rather than deleting partitions to force the issue.

If the entire device reports an unexpectedly small size, preserve the model details and layout and ask the vendor to explain the reported capacity. Avoid destructive capacity tests on a drive holding needed files.

A 1TB-to-931GB display difference is usually a units question. A disk-to-volume or capacity-to-free-space difference is a layout or usage question. Identifying which comparison you are making tells you whether anything actually needs to change.

References

• Microsoft: Get-Disk