Send a GB File: How Long a Gigabyte Transfer Really Takes

October 7, 2026

If you need to send a GB file, the first question is always the same: how long will this take? The honest answer is that it depends on a single number, the slowest link between the two devices, and once you know how to read that number you can predict a transfer to within a minute or two before you start.

The simple math behind a GB file transfer

Network speeds are quoted in megabits per second (Mbps), while file sizes are quoted in megabytes or gigabytes. A byte is eight bits, so one gigabyte is roughly 8,000 megabits. Divide 8,000 by your speed in Mbps and you get the time in seconds. At 100 Mbps, a 1 GB file takes about 80 seconds. At 50 Mbps it takes about 160 seconds. At 20 Mbps it takes about 400 seconds, or just under seven minutes. At 10 Mbps it takes more than thirteen minutes.

Scaling up: 5 GB, 10 GB and beyond

The math scales in a straight line. A 5 GB file at 100 Mbps takes about 400 seconds, which is just under seven minutes. A 10 GB file at the same speed takes around 800 seconds, a little over thirteen minutes. A 50 GB folder of footage at 100 Mbps is closer to an hour and a half. These are best-case figures, since real connections rarely hold their peak speed for the whole transfer, so add a margin of 20 to 50 percent when you are planning around a deadline.

Which speed actually matters: upload, download or Wi-Fi?

For a cloud link, you pay twice: the sender uploads the whole file first, then the recipient downloads it, and home connections are usually much slower at uploading than downloading. A direct device-to-device transfer removes that double trip, because the data only travels once, straight from sender to receiver. When both devices share a good Wi-Fi network and a direct path is available, the limit is the Wi-Fi link between them rather than your internet plan, which is why local transfers can feel dramatically faster than anything involving an upload.

Why real transfers are slower than the math

Several things pull a real transfer below the theoretical figure. Wi-Fi speed drops with distance, walls and interference, and a phone far from the router can run at a fraction of the advertised rate. Both devices share the connection with everything else on the network, such as streaming and backups. A phone that is running hot, or a laptop on battery saver, may throttle its radio. And if a direct path is blocked and the data goes through a relay, the speed is capped by that relay path rather than the local network.

How to make a GB file transfer faster

Move closer to the router, or put the laptop on a cable if you can. Pause other heavy downloads and cloud backups for the duration. Keep the screen on and the device awake on both ends, because a sleeping phone is the most common reason a long transfer stalls. Send one large file rather than thousands of tiny ones when you can, since many small files add per-file overhead. And do not compress video or photos that are already compressed, because zipping rarely shrinks them and just adds time on both sides.

How Nearsend handles a GB file

Nearsend sends the file straight from one browser to the other over an encrypted WebRTC connection, cut into 64 KB chunks with flow control so the sender never overruns the receiver. Nothing is uploaded to a server first, which is why there is no upload step and no cap on file size. The one practical limit is memory on the receiving side: the browser holds a file in memory until it is saved, so very large files are best received on a computer with plenty of free RAM, and Nearsend warns you before it accepts a very large transfer. If the connection is going through an encrypted relay rather than directly, the interface tells you.

A quick way to estimate your own transfer

Run a speed test on the slower of the two devices, note the upload figure for the sender and the download figure for the receiver, and take the lower of the two as your working speed. Divide the file size in megabits (gigabytes times 8,000) by that number, then add a third as a safety margin. If the result is longer than you can wait, move both devices onto the same strong Wi-Fi network, or plug one in with a cable, and try again.