How to share a password without texting it

You text someone the wifi password, or the login for the account you both use, and the job feels done. It is not done. That password is now a line of plain text living in two phones, probably backed up to two clouds, sitting in a thread you will both forget to clean up. Anyone who picks up either phone, or pulls either backup, can read it months from now. The convenient way to send a password is also the way that keeps it readable forever in the worst possible places.

So the real question is not how to send a password fast. It is how to get it to one person without leaving a readable copy behind. There are a few honest answers, and the right one depends on what kind of password it is.

The case against texting (and emailing) it

Plain text in a chat or an email has no protection on the way and no expiry once it lands. It can be forwarded with two taps. It shows up in notification previews on a lock screen. It survives in the sent folder, the recipient's inbox, and every backup either account ever made. None of that requires a hacker. It just requires someone, sometime, scrolling back far enough. A password is supposed to be a secret, and a secret loses most of its value the moment it exists as searchable text in a place you do not control.

The good options, honestly ranked

If you and another person share a login you both use all the time, a shared password manager vault is the right tool, full stop. Apps like 1Password, Bitwarden, and LastPass let you share an entry so the other person can use the credential without the plain text ever being handed around, and you can pull access back later. That is what they are built for, and nothing here replaces it for an account two people log into every week.

For a one-time handoff, an encrypted link that self-deletes after one view (Bitwarden Send is the common example) is a solid choice. So is reading it out loud on a phone call, which sounds old-fashioned and is genuinely hard to beat for something short. An encrypted messenger with disappearing messages, like Signal, is better than a normal text because the copy is meant to go away on both ends. Each of these is a real improvement over a green or blue bubble, and for a lot of people one of them is the answer.

They share one assumption worth noticing: the password still travels as text, just through a safer pipe. That works right up until the pipe is the problem. The link gets forwarded before it is opened. The disappearing message gets screenshotted. The call gets overheard. For most everyday passwords that risk is fine. For the handful where it is not, there is another shape worth knowing.

Hand it over inside something ordinary

The other approach is to not send readable text at all. Instead of a password in a message, you send something that looks like a normal photo or a normal QR code, and the actual password sits hidden inside it. To anyone who sees that photo, it is just a photo. The one person you meant it for opens it in an app, with a key you give them, and reads what is inside.

This is the model GhostCode uses. You write the password as a message, set a Key, and you get back an everyday-looking photo or QR code to send however you like, including over the same text thread you were going to use anyway. The trick is what you do with the Key. You share the Key on a different channel than the message itself: say it in person, or on a call, while the photo goes by text. Someone who intercepts the thread gets a picture and nothing to open it with. Someone who overhears the Key has no message to use it on. The two halves never travel together, so catching one is not enough.

That separation is the whole point, and it lines up with how the better methods above work: keep the secret and the means to read it apart. The difference is that what lands in the thread is not a disguised password, it is a normal-looking carrier with nothing readable on its face. If you want the mechanics of the carrier side, the walkthrough on putting a hidden message in a QR code covers the QR version, which is a natural fit for a wifi password a guest can scan.

Be honest about the limits

None of this is magic, and a tool that pretends to be is the dangerous kind. The person on the other end needs the app and the Key, so this is for someone you can hand a Key to, not a stranger. A screenshot taken while the message is open is out of everyone's control, including ours. If you would not want a particular person holding a still of that password, no app fixes that. Choosing who you send it to is still the real control.

And to repeat the part that matters: this is not a password manager. It does not store your logins or fill them in. It is for the handoff, the moment you need to get one secret to one person without leaving a readable copy in a chat log. For a guest wifi code, set a Self-Destruct timer so the message stops opening once the weekend is over and the credential stops being live.

The plain version of all this: stop putting passwords in places that keep them readable forever. Use a shared vault for the logins you both live in. For the one-off, send the secret one way and the key to it another, so no single screen ever holds both.