Buy a 1 TB drive and a computer may appear to show substantially less than 1 TB. A phone sold with 256 GB of storage also does not normally give you 256 GB of empty space for photos and apps on first use.

Neither observation necessarily means storage is missing. Several different things can make the number you see smaller: storage makers and software may count bytes with different units, a device needs space for its own software, and a formatted drive needs structures that keep track of files.

Understanding those differences makes storage specifications easier to compare and helps you tell normal capacity differences from an actual problem.

Start with the one thing both sides agree on: bytes

Digital storage ultimately holds bytes. The confusion begins when a large number of bytes is shortened into units such as gigabytes or terabytes.

For storage specifications, the decimal definitions are straightforward:

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

These prefixes use powers of 10, just as metric prefixes do in many other measurements.

Computing also has binary units based on powers of 2. The International Electrotechnical Commission introduced distinct names for them. A gibibyte (GiB) is 1,073,741,824 bytes, and a tebibyte (TiB) is 1,099,511,627,776 bytes.

A GB and a GiB therefore describe different quantities even though the names sound similar.

The same bytes can produce two different-looking numbers

Suppose a drive contains 1,000,000,000,000 bytes of raw capacity. Using decimal units, that is exactly 1 TB.

If software divides the same byte count by 1,099,511,627,776 instead, the result is about 0.91 TiB. Some software has historically displayed binary calculations while labeling the result with familiar decimal-looking terms such as GB or TB, which makes the difference especially confusing.

Nothing has disappeared in this conversion. It is similar to describing the same distance in kilometres and miles: the numerical value changes because the unit changes.

This also explains why the apparent gap becomes more noticeable at larger capacities. Decimal and binary units do not grow by the same factor at each step.

Why manufacturers commonly use decimal capacity

Storage products are commonly specified with decimal units. A 500 GB drive therefore represents roughly 500 billion bytes of capacity, while a 2 TB drive represents roughly 2 trillion bytes.

That convention is consistent with the standard meaning of SI prefixes such as giga and tera. Binary quantities have their own prefixes, including gibi and tebi.

The important point is not that one method is more truthful than the other. The problem arises when two interfaces use different unit conventions without making the distinction obvious.

When comparing a label with an operating system, compare the underlying byte count or check which unit convention the software uses before concluding that capacity is missing.

Formatting also uses some space

Unit conversion is only part of the story. Before a general-purpose drive can conveniently store folders and files, it is normally formatted with a file system.

A file system is the organizational structure that lets a device record information such as which storage areas belong to a file, where directories are located, and which space is free. Those bookkeeping structures themselves require capacity.

The amount depends on the file system, volume size, formatting choices, and implementation. It is therefore not useful to assume one universal percentage for “formatting overhead.”

Some storage can also be occupied by partitions or other structures that are not presented as ordinary user file space. A computer manufacturer, for example, may include a recovery partition used for repair or restoration tools.

A phone’s advertised storage is not the same as free storage

Phones, tablets, and many other devices add another distinction: total storage is not the same as storage available to you right now.

The operating system, built-in applications, update-related data, recovery components, and other system files need storage too. A new 256 GB phone can therefore have meaningfully less than 256 GB available for your own apps, photos, videos, and downloads.

The exact amount varies by device, operating-system version, preinstalled software, and configuration. System storage can also change over time as software is updated and temporary data is created or removed.

This is different from the GB-versus-GiB issue. Unit conversion changes how the same byte capacity is expressed; system files actually occupy part of the storage.

“Used,” “free,” and “available” can mean different things

Storage screens often show several numbers, and their labels are not perfectly consistent across operating systems.

Used space generally represents capacity currently assigned to files, applications, or system data. Free space usually refers to storage not currently allocated to files. Available space can be a more practical estimate of what applications can use, and some systems may count reclaimable caches or other automatically removable data differently.

For that reason, two storage tools on the same device can occasionally show slightly different totals without either one being broken. They may be measuring different categories or updating their calculations at different times.

If a difference is small, first check what each label actually represents.

Deleting a file does not always increase the number immediately

Another common surprise is deleting several large files and seeing little change in free space.

Many systems and applications use a trash, recycle bin, or recently deleted area. Moving a file there may remove it from its original folder without immediately releasing all of the storage it occupies. Space is reclaimed after the item is permanently removed, either manually or according to the platform’s retention behavior.

Cloud-synced files can add another layer. A file visible in a cloud folder may have a full local copy, a temporary cached copy, or only a small placeholder, depending on the service and settings. Its apparent file size therefore does not always tell you how much local storage it currently consumes.

The details vary by platform, so storage-management screens are generally more useful than guessing from folder names alone.

Reserved capacity is not automatically usable space

Some storage devices and systems reserve capacity for internal purposes. Solid-state storage, for example, may have physical flash capacity that is not exposed as ordinary user-addressable space. Controllers can use such spare capacity as part of flash management and reliability mechanisms.

That hidden physical capacity should not be confused with a visible partition that you can simply delete to gain more room. How a particular SSD, phone, or embedded device provisions its flash is an implementation choice.

Likewise, a recovery partition may be visible to disk-management software but still serve a useful system function. Removing unfamiliar partitions merely to increase the displayed free space can make recovery or other features stop working.

How to check whether a capacity difference is normal

When a storage number looks wrong, work from the broadest measurement toward the details.

First, check the product’s stated capacity and whether it is expressed in decimal GB or TB. Then inspect the device’s total reported capacity, not just its currently free space. If the software uses binary units, convert the advertised byte count using the corresponding binary unit before comparing the numbers.

Next, look at how much space is assigned to partitions, system data, applications, personal files, and any trash or recently deleted area. The names and categories vary between operating systems, but the distinction between total capacity and occupied capacity remains useful.

If an external drive is dramatically smaller than expected even after accounting for unit conventions, inspect its partition layout. A drive can contain unallocated space or a partition smaller than the physical device. Changing partitions can erase data, so back up important files before modifying a layout you do not understand.

For a phone or tablet, remember that system software consumes part of the advertised storage. A storage settings page can usually show broad categories, although the exact labels differ by platform and version.

Do not judge storage only by the number on the box

When choosing capacity, focus on how much usable headroom your workload needs rather than expecting every interface to repeat the advertised number exactly.

A drive’s decimal specification tells you its approximate byte capacity. The operating system may express those bytes using a different unit convention, formatting consumes some capacity, and a complete device may already contain system software before you add anything yourself.

Those are separate effects, and keeping them separate is the key mental model. If the reported total makes sense after unit conversion, but free space is lower, look for files, system data, partitions, or reserved areas. If the total capacity itself is unexpectedly low, then investigate the drive layout or hardware rather than assuming ordinary file use is responsible.