Home › All Tools ›

Text Decryptor

Use Text Decryptor online for free at FreeToolZones — no sign-up, no watermark.

Loading tool...

Encrypted text is only useful if it can be read again by the right person. The Text Decryptor on FreeToolZones is the companion to the Text Encryptor: it takes Base64 output produced by the encryptor, together with the password used to encrypt it, and restores the original readable text. Decryption runs entirely in your browser, using the same modern AES-256-GCM method and password-derived key as encryption. A wrong password, an incomplete copy, or damaged output causes decryption to fail with a clear message rather than producing garbled text. This article explains how decryption works, how to use the tool step by step, and how to troubleshoot the common failures.

What Is the Text Decryptor?

The Text Decryptor is a free online tool that reverses encryption performed by the Text Encryptor on FreeToolZones. You enter the password that was used to encrypt the text, paste the Base64 encrypted output, and press Decrypt text. The original text appears in a read-only output box, with buttons to copy it or download it as a plain text file. Everything runs in your browser using WebCrypto, and nothing is sent to a server. The tool can only decrypt output in the encryptor’s format: Base64 text containing a 16-byte salt, a 12-byte initialization vector, and AES-GCM ciphertext, produced with a PBKDF2-derived key using 100,000 iterations and SHA-256.

Decryption begins by validating the input. White space in the pasted text is removed, and the remaining string must be valid Base64 with a length that is a multiple of four, using only the Base64 alphabet. If it is not, the tool shows an error asking you to paste the complete encrypted output from the Text Encryptor. The decoded bytes must also be longer than 28 bytes, the combined size of the salt and vector, or the tool reports that the encrypted text is too short or incomplete. These checks catch the most common copying errors before any cryptographic work begins.

Once validated, the tool splits the bytes into salt, vector, and ciphertext, re-derives the key from the password and the salt using PBKDF2, and attempts AES-GCM decryption. AES-GCM is authenticated, which means decryption verifies that the ciphertext has not been altered and that the key is correct. If the password is wrong, or the ciphertext is incomplete or damaged, decryption fails as a whole and the tool shows an error asking you to check both the password and the encrypted text. No partial or garbled output is produced, which is a security feature: an attacker cannot learn anything from a failed attempt beyond the fact that it failed.

How to Use the Text Decryptor

Decrypting text takes four steps. You need both the complete encrypted output and the exact password used to encrypt it. Either one alone is not enough.

  1. Enter the password used to encrypt. Type the password in the Password field. The hint reminds you to use the same password that was used to encrypt the text. Passwords are case-sensitive and space-sensitive, so type it exactly, including capitals and any spaces that were part of it. If the field is empty, the tool shows an error asking for the password.
  2. Paste the encrypted Base64 text. Paste the complete output from the Text Encryptor into the Encrypted text box. Copy the full string from the first character to the last, with nothing missing and nothing added. If the box is empty, the tool shows an error asking you to paste the encrypted text.
  3. Press Decrypt text and wait briefly. Press the Decrypt text button. The button is disabled while decryption runs, and the status shows Decrypting. Key derivation takes a short moment, as it did during encryption.
  4. Read, copy, or download the decrypted text. On success, the original text appears in the Decrypted text box, and the status confirms that decryption succeeded. Press Copy result to copy it, or Download .txt to save it as decrypted-text.txt. Handle the readable text carefully, because it is no longer protected once decrypted.

Decryption requires a secure HTTPS page and a modern browser with WebCrypto support, just as encryption does. If either is unavailable, the tool shows an error explaining that decryption is not available in the browser or connection. Use a modern browser over HTTPS and try again.

Key Features of the Text Decryptor

  • AES-256-GCM decryption with authentication. Decryption verifies the ciphertext as it decrypts, so a wrong password or altered output fails cleanly instead of producing misleading partial text.
  • PBKDF2 key re-derivation. The key is rebuilt from the entered password and the salt stored in the output, using 100,000 iterations and SHA-256, matching the encryption process exactly.
  • Base64 input validation. The tool checks that the input is valid Base64 and long enough to contain the salt and vector, with specific error messages for invalid, short, or incomplete input.
  • Self-contained input format. The encrypted output carries its own salt and vector, so decryption needs only the output string and the password, with no separate files, settings, or key exchange.
  • Browser-only operation. Decryption runs entirely in your browser using WebCrypto. The password, ciphertext, and plaintext are never sent to a server or stored by the tool.
  • Copy and download. Copy result places the decrypted text on the clipboard, and Download .txt saves it as decrypted-text.txt in plain text format.
  • Clear failure messages. Missing password, missing input, invalid Base64, short input, unavailable WebCrypto, and failed decryption each produce a distinct message explaining what to check.

The output box is read-only, so the decrypted text you copy is exactly what the tool produced. If the decrypted text looks wrong, do not edit it in the tool; instead, recheck the password and the completeness of the pasted output and decrypt again.

Practical Use Cases for the Text Decryptor

Reading a message encrypted by a colleague

A colleague sends an encrypted note by email and shares the password by phone. The recipient pastes the Base64 string into the decryptor, enters the password from the call, and reads the original note. The separation of channels means that access to the email alone reveals nothing, and access to the phone call alone reveals only a password with no ciphertext to unlock. After reading, the recipient deletes the readable copy from downloads or clipboard history if the content must remain protected.

