[ENCRYPT TEXT ONLINE]

Turn a message into ciphertext you can paste anywhere — email, chat, a ticket, a note.

Paste your message, choose a password or generate a random key, and get back a block of base64 ciphertext. Anyone with the key can turn it back into the original message; anyone without it sees nothing usable. The encryption uses AES-256-GCM and runs entirely in your browser.

This is the practical way to put something sensitive through a channel you do not trust — a shared inbox, a chat log that gets archived, a support ticket, a pull request comment.

ENCRYPT_FILE_ONLINE_v1.0.0
🔒 [ENCRYPT] 🔓 [DECRYPT]

[1] SELECT FILE

[2] CHOOSE ENCRYPTION ALGORITHM

[4] ENCRYPT FILE

[WHEN ENCRYPTING TEXT IS THE RIGHT TOOL]

  • Sending credentials to a colleague. API keys, database passwords and access tokens routinely end up sitting in plain text in chat history for years. Encrypting the message and passing the password by another route fixes that.
  • Notes in a shared or synced service. Anything stored in a notes app or spreadsheet the whole team can read.
  • Recovery codes and seed phrases. Two-factor backup codes kept somewhere convenient but not private.
  • Personal information over email. Email hops through several servers in the clear; the body is readable at each one.

Because the output is plain base64 text, it survives copy-paste through any system that handles text — no attachments and no special client on the other end.

[GETTING THE PASSWORD TO THE RECIPIENT]

This is where message encryption usually goes wrong in practice. Sending the ciphertext and the password through the same channel provides no protection at all — anyone reading that channel has both halves.

  • Send the encrypted text by email, and the password by phone or SMS
  • Send the encrypted text in a chat, and read the password aloud in a call
  • Agree a shared passphrase in person, ahead of time, and reuse it for the exchange

The principle is simply that compromising one channel should not be enough. It is a low bar, and it is the one most leaks fail to clear.

[HOW THE TEXT ENCRYPTION WORKS]

Text mode uses AES-256-GCM, an authenticated cipher: it both conceals the message and detects any modification to the ciphertext. If a single character of the encrypted block is altered, decryption fails outright rather than returning a subtly wrong message.

When you supply a password, the key is derived with PBKDF2-HMAC-SHA256 at 600,000 iterations using a fresh 32-byte random salt. A new random 96-bit initialisation vector is generated for every message, so encrypting the same text twice produces two entirely different outputs — a property that matters, because identical ciphertexts would otherwise reveal that you had sent the same message twice.

Salt, IV and ciphertext are packed into the single base64 block you copy, so the recipient needs nothing but that block and the password.

[HOW TO ENCRYPT TEXT ONLINE]

Encrypt a text message with AES-256-GCM in your browser and share it safely.

  1. Enter your message. Type or paste the text you want to encrypt into the text field.
  2. Choose a password or random key. Enter a password, or have the tool generate a random 256-bit key. Use the built-in generator if you need a strong password.
  3. Encrypt. Click encrypt. AES-256-GCM encryption runs locally in your browser and produces a base64 block.
  4. Copy and share. Copy the encrypted text and send it however you like. Send the password through a different channel.

[FREQUENTLY ASKED QUESTIONS]

How do I encrypt a text message online?

Paste the message into the tool on this page, choose a password or generate a random key, and click encrypt. You receive a base64 block that can be pasted into email, chat or any other text field. The recipient decrypts it with the same password.

Is my text sent to a server?

No. Encryption happens in your browser using the Web Crypto API and nothing is transmitted. You can check this in the Network tab of your browser developer tools, or disconnect from the internet after the page loads and confirm it still works.

What encryption is used for text?

AES-256-GCM, an authenticated encryption mode that provides both confidentiality and tamper detection. Passwords are converted into keys with PBKDF2-HMAC-SHA256 at 600,000 iterations, with a random salt and a random IV generated for every message.

How long can the text be?

Up to 10,000 characters, which comfortably covers messages, credentials, recovery codes and notes. For anything longer, save it as a text file and use the file encryption tool instead.

Can I encrypt a text file rather than pasting text?

Yes — use the file encryption tool for that. It preserves the file exactly, including its name and encoding, and has no size limit. Pasting into text mode is better suited to short messages you intend to paste somewhere else.

Why does the same message produce different ciphertext each time?

A fresh random IV and salt are generated for every encryption, so the output differs even for identical input and password. This is intentional and important: identical outputs would let an observer detect that you had sent the same message more than once.