Security Insights · Sending documents · 8 min read
How to Send Documents Securely: 6 Methods Compared
How to send documents securely: email attachments, password-protected files, cloud links, SFTP, encrypted email and end-to-end encrypted sharing compared.
Attaching a file to an email or pasting a share link gets a document to its recipient. Neither one, on its own, decides who else can open the file, how long it stays available or whether you can tell who downloaded it.
This guide compares six common ways to send and share files securely, explains what each one protects, and ends with a step-by-step method for sending a sensitive document, including one that's too large for email.
How do you send documents securely?
To send a document securely, encrypt the file itself so only the intended recipient can open it, rather than relying on an encrypted connection alone. Then control access: confirm the recipient's address, set an expiry date, keep the ability to revoke access, and use a method that logs who opened or downloaded the file.
Two kinds of encryption are involved: in transit, while a file crosses a network, and at rest, while it's stored. NIST's control catalog, SP 800-53 Rev. 5, treats them as separate controls (SC-8 and SC-28), so a method can provide one without the other. The third question is who holds the keys, because whoever holds them can read the file.
Six ways to send documents, compared
The table compares six common methods on the questions that decide whether a sensitive document stays protected.
| Email attachment | Password-protected ZIP or PDF | Consumer cloud storage link | SFTP server | Encrypted email (S/MIME or OpenPGP) | End-to-end encrypted sharing platform | |
|---|---|---|---|---|---|---|
| Encrypted in transit | Only between mail servers that use TLS | Yes, the file itself is encrypted | Yes, over HTTPS | Yes, over SSH | Yes, end to end | Yes, end to end |
| Encrypted at rest | Depends on each mail provider | Yes, every copy stays encrypted | Usually, by the provider | Only if server storage is encrypted separately | Yes, except headers such as the subject line | Yes, stored as ciphertext |
| Who holds the keys | No file encryption: mail providers can read it | Anyone who knows the password | Usually the provider | The server operator | Sender and recipients, with their own private keys | Users' devices, not the platform |
| Can you revoke access? | No | No | Usually, by disabling the link | Yes, by removing the account or file | No | Yes, usually with expiry dates too |
| Opens and downloads logged | No | No | Varies by service | Depends on server settings | No | Usually, in an audit log |
| Large files | Limited by mail server size limits | Limited by the channel used | Good, within plan limits | Good, including automated transfers | Limited by mail server size limits | Varies; some have no file size limit |
What each method protects
Email attachment
A standard attachment is only as protected as each mail server on its route. STARTTLS, which adds TLS to mail delivery, is opportunistic, and its standard, RFC 3207, states that "SMTP is not an end-to-end mechanism": encrypting one hop doesn't make the whole chain private. RFC 8461 adds that an attacker who can tamper with the mail session can downgrade or intercept it.
NIST's Trustworthy Email guide (SP 800-177 Rev. 1) notes that attackers and privileged insiders can read unencrypted mail on the systems that submit and deliver it. The Australian Signals Directorate's Information Security Manual includes controls for opportunistic TLS and MTA-STS on email servers. Both protect mail between servers only: the attachment stays readable to each mail provider, and it can't be recalled once delivered.
Password-protected ZIP or PDF
Encrypting the file itself protects every copy, wherever it ends up. Its strength depends on the method and the password. Traditional ZIP encryption is weak by today's standards, so choose AES-256 when your tool offers it. Use a long, random password and send it by a different channel, such as a phone call. Once the recipient has it, you can't withdraw access or see who opened the file.
Consumer cloud storage link
A consumer cloud storage link avoids attachment size limits, and the file travels over HTTPS. The provider usually encrypts stored files but also holds the keys, so its systems can decrypt them. Links that work for anyone who has them can be forwarded, and activity records vary by service and plan. Disabling a link stops new access but doesn't reach copies already downloaded.
SFTP server
SFTP encrypts the whole session between client and server over SSH. The encryption ends at the server: unless the server's storage is encrypted separately, files sit there in readable form, and anyone with administrative access can open them. Each recipient also needs an account and an SFTP client. Our guide to SFTP vs FTPS covers the protocol in detail.
Encrypted email: S/MIME or OpenPGP
S/MIME (RFC 8551) and OpenPGP (RFC 9580) encrypt the message and its attachments in the sender's email software, so only the recipient's private key can decrypt them. NIST's Trustworthy Email guide recommends S/MIME for protecting email content. The catch is setup: the sender needs each recipient's public key before sending. With S/MIME, header fields such as the subject line stay unprotected unless the whole message is wrapped, and a sent message can't be revoked.
End-to-end encrypted sharing platform
An end-to-end encrypted sharing platform encrypts each file on the sender's device and decrypts it only on the recipient's, so the platform stores ciphertext it can't read. The software manages the keys, so there are no certificates to exchange. Because the file stays on the platform, the sender can set permissions and expiry dates, revoke access and see who opened it. CISA's mobile communications guidance for highly targeted individuals puts using only end-to-end encrypted communications first on its list. Our explainer on end-to-end encryption covers how it works.
How to send a sensitive document, step by step
- Check how it must be handled. If the document is marked, for example as Controlled Unclassified Information (CUI), or holds personal, health or legal information, its handling rules decide which methods you can use.
- Send only what's needed. If you redact, delete the underlying text rather than covering it.
- Encrypt the file, not just the connection. Use encrypted email or an end-to-end encrypted sharing platform; a strongly encrypted ZIP or PDF is the fallback.
- Confirm the recipient's address against a contact record you already trust, not an address from an unexpected request.
- Grant the least access needed: view only if the recipient doesn't need a copy, with an expiry date.
- Send any password by a different channel, never in the same email thread.
- Confirm receipt and close access. Check the access log, then revoke access when the work is done.
How to send large files securely
Email is the weakest option for large files. Attachments are usually converted to base64 text for transport, which the MIME standard, RFC 2045, notes makes data about 33 percent larger. Mail servers also set their own maximum message size and can announce it to senders (RFC 1870), so a large message can be rejected anywhere along the route.
For very large files:
- Use an end-to-end encrypted sharing platform without file size limits, or SFTP for system-to-system transfers, with stored files encrypted separately.
- Prefer tools that resume interrupted uploads, so a dropped connection doesn't restart the transfer.
- Have the recipient compare a checksum, such as a SHA-256 hash, to confirm the file arrived intact.
- Don't ship unencrypted drives. If physical media can't be avoided, encrypt it and send the password separately.
Where DekkoCORE fits
DekkoCORE is an end-to-end encrypted platform for sending and sharing documents. Files are encrypted on the sender's device with AES-256 keys before they're uploaded, DekkoCORE stores only ciphertext, and files are decrypted on the recipient's device as they open them. Keys are handled automatically in the background, so users never see a key. Each share gets one of seven permission levels, an optional expiry date and instant revocation, and every view and download is logged.
There are no file size limits, DekkoCORE runs in the browser with no agents or plug-ins to install, and an Upload Accelerator app for Windows handles large and bulk uploads. Secure mail is end-to-end encrypted the same way files are and can be revoked after it's sent. Read more about secure file sharing.
Common questions
Frequently Asked Questions
Is it safe to send sensitive documents by email?
A standard email attachment is protected only while it travels between mail servers that use TLS, and copies stay readable to each mail provider. Once delivered, it can't be recalled. For sensitive documents, use encrypted email or an end-to-end encrypted sharing platform.
Is a password-protected PDF secure enough?
A password-protected PDF or ZIP file is only as strong as its encryption method and its password. Use AES-256 where offered, a long random password and a separate channel for the password. Once the recipient has the password, you can't withdraw access.
What is the most secure way to send documents?
End-to-end encryption, where the file is encrypted on the sender's device and decrypted only on the recipient's, protects a document at every point between them. Encrypted email and end-to-end encrypted sharing platforms both work this way; sharing platforms add revocation, expiry dates and access logs.
How do I send a file that's too large for email?
Use an end-to-end encrypted sharing platform without file size limits, or SFTP for system-to-system transfers, instead of splitting the file across emails. Have the recipient compare a checksum to confirm it arrived intact.
Is SFTP secure for sending documents to clients?
SFTP encrypts files in transit over SSH, but they're stored in readable form on the server unless its storage is encrypted separately. Each recipient also needs an account and an SFTP client, so SFTP suits system-to-system transfers better than sending documents to people.
Can you unsend a document after sharing it?
You can't recall a delivered email attachment. Share links and sharing platforms let you revoke access or set an expiry date, but no method deletes a copy the recipient has already downloaded.