Bandwidth Converter — bits, bytes & download time

The bandwidth converter above translates internet speed between bits-based units (bps, Kbps, Mbps, Gbps) and bytes-based units (KB/s, MB/s), and then uses whichever speed you enter to calculate a realistic download time for any file size.

This single conversion causes more confused support tickets and one-star ISP reviews than almost any other number in consumer tech, because two industries settled on two different conventions for the same word "speed" and never reconciled them. Arb Digital builds and audits client sites where load-time expectations directly affect conversion rates, so we spend a lot of time explaining bandwidth math in plain terms to non-technical stakeholders — this tool is the version of that explanation you can actually click through yourself, whether you're troubleshooting a slower-than-expected connection or simply sizing up a new internet plan before signing a contract.

What This Bandwidth Converter Does

Enter a speed and pick its unit — bits per second in any of four common multiples, or bytes per second in two common multiples — and the converter instantly shows the same speed expressed every other way. The second section takes that speed and a file size you specify, then calculates how long the download would actually take, expressed in a readable format (seconds, minutes, or hours depending on scale) rather than a raw decimal that's hard to picture.

How to Use It

1. Enter your connection speed exactly as your ISP or router reports it.
2. Select the matching unit — almost always Mbps for home internet plans, sometimes Gbps for fiber or business connections.
3. Read the converted values across all six units in the result panel, with the byte-based MB/s figure highlighted since that's what download managers and browsers actually display.
4. Enter a file size in the second box — check the file's properties or the download page for the exact figure.
5. Read the estimated download time, which uses your converted real-world transfer rate from the first section.

The Formula / How It's Calculated

Every unit conversion here follows standard metric prefixes applied to a base unit of bits per second: 1 Kbps = 1,000 bps, 1 Mbps = 1,000 Kbps = 1,000,000 bps, and 1 Gbps = 1,000 Mbps. Converting from bits to bytes divides by 8, since one byte is defined as eight bits — so 1 MB/s = 8 Mbps, and conversely, 1 Mbps = 0.125 MB/s. Download time is simply file size divided by real transfer rate: a 10 MB file at a true 12.5 MB/s transfer rate takes 0.8 seconds, while the same file over a much slower 1 Mbps (0.125 MB/s) connection takes 80 seconds. Standards bodies like the International Electrotechnical Commission formally define these metric and binary prefixes, which is the same reference networking equipment vendors use when specifying throughput.

The 8x Bits-vs-Bytes Confusion, Explained Honestly

Here is the exact source of the confusion, stated plainly: internet service providers, network engineers, and telecom standards have always measured connection speed in bits per second, because that's the unit that describes how a signal is physically transmitted down a wire or through the air, one bit at a time. Computer file systems, operating systems, and download managers, on the other hand, have always measured file size and transfer progress in bytes, because a byte (eight bits) is the basic addressable unit of stored data — file sizes are quoted in KB, MB, and GB, never in kilobits or megabits.

Nobody did anything wrong; these were just two separate engineering communities standardizing independently, decades before broadband was a consumer product. But the result is that when your ISP sells you "100 Mbps," and your browser's download bar reports the transfer rate in MB/s, the two numbers look wildly different for the exact same connection, and it looks like you're getting robbed of 87.5% of your promised speed. You're not — you're just looking at the same number through two different units. Divide 100 Mbps by 8 and you get 12.5 MB/s, which is the realistic ceiling your download manager can show you, assuming perfect conditions with no overhead, congestion, or protocol losses eating into it (which in practice, a few always do).

Reference: Typical Real-World Speeds

These are illustrative benchmarks for context, not guarantees — actual throughput always depends on your specific plan, hardware, and network conditions:

• 25 Mbps (≈3.1 MB/s) — the FCC's historical baseline definition of "broadband" for a single user.
• 100 Mbps (≈12.5 MB/s) — a common mid-tier cable or fiber plan, comfortable for multiple simultaneous streams and video calls.
• 300–500 Mbps (≈37.5–62.5 MB/s) — typical higher-tier fiber plans aimed at large households or frequent large downloads.
• 1 Gbps (≈125 MB/s) — gigabit fiber, where the bottleneck often shifts from the connection itself to your Wi-Fi router or the far-end server's own upload speed.
• 10 Mbps (≈1.25 MB/s) — a common minimum for reliable HD video streaming without buffering.

Why ISPs Measure in Bits and Your Computer Measures in Bytes

It's worth understanding why this split happened in the first place, because it isn't arbitrary and it isn't going away. Telecommunications engineering has measured signal throughput in bits since the earliest days of modems and telegraph lines, because a bit — a single binary 1 or 0 — is the smallest unit a physical medium (copper, fiber, radio wave) can actually carry, one pulse at a time. When a standards body or a marketing team describes "how fast" a connection is, they are literally counting how many of those individual pulses can be sent per second, and bits per second is the natural, unambiguous unit for that.

Computer storage and file systems evolved along a completely separate track. A byte — eight bits grouped together — became the fundamental addressable unit of memory and storage almost from the beginning of modern computing, because it conveniently held enough combinations (256) to represent a full character set. Every file size, every hard drive capacity, every progress bar in an operating system has been built on bytes ever since, long before the two worlds of "network speed" and "file size" needed to talk to each other in the same download dialog box. By the time consumer broadband made the two industries collide daily, the conventions were already locked in on both sides, and neither party had a reason to switch. That's why the confusion persists today: it's not a bug or a scam, it's two mature engineering traditions that never needed a shared vocabulary until home internet made them sit next to each other on the same screen.

Upload vs Download Speed and Why They Differ

Many connection types — cable, DSL, and some fixed wireless plans — are deliberately asymmetric, meaning download speed is provisioned far higher than upload speed. A typical cable plan might offer 200 Mbps down but only 10-20 Mbps up, because historical residential usage patterns (streaming video, loading web pages, downloading files) were overwhelmingly download-heavy, and providers allocated shared network capacity accordingly. Fiber connections increasingly break from this pattern and offer symmetric speeds, since the physical medium doesn't have the same asymmetric bandwidth constraints that older cable and copper infrastructure does. This matters for the converter above: always double-check which direction (upload or download) a spec sheet number refers to, since running our download-time calculation with an upload speed by mistake will give you a wildly optimistic estimate for anything you're sending rather than receiving, like backing up photos to cloud storage or hosting a video call where your outgoing feed depends on upload capacity, not download capacity.

Common Mistakes to Avoid

• Confusing Mbps with MB/s when planning a download — they differ by exactly a factor of 8, and mixing them up leads to wildly wrong time estimates.
• Assuming advertised speed equals delivered speed. Real-world throughput is affected by Wi-Fi signal, network congestion, server-side limits, and protocol overhead — advertised speed is a theoretical ceiling.
• Forgetting upload and download speeds often differ significantly, especially on cable and DSL connections, unlike symmetric fiber plans.
• Blaming the ISP for a slow single-file download when the bottleneck is actually the server you're downloading from, which may not offer your full connection speed to a single connection.
• Ignoring that storage size units (GB) and speed units (Gbps) share letters but mean very different things — always double-check which one a spec sheet is actually using.

Related Free Tools From Arb Digital

Pair this converter with the Data Storage Converter for KB/MB/GB file size math, and the Flow Rate Converter and DPI/PPI Calculator for other everyday engineering conversions. Developers cleaning up CSS units will also want the Px to Rem Converter, and if you're testing how a site performs across devices, the Viewport Size Checker is a natural companion. Browse everything in our free online tools hub.

Frequently Asked Questions

This tool runs entirely in your browser using built-in JavaScript. Nothing you enter is uploaded, stored, or sent to any server.