50 GB at 100 Mbit/s with 5 % overhead
- File size
- 50 GB
- Connection speed
- 100 Mbit/s
- Protocol overhead
- 5%
- Time in seconds
- 4,210.53 s
- Effective speed
- 95 Mbit/s
검증 출처: 50 × 8 × 10⁹ bits ÷ (100 × 10⁶ × 0.95) bit/s = 4210.526… s (Python fractions)
Calculate how long a file takes to download or upload from its size in MB, GB or TB and your internet speed in Mbps, allowing for protocol overhead.
업데이트 검증한 예제: 5
At 100 Mbit/s with 5% overhead, the useful rate is 11.88 MB/s, so 50 GB takes 1 h 10 min 10 s.
1 byte = 8 bits. GB means 10⁹ bytes; GiB means 2³⁰ bytes.
That is 1 h 10 min 10 s.
Download time is file size divided by the useful data rate. The calculator turns the size into bits (1 byte = 8 bits; GB means 10⁹ bytes and GiB means 2³⁰ bytes), takes the connection speed in bits per second, and removes the share of each packet taken by protocol headers: time = bits ÷ (speed × (1 − overhead)).
People use it before downloading a game or a cloud backup, and to judge whether a faster plan is worth paying for. The default, a 50 GB file on a 100 Mbit/s line with 5% overhead, takes 1 h 10 min 10 s; at 1,000 Mbit/s the same file takes about 7 minutes.
The result is a best case. The 5% default is the framing cost of TCP/IPv4 over Ethernet; the server's own limit, Wi-Fi signal and other traffic are not modelled. For an upload, enter your upload speed, which on asymmetric lines such as ADSL is lower than the download speed.
검증 출처: 50 × 8 × 10⁹ bits ÷ (100 × 10⁶ × 0.95) bit/s = 4210.526… s (Python fractions)
검증 출처: 8 × 10⁹ / 10⁸ = 80 s
검증 출처: 2³⁰ × 8 bits / 10⁹ bit/s = 8.589934592 s
검증 출처: 4.7 × 8 × 10⁹ / (25 × 10⁶ × 0.9) = 1671.11 s (Python fractions)
About 84 seconds with 5% protocol overhead, or 80 seconds at the raw line rate. 1 GB is 8,000 megabits, and 8,000 ÷ 100 = 80 s. Halving the speed doubles the time: 160 s raw at 50 Mbps. At 1 Gbps the same gigabyte takes 8 s raw, about 8.4 s with overhead.
Mbps (megabits per second) is how connection speeds are sold; MB/s (megabytes per second) is how browsers and download managers show progress. A byte is 8 bits, so divide Mbps by 8: a 100 Mbps line moves at most 12.5 MB/s, and about 11.9 MB/s after 5% overhead. Both use decimal prefixes, so 1 Mbit = 10⁶ bits (NIST).
Part of every packet is headers, not your file. With a 1,500-byte Ethernet MTU, TCP/IPv4 carries 1,460 bytes of data in every 1,538 bytes on the wire (IEEE 802.3 framing plus 20-byte IP and TCP headers), a 5.1% loss; the 12-byte TCP timestamp option cuts the data to 1,448 bytes, 5.9%. Beyond that, the server's upload limit, Wi-Fi signal and other devices sharing the line slow it further.
Because Windows File Explorer counts in binary units but labels them GB: it divides by 2³⁰ (1,073,741,824) bytes, so 50 × 10⁹ bytes appears as 46.6 GB. Stores and ISPs use decimal gigabytes (10⁹ bytes, IEC 80000-13), and macOS has shown decimal sizes since Mac OS X 10.6 in 2009. Choose GiB in the size field for a size copied from Windows.
정확도는 입력값과 계산 방법의 가정에 따라 달라집니다. 십진 연산은 유효숫자 50자리를 사용하지만, 추정값·수치해석 방법·원본 데이터의 정밀도는 더 낮을 수 있습니다. 표시값을 반올림해도 이러한 한계는 사라지지 않습니다. 독립적인 출처의 풀이와 대조한 계산 예시: 5. 예를 들어 “50 GB at 100 Mbit/s with 5 % overhead”은 50 × 8 × 10⁹ bits ÷ (100 × 10⁶ × 0.95) bit/s = 4210.526… s (Python fractions)와 대조해 확인합니다.
NIST — Prefixes for binary multiples (IEC 80000-13): 1 byte = 8 bits, GB vs GiB; IEEE 802.3 Ethernet framing (1,500-byte MTU + 38 bytes of preamble, header, FCS and gap) with RFC 791 / RFC 793 20-byte IPv4 and TCP headers.
이 계산기에는 독립적인 출처에서 답을 얻은 계산 예제가 5개 있습니다. 테스트 모음에서 실행되며 여기에서도 실행할 수 있습니다.
GB를 MB로, TB를 GB로, GiB를 GB로 변환합니다. 십진 접두어(kB, MB, GB, TB)와 이진 접두어(KiB, MiB, GiB, TiB)를 구분하며 비트와 바이트도 지원합니다.
Mbps를 MB/s로, Gbps를 MB/s로, kbps를 kB/s로 변환합니다. 네트워크 속도는 초당 비트로, 파일 크기와 다운로드 표시는 바이트로 나타냅니다.
Download or upload time for a file at a given speed, the data a link moves in a set time, and a website's monthly bandwidth from page views.