Article — KB to MB Converter
KB to MB: the binary and decimal versions of the megabyte
In binary mode, 1 megabyte equals 1024 kilobytes. In decimal mode, 1 megabyte equals 1000 kilobytes. The default in Windows and most operating systems is binary, so a 5120 KB file shows up as 5 MB. The same file on a hard-drive label or on macOS counts as 5.12 MB, since storage marketing uses the decimal base. Pick the right base for the context and divide.
The converter at the top of this page exposes the toggle explicitly, so a Windows user can confirm the value Explorer is already showing and a hard-drive shopper can match the box label. The article covers where the two bases come from, why the gap exists, and where it actually shows up in everyday computing.
What is a kilobyte?
A kilobyte is a unit of digital information, abbreviated KB. The byte itself is 8 bits. A short plain-text email is 5 to 25 KB, an HTML page 50 to 200 KB, and a PDF report 500 to 2000 KB. Above a few thousand KB, the megabyte becomes the more convenient unit.
The complication is that "kilo" has two operational definitions in computing. In SI, kilo means exactly 1000. In the binary system that emerged with early computers, kilo became shorthand for 2 to the tenth power, which is 1024. The 24-unit gap stays small at the kilobyte but grows with every step up the prefix ladder.
The dual usage of kilo in computing dates to the early 1960s, when memory addressing was naturally binary. IBM engineers writing about a "65K word" memory meant exactly 65,536 words, which is 2 to the sixteenth power, not 65,000. The convention spread, and by the time storage vendors started selling drives by capacity, the same prefix was being used to mean two different things in the same product spec sheet.
The KB to MB formula
To convert kilobytes to megabytes, divide by the base. The base is 1024 in binary mode or 1000 in decimal mode. That is the whole calculation; the difficulty lies in picking the right base for the context.
Binary: KB ÷ 1024 = MBDecimal: KB ÷ 1000 = MBMB × 1024 = KB (binary)MB × 1000 = KB (decimal)For reverse conversions, multiply megabytes by the base. 5 MB in binary equals 5120 KB; in decimal it equals 5000 KB. The 120 KB difference looks trivial at this scale but it scales with the value. At the terabyte level the gap grows to a tenth of the marketed capacity, which is why a 1 TB drive shows up in Windows as roughly 931 GB.
Binary vs decimal: 1024 or 1000
Two answers exist for the question "how many KB are in a megabyte," and both are correct in their own context. Binary uses 1024 because computer memory is organised in powers of two, and 2 to the tenth is the closest power of two to 1000. Decimal uses 1000 because the International System of Units defines kilo as exactly 1000, and storage capacity follows the SI rule.
- Windows — binary (1024), labels the result KB and MB
- macOS since 10.6 (2009) — decimal (1000), labels match the hard-drive box
- Linux — binary by default with
df -h, decimal withdf -H - RAM specs — always binary, since memory chips are addressed in powers of two
- HDD and SSD labels — always decimal, since that is the SI standard
- Network speeds — decimal, and quoted in bits per second, not bytes
The 24-byte gap at the kilobyte level is 2.4 percent. By the megabyte level it has grown to 4.86 percent (since the binary megabyte is 1024 times 1024 bytes, or 1,048,576). At the gigabyte level the gap reaches 7.4 percent, and at the terabyte level 10 percent. These percentages are the source of the apparent "missing" storage when a drive is plugged into a Windows machine.
KB to MB conversion table
The most-searched KB values, converted across both bases:
- 100 KB = 0.0977 MB (binary) / 0.1000 MB (decimal)
- 500 KB = 0.4883 MB (binary) / 0.5000 MB (decimal)
- 1000 KB = 0.9766 MB (binary) / 1.0000 MB (decimal)
- 1024 KB = 1.0000 MB (binary) / 1.0240 MB (decimal)
- 5000 KB = 4.8828 MB (binary) / 5.0000 MB (decimal)
- 10,000 KB = 9.7656 MB (binary) / 10.0000 MB (decimal)
- 100,000 KB = 97.6563 MB (binary) / 100.0000 MB (decimal)
- 1,000,000 KB = 976.5625 MB (binary) / 1000.0000 MB (decimal)
The decimal answers look cleaner because they line up with the way humans write thousands. The binary answers stay small enough at the megabyte level that most people treat them as decimal anyway. The conversion only feels weird at the gigabyte and terabyte scale, where 7 to 10 percent of the marketed capacity goes "missing" in the file manager.
Why hard drives look smaller in Windows
A 1 TB drive shows up in Windows as 931 "GB". The drive is not defective. The manufacturer counts in decimal terabytes (1 TB = 10^12 bytes), and Windows reformats that count into binary gigabytes (1 GiB = 2^30 bytes, or 1,073,741,824). Same byte count, different bases.
The gap grew large enough by the mid-2000s that consumer lawsuits landed. A 2006 class action against Western Digital settled with cash payments and free backup software for buyers who felt the "80 GB" label was misleading when Windows reported 74.5 GB. Similar suits hit Seagate in 2007 and Apple in 2014. Modern packaging now usually includes a footnote noting that 1 GB equals 1,000,000,000 bytes for marketing.
At 1 TB the gap is 9.95 percent. At 4 TB the gap of 9.95 percent is about 398 GB — missing from Windows' file-manager view. At 16 TB the gap reaches 1.59 TB. The bytes are still on the disk; Windows just translates them through a different base when it labels them in GB or TB.
KiB and MiB: the IEC standard nobody uses
The IEC introduced a fix in 1998. IEC 60027-2, later folded into IEC 80000-13, defined a new set of prefixes for binary multiples: kibibyte (KiB) for 1024 bytes, mebibyte (MiB) for 1024 KiB, gibibyte (GiB) for 1024 MiB, tebibyte (TiB) for 1024 GiB. SI prefixes keep meaning thousand, million, billion; the new IEC prefixes carry the binary meaning.
Twenty-five years later, adoption outside Linux is marginal. Ubuntu started using IEC prefixes in 10.10 (2010); GNU coreutils df shows them with -h since version 8.21. Windows, macOS, iOS, and Android still use "KB", "MB", and "GB" with the binary meaning. IEEE 1541-2002 endorses the IEC prefixes too, but consumer software has not followed.
When precision matters — engineering documentation, cloud-storage billing, networking standards — use the IEC prefixes. Write 1 MiB when you mean 1,048,576 bytes, and 1 MB when you mean 1,000,000 bytes. In a consumer or marketing context, just use MB and label the base you used. Most readers will read MB as binary on a Windows machine and decimal on a hard-drive box without thinking about it.
KB, Kb, kb: bits versus bytes
Three letter combinations look similar and mean different things. KB (capital K and B) is kilobytes, used for file size. Kb or kbit is kilobits, used for data-transfer rates. kB with a lowercase k is the technically correct SI spelling, although KB dominates in IT.
The bit-versus-byte confusion is the most expensive of the three. ISPs advertise speeds in megabits per second (Mbps), not megabytes. A 100 Mbps line delivers 100 million bits per second, which is 12.5 MB/s. Buyers expecting 100 MB/s from a 100 Mbps connection see throughput at one-eighth of their expectation. The factor-of-eight gap dwarfs the 1024-vs-1000 issue.
Common KB to MB mistakes
- Treating Windows MB as decimal — the file Explorer shows binary megabytes labelled MB. A 5 MB file in Windows is 5 MiB, or 5,242,880 bytes.
- Comparing macOS file size to Windows file size — the underlying bytes are identical, the labels differ. Mac 5.24 MB equals Windows 5 MB.
- Reading network speed as bytes per second — 100 Mbps is 12.5 MB/s, not 100 MB/s. Divide by 8 for byte throughput.
- Buying a hard drive and expecting Windows numbers — a "1 TB" drive shows 931 GB in Windows. The bytes are there.
- Using 1024 in pharmaceutical or scientific work without labelling — for any rigorous documentation, write KiB or MiB when 1024 is meant.
- Confusing KB with Kb in transfer specs — a "1 KB" file is 8 times the bit count of a "1 Kb" data segment. Lowercase b for bits, uppercase B for bytes.