Recovering your own protected notes

A user who encrypted personal notes before storing them in a shared location returns to read one. Pasting the stored Base64 string and entering the password restores the note exactly as written. Because the tool stores nothing, the user must keep the encrypted strings in their own files and the password in a safe place. Losing either one means the note cannot be read again, which is the intended consequence of real encryption.

Verifying an encryption round trip

After encrypting an important text, a careful user decrypts the output immediately and compares the result with the original. A matching result proves that the password was recorded correctly, the output was copied completely, and the encryption process worked. This verification step should happen before the original readable text is deleted, because it is the last chance to catch a password typo or a copying error at no cost.

Accessing secrets stored in shared documents

A team stores an encrypted access code in a shared document that many people can read. Only team members who know the password can decrypt it. A new team member who receives the password through a trusted channel pastes the stored string into the decryptor and obtains the code. Team members who never receive the password see only Base64 text. When the code changes, the old string is replaced with a newly encrypted one, and the password is rotated if the old one may have spread too widely.

Demonstrating authenticated encryption

A teacher demonstrating modern encryption encrypts a sentence, then changes one character in the Base64 output and attempts decryption. The attempt fails entirely, showing that AES-GCM authentication detects tampering. Changing one character in the password produces the same failure, showing that decryption is all or nothing. These demonstrations teach why modern encryption is stronger than simple scrambling or reversal, where a small change produces a small, readable error.

Tips and Best Practices

  • Copy the full encrypted string. Select from the first character to the last, including any trailing equals signs used as Base64 padding. A truncated copy is the most common cause of decryption failure, and the short input error is the clue.
  • Type the password exactly. Passwords are sensitive to capitals, spaces, and punctuation. If decryption fails, retype the password slowly, check caps lock, and confirm that no leading or trailing space was added by copying from a message.
  • Check for added line breaks or spaces inside the string. Some email and messaging systems wrap long strings onto several lines. The decryptor removes white space before validating, so wrapped lines are usually harmless, but a character lost at a line break is not. Repaste from the original source when in doubt.
  • Confirm the output came from the Text Encryptor. The decryptor only handles output in the encryptor’s format. Base64 text from another tool, a different password scheme, or a plain Base64 encoding of readable text will fail validation or decryption.
  • Protect the decrypted text. Once decrypted, the text is readable plain text. Do not paste it into a shared document, leave it in a download folder, or forward it without considering who can read it. The protection ends at decryption.
  • Keep the encrypted copy after decrypting. Decryption does not destroy the encrypted string. Keep it as the stored form, and decrypt again whenever the text is needed, rather than keeping a readable copy alongside it.

If decryption fails repeatedly with a password you believe is correct, ask the sender to re-encrypt and resend, or re-encrypt the original yourself if you still have it. Guessing passwords repeatedly will not help, and there is no recovery mechanism by design.

Limitations of the Text Decryptor

The decryptor can only decrypt output produced by the Text Encryptor in its exact format. It cannot decrypt text encrypted by other tools, other algorithms, or other password schemes, and it cannot decode plain Base64 text into readable form when that text was never encrypted with this method. It cannot recover text when the password is forgotten, and it cannot tell you whether the password or the ciphertext is at fault when decryption fails, because authenticated decryption fails identically for both causes.

Decryption requires WebCrypto, a modern browser, and a secure HTTPS connection. The tool decrypts text only; it cannot decrypt files, images, or folders. It does not verify the identity of the sender, so a valid decryption proves only that the password matches, not who encrypted the message. It does not store passwords, ciphertexts, or plaintexts, and offers no history or recovery. The download is a plain text file, so the decrypted text saved to disk is unprotected and must be handled accordingly.

Frequently Asked Questions

Why does decryption fail even though I am sure the password is right?

The most common cause is an incomplete or altered copy of the encrypted string, such as a missing character at the end or a character changed by a messaging system. Repaste the complete string from the original source and retype the password carefully. Authenticated decryption fails identically for a wrong password and damaged ciphertext, so both must be checked.

What does the invalid Base64 error mean?

The pasted text is not valid Base64: it may contain characters outside the Base64 alphabet, have a length that is not a multiple of four, or be missing its padding. Paste the complete output from the Text Encryptor without adding or removing characters.

Can the tool decrypt text encrypted by another program?

No. It handles only the Text Encryptor format, with its specific salt, vector, key derivation, and cipher settings. Output from other tools will fail, even if it is also Base64 and also uses AES, unless every format detail matches.

Is my password or decrypted text sent anywhere?

No. Decryption runs in your browser using WebCrypto, and nothing is sent to a server. The tool stores no password, ciphertext, or plaintext. Your decrypted text exists only in the page until you copy, download, or leave.

Can I recover text if I forgot the password?

No. There is no recovery mechanism, no master password, and no stored copy. The password is essential to rebuilding the key. If the password is lost and no readable copy exists, the text cannot be recovered.

Why do I see an error that decryption is not available?

WebCrypto needs a secure HTTPS page and a modern browser. The error appears when the browser or connection does not provide it. Open the page over HTTPS in a current browser and try again.

Related Tools

These tools encrypt, measure, and compare the text you decrypt.

Browse More Tools