AES Decryptor

Paste the encryptor output and the same password.

Use this tool

Result

The result appears in this panel after you run the tool.

About this tool

A wrong password fails the authentication tag.

This does not decrypt unrelated AES formats.

How to use it

  1. Open this page and provide the input it asks for.
  2. Set the options that are visible, then use Decrypt.
  3. Read the result in the panel. Copy it or download it when a file is offered. The input stays in this browser.

Limitations

The tag fails closed

Where the nonce comes from

The password must still be at least four characters. The box must be the base64 package the encryptor wrote. After the base64 decode, the first 16 bytes are the salt, the next 12 are the IV, and the rest is the ciphertext including the GCM tag. The key is derived again with PBKDF2-SHA-256, 100000 iterations, and AES-256-GCM, using that salt rather than a new one. Decrypt uses the IV from the package. This page does not call getRandomValues for a nonce. Minting a new nonce would make the ciphertext undecryptable, so the stored nonce is the only one that can work.

That is why the encryptor generates a new IV every time. The nonce that lands in the package must be unique for that derived key. On this side the rule is the opposite: reuse the nonce that was stored, and reject the message if the tag does not match. You do not get to pick a different IV and still recover the text.

How failure looks

A wrong password derives a different key, the tag check fails, and Web Crypto throws. Flipped ciphertext or a truncated package fails the same way. You do not receive a plausible wrong plaintext. The panel shows the error. Bad base64 throws before the cipher runs. A package that is valid base64 but too short to slice into salt, IV, and tag fails on decrypt. The page does not try other layouts. A string that is base64 of something else, including a PEM or a bare hash, is not decrypted by relaxing the format.

What success means

Success means the password, salt, IV, and tag agreed, and the UTF-8 plaintext is shown. It does not mean a third party audited the message. It does not mean the encryptor page was the only software that could have built the package, only that the bytes match this layout and this KDF. It does not rotate the password. If you need a new package under a new password, encrypt again on the encryptor, which will draw a new salt and a new IV. Decrypting twice with the same package yields the same text. There is no second layer to peel.

Privacy

Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.