What KB, MB, and GB actually mean

Kilobyte (KB), megabyte (MB), and gigabyte (GB) are units used to describe how much digital data is involved—such as the size of a file, a web download, or storage capacity.

A key point is that the same letters can be used with two different base calculations:

  • Decimal (powers of 10) is commonly used for storage marketing and many industry contexts: 1 KB = 10^3 bytes, 1 MB = 10^6 bytes, 1 GB = 10^9 bytes.
  • Binary (powers of 2) is common in computing internals and some device readouts: 1 KiB = 2^10 bytes, 1 MiB = 2^20 bytes, 1 GiB = 2^30 bytes.

When people say “KB/MB/GB” they often mean the decimal interpretation, but some systems display binary values while still labeling them KB/MB/GB, which creates a mismatch.

How the scaling works (and why numbers don’t always match)

At a byte level, the relationships are straightforward:

  • 1 kilobyte scales a thousand bytes (decimal) or 1,024 bytes (binary).
  • 1 megabyte scales a million bytes (decimal) or 1,048,576 bytes (binary).
  • 1 gigabyte scales a billion bytes (decimal) or 1,073,741,824 bytes (binary).

So if you compare a file size shown in one system to a storage or network capacity shown in another, you may see “missing space” or “slightly off” download sizes. This isn’t necessarily an error; it’s often a unit interpretation difference.

These units measure bytes (groups of 8 bits). File sizes are usually reported in bytes-based units (KB/MB/GB). Network speeds are often shown in bits per second (bps), which is a different unit type even though both use prefixes like “K” or “G”. As a result, speed and size comparisons can be confusing unless you convert consistently.

Differences and limits you should watch for

1) Decimal vs binary labeling

The most common practical limitation is labeling ambiguity. A device might show “MB” but behave like “MiB”. The solution is to look for explicit guidance:

  • If you see KiB/MiB/GiB, you’re dealing with binary units.
  • If you only see KB/MB/GB, you must assume decimal unless the device documentation states otherwise.

Because you may not always get documentation, it’s reasonable to treat any “KB/MB/GB” display as an information cue and verify by comparing against a known file size or stated conversion basis.

2) Not all storage “size” is usable

Even when units match, usable storage can be less than the marketed capacity due to formatting, system files, and file system overhead. This is separate from KB/MB/GB conversion, but it often shows up at the same time, making the cause harder to isolate.

3) Compression and formats change what you see

A file’s size is not the same as its content “weight” after processing. For example, a compressed file can be much smaller than the data it represents. That means you can’t infer how much “stuff” is inside—only how many bytes the stored representation occupies.

Practical checks you can do

Check A: Read the unit name carefully

When possible, look for KiB/MiB/GiB (binary) versus KB/MB/GB (often decimal). If the display doesn’t specify, note that the same label can still represent binary math.

Check B: Use a known conversion sanity check

Pick a simple reference:

  • If a system displays “1 MB” and you know the file is “about a million bytes” (decimal), the numbers should line up with decimal scaling.
  • If the displayed MB values are consistently closer to 1,048,576 bytes per MB, that suggests binary behavior.

Even without perfect certainty, consistency over a few examples helps you infer what your system is doing.

Check C: Keep the same basis when comparing

When comparing:

  • file size vs free space
  • network transfer size vs expected download size try to ensure they’re reported on the same basis (or at least understand which one likely uses decimal and which uses binary). Mixing them can create the illusion that something is wrong.

Bottom line

KB, MB, and GB are data size units. The main “gotcha” is decimal versus binary interpretation, which shifts the numeric values even when the labels look identical. With careful reading of the unit naming (KB/MB/GB vs KiB/MiB/GiB) and consistent comparisons, you can place sizes correctly and avoid most confusion.