Bandwidth Calculator
Moving 10 GB in 15 minutes takes a steady 88.8889 Mbps, while 1 TB spread over a 30-day month averages only 3.0864 Mbps. A bandwidth calculator estimates the transfer rate needed to move a file or dataset within a set time window. Enter a data amount such as MB, GB, or GiB, enter a duration in seconds, minutes, hours, or days, and the tool converts both inputs into a required bandwidth figure. This bandwidth calculator is useful when you are sizing an internet connection, planning backups, checking upload windows, comparing cloud sync jobs, or testing whether a maintenance window is long enough for a large transfer. It reports the answer in bits per second and also shows Kbps, Mbps, Gbps, and MB/s so you can compare the result with ISP plans, switch uplinks, NAS throughput, or software copy targets. It also supports both decimal units like GB and binary units like GiB, which matters when storage labels and operating system reports describe the same payload in different ways.
Quick answer
The calculator converts the selected data unit into bytes, then multiplies by 8 to get total bits.
What this tells you
- •The calculator converts the selected data unit into bytes, then multiplies by 8 to get total bits.
- •It converts the selected time unit into seconds so minutes, hours, and days all use the same base.
- •The main result is the average required rate, not a guaranteed real-world speed under load.
- •Decimal units like GB and binary units like GiB can produce different answers for the same displayed number.
- •Secondary outputs help you compare the result with network plans quoted in Mbps and software speeds quoted in MB/s.
How to Use
- 11. Enter the total amount of data you need to move. Use the full payload size, not a rough guess, if you are planning a backup window or a scheduled file push.
- 22. Choose the matching data unit. Pick GB or TB for decimal storage labels and GiB or TiB if the source system reports binary units.
- 33. Enter the time available for the transfer, then choose seconds, minutes, hours, or days so the tool can convert the duration to seconds.
- 44. Calculate the result and read the primary Mbps output first. Then use the secondary results if your provider, hardware, or software reports speed in another unit.
- 55. Add practical headroom before making a network decision. If the tool says you need 88.8889 Mbps, a nominal 100 Mbps link may still feel tight once overhead and shared traffic are included.
How It Works
Formula
Bandwidth (bps) = (Data size in bytes x 8) / Time in secondsThe formula has two conversion steps before the final division. First, the tool converts the selected data unit into bytes. For example, 10 GB becomes 10,000,000,000 bytes, while 10 GiB becomes 10,737,418,240 bytes. It then multiplies bytes by 8 to get total bits because bandwidth is usually quoted in bits per second. Next, the tool converts the selected time unit into seconds. Minutes are multiplied by 60, hours by 3,600, and days by 86,400. After that, total bits are divided by total seconds to get the average required rate in bps. The secondary outputs scale the same answer into Kbps, Mbps, Gbps, and MB/s for easier comparison.
Calculation note: values are processed in the order shown above, using the current input units.
Worked Examples
Transfer 10 GB in 15 minutes
10 GB equals 10,000,000,000 bytes. Multiply by 8 to get 80,000,000,000 bits, then divide by 900 seconds. The result is 88,888,888.89 bps, which the tool displays as 88.8889 Mbps. This is a good planning check for a short upload window or a media handoff.
Transfer 500 GB in 8 hours
500 GB equals 500,000,000,000 bytes and 4,000,000,000,000 bits. Eight hours equals 28,800 seconds. Dividing 4,000,000,000,000 by 28,800 gives 138,888,888.89 bps, or 138.8889 Mbps. This is the average sustained rate needed to finish a large daytime migration in one work shift.
Transfer 500 GiB in 8 hours
500 GiB equals 500 x 1,073,741,824 bytes, which is 536,870,912,000 bytes. Multiply by 8 to get 4,294,967,296,000 bits, then divide by 28,800 seconds. The result is 149,130,808.89 bps, or 149.1308 Mbps. This example shows why GiB needs more bandwidth than GB for the same numeric value.
Transfer 25 MB in 30 seconds
25 MB equals 25,000,000 bytes, which becomes 200,000,000 bits after multiplying by 8. Dividing by 30 seconds gives 6,666,666.67 bps. The tool rounds that to 6.6667 Mbps. This is the kind of estimate you can use for small file uploads, camera exports, or quick sync checks.
Transfer 1 TiB in 1 day
1 TiB equals 1,099,511,627,776 bytes. Multiply by 8 to get 8,796,093,022,208 bits, then divide by 86,400 seconds in one day. The result is 101,806,632.20 bps, which the tool shows as 101.8066 Mbps. That makes this example useful for checking whether an overnight or full-day replication job fits within a fixed window.
Scenario: Priya turns her recipe blog's traffic into Mbps
Priya's blog served 75,000 page views last month, and the browser's network panel with the cache disabled shows a recipe page pulling 2.4 MB. Counting every view as a first visit, 75,000 x 2.4 MB is 180,000 MB, or 180 GB, an upper bound because returning visitors reload fewer files. Run 1 spreads that over 30 days and needs only 0.5556 Mbps on average. Her server log shows the busiest hour, the evening a stew recipe got shared, carried 1,500 page views, which is 3.6 GB. Run 2 puts that through 1 hour and gets 8 Mbps, 14.4 times the monthly average. A plan metered by monthly transfer only counts the 180 GB. A port capped below 8 Mbps would have slowed pages that evening. Under 95th percentile billing, one busy hour falls inside the 36 hours of samples a month that get dropped, so it only raises the bill if busy periods add up to more than that.
Average bandwidth needed by data size and time window
Each cell is the primary result this bandwidth calculator prints, in Mbps rounded to four decimal places, for the data in the row moved within the time in the column. Sizes are decimal (1 GB = 1,000,000,000 bytes) except the 1 TiB row, and the 30-day column is entered as 30 with the time unit set to days.
| Data to move | 15 minutes | 1 hour | 8 hours | 1 day | 30 days |
|---|---|---|---|---|---|
| 1 GB | 8.8889 Mbps | 2.2222 Mbps | 0.2778 Mbps | 0.0926 Mbps | 0.0031 Mbps |
| 10 GB | 88.8889 Mbps | 22.2222 Mbps | 2.7778 Mbps | 0.9259 Mbps | 0.0309 Mbps |
| 50 GB | 444.4444 Mbps | 111.1111 Mbps | 13.8889 Mbps | 4.6296 Mbps | 0.1543 Mbps |
| 100 GB | 888.8889 Mbps | 222.2222 Mbps | 27.7778 Mbps | 9.2593 Mbps | 0.3086 Mbps |
| 500 GB | 4444.4444 Mbps | 1111.1111 Mbps | 138.8889 Mbps | 46.2963 Mbps | 1.5432 Mbps |
| 1 TB | 8888.8889 Mbps | 2222.2222 Mbps | 277.7778 Mbps | 92.5926 Mbps | 3.0864 Mbps |
| 1 TiB | 9773.4367 Mbps | 2443.3592 Mbps | 305.4199 Mbps | 101.8066 Mbps | 3.3936 Mbps |
| 5 TB | 44444.4444 Mbps | 11111.1111 Mbps | 1388.8889 Mbps | 462.963 Mbps | 15.4321 Mbps |
| 10 TB | 88888.8889 Mbps | 22222.2222 Mbps | 2777.7778 Mbps | 925.9259 Mbps | 30.8642 Mbps |
Computed with this tool's formula, bits per second = bytes x 8 / seconds, then divided by 1,000,000 and rounded to four decimals the way the result card shows it, so trailing zeros drop (462.963, not 462.9630) and large values print without thousands separators. The 30-day column is the average rate a monthly transfer allowance implies. Small monthly volumes lose detail at four decimals, so for 1 GB over 30 days read the Kilobits per second line instead, which shows 3.09. The 1 TiB row runs 9.95 percent above the 1 TB row because 1 TiB is 1,099,511,627,776 bytes. Every cell is file data only, before the packet overhead covered in the section below.
Average rate, peak rate, and what a hosting plan meters
The number this calculator returns is an average over the whole window. Spread 1 TB across a 30-day month and it comes to 3.0864 Mbps, a rate almost any connection can carry. That is why a hosting plan's monthly transfer allowance, counted in GB or TB, and a port or plan speed, counted in Mbps, are hard to compare at a glance. The allowance counts bytes whenever they move. The speed caps how fast they can move in any one second, and visitors do not arrive at an even rate. Run the tool twice, once with the month's volume over 30 days and once with the busiest hour's volume over 1 hour, and the ratio between the two answers shows how far your peak sits above your average.
Some providers meter the rate instead of the volume. Under 95th percentile billing, also called the 95/5 method, the provider samples port usage every 5 minutes, sorts the month's samples, drops the top 5 percent, and bills on the highest sample left. Link11's billing documentation works through a 30-day month of 8,640 samples in which the 432 busiest are ignored, and Advanced Hosting's documentation describes the same cut. Those 432 samples add up to 36 hours, so short bursts cost nothing, but busy periods that total more than about 36 hours in a month set the bill. No standard defines the method, and providers differ on details such as how inbound and outbound traffic are counted, so the contract wording decides. This calculator cannot predict a 95th percentile figure, because that depends on the shape of the traffic, not its total.
For a website, monthly transfer is roughly page views times the bytes each view pulls from the server, and HTTP caching decides how many of those bytes travel at all. RFC 9111 lets a browser or CDN that holds a fresh stored response reuse it without contacting the origin server, and the Cache-Control max-age directive sets how many seconds a response stays fresh. Once a copy goes stale, the cache can ask again with a conditional request, and a 304 Not Modified reply (RFC 9110, section 15.4.5) carries headers but no content. Long max-age values on images, scripts, and stylesheets can mean a returning visitor downloads little beyond the HTML. Measure page weight the way a first-time visitor sees it, for example in Chrome DevTools with Disable cache checked, and treat that figure as the most a single view can cost.
Compression shrinks the bytes that do travel. RFC 9110 defines content codings: the browser lists the ones it accepts in the Accept-Encoding header, and the server names the one it applied in Content-Encoding. The RFC defines three of them, gzip, deflate, and compress, and Brotli joined the IANA content coding registry as br through RFC 7932. Text such as HTML, CSS, JavaScript, and JSON usually compresses well. JPEG, PNG, WebP, and video are compressed formats already, so a second pass saves little. Enter the compressed size as it crosses the network, since that is what the link carries and what a metered plan counts.
The answer is file data only. Every packet also carries IP and TCP headers and Ethernet framing, which take about 5 to 6 percent of a clean wired link, as the download time calculator works out byte by byte. Divide the result by about 0.94 before comparing it with a link speed, then leave room for whatever else shares the line. The 10 GB in 15 minutes example needs 88.8889 Mbps of file data, or about 94 Mbps on the wire, which leaves a nominal 100 Mbps link about 6 Mbps for anything else.
Common mistakes
- Choosing GB when the source system actually reports GiB, or choosing TB when the source is really TiB
- Reading Mbps and MB/s as the same unit even though 1 byte equals 8 bits
- Treating the result as a promise instead of an average theoretical rate
- Ignoring that other users, backups, video calls, or cloud sync traffic may already consume part of the link
- Planning for the exact calculated speed with no headroom for overhead, retries, or temporary slowdowns
- Comparing a monthly transfer allowance in GB or TB with a port speed in Mbps without converting one into the other, then forgetting that the monthly average hides the busiest hours
Embed this calculator on your site
Paste this code where you want the calculator to appear. It is responsive, mobile-friendly, resizes automatically, and is free to use as long as the credit line stays in place.
<script src="https://calctide.com/embed.js" data-tool="bandwidth-calculator" async></script>
<p style="font-size:12px;margin:4px 0 0">Bandwidth Calculator by <a href="https://calctide.com/tech/bandwidth-calculator/">CalcTide</a></p>Preview the embed at /embed/bandwidth-calculator/.