---
title: How to Send an Encrypted File (Free, No Account Needed)
date: 2026-11-17
description: Four ways to send an encrypted file, from a one-time link in your browser to 7-Zip and GPG. What actually gets encrypted, where the password goes, and which method to pick.
tags: ["encryption", "file-sharing", "how-to", "privacy", "one-time-links"]
---

# How to Send an Encrypted File (Free, No Account Needed)

Tax documents, a scan of your passport, a contract, a medical record, a database export. Some files shouldn't sit in an email attachment or a shared drive link forever. Encrypting them first means that even if the copy leaks, it's useless without the key.

Here are four ways to do it, from easiest to most technical.

## Method 1: A one-time encrypted link (easiest)

Upload the file to a service that encrypts it in your browser and gives you a link that works once.

With [Dropzone](https://dropzone.sh):

1. Go to [dropzone.sh](https://dropzone.sh) and drop in the file (up to 100MB).
2. Copy the link and send it by email, chat or text.
3. The recipient opens the link and clicks Reveal. The file is decrypted in their browser and downloaded.
4. The encrypted copy is deleted from Dropzone's servers.

**Why it's secure:** the file is encrypted with AES-256-GCM before it leaves your computer. The key is in the part of the link after `#`, which browsers never send to servers, so Dropzone only stores ciphertext. Even the filename is encrypted.

**Why it's convenient:** the recipient doesn't need an account, a password or any software, and there's no separate password to send.

**The trade-off:** whoever has the link can open it, so send it through a channel only your recipient can read. If they find it already opened, someone else got there first.

## Method 2: An encrypted zip with 7-Zip

[7-Zip](https://www.7-zip.org) (Windows) and similar tools on Mac and Linux can create a password-protected archive with AES-256 encryption.

1. Right-click the file and choose **7-Zip → Add to archive**.
2. Choose the **7z** format, set **Encryption method** to **AES-256**, and enter a strong password.
3. Tick **Encrypt file names**.
4. Send the archive however you like, and **send the password through a different channel**, for example by text message, or with a [one-time link](/blog/how-to-send-a-password-securely).

**Watch out:** the older "ZipCrypto" encryption in standard `.zip` files is weak. Use 7z with AES-256. And the archive stays in the recipient's inbox forever, so its safety depends entirely on the password.

## Method 3: GPG (for technical users)

If your recipient has a GPG public key, you can encrypt the file so only their private key can open it:

```sh
gpg --encrypt --recipient their@email.com report.pdf
# produces report.pdf.gpg
```

This is very secure and there's no shared password to send, but both people need GPG set up, which rules it out for most recipients.

## Method 4: The command line, end to end

If you'd rather not trust a website's JavaScript, the [Dropzone CLI](https://dropzone.sh/dropzone.mjs) is a single file you can read before you run it. It encrypts on your machine and prints a one-time link:

```sh
curl -fsSO https://dropzone.sh/dropzone.mjs
node dropzone.mjs send contract.pdf
```

The recipient can open the link in a browser, or with the CLI:

```sh
node dropzone.mjs open "$LINK"
```

The CLI supports files up to about 4MB; use the website for larger files.

## Which method should you use?

| Situation | Best method |
| --- | --- |
| Sending to someone non-technical | One-time link |
| The file is large (up to 100MB) | One-time link in the browser |
| The recipient needs to keep the file in an archive | 7-Zip with AES-256, password sent separately |
| Both of you already use GPG | GPG |
| You're scripting it or using an AI agent | Dropzone CLI or [API](/agents) |

## Common mistakes

- **Sending the password in the same email as the file.** Then the encryption protects nothing.
- **Using a weak password on a zip file.** Archive passwords can be attacked offline at high speed. Use a long, random one.
- **Assuming "encrypted in transit" means encrypted.** HTTPS and email TLS protect the file on the way. The copy stored at the other end is not encrypted unless you encrypted it first.
- **Leaving the file in cloud storage.** A "shared with anyone with the link" file in a drive lives until someone remembers to delete it.

---

**Related:** [The hidden risks of cloud storage](/blog/the-hidden-risks-of-cloud-storage) · [Best secure file sharing tools](/blog/best-secure-file-sharing-tools-in-2025)
