AES Decryptor

Decrypt AES JSON envelopes from InBrowser.App with the original password or raw hexadecimal key.

Encrypted JSON
Paste the AES JSON envelope from the encryptor or choose a local .json file. Nothing leaves this browser.

Choose a downloaded AES encryptor JSON file instead of pasting.

Key material
The JSON envelope declares whether decryption needs the original password or an exact-length raw AES key.

Password

Envelope details
Review the stored AES parameters before decrypting.
No envelope loaded
Paste or choose an AES encryptor JSON file to inspect its settings.
Plaintext
Successful decryption restores text for copying or file bytes for download.
No plaintext yet
Load an envelope, enter the matching key material, then run decryption.

AES decryption restores plaintext from data encrypted with the same AES key material. This tool is designed for the JSON envelope produced by the InBrowser.App AES Encryptor. The envelope keeps the algorithm, key derivation settings, salt, IV, ciphertext, and plaintext metadata together, while the password or raw key remains separate.

All work happens locally with the browser Web Crypto API. The encrypted JSON, password, raw key, and decrypted result are not uploaded.

When To Use This Tool

Use it when someone gives you an inbrowser-aes-v1 JSON envelope or when you need to recover a note, token, configuration snippet, or file that you encrypted earlier with the matching AES Encryptor page.

If the envelope was created with a password, enter the same password and the tool will reuse the stored PBKDF2 hash, iteration count, salt, AES mode, and key length. If the envelope was created with a raw key, paste the exact hexadecimal key length recorded in the envelope.

Practical Notes

AES-GCM authenticates the encrypted data, so wrong keys or changed JSON should fail instead of returning altered plaintext. AES-CBC and AES-CTR can decrypt compatible envelopes, but they do not authenticate ciphertext by themselves.

Keep the password or raw key separate from the JSON envelope. Anyone with both the envelope and the key material can recover the plaintext. For file envelopes, the recovered download uses the original filename and media type stored in the JSON.