How to transfer large files
Past a few gigabytes, email attachments stop working and every other option trades something away: time, money, convenience or setup. Here’s how the realistic choices compare, and how to pick one.
Cloud storage and upload links
Services like Google Drive, Dropbox, OneDrive or a file-sending link site: you upload the file, and the recipient downloads it whenever they like.
- Good for: sending to someone who isn’t online right now, or to many people with one link.
- The catch: the file crosses the internet twice — your upload, then their download. Free plans cap file size or total storage, share links on sending services often expire, and the provider keeps a copy.
A physical drive
Copy the files to an external drive or SSD and hand it over or ship it.
- Good for: hundreds of gigabytes or more, especially over slow internet. Copying locally is fast and needs no connection at all.
- The catch: you need to meet in person or post it, you pay for the drive, and it can be lost in transit — encrypt it.
FTP, SFTP or a self-hosted server
Run a server — a classic FTP or SFTP server, or a self-hosted storage app — and share access to it.
- Good for: teams that transfer large files regularly and want full control, with no third-party limits.
- The catch: someone has to set it up and keep it secure and updated, it needs a machine that stays online, and reaching it from outside usually means router and firewall configuration.
Direct peer-to-peer transfer
Tools like ecoos3 connect the two computers directly, so the file goes from one disk to the other without being stored anywhere in between.
- Good for: very large files between two people who can be online together. There’s no upload step and no size cap, and on the same network it’s as fast as the network.
- The catch: both people must be online at the same time, speed is limited by the sender’s upload, and some strict networks block direct connections.
Side by side
| Cloud upload | Physical drive | FTP / self-hosted | Direct (ecoos3) | |
|---|---|---|---|---|
| Size limit | Set by your plan | Drive capacity | Your server’s storage | Receiver’s free disk space |
| Recipient online at the same time | No | Hand-over or shipping | No | Yes |
| Setup | None | Buy a drive | Server and network setup | None |
| Someone else holds a copy | Yes | No | Only your server | No |
| Speed depends on | Your upload, then their download | Local copying | The server’s connection | The slower connection |
| Many recipients | Easy — share a link | One drive each | Easy | Up to 4, sent separately |
How long will it take?
Over the internet, the limit is almost always the sender’s upload speed, which is often much lower than the download speed your provider advertises. Rough transfer times:
| File size | 20 Mbps upload | 100 Mbps upload | 500 Mbps upload |
|---|---|---|---|
| 10 GB | ~1 h 7 min | ~13 min | ~3 min |
| 100 GB | ~11 h | ~2 h 13 min | ~27 min |
| 1 TB | ~4.6 days | ~22 h | ~4.4 h |
Calculated as gigabytes × 8,000 ÷ Mbps. Real transfers run a little slower because of protocol overhead and other traffic on the connection.
Recovering from a dropped connection mid-transfer
A transfer like the ones above can run for hours. Once it’s underway, the two devices send data directly to each other and no longer need the signaling connection that helped them find each other, so that connection closes. If the direct connection between the devices then fails — a Wi-Fi switch, a sleeping laptop, a dropped network — each device reopens a connection to the signaling server on its own and rejoins using the same room code. If that room had since been cleaned up, it’s recreated, so the code still works.
The two devices reconnect to each other and the transfer continues from where it stopped. The receiver already knows which chunks it has, so only the missing ones are sent again — an interruption at 80% resumes at 80%. A cloud upload that fails partway usually means starting over; here, the progress made on both ends is kept.
This reconnection is automatic, but it isn’t instant or unconditional: both devices still need to be online at the same time for the transfer to progress, the browser can take a minute or so to decide a connection is dead before it tries again, and if a device is closed entirely, the transfer waits until it’s reopened and resumed by hand.
When ecoos3 is a good choice
- The file is bigger than your cloud plan allows, and you don’t want to pay for more storage just to send it once.
- You and the recipient can be online together — even in short sessions, because transfers resume where they stopped.
- You’d rather no third party keeps a copy.
- You’re on the same network, where a direct transfer runs at full local speed.
When ecoos3 is the wrong choice
- The recipient can’t be online when you are. ecoos3 has nowhere to leave a file. Use cloud storage or a sending link.
- You’re sending one file to many people. A room holds four people, and each recipient gets their own stream from your upload. A shared link scales much better.
- The recipient uses Firefox or Safari. Receiving needs a Chromium browser, so they’d need Chrome, Edge, Brave or Arc.
- Either of you is on a network that blocks direct connections, such as a strict corporate firewall. Until relay support arrives, use cloud storage or a drive.
- Terabytes over a slow connection. 1 TB over a 50 Mbps upload is about 44 hours of transfer time. Resume lets you spread that over several days, but posting a drive may still be quicker.