Send 100GB Files Between Browsers Without Cloud Storage

Updated 7 November 2026 · Standard formula, shown below

This guide shows you how to transfer very large files—up to 100GB or more—directly from one browser to another over the internet, without uploading to any cloud service. You’ll use a peer-to-peer (P2P) web app that creates a direct connection between the sender’s and receiver’s browsers, so your data never touches a third-party server. All you need is a modern browser, a stable internet connection, and a way to share a short code or link.

What You’ll Need

Two devices with a modern browser (Chrome, Edge, Firefox, or Safari) on desktop or mobile.
Internet connection on both ends—the faster the better, especially on the sender’s side.
A way to communicate the transfer code or link (e.g., messaging app, email, or phone call).
Patience—large transfers take time, even on fast connections.

Step-by-Step

Choose a peer-to-peer file transfer service. Open a reputable P2P web app like ShareDrop, Snapdrop, or ToffeeShare in your browser. These services use WebRTC to connect browsers directly. Avoid services that require you to upload to a server first.
Open the same service on the receiving device. The receiver should open the same URL in their browser. Some services generate a short room code or a link—if so, share that with the receiver.
Ensure both devices are on the same “room” or network. Most P2P services automatically detect other devices on the same local network. If the receiver is far away, use the service’s “link” or “code” feature to connect over the internet. For example, ShareDrop lets you create a room and share its URL.
Initiate the transfer from the sender’s side. On the sender’s browser, click the “Send” or “+” button, select the file(s) you want to send, and choose the receiver’s device from the list of connected peers.
Accept the transfer on the receiver’s side. The receiver will see a pop-up notification asking to accept the incoming file. They must click “Accept” or “Save” to start receiving. If the receiver misses the prompt, they can usually find the pending request in the app’s interface.
Wait for the transfer to complete. The browser will show progress bars for both upload and download. Keep both browser tabs open and the devices awake. Do not switch to another tab or lock the screen—this can pause or break the connection.
Verify the file after completion. Once the progress bar reaches 100%, the receiver should check the file size and integrity (e.g., open it or compare a checksum) to ensure it wasn’t corrupted during transfer.

Common Mistakes

Using a service that stores files on a server. Many “file transfer” sites actually upload to their cloud first, which defeats the purpose and may have size limits. Stick to known P2P services.
Both devices not on the same network or room. If the receiver is remote, you must use the room link or code; simply having the same app open isn’t enough.
Closing the browser tab or putting the device to sleep. This interrupts the direct connection and can corrupt the transfer.
Ignoring firewall or router restrictions. Some networks block P2P traffic. If the transfer fails, you may need to adjust settings (see Troubleshooting).
Assuming the transfer is instant. A 100GB file will take hours on typical broadband. Plan accordingly.

Tips

Use a wired connection for the sender if possible—Ethernet is more stable than Wi-Fi for long transfers.
Disable VPNs or proxies on both ends, as they can interfere with WebRTC’s NAT traversal.
Keep both browsers updated to the latest versions to avoid WebRTC bugs.
If the service offers a “pause” feature, use it if you need to interrupt—but know that not all services support resuming.
For maximum speed, ensure both devices have upload and download bandwidth available. The transfer speed is limited by the slower of the two connections.
Use a checksum tool (like MD5 or SHA-1) to verify the file after transfer, especially for critical data.

Troubleshooting

Transfer fails to start or connect. First, check that both devices can see each other in the app. If not, try refreshing the page, or use a different service. If you’re behind a strict firewall, you may need to enable UDP ports (usually 49152–65535) or use a service that supports TURN relays (most do, but they slow things down).

Transfer is extremely slow. This often happens when the connection falls back to a TURN relay instead of a direct P2P path. Try moving both devices to the same network, or ask your ISP to allow P2P traffic. Also, close other bandwidth-heavy apps.

File appears corrupted after transfer. This can happen if the connection drops briefly. Re-transfer the file, and this time keep both devices on stable connections. If the issue persists, try a different service.

Receiver doesn’t get the prompt to accept. Make sure the receiver’s browser is open and the tab is active. Some browsers block notifications—check the browser’s settings to allow notifications for the site.

Browser crashes or runs out of memory. Large files can use significant RAM. Close other tabs and applications, and consider using a desktop browser instead of mobile.

Frequently Asked Questions

Is it really private?

Yes, because the data travels directly between browsers. However, the connection can be relayed through a TURN server if a direct path fails, which means that server could theoretically see the data. Choose a service that uses end-to-end encryption (most do) to mitigate this.

Can I send multiple files at once?

Yes, most P2P services allow you to select multiple files. They are transferred as a batch, but the total size still counts.

What if the receiver is on a different continent?

It works as long as both have internet. The speed will depend on the distance and network conditions, but the direct connection is still possible.

Do I need to install any software?

No, everything runs in the browser. No downloads or plugins are required.

What is the maximum file size?

There’s no hard limit, but browser memory and connection stability may cause issues with files larger than a few hundred GB. For 100GB, it’s fine.

Can I pause and resume the transfer?

Some services support pausing, but not all. Check the service’s documentation. If you need to resume, you may have to start over.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.