Bandwidth Calculator

What the Bandwidth Calculator does

The Bandwidth Calculator is a three-variable solver for the relationship between data size, transfer time, and bandwidth. Pick the variable you want, give it the other two, and it returns the answer. It's the same physics as velocity = distance / time from high-school class, applied to networks:

The questions it answers are the everyday ones: How long will this download take? How much bandwidth do I need to back up 1 TB overnight? How much data did I burn streaming for three hours? The calculator also handles the unit-conversion footgun that catches almost everyone the first time: ISPs quote bandwidth in bits per second (Mbps), but file sizes are measured in bytes (MB). There are 8 bits in a byte, so a 100 Mbps connection moves files at 12.5 MB/s, not 100 MB/s. Get that wrong by a factor of 8 and you'll spend an evening confused.

How to use the calculator

The widget has three solve modes, one for each variable. Pick the one whose answer you're looking for, enter the two values you know, and read the result.

1. Pick a solve mode: find time (most common), find data size, or find bandwidth.
2. Enter the two known values with their units. The unit dropdowns include MB / GB / TB for data, Mbps / Gbps / MB/s / GB/s for bandwidth, and seconds / minutes / hours for time.
3. Read the headline result, expressed in the unit that makes the number most readable. Below the headline, the calculator shows the same value in other common units for context.

The math is one division or multiplication and runs instantly in your browser. There's nothing to send anywhere.

Mbps versus MB/s — the eight-times factor

This is the single confusion that motivates this entire tool. Two units that look almost identical mean very different things:

• Mbps (lowercase b) = megabits per second. The unit ISPs and network hardware use. 1 megabit = 1,000,000 bits.
• MB/s (uppercase B) = megabytes per second. The unit file managers and download dialogs use. 1 megabyte = 1,000,000 bytes = 8,000,000 bits.

Because there are 8 bits in a byte, the two units differ by a factor of 8:

Marketing departments love Mbps because the number is bigger (advertising "1000 Mbps" reads better than "125 MB/s," even though they describe the same connection). Your file download dialog uses MB/s because file sizes are bytes. The Bandwidth Calculator handles both — pick whichever your source uses, and the math works out either way.

Worked example: a 4.5 GB game download on a 50 Mbps connection

You're downloading a game patch that's 4.5 GB. Your ISP says you're paying for 50 Mbps. How long does it take, ideally?

First, get both values into compatible units. 50 Mbps in megabytes per second:

Now divide the data by the speed:

That's the theoretical minimum. In practice, expect 13–15 minutes. The reasons are covered below — TCP overhead, server speed limits, WiFi loss, and similar real-world frictions typically eat 10–20% off the headline number. If you see substantially more than 15 minutes for a 4.5 GB download on a 50 Mbps connection, something's wrong: the server is slow, your WiFi is congested, or there's a routing issue between you and the source.

Download times for common file sizes and speeds

The table below shows theoretical minimum download times for various combinations. These are ideal-conditions numbers — divide by 0.85 to estimate realistic times.

A few things jump out from the table. First, the jump from 100 Mbps to 1 Gbps is the difference between an overnight backup and a coffee-break backup — for big files, fiber genuinely changes what's possible. Second, even on gigabit fiber, a 1 TB backup is still over two hours of saturated upload; cloud backup services like Backblaze regularly take days or weeks for the first full upload. Third, the difference between 1 Mbps DSL and 10 Mbps "basic" broadband is enormous — 10× the speed for typically twice the price, and the math compounds: a 100 GB game install drops from over a week of download to under a day.

Why your actual speed is lower than the calculator says

The calculator gives you the theoretical minimum — the time the download would take if every bit moved at exactly the quoted bandwidth with no overhead. Reality is always slower for several stacked reasons:

