Bits, bytes and bandwidth
Network speeds are quoted in bits per second, while file sizes and data allowances are quoted in bytes. A byte is 8 bits, so a connection that advertises 8 megabits per second moves at most 1 megabyte per second. Mixing the two is the most common source of confusion when estimating how long a download will take, and this calculator handles the conversion for you.
Data unit converter
Enter an amount and its unit, from bits to terabits or from bytes to terabytes, and the tool shows the equivalent in every unit. Prefixes here are decimal, so one kilobyte is 1,000 bytes, one megabyte is 1,000,000 bytes and so on. Lowercase letters mean bits and uppercase letters mean bytes.
Download and upload time
The time to move a file is its size in bits divided by the bandwidth in bits per second.
A 1 GB file on a 100 Mbit/s link is 8,000,000,000 bits at 100,000,000 bits per second, which is 80 seconds. Real transfers are slower because of protocol overhead, shared links and server limits, so treat the result as a best case.
Website bandwidth
Estimate the bandwidth a site needs by multiplying traffic by page weight. Enter the page views, the period they occur over, the average page size and a redundancy factor. The redundancy factor lets you add headroom for traffic spikes, bots and protocol overhead. A factor of 1 means no extra, while 2 doubles the estimate.
For example, 5,000 page views per day at 500 KB each is 2.5 GB per day, or about 0.23 Mbit/s of sustained bandwidth, and about 76.1 GB over an average month of 30.4375 days. With a redundancy factor of 2 that becomes 0.46 Mbit/s and 152.2 GB per month.
Hosting bandwidth converter
Hosting plans often cap monthly data transfer, while network gear is rated in bit rates. The converter links the two by assuming the rate is sustained for a whole average month of 30.4375 days (365.25 days divided by 12), which is 2,629,800 seconds. At that rate 1 Mbit/s moves 328.725 GB a month, and 1,000 GB a month needs about 3.04 Mbit/s. Real traffic is bursty, so most sites use far less than the rate their peak implies.
Typical connection speeds
| Technology | Speed |
|---|---|
| Dial-up modem | 56 kbit/s |
| ADSL2+ | 24 Mbit/s |
| Fast Ethernet | 100 Mbit/s |
| Wi-Fi 802.11n | 600 Mbit/s |
| Gigabit Ethernet | 1 Gbit/s |
| USB 3.0 | 5 Gbit/s |
| 10 Gigabit Ethernet | 10 Gbit/s |
| Thunderbolt 3 | 40 Gbit/s |
Tips
- Divide an advertised speed in megabits per second by 8 to get megabytes per second.
- Compress images and enable caching to shrink page size, which cuts bandwidth directly.
- Plan for peaks, not averages, when you choose a hosting tier.
- Upload speeds on consumer links are often much lower than download speeds.
Putting the pieces together
The four calculators answer different questions about the same quantity. Use the data unit converter when you only need to translate a size, for instance 250 megabytes into megabits before comparing with a link speed. Use the download time calculator when you know the file and the link. Use the website calculator when you are sizing a connection for a site you run, and the hosting converter when a provider quotes a monthly transfer allowance and you want to know the speed it implies. Because the tools share the same unit definitions, you can chain them: compute the monthly usage of your site, then convert it to a bit rate to compare with a plan.
Why real speeds fall short
The figures here are theoretical best cases. Real transfers lose a few percent to protocol headers such as TCP and IP, and more to Wi-Fi interference, congested networks, slow servers and disk limits. A practical rule is to expect 80 to 90 percent of the nominal rate on a good wired link and much less on a busy wireless one. If a download takes far longer than the estimate, test the connection at another time or from another device before suspecting the file.