MB vs KB Explained: Why Your File Size Doesn't Match
You compress a photo, one tool says 98KB, another says 102KB — same file, same settings. You didn't do anything wrong. This comes down to two competing ways of counting a kilobyte, and once you know which one a form actually means, the confusion goes away for good.
The Short Answer
There are two standards:
- Binary (1024): 1 MB = 1024 KB — this is what Windows, macOS, and your phone use to show file sizes.
- Decimal (1000): 1 MB = 1000 KB — this is what some web forms, storage manufacturers, and network speed measurements use.
A 2 MB photo is either 2048 KB (binary) or 2000 KB (decimal) — a difference small enough to matter when a form has a strict cutoff, but easy to account for once you know it exists.
Why This Actually Happens
The confusion traces back to how computers count versus how humans count. Computers work in powers of two — 1024 is 2¹⁰, a natural boundary in binary math. But "kilo" in the metric system has always meant exactly 1000. When early computing borrowed the metric prefix "kilo" for 1024, it created a naming collision that's persisted for decades.
Some systems later introduced "kibibyte" (KiB) to mean 1024 bytes specifically, keeping "kilobyte" (KB) for 1000 — but that distinction never really caught on in everyday use, which is why you still see KB used both ways.
A Worked Example
Say your phone shows a photo as "2.4 MB." Here's what that becomes under each standard:
| Standard | Calculation | Result |
|---|---|---|
| Binary (1024) | 2.4 × 1024 | 2,457.6 KB |
| Decimal (1000) | 2.4 × 1000 | 2,400 KB |
A ~58 KB gap on a single photo. Now scale that to a form with a strict "under 200 KB" limit — if you're compressing right up to the edge, this gap can be the difference between a successful upload and a rejected one.
How to Avoid the Problem Entirely
The safest approach isn't to figure out which standard a specific form uses — it's to not rely on the math at all. When you compress a file, check the actual resulting size shown by your compression tool before uploading, rather than calculating it yourself from the original MB number.
Our MB to KB Converter shows you the live, exact output size — the number you see is the number the form will see, regardless of which counting standard it uses internally.
Pro Tip: If a form gives you a hard limit (say, exactly 100 KB), it's worth compressing to slightly under that — 90-95 KB — to leave a small buffer for any rounding differences between systems.
KB to MB — The Reverse Direction
If you're going the other way — you have a KB number and want to know the MB equivalent — the same two standards apply:
- Binary: divide by 1024
- Decimal: divide by 1000
For most everyday purposes (checking if a file fits under a limit), the exact standard rarely matters — what matters is confirming the final number against the actual requirement, which is what a live compression preview does automatically.
Frequently Asked Questions
Why do two compressors show different KB numbers for the same file?
They're likely using different rounding or measurement conventions internally, or measuring at slightly different points in the compression pipeline. The difference is usually small (under 5%) and rarely affects whether a file meets a size limit.
Which standard should I trust for government forms?
Government and portal forms don't usually specify — treat the limit as approximate and compress to a few KB under the stated maximum as a safety margin, rather than exactly at it.
Is 1 MB always 1024 KB?
Not universally — it depends on the system. Operating systems (Windows, macOS, Android, iOS) almost always use 1024. Some web-based tools and hard drive manufacturers use 1000. Both are "correct" under their respective standard; there's no single universal rule.