• TCP overhead. The TCP protocol that handles most internet traffic adds headers and acknowledgment packets to every transfer. Typical real-world overhead: 3–5%.
• HTTPS encryption. The encrypt-and-decrypt step adds a small CPU cost and packet overhead. Typical: 1–3%.
• WiFi losses. Wireless is shared, half-duplex, and prone to interference. 5 GHz WiFi typically delivers 300–800 Mbps in practice, even when both ends support gigabit speeds. 2.4 GHz is much worse — often 50–150 Mbps in practice. If your bandwidth test gives you 1 Gbps wired but 400 Mbps wireless, your WiFi is the bottleneck, not your ISP.
• Server bandwidth. Your 1 Gbps connection doesn't help if the file you're downloading is hosted on a server that only serves at 100 Mbps. Public file-sharing sites and game-update CDNs often throttle individual connections; the cumulative result is downloads that crawl regardless of your connection speed.
• Routing congestion. Internet traffic is routed through dozens of intermediate networks. If any segment along the path is congested, your effective speed drops to match the slowest link.
• Concurrent traffic. If someone else in the house is streaming 4K, your effective bandwidth drops by whatever they're using (25 Mbps for a 4K stream).

The rule of thumb: realistic throughput is 80–90% of the quoted bandwidth on a wired connection, and 50–75% on WiFi. The calculator's number tells you what's physically possible; reality is some fraction of that.

How much bandwidth different tasks need

Going the other way — given a task, how much bandwidth do you need? Here are the typical numbers used by the services themselves:

