A direct answer, with two different assumptions
A 50 GB transfer over a constant 100 Mbps connection takes 4,000 seconds: 1 hour, 6 minutes and 40 seconds. That is the ideal transfer calculation, using decimal gigabytes and every entered bit per second for the file. If you choose an 80% throughput scenario, the same input becomes 5,000 seconds: 1 hour, 23 minutes and 20 seconds. The calculator does not claim that 80% is typical for your provider, server or device.
Use the size actually being transferred. A game’s installed storage requirement can include unpacked assets and reserved space, so it is not automatically the number of bytes the store will send. A patch can also require local verification or rewriting much more data than its download size. This planner times the transfer you enter, not the whole update process.
The formula you can check
First convert the file size to bytes. Multiply by eight to get bits, then divide by the entered connection rate in bits per second. Finally divide by your chosen throughput fraction. In symbols: seconds = bytes × 8 ÷ bits-per-second ÷ fraction. With 50 × 1,000,000,000 bytes, 100 × 1,000,000 bits per second and a fraction of 1, the result is exactly 4,000 seconds.
If the downloader already reports a stable measured MB/s rate, select MB/s and use 100% to calculate from that observed rate. Applying another overhead allowance to a rate that already includes it can count the same limitation twice. A speed-test result or advertised connection rate is a different input: it may not be available continuously to a particular download.
GB and GiB are different; Mbps and MB/s are different too
NIST lists one gigabyte as 1,000,000,000 bytes and one gibibyte as 1,073,741,824 bytes. At 100 Mbps, 50 GiB therefore needs about 4,294.97 ideal seconds, rounded up here to 1 hour, 11 minutes and 35 seconds. That is longer than 50 GB without any change to the network. Match the unit displayed by your source instead of silently treating both labels as the same quantity.
There are eight bits in a byte. A 100 MB/s transfer is eight times the rate of a 100 Mbps transfer. For the same 50 GB file, 100 MB/s means 500 ideal seconds: 8 minutes and 20 seconds. Capitalisation matters in these labels; this calculator displays both the unit and its full meaning so the choice remains visible.
What can make the wall-clock time longer
The result assumes a constant rate. Server limits, other users on the connection, Wi-Fi conditions, pauses, changing congestion and local disk work can change it. The throughput percentage is an explicit what-if control, not a diagnosis of any of those causes. If you have a measured range, run both ends as separate scenarios rather than treating one output as a promised finish time.
This page does not contact a speed-test service or inspect your connection. Inputs stay in the calculator in this browser. Downloading the file, installing it, unpacking it and checking it are separate activities. Start with the transfer estimate, then leave time for the additional work your store or application actually reports.
Useful limits and checks
Zero transferred bytes returns zero transfer time. A zero or negative rate is rejected because it cannot define a finite download. The throughput share must be above zero and at most 100%. Results round up to whole seconds; that display choice does not increase the precision of an uncertain rate.
The arithmetic is tested with decimal and binary file units, megabits and megabytes per second, the 50 GB examples, zero-byte transfers and invalid inputs. These are calculation checks with hypothetical inputs. They are not measured game-download benchmarks, provider rankings or a forecast of your actual completion time.
Original tool and worked arithmetic with AI assistance, checked against NIST unit definitions and regression cases. Inputs are hypothetical planning scenarios; no connection measurement or download benchmark is claimed.