The safest way to send a password is through a different channel from the thing it unlocks. If you emailed an encrypted file, send the password by text message, an end-to-end encrypted messaging app, or a phone call, never in the same email or a follow-up email. For very sensitive material, read it out on a call to a number you already know belongs to the person. That way, someone who gets into one account or device does not get both the file and the key.
Here is how to choose the channel, how to make the password easy to pass on correctly, and the habits that stop the password becoming the weak link.
The one rule: separate the file and the password
Encryption turns a file into something useless without its password. The whole benefit disappears if the password travels with the file. The most common mistakes are:
- Putting the password in the same email as the encrypted attachment.
- Sending it in a second email a minute later. Both emails sit in the same mailboxes.
- Posting it in the same chat thread or shared folder as the file link.
- Writing it in the file name or the subject line, which happens more often than you would think.
If an attacker gets into your mailbox, the recipient's mailbox, or any account the message was forwarded to, they get both halves. Using two channels means they would need to compromise two separate things.
Which channel to use
| Channel | Security | Good for | Watch out for |
|---|---|---|---|
| Phone call | High | The most sensitive files | Call a number you already have, not one from the email |
| In person | High | Regular contacts, agreed passphrases | Not always practical |
| End-to-end encrypted messaging app | High | Most situations | Messages may sync to other devices; delete after use |
| Password manager sharing | High | Colleagues and family using the same manager | Both people need accounts |
| Text message (SMS) | Medium | Everyday client files sent by email | SMS is not end-to-end encrypted |
| One-time secret link | Medium | When nothing else is available | Do not send the link in the same email as the file |
| Same email or second email | Low | Nothing sensitive | Defeats the encryption |
For most people sending a tax return, a contract or medical paperwork by email, a text message to the recipient's known mobile number is a sensible balance. It means an attacker would need both the email account and the phone.
In a business setting
If your firm has a client portal, a secure messaging system or a policy on sending confidential files, use it, and follow the policy for passwords too. Where there is no policy, write a simple one: encrypted files go by email or cloud link, passwords go by text or phone to numbers held on the client record, and nobody sends a password in reply to an email request. Writing it down means everyone in the office does it the same way, and clients learn what to expect from you, which also makes impersonation easier to spot.
Make the password easy to pass on correctly
Passwords sent by phone or text get mistyped, and a mistyped password looks exactly like a wrong one. A few choices help:
- Use a passphrase. Five or six random words, such as "orbit candle maple fossil drift", are long and strong, and easy to read out or type from a text.
- Avoid look-alike characters such as capital O and zero, or lowercase l, capital I and the number 1, if you must use a random string.
- Avoid symbols that move between keyboards, like @, " and #, which sit in different places on US and UK layouts.
- Say how it is written: "all lowercase, spaces between the words".
A tool with a password generator makes this easier. Document Key includes a generator and strength meter when you encrypt files or create a share package, so you are not tempted to reuse an old password. For more on choosing passwords, see how to create a strong password for encryption.
Check you are sending it to the right person
Scammers sometimes ask for passwords by pretending to be the intended recipient. Before you send a password:
- Use contact details you already had, not ones from the email asking for it.
- If someone asks you to send the password to a new number or address, confirm by calling them on the number you already know.
- Be suspicious of urgency. "Please send the password now, I'm about to board a plane" is a classic pressure tactic.
Agreeing a password in advance
If you send files to the same person regularly, such as an accountant or a family member, you can agree a passphrase in person or on a call and use it for a period of time. It removes the step of sending a password each time.
The trade-off is that one leaked password exposes every file that used it. Keep the period short, for example one tax season, change it if you have any doubt, and do not use the same passphrase for anything else.
Reduce the damage if a password leaks
Even with good habits, things go wrong. You can limit the impact:
- Use a different password for each file or package, or at least for each recipient.
- Set an expiry date on shared files where you can. Document Key's secure sharing packages can carry an expiry date, so a package cannot be opened after a set time even if the password turns up later. Our guide to sending a file with an expiration date explains what expiry does and does not stop.
- Delete the password message once the recipient has opened the file, on both sides if you can.
- Never reuse an encryption password for an account login, such as email or banking.
A routine for sending an encrypted file
- Encrypt the file or create an encrypted package with a new, generated passphrase.
- Send the file by email or cloud link, with a note saying the password will follow by text or phone.
- Send the password by the agreed second channel, to contact details you already had.
- Confirm the recipient has opened it.
- Delete the password message and any unencrypted copies made for sending.
Our guide to sending encrypted files by email covers the file side of this routine, including size limits and blocked attachments.
Never send a password in reply to an unexpected request, even one that appears to come from someone you know. Call them first. This one habit stops a large share of document-related scams.
Frequently asked questions
Is it safe to text a password?
It is reasonable for most files when the encrypted file went by email, because an attacker would need both your email and your phone. For highly sensitive material, read it out on a call instead.
Should I send the password in a second email?
No. If someone has access to the mailbox, they get both emails. Use a different channel.
Can I reuse the same password for every file I send a client?
It is better not to. If one password leaks, every file using it is exposed. Use a different strong password for each package, or at least for each client.
