Bytes per second to Mbps

Where raw byte rates turn up

Plain bytes per second rarely appear in consumer apps, but they are everywhere in technical work: web server logs record bytes sent, monitoring tools graph interface counters in bytes, and programming APIs report transfer progress as byte counts. Converting to Mbps lets you compare those numbers with the link or plan you are paying for.

• A log total over an hour. A server that sent 5,400,000,000 bytes in one hour averaged 5,400,000,000 ÷ 3,600 = 1,500,000 B/s. Times 8 is 12,000,000 bit/s, or 12 Mbps. For monthly totals, the bandwidth calculator works from visitors and page size instead.
• A progress callback. If your code reports 45,000,000 bytes transferred in the last second, that is 360 Mbps: likely the limit of the remote server, not a gigabit connection.
• A counter delta. An interface counter that rose by 62,500,000 bytes in one second means the port carried 500 Mbps in that second.

Pitfall: counters that are really in KiB or MiB

Some tools label figures as bytes but group them in 1,024s before display, and some rate-limit settings count kilobytes as 1,024 bytes. If you feed a binary figure into a decimal formula, the result is off by about 2.4% at the kilo scale and about 4.9% at the mega scale. When a tool's documentation says KiB or MiB, pick those units in the converter above instead of B/s. For bit-based figures that need no ×8 step at all, see kbps to Mbps.

Also check the time window. Many logs store totals, not rates. Divide the byte total by the number of seconds it covers before you convert, or the answer will be a volume dressed up as a speed. To go the other way, from a Mbps target to a byte figure for a throttle setting, use Mbps to bytes per second. The Mbps vs MB/s guide explains why the factor of 8 keeps catching people out.