Text Decryptor

Free online text decryptor — reading AES-encrypted notes on any device.

100% Private — Runs entirely in browserInstant calculation & resultFree, no sign-up

Decrypt AES-256-GCM encrypted text — read encrypted notes on any device

ToolJiffy Text Decryptor reverses the AES-256-GCM encryption applied by the ToolJiffy Text Encryptor, recovering the original plaintext from a Base64-encoded ciphertext using the correct passphrase — entirely in your browser, with no server involvement. Whether decrypting a private note you previously encrypted, reading a secure message from a colleague, or recovering an encrypted password list, the decryptor handles the complete cryptographic pipeline using the browser's native Web Crypto API.

How AES-256-GCM decryption works

ToolJiffy's ciphertext format is a self-contained Base64-encoded binary blob with three components prepended:

  1. 16-byte random salt — used with your passphrase to re-derive the same 256-bit AES key via PBKDF2
  2. 12-byte initialization vector (IV) — the unique nonce that was used for this specific encryption operation
  3. AES-GCM ciphertext + 16-byte authentication tag — the encrypted content with its integrity verification tag

The decryptor reads these components, re-derives the identical AES key from the passphrase and salt using PBKDF2 (100,000 SHA-256 iterations), feeds the IV and ciphertext into AES-256-GCM decryption, and verifies the authentication tag before returning plaintext. If the authentication tag verification fails — due to wrong passphrase, corrupted ciphertext, or tampered data — an error is returned, not incorrect plaintext.

Authentication failure as a security feature

Unlike many simpler encryption schemes that silently return garbled output when given the wrong key, AES-256-GCM's Galois/Counter Mode verifies an authentication tag before returning any plaintext. This means:

  • A wrong passphrase produces an explicit "authentication failed" error — not confusing garbled text that might be mistaken for a successful decrypt
  • Any tampering with the ciphertext (bit-flip attacks, partial truncation) is detected and rejected
  • The system is resistant to chosen-ciphertext attacks that exploit decryption oracle behavior

When decryption fails unexpectedly

If decryption fails even when you believe you have the correct passphrase, common causes include:

  • Whitespace corruption: Rich-text editors and email clients sometimes add line breaks to long Base64 strings — ensure the ciphertext is pasted as a single unbroken string
  • Character encoding changes: Smart-quote conversion or special character substitution in email clients can corrupt the Base64 ciphertext
  • Truncation: Ensure the complete ciphertext was copied, not just the beginning
  • Passphrase case: Passphrases are case-sensitive — verify caps lock is not active

Step-by-step guide to decrypting text

  1. Paste the ciphertext: Copy the complete Base64-encoded ciphertext string produced by the Text Encryptor and paste it into the ciphertext field above.
  2. Enter the passphrase: Type the exact passphrase used during encryption — case-sensitive, including any special characters.
  3. Decrypt and read: Click Decrypt. The original plaintext appears in the output field if the passphrase is correct.

Frequently asked questions

How does the Text Decryptor work in browser memory?

ToolJiffy Base64-decodes the ciphertext, extracts the embedded salt and IV, re-derives the AES-256 key from your passphrase using PBKDF2, and decrypts using AES-256-GCM via the browser's Web Crypto API — zero server uploads.

Is my ciphertext or passphrase sent to any cloud server?

Absolutely not. All decryption runs 100% locally in your browser. Your passphrase and decrypted plaintext never leave your device.

What happens if I enter the wrong passphrase?

AES-256-GCM authentication tag verification fails — producing an explicit error, not garbled output. This protects against oracle attacks.

Is the Text Decryptor compatible with the ToolJiffy Text Encryptor output?

Yes. The decryptor is specifically designed to accept Base64-encoded ciphertext from the ToolJiffy Text Encryptor.

Can I decrypt text encrypted by other AES-256-GCM tools?

Only if they use the same format: Base64([16-byte salt][12-byte IV][ciphertext][auth tag]) with PBKDF2 key derivation. Different formats cannot be decrypted here.

Why does decryption fail even with the correct passphrase?

Common causes: extra spaces added during copy-paste, character encoding changes from rich-text editors, or ciphertext truncation. Always paste the full Base64 string.

How long does decryption take?

Approximately 200–500ms, dominated by the PBKDF2 100,000-iteration key re-derivation step.

Is ToolJiffy Text Decryptor free without limits?

Yes. ToolJiffy is 100% free with unlimited text decryption, zero account registration, and zero server uploads.

Related security tools

Encrypt text with Text Encryptor, generate secure passwords with Password Generator, decode Base64 with Base64 Encoder/Decoder, or check HTTPS status with HTTP Status Checker.

310 free tools
Instant — runs on your device
Files never uploaded
Free — no sign-up