Text Encryption

Encrypt or decrypt text locally with AES-GCM and a passphrase.

Text or encrypted payload

Encrypted output is returned as JSON with version, algorithm, iterations, salt, iv, and ciphertext fields.

Result


                        
                        
                    

When to use Text Encryption

Common reasons to encrypt or decrypt text locally in your browser:

  • Protect short notes or secrets

    Encrypt sensitive text such as snippets, notes, or one-off values with a passphrase before sharing the payload.

  • Decrypt a shared payload

    Paste an encrypted JSON payload, enter the matching passphrase, and recover the original text locally.

  • Verify round-trips during debugging

    Encrypt sample text and immediately decrypt it again to confirm that the payload and passphrase handling work as expected.

  • Copy encrypted payloads safely

    Generate a structured payload and copy it into tickets, chats, or notes without exposing the original plaintext in transit.

  • Handle quick mobile checks

    Paste text on a phone or tablet, encrypt or decrypt it with a passphrase, and copy the result without leaving the page.

Frequently Asked Questions

What encryption does this tool use?
The app encrypts and decrypts with AES-GCM. The AES key is derived from your passphrase with PBKDF2-SHA-256 inside your browser.
What does the encrypted payload contain?
The encrypted result is JSON with version, algorithm, key-derivation settings, salt, iv, and ciphertext fields. That payload is what you paste back in when you want to decrypt.
Are my text and passphrase sent to a server?
No. Encryption and decryption happen locally in your browser. AppDoesIt may still load shared page assets and browser-stored preferences, and clipboard access happens only when you click Paste or Copy.
Why can't the app decrypt my payload?
Decryption fails when the passphrase is wrong, the JSON payload is incomplete or malformed, or the ciphertext, salt, or iv was altered.
Can I reuse the encrypted payload later?
Yes. Keep the JSON payload exactly as generated and reuse the same passphrase later to decrypt it in a compatible browser.