Sometimes a message should only be readable by the person it is for. This encryptor turns any text into an unreadable blob using AES-256-GCM — the same encryption standard used by banks and messaging apps — with a passphrase you choose. The blob can be pasted into an email, a chat or a note; only someone with the passphrase can turn it back into the message.
How to use
- Choose “Encrypt a message”, type the message and a strong passphrase, then press “Encrypt message”.
- Copy the blob (it starts with “ST-AES1.”) and send it to the recipient.
- Share the passphrase separately — never in the same message as the blob.
- To read a message, choose “Decrypt a message”, paste the blob, enter the passphrase and press “Decrypt message”.
About this AES text encryptor
The passphrase is never used directly as a key. It is stretched with PBKDF2 — 100,000 rounds of SHA-256 with a fresh random salt — into a 256-bit key, and the message is encrypted with AES-GCM, which also authenticates the result: if even one character of the blob is changed, decryption fails instead of producing garbled text. Each encryption uses a new random salt and IV, so encrypting the same message twice gives two different blobs. The output packs the salt, IV and ciphertext into a single Base64 string, so there is only one thing to copy and paste. Everything runs in your browser with the built-in WebCrypto API; no server is involved.
How do I use this tool?
- Pick Encrypt or Decrypt from the mode dropdown.
- Type the message (or paste a blob) and enter the passphrase.
- Press the main button and copy the result with “Copy result”.
- Use “Clear” to wipe the fields when you are done.
Where is this tool used?
Sending a password, account detail or private note through a channel you do not fully trust; storing a sensitive note where only the passphrase holder should read it; and sharing credentials with a colleague without leaving them in plain text in chat history. It is also a practical way to learn how modern encryption works — the same construction (PBKDF2 + AES-GCM) protects real applications.
What are the limitations?
The security is only as good as the passphrase: a short or guessable passphrase can be brute-forced, so use a long, random one. The blob only protects the message itself — it does not hide who sent it, when, or through which service. And there is no recovery: lose the passphrase and the message is unreadable forever, so keep the passphrase somewhere safe before you encrypt something important.
Frequently asked questions
Is my message uploaded anywhere?
No. Encryption and decryption run entirely in your browser. Your message and passphrase never leave your device, and nothing is stored.
What does the ST-AES1. blob contain?
One Base64 string holding three parts: a random salt (16 bytes), a random IV (12 bytes) and the AES-256-GCM ciphertext. The salt and IV are not secret — they just make every encryption unique — but the passphrase is essential.
Can I decrypt a message encrypted somewhere else?
Only if it was made with this same format. Blobs from other tools use different formats and key derivation, so this page only decrypts blobs that start with “ST-AES1.”.
What happens if I forget the passphrase?
The message cannot be recovered — by you, by us, or by anyone. That is the point of encryption. Store the passphrase safely before encrypting anything you cannot afford to lose.
How strong is AES-256-GCM?
It is the current standard for protecting data, used by governments, banks and messaging apps. With a strong passphrase and the PBKDF2 stretching used here, it is considered secure against any practical attack.
Updated November 2026 · Built and tested by Sharjeel Tahir · How our tools are tested