• Email and web browsing: <1 Mbps. Most pages are under 5 MB; load time is dominated by latency, not bandwidth.
• SD video streaming: 1–3 Mbps per stream.
• HD video streaming (1080p): ~5 Mbps per stream.
• 4K video streaming: ~25 Mbps per stream (Netflix's recommendation).
• Video calls (1-on-1, HD): 1.5–3 Mbps both directions.
• Video calls (group, HD): 4–8 Mbps both directions.
• Online gaming: 3–5 Mbps is plenty. Latency (ping) matters far more than bandwidth for game responsiveness.
• Cloud backup: required bandwidth = total data ÷ acceptable backup time. To back up 1 TB overnight (8 hours), you need 1 TB ÷ 8 hours = 125 GB/hour = ~280 Mbps sustained.
• Software/game downloads: use the calculator — it depends on file size.

For a household, roughly sum the simultaneous needs. Two people on HD video calls plus a 4K stream = 3 + 3 + 25 = 31 Mbps minimum, plus some headroom. The "200 Mbps for a family of four" sales pitch isn't arbitrary — it's enough headroom for everyone to do their thing without anyone's stream stuttering.

Edge cases worth knowing

A few situations where the simple math gives a misleading answer:

• Compressed transfers. Text-heavy data (HTML, JSON, source code) often transfers compressed with gzip or brotli, shrinking 2–10× on the wire. The calculator uses raw file size, so it overestimates time for compressible payloads. Already-compressed formats (JPEG, MP4, ZIP) don't compress further — the number is accurate for those.
• Many small files vs one big file. Downloading 10,000 tiny files takes much longer than downloading one file of the same total size, because each request has connection overhead. The calculator assumes one continuous transfer.
• Streaming bitrates aren't constant. Netflix and YouTube use adaptive bitrate — quality adjusts to your real bandwidth in real time. The "25 Mbps for 4K" figure is the peak; the average is lower. Stream data usage is roughly bitrate × time, but bitrate fluctuates.
• Asymmetric connections. Most home connections have higher download than upload speeds (a typical 1 Gbps cable plan might have only 50 Mbps upload). The calculator treats them as one number; specify whichever direction you're solving for.

Related tools

Bandwidth is one piece of a small family of measurement and conversion tools. A few that pair naturally:

• Data Storage Converter — convert between MB, GB, TB, GiB, and the other binary-versus-decimal storage units (1 GB = 1,000 MB versus 1 GiB = 1,024 MiB, the source of another common confusion).
• Time Duration Calculator — convert between seconds, minutes, hours, days when the calculator's output unit isn't the one you want to think in.
• Speed Converter — general-purpose speed unit conversion (mph, kph, m/s, knots) — different problem, similar shape.
• IP Subnet Calculator — for the other half of network planning, working out address ranges and subnet sizes.
• JSON Formatter — for inspecting the API responses that move across the bandwidth you just calculated.

Frequently asked questions

Why is the calculator's number lower than my ISP's quoted speed?

Two reasons. First, ISPs quote bandwidth in Mbps (megabits per second), but file sizes are MB (megabytes). 1 byte = 8 bits, so a 1 Gbps connection theoretically downloads at 125 MB/s — and that's the calculator's math. Second, real-world speeds run 10–20% below theoretical because of TCP overhead, retransmissions, HTTPS encryption, and the source server's response speed. A 1 Gbps connection downloading a big file from a fast server typically achieves 90–110 MB/s in practice, not the full 125.

What's the difference between Mbps and MB/s?

A factor of 8. Mbps (lowercase b) is megabits per second — the unit ISPs and network hardware use. MB/s (uppercase B) is megabytes per second — the unit file managers and download dialogs use. 1 byte = 8 bits, so 100 Mbps = 12.5 MB/s. Marketing prefers Mbps because the number is bigger. File transfer dialogs use MB/s because that's how the data is sized. Always check which one you're looking at — confusing them gives you an answer that's off by 8×.

Why does my actual download seem faster or slower than the calculator predicts?

Several variables stack up. The server's outbound bandwidth might be lower than yours — your gigabit connection doesn't help if the source serves at 50 Mbps. WiFi can drop wireless throughput by half or more compared to wired. TCP windowing and packet loss recovery add overhead. HTTPS encryption costs 1–3%. Concurrent traffic on your network divides the pipe. The calculator assumes ideal conditions; reality typically delivers 80–90% of theoretical on wired, 50–75% on WiFi.

How long should a 4K Netflix stream take?

Netflix recommends 25 Mbps for 4K HDR streaming. That's 25 ÷ 8 = 3.125 MB/s of throughput. A 2-hour 4K movie at that bitrate is about 22.5 GB of data. Netflix uses adaptive bitrate, so the quality drops to fit your real bandwidth — the calculator's number tells you what's theoretically possible, not what Netflix actually serves. HD 1080p needs ~5 Mbps, 720p ~3 Mbps, SD ~1 Mbps. If you're seeing buffering at 25 Mbps quoted, the issue is usually WiFi or other traffic on the network, not the ISP.

How long to back up 1 TB at 100 Mbps?

1 TB = 1,000,000 MB. 100 Mbps = 12.5 MB/s = 750 MB/minute = 45 GB/hour. 1 TB ÷ 45 GB/hour ≈ 22 hours theoretical. In practice, expect 25–30 hours with TCP overhead and the backup service's own throttling. Cloud backup services (Backblaze, Carbonite, etc.) often deliberately throttle upload to avoid saturating your connection, so initial backups commonly take days. After the first full backup, only changed files upload — incremental backups are much faster.

What bandwidth do I need for working from home?

For one person doing video calls, screen sharing, and normal web work, 10–25 Mbps download and 5–10 Mbps upload covers it. Upload matters more than people expect because video calls and screen shares are upload-heavy. If two people are on simultaneous HD video calls in the same house, plan for at least 30 Mbps symmetric. Add 25 Mbps per concurrent 4K stream from anyone else. For developers pushing large repos or designers uploading big assets, faster upload helps — symmetric gigabit connections are increasingly common in fiber markets and remove the upload bottleneck entirely.

Does the calculator account for compression?

No — the calculator uses raw file size. If your data is compressible (HTML, JSON, source code, uncompressed images), tools like gzip or brotli can shrink it 2–10× before transfer, dramatically reducing actual transfer time. Most modern protocols (HTTP, S3, rsync) handle compression automatically. Already-compressed formats (JPEG, MP4, ZIP, modern game assets) don't compress further — the calculator's number is accurate for those.

What's the fastest residential internet available?

10 Gbps (1.25 GB/s theoretical) is the current top in fiber markets — available from Verizon Fios, Google Fiber, AT&T Fiber, and similar carriers in select metros. Most US homes have 100–1000 Mbps. Even with a 10 Gbps WAN connection, the practical bottleneck is usually the WiFi router (Wi-Fi 6E and Wi-Fi 7 are needed to get past 1 Gbps wireless) or the source server, not the connection itself. Enterprise and datacenter Internet routinely runs 100–400 Gbps, with 800 Gbps and 1.6 Tbps standards rolling out for backbone links.

How do I know if I'm getting the speed I'm paying for?

Run a speed test (Fast.com, Ookla Speedtest, or Cloudflare's speed test) directly connected via ethernet to your router or modem. Wired tests bypass WiFi limits and give the real connection speed. If wired speeds match the ISP's quote to within ~10%, the connection is delivering. If they're far below, the issue is your line (call the ISP) or your modem (some are limited to lower speeds and need to be upgraded). Test multiple times — single measurements can be noisy.