What is a byte, and why does "MB" mean two things?
The Bytes to MB Converter takes a raw byte count and gives you megabytes — both of the numbers that word can mean. Type 1500000 and you get 1.5 MB, with 1.4305 MiB on the line underneath. The answer updates as you type. There's no Calculate button, no account, and nothing leaves your browser.
The byte
A byte is eight bits, and it's the unit your computer actually stores file sizes in. One plain-text character is one byte. A short email is a few thousand. A photo off a phone camera is a few million. When an API returns a file size, when a server log records an upload, when a directory listing prints a number — that number is bytes. Unlabelled, ungrouped, and usually long enough that you can't read it at a glance. Which is the whole reason anyone converts it.
The megabyte — both of them
Here's the mess. A megabyte is 1,000,000 bytes under the SI standard. That's what drive manufacturers print on the box, what macOS and iOS show you, and what every transfer-rate figure on a spec sheet assumes. But a megabyte is also 1,048,576 bytes — two to the twentieth power — because that's the number that falls out naturally when you address memory in binary. Windows Explorer uses that one and labels it "MB" anyway.
The IEC tried to end the argument in 1998 by giving the binary version its own name: the mebibyte, or MiB. Linux tooling adopted it. RAM specs adopted it. Standards documents adopted it. Consumer Windows never did. So both numbers are still in circulation, both still get called "MB", and they differ by 4.86%. On a text file that's noise. On a 4 TB drive it's the difference between the 4 TB on the box and the 3.64 TB your file manager reports.
How bytes to MB conversion works
MB = bytes ÷ 1,000,000 | MiB = bytes ÷ 1,048,576 — same byte count, two divisors, two correct answers.
Both are plain division, and the decimal one you can do in your head: move the decimal point six places left. 1,500,000 bytes becomes 1.5 MB. The binary one is harder to eyeball, but there's a shortcut — divide by 1,024 twice, or just take about 95% of the decimal answer.
Take a real file. You upload a 1,500,000-byte image and want to know if it clears a size limit. The Bytes to MB Converter reads it as 1.5 MB, and shows you the working: 1,500,000 bytes ÷ 1,000,000 = 1.5 MB. Underneath, it tells you that's 1,500 kB, and that if your computer counts a megabyte as 1,048,576 bytes — Windows does — it's 1.4305 MiB. Both numbers, one glance, no guessing which definition the limit was written against.
Now run the number that started the confusion. Paste 1,048,576 and the converter says 1.0486 MB and exactly 1 MiB. That single row is the entire problem in miniature: a file that is precisely one megabyte by Windows' reckoning is slightly over one megabyte by the standard's. If a form said "1 MB max" and meant the SI definition, that file just failed.
Common bytes to MB conversions
These are the byte counts that come up most, with both readings side by side. The Bytes to MB Converter shows the same pairing for whatever number you paste in.
| Bytes | MB (decimal) | MiB (binary) | What it usually is |
|---|---|---|---|
| 1,024 | 0.001024 | 0.000977 | 1 KiB — a small config file |
| 4,096 | 0.004096 | 0.003906 | One disk block on most systems |
| 100,000 | 0.1 | 0.095367 | A long email with no attachments |
| 512,000 | 0.512 | 0.488281 | A compressed logo or small PDF |
| 1,000,000 | 1 | 0.953674 | Exactly one decimal megabyte |
| 1,048,576 | 1.0486 | 1 | Exactly one mebibyte — what most upload limits mean |
| 1,500,000 | 1.5 | 1.4305 | A high-resolution JPEG |
| 5,242,880 | 5.2429 | 5 | A common 5 MiB attachment cap |
| 10,000,000 | 10 | 9.5367 | A short 1080p video clip |
| 26,214,400 | 26.2144 | 25 | A typical 25 MiB mail attachment ceiling |
| 104,857,600 | 104.8576 | 100 | A typical 100 MiB repository file limit |
| 1,000,000,000 | 1,000 | 953.6743 | One decimal gigabyte |
Read down the MiB column and you'll spot the tell: the round numbers are on the binary side. 5, 25, 100 — those are the limits humans actually wrote, because the code that enforces them says 1024 * 1024 * 25, not 25,000,000. The decimal column is where those same limits go ragged: 5.2429, 26.2144, 104.8576. When you see a size limit that looks oddly precise in MB, it almost always started life as a clean number in MiB.
The gap also widens as the units get bigger. It's about 2.4% at the kilobyte, 4.86% at the megabyte, 7.4% at the gigabyte, and just under 10% at the terabyte. That's why nobody argues about kilobytes and everybody argues about hard drives.
A unit conversion is arithmetic that fits on a napkin. It doesn't need an account, a per-seat licence, or a 14-day trial that quietly becomes a subscription. Plenty of file-size converters are one tab buried inside a "developer toolkit" that gates its basics behind a sign-up form and bundles AI features into a contract you can't opt out of. This is just the converter.
When the MB and MiB gap actually bites
Upload limits. A form says "max 1 MB" and your file is 1,048,576 bytes. Are you over? It depends entirely on which definition the server used, and it's usually the binary one, because upload caps get written in code as 1024 * 1024. When a file is close to a limit, convert the limit instead of trusting its label.
Drive capacity. You buy 500 GB and the machine reports 465. Nothing is missing. The manufacturer sold you 500,000,000,000 bytes, which is 500 GB decimal; Windows divides by 1,073,741,824 and prints 465.7, still calling it "GB". Same bytes, different divisor.
Cloud bills and quotas. Storage and egress are usually billed in decimal GB while your local tooling reports binary. A 7.4% discrepancy on a storage line item looks like a billing error until you check which unit each side is counting in.
Transfer times. This one isn't MB versus MiB at all — it's bytes versus bits, and it catches more people than either. A 100 Mbps connection moves 100 megabits per second, which is 12.5 megabytes per second at the theoretical best. That's why a "100 megabit" line takes about 80 seconds on a 1 GB download rather than 10. If you're working out how long a transfer will take, the bandwidth calculator handles the bits-to-bytes step for you.
Edge cases and gotchas
Small files look like zero. A 4,096-byte file is 0.004096 MB. Round that to two decimals and you get 0.00, which tells you nothing. Below 1 MB the Bytes to MB Converter shows up to six decimals, from 1 MB up it shows four, and past a million megabytes it switches to grouped whole numbers. It never falls back to scientific notation, so the number you copy is always the number you can paste into a spreadsheet.
It won't guess at other units. Type "5 MB" and the converter stops you: "This converter takes bytes. Type the raw byte count, like 1500000 or 1500000 B." That refusal is deliberate. Reading "5 MB" as five bytes would hand back 0.000005 MB — a wrong answer that looks perfectly reasonable. Same for bits: "100 Mb" gets the same message rather than a silently mangled result.
Commas mean different things in different places. "1,500,000" reads as one and a half million here. In much of Europe a comma is the decimal separator, so the converter flags grouped input rather than assuming. If you want a decimal, use a dot — type "1,5" and it tells you so: "Use a dot for decimals, like 1500.5."
Negatives and ceilings. Byte counts can't be negative, and the converter says so instead of returning a negative megabyte. The upper limit is 9,007,199,254,740,991 bytes, about 9 petabytes. That's not arbitrary — it's the largest whole number a browser can hold exactly, so past it your input would already have lost precision before any division happened. Better to be told than handed a number that looks right.
Paste what you've got. Grouped thousands, exponent notation and trailing units all parse: "1500000", "1,500,000", "1.5e6" and "1500000 bytes" all give 1.5 MB. You don't have to clean up a log line before pasting it.
Related converters
Bytes are base-two arithmetic wearing a base-ten costume, so the tools sitting next to the Bytes to MB Converter tend to be about bases. The decimal to binary converter shows the divide-by-two working, which is a quick way to see why 1,048,576 is a round number to a computer and an ugly one to you. The number base converter moves between base 2, 8, 10 and 16 in one step, and the decimal to hex converter is the one you want when you're reading memory offsets rather than file sizes.
If the byte count you're checking came from a download you're trying to validate, the file hash verifier is the better test — size matching is weak evidence that a file is intact, and a SHA-256 checksum is strong evidence. Like this one, it runs entirely in your browser; the file is never uploaded.
Frequently asked questions
How many bytes are in a MB?
Either 1,000,000 or 1,048,576, depending on who's counting. The SI and IEC standards say 1,000,000, and that's what drive makers, macOS, iOS and network figures use. The 1,048,576 figure is two to the twentieth power, properly called a mebibyte (MiB) — but Windows still labels it "MB". The Bytes to MB Converter divides by 1,000,000 for the headline number and shows the 1,048,576 result right below it, so you don't have to pick blind.
Is 1,048,576 bytes equal to 1 MB?
It's exactly 1 MiB, and the converter displays it as 1.0486 MB. So if a limit says "1 MB" and means the decimal definition, a 1,048,576-byte file is fractionally over. If the limit means the binary definition — and most upload caps do — it fits exactly. When a file is near a boundary, convert the boundary too.
Why does my 500 GB drive show up as 465 GB?
Because the two numbers count in different bases. You were sold 500,000,000,000 bytes, which is genuinely 500 GB by the decimal standard. Your operating system divides that same byte count by 1,073,741,824 and prints 465.7, still writing "GB" on the label. No storage is missing and nobody lied — the gap is about 7.4% at gigabyte scale and grows to nearly 10% at terabyte scale.
What's the difference between MB and MiB?
MB is decimal: 1,000,000 bytes. MiB is binary: 1,048,576 bytes, or 4.86% more. The IEC introduced the MiB, GiB and TiB names in 1998 to end exactly this confusion, and Linux tooling, RAM specifications and standards documents took them up. Consumer Windows didn't, which is why your download manager and your file properties panel can quote different sizes for one file and both be telling the truth.
Can I convert MB back to bytes here?
Not directly — this one takes bytes in, on purpose, so it never has to guess which megabyte you meant. Going the other way is easy by hand: multiply by 1,000,000 for decimal MB, or by 1,048,576 for MiB. So 8 MB is 8,000,000 bytes, and 8 MiB is 8,388,608 bytes.
Does it handle bits, like a 100 Mbps connection?
No, and it tells you rather than quietly converting the wrong thing. A bit is an eighth of a byte, so divide your bit count by 8 before pasting it in. 100 megabits is 12.5 megabytes.
Is what I type saved or sent anywhere?
No. The conversion runs in your browser — nothing reaches a server, nothing is stored, and closing the tab clears it. There's no sign-up and no cap on how often you use it. Microapp gives 10% of every dollar it earns to charity, off the top and audited quarterly, and none of that dollar comes from this converter.