WispFile

How to send large files over slow internet

By the WispFile team · Updated 24 September 2026

On a slow connection, the upload speed decides everything: at 10 Mbit/s a 5 GB file takes over an hour however you send it. What you can control is how many times the file crosses that slow link, whether a dropped connection starts it over, and whether anything else is fighting for the same bandwidth.

Key facts

  • Home lines often upload at a tenth of their download speed; check the upload figure.
  • An upload service sends the file twice: up to its servers, then down to the receiver.
  • A direct transfer sends it once, and the receiver gets it while you send.
  • Resume matters more than speed: a drop at 90% should not mean starting again.

How long it will take

Time depends on the size and the slower of your upload and their download:

Upload speed1 GB5 GB20 GB
5 Mbit/s27 minutes2.2 hours8.9 hours
10 Mbit/s13 minutes67 minutes4.4 hours
20 Mbit/s7 minutes33 minutes2.2 hours
50 Mbit/s3 minutes13 minutes53 minutes

For other sizes, see the upload time table.

Seven ways to make it faster

  1. Send it once, not twice. With an upload service the receiver cannot start until your upload ends. A direct transfer overlaps the two.
  2. Use a cable, or sit near the router. Weak Wi-Fi can halve what the line can do.
  3. Stop everything else uploading: cloud backup, photo sync, video calls.
  4. Send at night if the line is shared with a household or an office.
  5. Compress only what compresses. Video and photos barely shrink; raw data and documents often do. See when compressing helps.
  6. Send the most urgent part first, for example an edit before the camera originals.
  7. Use something that resumes. On a patchy line this saves more time than anything above.

When the connection drops

With WispFile a dropped connection pauses the download, and when both sides are back it continues from the last verified piece. If the receiver reloads the page, the browser can keep what already arrived and ask only for the rest. See resuming an interrupted transfer.

The trade-off of a direct transfer is that your device stays online until the receiver finishes. On a slow line, leave it plugged in with sleep turned off.

Find out your real upload speed

  1. Run a speed test on the device you will send from, not your phone.
  2. Note the upload figure; download is what your plan advertises.
  3. Test again with a cable, if you can. A big difference means Wi-Fi is the bottleneck.

Is it your Wi-Fi or your line?

If the cable test is much faster, fix the Wi-Fi first: move closer to the router, use the 5 GHz band, or use the cable for the transfer. If the cable test is just as slow, it is the line itself, and the tips above about sending once, at a quiet time, and with resume matter most. On some connections, a phone’s mobile data uploads faster than the home line; see sending over mobile data for what that costs.

Frequently asked questions

Is a direct transfer faster than WeTransfer on slow internet?

For the receiver, usually. An upload service makes them wait for your whole upload before their download starts; a direct transfer delivers while you send, so their wait is roughly halved. Your own upload time is the same either way.

Why is my upload so much slower than my download?

Most home broadband is asymmetric: cable and DSL lines often upload at a tenth of their download speed. Fibre is usually symmetric. A speed test shows both numbers.

Can I pause and continue later?

Yes, as long as the sender keeps the link open. If the receiver closes their page, they can open the link again later and resume from what their browser kept (verified in Chrome and Edge).

Does WispFile slow down on a slow line?

It goes as fast as the slower end allows and adapts to it: it sends only as fast as the connection drains, so nothing piles up in memory on either side.

Related guides

Send it directly now

Open WispFile, add your files and share the link. No account, nothing uploaded, nothing stored. Free.

Send files with WispFile