Ever had a friend ask for that 1 GB event video on your phone, only to find that your messaging app chokes on it, email refuses to send it, and cloud storage means a ten-minute upload plus a login for the other person? In moments like that, you do not actually need to park the file on someone else's server. Two browsers can simply connect to each other and pass the file across. Safe2Send is a small, no-sign-up tool built around exactly that idea.
According to the official website, Safe2Send is a peer-to-peer (P2P) file transfer service that promises no sign-up, no stored data, and no tracking. Files travel straight from the sender's browser to the receiver's browser and do not pass through the site's servers. The technology behind it is WebRTC, a standard built into modern browsers that lets two ends talk to each other directly. Tools like this are not new, but what stands out here is that the terms of service and privacy policy are written in plain language and spell out the connection details and limits. I will walk through how to use it and flag the caveats along the way.
What Is Safe2Send?
Safe2Send is a no-sign-up, browser-based P2P file transfer service that lets two people exchange files directly over WebRTC without uploading anything to the cloud. Think of the server as a matchmaker: it only passes along the signaling data needed to set up the connection, while the actual file contents, file names, and in-room chat messages move between the two devices alone. According to the privacy policy, that connection data sits in memory only briefly and is wiped once the link is established. The server additionally keeps only an aggregate count of successful transfers and total data volume. For anyone who wants to send a file without leaving a trail of cloud records, this design is refreshingly direct.
The homepage says "Serverless P2P", yet the terms of service make clear that the site does run a signaling server to help peers find each other. A more accurate way to put it is that your files do not go through a server, not that there is no server at all, and that difference is worth keeping straight when you describe the tool to others. Beyond file transfer, each room has an optional live chat, and those messages also travel over an encrypted channel between the two devices. If a transfer is interrupted, the pieces already received are cached in your own browser so the transfer can resume later.
How Do You Use Safe2Send?
Using Safe2Send comes down to one person creating a room and another person joining it, and once the two are connected, the transfer can begin. There is nothing to download and no account to create, and both sides only need a modern browser that supports WebRTC. The steps below are based on the official site and its documentation, so the screens you see may differ slightly after future updates.
Step 1: Open the Website and Pick Your Language
Open safe2send.cc on your computer or phone. The most prominent item on the homepage is the "Create a room" button, with a field beside it where the other person can paste a room code. There is a language selector at the bottom of the page if you want to switch the interface language. Both sender and receiver need the site open, so it helps if both of you are on an up-to-date browser.
Step 2: Create a Room and Decide on a Password
Before clicking "Create a room", the sender can tick "Password protect this room" to put a password on it. A room link works a bit like an unlisted link, so anyone who has the URL can walk in. Unless you are sharing something casual like holiday snapshots, I would turn the password on. Send the password through a different channel, such as a phone call or another messaging app, rather than in the same message as the link.
Step 3: Give the Link or Room Code to the Other Person
Once the room exists, the site gives you a shareable link and a room code, and you can send either one to the receiver. Keep in mind that a room expires 6 hours after it is created, and the sender's page has to stay open the whole time, because closing it cuts the other person off. The smoother approach is to agree on a time first and create the room only when you are both online.
Step 4: The Receiver Joins the Room
The receiver has two options: open the link you sent, or go to the Safe2Send homepage, click "Paste" in the join-room area to enter the code, and then click "Join Room". If the room has a password, the receiver will be asked for it at this point. One more thing to remember is that a room accepts only one receiver at a time, so if you want to send the same file to several people, you need to create a separate room for each of them.
Step 5: Pick Your Files Once You Are Connected
After both of you are in the room and the connection is established, the sender can choose the files to send, and the receiver will start getting them. Keep both pages open for the whole transfer, and do not let a phone fall asleep mid-way, or the connection may drop. If it does drop, the official documentation says the pieces already received stay cached in the browser, so the transfer can pick up again after reconnecting instead of starting over. The in-room chat is handy for confirming that the other person got everything.
Step 6: Clear Your Local Data When You Are Done
When the transfer is finished, and especially if you used a shared computer or a friend's device, click "Clear local data" on the page to remove the resume fragments and chat history stored in the browser for that room. The official policy says this data lives only on your own device and is never uploaded, but clearing it is still a good habit. Once a room expires or closes, its connection data is also discarded.
Is Safe2Send Safe, and What Should You Watch Out For?
Safe2Send protects transfers with the encryption built into WebRTC, but the operator does not guarantee the security or confidentiality of your files, so most of the risk management falls to you. According to the privacy policy, the connection signaling runs over encrypted HTTPS and WSS, and the peer-to-peer transfer itself is encrypted by the standard WebRTC protocol. The terms of service, however, state plainly that the operator does not guarantee the security, integrity, or confidentiality of transmitted files, and that the service is provided as is. In my view that is an honest way to write it, but readers should understand that "encrypted" does not mean "perfectly safe".
The detail people tend to overlook is your IP address. Because the connection is peer to peer, the sender and the receiver can see each other's network connection information, which is simply how WebRTC works. During setup, your IP also passes briefly through public STUN servers run by Cloudflare and Google to work out each side's public address, though those servers never touch file content. If you do not want a stranger to learn your IP, this is not the tool to use with people you do not know.
Connection success is the other limit to be aware of. The policy states that no TURN relay server is used, so on strict networks, such as some corporate firewalls or symmetric NAT setups, a failed direct connection means the transfer simply cannot go ahead. In an office environment that is a realistic problem, and a work network refusing to connect would not be a surprise. The flip side is that, with no relay in the middle, your file is not rerouted through anyone else's machine.
To pull it together, here is a quick table of the main limits, so you can see which ones affect how you plan to use it. The first two columns come straight from the official terms and privacy policy, and the last column is my own practical advice. The two that trip people up most are room expiry and connection conditions.
| Item | What the official documents say | Practical advice |
|---|---|---|
| Room lifespan | Expires 6 hours after creation | Agree on a time and create the room when both of you are online |
| Who you can send to | One sender and one receiver per room | To reach several people, open one room per person |
| Connection conditions | No TURN relay, so strict networks may fail to connect | If it will not connect, try a different network, such as mobile data |
| IP address | Both sides can see each other's IP | Only transfer with people you know |
| File contents | Not passed through or stored on the operator's servers | Encrypt sensitive files into a protected archive yourself before sending |
| File size | No limit is stated on the site or in the terms | The real ceiling depends on both networks and devices, so test large files with a small one first |
One more point worth mentioning: according to the privacy policy, the service was created by an individual developer named Akira Akiyama, the terms are governed by Hong Kong law, and both documents were last updated in September 2026. In other words, this is a young, individually maintained service, and its features and policies could change. My suggestion is to try it first with a file that does not matter, confirm that both networks cooperate, and only then decide whether to trust it with the real thing.
How Does Safe2Send Differ From Cloud Storage and Other P2P Tools?
Safe2Send is a one-to-one, both-online-at-once transfer tool, which is a different approach from cloud storage where you upload first and share a link afterward. The advantage of cloud storage is that you can upload and go offline, and the other person can download whenever they like, but your file sits on a third-party server in the meantime. P2P flips that around: no upload wait and no file left in the cloud, at the price of both people needing to be online together. A table makes the differences easier to see.
| Comparison | Safe2Send | Cloud storage or share links |
|---|---|---|
| Sign-up needed? | No | Often yes, depending on the service |
| Where the file lives | Only moves between the two devices, and the operator says it does not pass through its servers | Uploaded first to the provider's servers |
| Other person must be online? | Yes, and closing the page ends the transfer | No, they can download later |
| Number of recipients | One receiver per room | A link can be shared with many people |
| Wait before sending | No upload step, so it sends right after connecting | You wait for the upload to finish |
| Reliability | Depends on both networks, with no relay as a fallback | Usually more dependable |
| Best for | Quick, one-to-one, live transfers | Sending to many people or to someone whose schedule is unclear |
There are plenty of similar browser-based P2P tools out there, and some, like ShareDrop, have historically expected both people to be on the same network before they could find each other. Safe2Send pairs people with a room link and code instead, so you do not need to share the same Wi-Fi, and it can connect across networks as long as the network conditions allow. For anyone who often sends things to clients or friends in another city, that pairing method is a real convenience.
Who Should Use Safe2Send?
Safe2Send suits people who need to send files to one person at a time, on short notice, without creating an account or putting the file in the cloud. Picture a freelance video editor who needs to hand a client a rough cut of a few hundred MB. The client does not want to sign up for any platform, and the editor does not want to upload to the cloud for a single delivery. They agree on a time, the editor creates a room with a password, sends the link and the password separately, and as long as both are online the file goes straight across. For a one-off job like that, Safe2Send skips quite a few steps compared with cloud storage.
On the other hand, there are cases where I would not use it. If you need to reach a dozen people at once, if the other person's online hours are unpredictable, or if the file is truly confidential and you have not encrypted it yourself, cloud storage with encrypted sharing is the steadier choice. Strict work networks may also block the connection. Safe2Send has a clear niche, which is quick, temporary, and one to one, so do not expect it to replace a cloud drive or an enterprise transfer solution.
Is Safe2Send Worth Bookmarking?
Safe2Send is a small tool that does "no sign-up, one to one, files never through a server" well, but it is not a replacement for cloud storage. Having gone through it, what I like most is that the operator spells out the connection limits and privacy details so clearly, while the downsides are the unstated file size limit and a connection success rate that depends on both networks. For a quick transfer, one fewer account and one fewer upload means one fewer thing that can go wrong. I would bookmark it now and pull it out next time you hit a "they do not want to sign up and I do not want this in the cloud" moment.
Safe2Send FAQ: What Do People Ask Most?
The Safe2Send FAQ covers six of the most common questions: cost, whether files are stored, how many people you can send to, size limits, connection failures, and when to use it. The answers below follow the official site and terms, and anything they do not state is marked as such.
Do I need to sign up or pay to use Safe2Send?
You do not need to sign up. The homepage says no registration is required, and I did not see a paid plan, only a Ko-fi link for donations. The terms do say the service is provided as is, with no warranty of any kind.
Are my files stored on Safe2Send servers?
The operator says they are not. Files, file names, and chat messages move only between the two browsers, while the server handles only the signaling data and IP addresses needed to connect them, and it records only the number of transfers and the total data volume.
Can I send to many people at once?
No. Each room allows one sender and one receiver, and once a receiver has joined, nobody else can enter. To send to several people, create a separate room for each one.
Is there a file size limit?
Neither the site nor the terms state a size limit, so what you can send depends on both networks, devices, and browsers. Test large files with a small one first, and remember that the room expires 6 hours after creation.
What if it will not connect or the transfer fails halfway?
First make sure both pages are still open and the room has not expired. Because no TURN relay is used, strict networks may fail to connect, so try a different network, such as mobile data. If the connection drops mid-transfer, the pieces already received are cached in the browser and the transfer can resume after reconnecting.
Is Safe2Send better than cloud storage, and is it worth using?
It depends on the situation. For a quick one-to-one transfer when both of you are online, Safe2Send saves you the sign-up and the upload. For sending to many people or to someone who cannot be online at the same time, cloud storage fits better. For important or confidential files, encrypt them yourself before sending, whichever method you choose.