b2KIT

Text Encryption / Decryption

Encrypt and decrypt text using AES-256, RSA, or other ciphers with password-based key derivation.

How to Use Text Encryption / Decryption

  1. 1

    Enter your text

    Type the message you want to encrypt or decrypt.

  2. 2

    Set a password

    Enter a secret key to use for the encryption.

  3. 3

    Encrypt or decrypt

    Click encrypt to protect or decrypt to reveal the message.

  4. 4

    Copy the result

    Click copy to grab the encrypted or decrypted output.

Tested tool guide Tested browser tools Checked August 16, 2026

What Text Encryption / Decryption does and how it behaves

Encryption turns readable text into an unreadable string of characters; decryption reverses it for anyone holding the same password, or the matching private key in RSA mode. The password never becomes the key directly: a password-based key-derivation function stretches it into the AES-256 key, and the salt and initialization vector needed to decrypt travel inside the output, so you can paste the ciphertext anywhere and recover the text later with the password alone. Everything runs in the browser - nothing is uploaded. The usual surprise: encrypting the same text twice never yields the same ciphertext, so outputs cannot be compared to check a password.

How the result is produced

1

Password to key

The password is stretched into the AES-256 key by a password-based key-derivation function, which mixes the password with a random salt and repeats hashing so that guessing attempts stay expensive. The salt is stored alongside the ciphertext so the identical derivation can be repeated at decryption time. Because the salt is chosen fresh for every run, the same password and plaintext never produce the same ciphertext twice.

2

What a wrong password returns

Decryption with the wrong password fails in one of two ways, depending on the cipher mode. If the mode authenticates the ciphertext with an integrity tag, the tool reports an error and returns nothing. Without that check, it silently returns garbage that may still look like plausible text. Either way, nothing about the real password is revealed - a wrong guess behaves exactly like a wrong key, which is the point.

Good uses

  • Sending a secret through an untrusted channel - a pastebin, a support ticket, a group chat. Encrypt, post the ciphertext publicly, and deliver the password by a separate route such as a phone call.
  • Keeping credentials or one-time tokens in a file or note that could be skimmed. Store only the ciphertext and decrypt when you actually need the value.
  • Directing a message to one specific recipient: with RSA, encrypt using their public key, and not even the person who encrypted it can read it back - only the private key holder can.

Limits and checks

  • Same input, different output: encrypting identical text with the identical password produces different ciphertext on every run, because the salt is random. Re-encrypting and comparing outputs proves nothing; decryption is the only test of a password.
  • A lost password is final. The key is derived from the password at the moment of use and never stored, so a forgotten password leaves the ciphertext permanently unreadable - including to the site's operators.
  • Weak password, weak security: AES-256 protects the derived key, not your choice of password. A short or common password can be guessed offline using the salt that ships with the ciphertext, which defeats the encryption entirely.

Common questions

I forgot the password. Can the tool recover my text?

No. The encryption key is derived from the password at the moment of use and is never stored anywhere, so there is nothing to recover or reset. Treat the password as the only copy of your data: keep it in a password manager, or keep a plaintext copy of anything you cannot afford to lose.

Can I send the ciphertext and the password in the same email?

Not if you want secrecy. An attacker who can read that one channel gets both pieces, and the encryption accomplishes nothing. The scheme assumes the two travel separately - ciphertext on one channel, password on another, such as a phone call or a message sent in person. If only one channel is compromised, the secret survives.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools