Send files of any size,
instantly & free.
No account. No upload wait. No size limit. Your file streams straight from your device to theirs, encrypted, and is never stored on a server.
Sender tab must stay open: their screen must stay awake, the file streams live from their device.
Only connect to people you trust: files arrive directly, we never scan or store them.
A direct line between two browsers.
Most file-sending services work like a post office: you upload your file to their servers, they keep it for a while, and the other person downloads it later. That is convenient, but it is also why free plans come with size caps, monthly quotas and expiry dates. Storage and bandwidth cost money.
TransferFiles.net works more like a phone call. Your browser and the receiver's browser connect to each other using WebRTC, the same open standard that powers browser video calls, and the file streams across while you both have the page open. Nothing is uploaded to a storage server, so there is nothing for us to cap, keep or scan.
The trade-off is that both of you need to be online at the same time. If you need to send something now and have it picked up tomorrow, a cloud link is the better tool, and our comparison of transfer services will help you choose one.
How a transfer works
Most transfers start within a few seconds of the receiver opening your link.
Choose your files
Tap Send a File and pick one or more files. They are read from your device as the transfer runs; nothing is uploaded in advance.
Share the link or code
Send the link by any messaging app or email, or read out the short code (like ABCD-1234) if you're sitting next to each other.
The receiver connects
They open the link and tap Connect. A broker server introduces the two browsers, then the encrypted connection runs between them.
Stay until 100%
Keep both pages open and both screens awake until the bar finishes. The file lands in the receiver's Downloads (or the Files app on iPhone).
When to use us, and when not to
No single way of sending files is best for everything. Here is our honest take.
TransferFiles.net is a good fit when…
- The file is bigger than your email or messaging app allows.
- You and the receiver can both be online for the next few minutes.
- You don't want the file sitting on someone else's server afterwards.
- You're moving files between your own devices, such as an iPhone and a Windows PC.
- Neither of you wants to create an account.
Use something else when…
- The receiver will download later, after you have gone offline. Use a cloud link (see WeTransfer or Google Drive).
- You need to send the same file to many people over days or weeks.
- You're sending a very large file to a phone using Safari or Firefox, where the browser has to hold it in memory. A desktop with Chrome or Edge is more reliable.
- Your workplace network blocks peer-to-peer connections and you're not allowed to use another network.
Help with sending files
File transfer services compared (2026)
One table with the free limits, retention, encryption and paid entry price of eleven file transfer services, plus which one fits which job.
How-toHow to send files between iPhone and Android
Quick Share with AirDrop, Google Photos, LocalSend, browser transfer or a cable: which works for your phones and how to keep full quality.
GuidesEmail attachment size limits: every major provider, and why your file still bounces
Per-provider sending and receiving limits for Gmail, Outlook, Microsoft 365, Yahoo, iCloud, Proton and Zoho, and why encoding makes files bigger.
How-toHow to send photos and videos without compression
App-by-app steps for WhatsApp, iMessage, Telegram, Signal, Messenger and Instagram to send originals instead of compressed copies.
GuidesFile transfer time calculator
Work out how long a file will take to send at your connection speed, and why Mbps is not MB/s.
GuidesIs it safe to receive files? A checklist before you open anything
A practical safety checklist for files from strangers, clients and friends, including fake 'you've received files' emails.
Common questions
We don't set one. Because the file goes straight from your device to the receiver's, we have no storage to fill up. In practice, the limits are how long both devices can stay connected and, on browsers that hold the file in memory (Safari, Firefox and most phone browsers), how much memory the receiving device has. For very large files, a computer running Chrome or Edge is the most reliable receiver.
Every WebRTC connection is encrypted with DTLS, and that can't be turned off. Your file isn't uploaded to or stored on any server. If your two networks can't connect directly, the encrypted data is passed through a relay server, which can't read it. As with any transfer, only accept files from people you know.
The file is read from the sender's device and streamed to the receiver as the transfer runs. There's no copy on a server to fall back on, so if either page closes or a phone screen locks, the stream stops.
Current versions of Chrome, Edge, Firefox and Safari, on Windows, macOS, Linux, Android and iOS. Any combination works, such as iPhone to Android or Mac to Windows. No app or plug-in is needed.
No. A dropped connection ends the stream. The sender needs to choose the file again and share a new link. Keeping both screens awake and staying on Wi-Fi is the best way to avoid this.
On computers and Android, files go to the browser's Downloads folder. On iPhone and iPad, Safari saves them to the Files app. For files over 200 MB, desktop Chrome and Edge ask where to save, so the file can be written straight to disk.
Ready to send a file?
No sign-up, nothing to install. It takes about thirty seconds to start.
Send a File Now