b2KIT

AES Encryption Tool

Encrypt and decrypt text using AES-256-GCM with password-derived keys via PBKDF2, entirely in the browser.

Tested tool guide Tested browser tools Checked August 16, 2026

What AES Encryption Tool does and how it behaves

This tool turns a password into an AES-256 key with PBKDF2, then uses that key to encrypt or decrypt the text you paste, using AES-GCM so tampering is detectable. Nothing leaves the browser. The mistake people make most often: assuming two encryptions of the same text with the same password produce the same output. They won't, because a fresh random salt and IV are generated each time, and both are needed later to decrypt, so the tool bundles them with the ciphertext in the output rather than making you track them separately.

How the result is produced

1

Password-based key derivation

Your password is not used directly as the AES key. PBKDF2 repeatedly hashes it together with a randomly generated salt to stretch it into a 256-bit key, which makes brute-forcing the password against a stolen ciphertext far more expensive than hashing it once. A new salt is generated for every encryption, so the same password never derives the same key twice.

2

Authenticated encryption with GCM

The derived key encrypts your plaintext under AES in Galois/Counter Mode with a freshly generated IV (initialization vector). GCM produces ciphertext plus an authentication tag; decryption fails outright if either the ciphertext or the tag has been altered, so corrupted or tampered input is rejected rather than silently decrypted into garbage.

Good uses

  • Encrypting a block of sensitive notes before pasting them into a shared doc, chat, or ticket you don't fully trust
  • Password-protecting a secret (API key, recovery phrase, one-off credential) so it can be sent over an insecure channel like email
  • Encrypting text before storing it in a browser bookmark, local file, or note-taking app that itself has no encryption

Limits and checks

  • Output is different every time you encrypt the same text with the same password, because the salt and IV are randomized per run - this is expected, not a bug, and it means you cannot use this tool to check whether two ciphertexts match
  • Security depends entirely on the password you choose; a short or common password is crackable regardless of how strong AES-256-GCM itself is, since the tool does not enforce password complexity
  • There is no password recovery. If you forget the password, the ciphertext is permanently unreadable - that is the intended behavior of the algorithm, not a limitation of this specific implementation

Common questions

Can I decrypt something I encrypted with OpenSSL or another AES tool?

Only if that tool used the exact same construction: AES-256-GCM, the same PBKDF2 iteration count and salt length, and the same way of packing salt, IV, ciphertext, and tag together. In practice, different tools rarely match on all of these, so treat this tool's output as compatible mainly with itself.

Is this safe enough for genuinely sensitive data, like financial or health information?

AES-256-GCM with PBKDF2 is a sound, standard construction, but this tool runs in your browser tab with no independent security audit stated on the page. For regulated or high-stakes data, that combination is a reasonable stopgap, not a substitute for a vetted, audited encryption product.

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