# Secure file sharing: a practical guide

> How to share files securely: end-to-end encryption, verifying the recipient, avoiding stored copies, and choosing the right tool for sensitive files.

_Security · Updated 2026-10-28 · By Rishi Shah · https://relay.rishishah.in/secure-file-sharing_

**Secure file sharing comes down to three questions: who can read the file in transit, who keeps a copy afterwards, and how sure you are that the right person received it.** The safest option answers "only the recipient", "nobody" and "verified".

## 1. Encrypt end to end, not just "in transit"

Almost every service encrypts the connection between you and *its servers* (HTTPS). That protects against eavesdroppers on your Wi-Fi, but the service itself can still read the file once it arrives. **End-to-end encryption** means only the sender and recipient hold the keys.

- **Relay** sends files over WebRTC, which is always encrypted between the two browsers. [How that works](/end-to-end-encrypted-file-transfer).
- Some cloud tools add their own end-to-end encryption on top (for example Wormhole).
- Plain email attachments and most cloud drives are **not** end-to-end encrypted.

## 2. Don't leave copies behind

A file uploaded to a server can be breached, subpoenaed, scanned or forgotten. Tools that stream directly between devices leave nothing behind. With Relay, nothing is stored on any server; the only copies are on the two devices.

## 3. Verify who is on the other end

Encryption is only as good as knowing who holds the other key. Look for a way to verify the recipient:

- Relay shows a **[safety number](/verify-safety-number)** on both screens. If they match, nobody is in the middle, not even Relay's server.
- Relay also makes you **approve every device** that joins and **accept every file**.

## 4. Use short-lived connections and strong codes

- Prefer room codes that expire and cannot be brute-forced. Relay limits wrong guesses and lets you add a room password.
- For links to stored files, set an expiry and a password.

## 5. Protect the endpoints

No transfer method protects a file from malware on the sending or receiving computer. Keep devices updated, and be careful opening files from people you don't know.

## Checklist: choosing a secure file sharing tool

| Question | Good answer |
|---|---|
| Is it end-to-end encrypted? | Yes, keys only on the two devices |
| Is the file stored on a server? | No, or encrypted and auto-deleted |
| Can I verify the recipient? | Safety number, PIN or similar |
| Can strangers join or guess links? | No: approval, rate limits, passwords |
| Is the code open source? | Yes, so claims can be checked |

Relay is built to give the "good answer" to every row. [Try it](/) or read the [security model](/security).

## FAQ

### What is the most secure way to share a file?
Send it directly over an end-to-end encrypted connection, verify the recipient (for example by comparing a safety number), and avoid leaving copies on third-party servers.

### Is email secure for sending files?
Usually not for sensitive files. Attachments are stored on mail servers, often unencrypted end to end, and are hard to delete everywhere.

### Is Google Drive secure for sharing files?
Google Drive encrypts files in transit and at rest, but Google holds the keys and keeps the file. For sensitive one-off transfers, a direct end-to-end encrypted transfer leaves less exposure.

### Does Relay store my files?
No. Files go straight between the two browsers and are never stored on Relay's servers.
