Data Rate Converter & Usage Calculator
Convert a data rate between Mbit/s, MB/s, MiB/s, Gbit/s and more, and see how much data it moves per second, hour, day, month or over any duration.
The same speed in bits and bytes, decimal and binary, plus the gigabytes a stream or link at that rate consumes per hour, per day and over your own time span.
Example: 100 Mbit/s is 12.5 MB/s or 11.92 MiB/s and moves 45 GB per hour, 1.08 TB per day; a 5 Mbit/s stream watched for 2 hours uses 4.5 GB.
Bits per second,
bytes per hour.
Why the speed on the bill and the speed in the download window differ by eight, and how the usage totals are computed.
Bits versus bytes
Network links are sold in bits per second with decimal prefixes — 100 Mbit/s is 100,000,000 bits each second. File transfers are shown in bytes, and a byte is eight bits, so the same link is 12.5 MB/s. Some download windows count in binary megabytes (MiB/s = 1,048,576 bytes), which reads a little lower again: 11.92 MiB/s. The converter turns your rate into bits per second with the exact factor and divides back out for every unit.
Usage over time
Usage is rate × time: 100 Mbit/s for an hour is 12.5 MB × 3,600 = 45 GB. The table gives the total per second, minute, hour, day and 30-day month, and the duration field gives it for any span you type — for a stream, use the stream's bitrate (5 Mbit/s for two hours is 4.5 GB). These are constant-rate figures: real streams vary their bitrate and every protocol adds headers, so the totals are an upper bound for a link actually running flat out at that rate. The Download Time page does the inverse — file size and rate to time.
What is not measured
This page does not test your connection or look anything up; it converts the number you enter. Nothing leaves the browser; the same four anonymous usage counts as the rest of the site apply.
SOURCES
- IEC 80000-13:2008 — prefixes for binary multiples; bit and byte as units of information
- NIST SP 811 — SI prefixes and the byte; prefixes for binary multiples
Last reviewed 19 September 2026. How results are checked: How we verify.