How to Create and Share Encrypted Text: A 3-Step Workflow

You need to share something sensitive — a password, a code, private information — but you don't want it readable in whatever channel you're using. This guide walks through the complete workflow: create the encrypted text, share it through any channel, let the recipient decrypt it. Three steps, under two minutes, no software required on either end.

Step 1: Encrypt Your Text in the Browser

Open the text encryption tool in any browser on any device.

In the Encrypt panel:

• Type or paste your sensitive text. This can be a single password, a paragraph, a list of credentials, or any text you want protected.
• Enter a password in the password field. This is the key that will lock and unlock your text. Make it strong and memorable.
• Click Encrypt.

You'll see a base64 cipher string appear in the output box. It will look something like:

3a9f2e...AABbCcDd1234...==

This cipher string is meaningless without the password. It's safe to paste into any document, email, message, or text field.

Copy the cipher string. That's your protected content.

Step 2: Share the Cipher String Through Any Channel

The cipher string can go anywhere. Channel security doesn't matter — it's unreadable without the password.

Options for sharing:

• Email — paste the cipher into the email body. Add a brief note: "Encrypted text below — decrypt using our agreed password."
• Slack or Teams — paste as a message. Use a code block (triple backticks) for cleaner formatting.
• Text message / WhatsApp — paste and send. Recipient copies the cipher from the message thread.
• Google Doc or Notion — paste into a shared document.
• Calendar invite or meeting notes — embed in any text field.
• GitHub issue or PR — paste into a comment.

The cipher will be an unusual-looking string in any of these contexts. A short context note helps the recipient know what to do with it.

Sell Custom Apparel — We Handle Printing & Free Shipping

Step 3: Share the Password Through a Different Channel

This step is the key to the entire workflow. Don't send the password through the same channel as the cipher.

If someone intercepts your email (which contains the cipher), they still can't decrypt it without the password. But if you put "password: XYZ" in the same email, you've handed them both halves of the lock.

How to share the password:

• Phone call — speak the password verbally. Not recorded by most services.
• Different channel — if cipher is in email, text the password. If cipher is in Slack, call them.
• Pre-agreed password — ideal for ongoing use with the same person. Agree on a shared password once (in person or by phone), and reuse it for future cipher shares.
• Secure messaging app — if one exists between you and the recipient, use it only for the password, not the cipher.

How the Recipient Decrypts the Text

The recipient needs:

1. The cipher string you sent
2. The password you shared separately
3. A browser

Steps for the recipient:

1. Open the same text encryption tool in any browser
2. In the Decrypt panel, paste the cipher string
3. Enter the password in the password field
4. Click Decrypt
5. Read the original plaintext

The recipient doesn't need an account, doesn't need to install software, and doesn't need to have any relationship with the tool provider. They just need a browser and the password you shared.

If the password is wrong, they'll get an error — not garbled text. This authentication is built into AES-256-GCM (the auth tag verifies the correct password was used).

Variations and Tips for Common Scenarios

Sharing with multiple recipients — encrypt once with a shared password, send the same cipher to all recipients. They each decrypt with the same password. Keep the group small to reduce password exposure risk.

Time-sensitive information — if the information is only valid for a short window, instruct the recipient to decrypt and then delete both the cipher and the plaintext after reading. Nothing about the tool enforces this, but the workflow can include the instruction.

Verifying the decryption worked — include a known phrase at the start of your plaintext: "If you see this, decryption was successful." The recipient can confirm decryption before reading sensitive content.

Re-encrypting for new recipients — if you need to send the same information to a different person with a different password, just re-encrypt the original plaintext with the new password. Each recipient gets their own cipher.

Frequently Asked Questions

Can the cipher string be too long to paste in some apps?

Most modern apps handle long text strings without issue. If you're pasting into an app with a character limit (like Twitter/X), the cipher string for long text might exceed it. For short text (passwords, codes), the cipher will typically be 200-400 characters.

Does the cipher expire or stop working after a certain time?

No. The cipher is a static string — it decrypts correctly as long as you have the right password, regardless of how much time has passed. The encryption has no built-in expiration.

What if the recipient makes a typo when pasting the cipher?

Any corruption of the cipher string will cause decryption to fail due to the AES-GCM authentication tag. Even a single character change will result in an error, not a garbled or partially decrypted output. This is a feature — it prevents accidentally reading corrupted data.

Can I forward the cipher to a third party later?

Yes. The cipher remains valid indefinitely. If you forward it to someone else and they have (or you give them) the password, they can decrypt it. This is worth considering when deciding which password to use — choose a password you haven't shared with others if you don't want it redistributable.