What Is a Kibibyte? (And Why Kilobyte Doesn’t Always Mean 1,024 Bytes)

A kibibyte (KiB) is a unit of digital storage equal to 1,024 bytes, or 2^10. It’s part of a set of binary prefixes such as kibi, mebi, gibi, tebi, pebi created by the International Electrotechnical Commission (IEC) in 1998 to replace the ambiguous use of “kilobyte,” “megabyte,” and “gigabyte” for both 1,000-based and 1,024-based counts.

Kibibyte is a computing and digital storage unit of measurement. It follows the IEC binary-prefix standard and isn’t used outside of data and memory contexts.

Kibibyte vs. Kilobyte: What’s the Difference?

A kilobyte (KB) means two different things depending on who’s using it. As defined by the International System of Units, “kilo” means 1,000 (10^3), and that’s the definition most storage manufacturers use: 

• 1 kilobyte = 1,000 bytes
• 1 megabyte = 1,000 kilobytes, and so on.

RAM vendors and most operating systems instead use base 2, where 1 kilobyte = 1,024 bytes.

That means the same word, “kilobyte,” can refer to two different byte counts depending on context. If you’re talking about raw hard drive capacity, a gigabyte is 1,000,000,000 bytes. If you’re talking about the file system on top of that drive, a gigabyte usually means 1,073,741,824 bytes.

“Kibibyte” removes the ambiguity. It always means 1,024 bytes. The same binary-prefix pattern applies one level up at each step:

• Mebibyte (MiB) is the unambiguous binary-prefix term for 2^20 bytes, used in place of “megabyte” when the base needs to be exact
• Gibibyte (GiB) for 2^30 bytes, instead of “gigabyte”
• Tebibyte (TiB) for 2^40 bytes, instead of “terabyte”
• Pebibyte (PiB) for 2^50 bytes, instead of “petabyte”

(Larger prefixes exist too, but if you’re routinely working in exbibytes (EiB), you already know where to find them.)

Kibibyte, Mebibyte, Gibibyte, Tebibyte: Decimal vs. Binary

The table below compares decimal and binary storage units from kilobytes and kibibytes to terabytes and tebibytes, including the exact number of bytes in each unit.

At the kilobyte level, the difference between 1,000 and 1,024 bytes is trivial. At the terabyte level, it’s roughly 100 gigabytes — enough to notice, and enough to cause real confusion if you’re reading a monitoring dashboard or a drive spec sheet without knowing which convention is in use.

Why This Distinction Actually Matters

Our founder Steve is known for being both frugal and precise, and he’s fond of walking into the engineering area and asking a simple-sounding question: “Kilobytes, or kibibytes?” It tends to catch even senior engineers off guard, because most people use “kilobyte” as a stand-in for both meanings without thinking about which one applies.

The stakes are higher than they sound. If your OS, your monitoring tool, and your vendor’s spec sheet aren’t using the same base, the numbers won’t line up — and that mismatch is where storage-capacity confusion and “missing space” support tickets usually come from.

Worked Example: A 2 TB Drive That Reports as 1.82 TiB

Take a drive advertised as having 2 terabytes (2 × 10^12 bytes) of capacity. Formatted as a VMFS volume in a VMware lab, that drive reports 2,000,112,582,656 bytes of usable capacity — slightly more than 2 TB, which is a rounding artifact of how the drive was partitioned, not a bonus.

Here’s how that byte count reads depending on which unit you use:

• As terabytes (base 10): 2,000,112,582,656 ÷ 1,000 ÷ 1,000 ÷ 1,000 ÷ 1,000 = 2.00 TB
• As tebibytes (base 2): 2,000,112,582,656 ÷ 1,024 ÷ 1,024 ÷ 1,024 ÷ 1,024 = 1.82 TiB

There’s no missing capacity here. 2.00 TB and 1.82 TiB describe the exact same 2,000,112,582,656 bytes — the number just looks smaller once you divide by 1,024 four times instead of 1,000. Most operating systems show the smaller, 1.82 number, but still label it “TB.”

How Operating Systems Report File and Drive Sizes

Unless you’re on a Mac, your OS and file manager most likely report capacity and file size in tebibytes and gibibytes (labeled as TB and GB anyway). The df command on Linux would show a 2 TB drive as roughly 1.8 TB. Windows Explorer would show 1.82 TB. Windows follows the JEDEC standard, which defines a kilobyte as 1,024 bytes, so the value matches tebibytes even though the label says terabytes.

macOS is the exception. Since OS X 10.6 (Snow Leopard), Apple has reported file and drive sizes in base 10, which matches how storage manufacturers label capacity. So on a Mac, that same 2 TB drive shows up as 2.00 TB, not 1.82 TB.

How LogicMonitor Displays Storage Values in Graphs

By default, LogicMonitor scales graphed values using base-10 kilobytes. Graph 2,000,112,582,656 bytes without changing anything, and the mouseover tooltip reads 2.00T — which won’t match what your OS reports for the same volume.

To make LogicMonitor match your OS, every graph definition includes a Scale by units of 1024 option. Check that box, make sure your values are converted to bytes, and LogicMonitor handles the rest. It is displaying 1.82T instead of 2.00T for that same drive.

LogicMonitor defaults to base 10 because most of what gets monitored isn’t storage. Network throughput in bits per second, HTTP requests per second, latency, SQS queue depth, and cache object counts all scale in base 10 by convention. File systems and memory are the exception, not the rule — so the “scale by 1024” checkbox is really something you reach for specifically when graphing storage or RAM, not as a general setting.

FAQs