Encrypted text is only useful if you can turn it back into readable text when you need it, and only if the right password unlocks it. The AES Decryption Tool is the companion to the AES Encryption Tool on this site. It takes the Base64 ciphertext produced by that tool, together with the password used to encrypt it, and recovers the original plaintext in your browser. If the password is wrong, if the ciphertext has been changed, or if the text was not produced by the encryption tool, decryption fails with a clear error instead of producing misleading output. That strict behavior is a feature of authenticated encryption: it protects you from reading text that has been tampered with or decrypted with the wrong key.
What Is the AES Decryption Tool?
The AES Decryption Tool reverses the encryption performed by the AES Encryption Tool. It expects one specific format: Base64 text containing a 16-byte salt, followed by a 12-byte initialization vector, followed by the ciphertext, where the key was derived from the password with PBKDF2 using 100,000 iterations and SHA-256, and the cipher is AES-256-GCM. The tool decodes the Base64, splits out the salt and IV, re-derives the key from the password you enter, and asks the browser cryptographic library to decrypt and authenticate the ciphertext. If authentication succeeds, the original text is shown. If it fails for any reason, the tool reports that decryption failed and explains the likely causes: a wrong password, altered text, or input that is not output from the encryption tool.
The tool validates its input before attempting decryption. Text that is not valid Base64 produces an error telling you to paste the full output from the encryption tool. Text that decodes to fewer than 29 bytes is rejected as too short, because a valid output must contain at least the salt, the IV, and one byte of ciphertext. These checks catch the most common mistakes, such as pasting only part of the output, pasting text with extra characters, or pasting plain text that was never encrypted. The tool requires the Web Cryptography API over HTTPS in a modern browser, just like the encryption tool, and it explains the requirement if the API is unavailable.
Decryption, like encryption, happens entirely in your browser. The ciphertext and the password are never sent to a server. The decrypted text is shown in a read-only field, and you can copy it or download it as a plain text file. Because the decrypted text is sensitive by definition, you should handle it with the same care as the original plaintext.
How to Use the AES Decryption Tool
- Obtain the full ciphertext. Copy the complete Base64 block from the message, file, or note where it was stored. Make sure you include the first and last characters, with no missing lines and no extra text mixed in.
- Paste it into the Encrypted text field. Paste the Base64 text into the field labeled Encrypted text (Base64). The field accepts multiple lines, and leading or trailing whitespace is trimmed before processing.
- Enter the decryption password. Type the exact password that was used to encrypt the text. Passwords are case-sensitive, and even a single different character will cause decryption to fail.
- Show the password if needed. Tick Show password to check the password as you type it. This helps catch typing errors, especially with long random passwords, but keep the screen private.
- Click Decrypt. Press the Decrypt button. The tool shows a brief Decrypting message while it derives the key and decrypts, then displays the result.
- Read, copy, or download the plaintext. The decrypted text appears in a read-only field. Use Copy Decrypted Text to copy it, or Download .txt to save it as decrypted.txt. Handle the downloaded file carefully, because it contains the unprotected text.
- If decryption fails, check the likely causes. Confirm the password is correct, confirm the ciphertext is complete and unaltered, and confirm the text came from the AES Encryption Tool. Try copying the ciphertext again from the original source rather than retyping it.
Key Features of the AES Decryption Tool
- Matched format with the encryption tool. The tool implements the exact documented format, so any output from the AES Encryption Tool on this site decrypts here with the correct password, without configuration or extra parameters.
- Authenticated decryption. AES-GCM authentication means tampered ciphertext is rejected outright. You will never see silently corrupted plaintext presented as if it were genuine.
- Input validation with helpful errors. Invalid Base64, truncated input, and wrong-password failures each produce a distinct, plain-language error that points to the likely cause.
- PBKDF2 key re-derivation. The key is re-derived from the password and the salt stored in the ciphertext, using the same 100,000 iterations and SHA-256, so no key file is needed beyond the password.
- Copy and download options. Copy the plaintext for immediate use, or download it as a text file for storage. Both actions work from the read-only result field.
- Private by design. Everything runs locally in the browser. The ciphertext, password, and plaintext are never transmitted or stored by the site.
- Clear status feedback. A Decrypting message appears during processing, so you know the tool is working, and errors are shown in place of a result rather than as a blank page.
Practical Use Cases With Concrete Examples
Reading a message a colleague encrypted for you. A colleague emails you ciphertext and shares the password by phone. You paste the ciphertext here, enter the password, and read the message. The email itself remains unreadable to anyone else who can access the mailbox, because only the ciphertext was stored in it.
Recovering a stored private note. You encrypted a journal entry months ago and stored the ciphertext in a notes app. Now you want to read it. Paste the ciphertext and the password from your password manager, and the original entry appears. This is the normal round trip the two tools are designed for.
Verifying an encryption before deleting the original. Before you delete a plain-text original after encrypting it, decrypt a copy of the ciphertext here to confirm that the password is correct and the output is intact. This single check prevents the painful discovery that a password was mistyped during encryption.
Recovering handover credentials. A freelancer hands over a project with encrypted account details in the handover document. The client decrypts the details with the agreed password, uses them to take over the accounts, and then changes the passwords. The handover document can be archived safely because it contains only ciphertext.
Checking whether ciphertext was altered. If you suspect a stored ciphertext was edited, accidentally or deliberately, attempting decryption is a reliable test. Authenticated encryption will reject altered ciphertext, telling you that the stored copy cannot be trusted, rather than returning garbled text.
Learning how authenticated encryption behaves. Students can encrypt a message, change one character of the ciphertext, and observe that decryption fails completely. That experiment demonstrates the difference between authenticated encryption and older methods that would return corrupted output without warning.
Tips and Best Practices
- Copy, do not retype, the ciphertext. Base64 text is long and unforgiving. Retyping introduces errors that cause decryption to fail. Always copy and paste the full block.
- Double-check the password. Passwords are case-sensitive and space-sensitive. If decryption fails, re-enter the password carefully, using the show-password option to compare it with the password stored in your password manager.
- Keep the password separate from the ciphertext. Storing them together defeats the purpose of encryption. Keep the password in a password manager and the ciphertext wherever it needs to live.
- Handle decrypted text as sensitive data. Once decrypted, the text is plain and readable. Do not leave it open on a shared screen, do not paste it into untrusted applications, and delete downloaded copies when you no longer need them.
- Test the round trip before relying on it. Whenever you encrypt something important, decrypt a copy immediately to confirm the password and ciphertext work together. Do this before deleting the original.
- Use a trusted device. Decryption reveals the plaintext on the device you use. Only decrypt on a device you trust, free of malware that could capture the text or the password.
- Store the password durably. If the password is lost, the ciphertext is permanently unreadable. A password manager, with its own backup, is the right place for encryption passwords.
Limitations
The AES Decryption Tool decrypts only the format produced by the AES Encryption Tool on this site. It cannot decrypt output from other encryption programs, files encrypted with different settings, or text that was merely encoded with Base64. Base64 is an encoding, not encryption, and pasting Base64-encoded plain text here will fail because it lacks the salt, IV, and authentication tag the tool expects. The tool cannot recover a forgotten password, and there is no reset or recovery option: a wrong password and a tampered ciphertext produce the same failure, by design, because revealing which one occurred could help an attacker. The tool does not verify who created the ciphertext. Anyone with the password can produce valid ciphertext, so decryption proves only that the password is correct, not that the sender is who they claim to be. Like the encryption tool, it requires WebCrypto over HTTPS in a modern browser, and it handles text only, not files. Finally, the tool cannot protect plaintext after decryption. Once you copy or download the result, its safety depends on how you store and share it.
Frequently Asked Questions
Why does decryption fail when I am sure the password is right?
The most common cause is an incomplete or altered ciphertext. Check that you copied the full Base64 block, with no missing characters and no extra text. Also check for an extra space or a changed character in the password, and try copying the ciphertext again from the original source.
Can the tool decrypt files or output from other programs?
No. It decrypts only text in the specific format produced by the AES Encryption Tool on this site. Other programs use different formats, key derivations, or settings, and their output will not decrypt here.
What does it mean that decryption is authenticated?
It means the encryption includes a check value that decryption verifies. If the ciphertext was changed in any way, verification fails and the tool refuses to return plaintext, instead of returning corrupted text that might mislead you.
Is my password or decrypted text sent to a server?
No. Decryption happens entirely in your browser. The ciphertext, the password, and the plaintext never leave your device, and nothing is stored by the site.
What if I only have part of the ciphertext?
Partial ciphertext cannot be decrypted. The salt, IV, and full ciphertext are all required. You will need to obtain the complete original output from whoever encrypted the text or from wherever it was stored.
Can I decrypt the same ciphertext more than once?
Yes. Decryption does not consume or alter the ciphertext. You can decrypt the same block as many times as you like, on any device, as long as you have the password.
Understanding Decryption Errors in Detail
Decryption errors can be frustrating, because the tool deliberately gives the same failure message for a wrong password and for altered ciphertext. That sameness is a security property: if the tool distinguished the two cases, an attacker could use the distinction to learn whether a guessed password was correct even when the ciphertext was damaged, or vice versa. In practice, you can still diagnose the problem by checking the most likely causes in order. First, confirm the ciphertext is complete by comparing its length with the original, if you still have access to it, and by checking that no characters were lost when copying from an email client or messaging app that wraps long lines. Some apps insert line breaks or truncate very long pasted text, and a single missing character is enough to fail authentication. Second, confirm the password by checking it against the entry in your password manager, paying attention to capitalization, spaces, and similar-looking characters. Third, confirm the source: text produced by a different encryption program, or text that is only Base64-encoded and never encrypted, will fail in the same way, because it lacks the expected salt, IV, and authentication tag. Working through those three checks resolves nearly every failure. If all three check out and decryption still fails, the most likely explanation is that the stored ciphertext was corrupted at some point, for example by an editor that altered characters, and you will need an uncorrupted copy from the original source.
Related Tools
Use these tools together: the AES Encryption Tool creates the ciphertext this tool reads, the Password Generator creates strong encryption passwords, the Hash Checker verifies text integrity, the Text Decryptor handles simpler decoding tasks, and the Base64 Decoder decodes plain Base64 text. Find every tool from the homepage.