Crypto

Encrypt / Decrypt Text

Experiment with password-derived AES-GCM encryption while keeping the ciphertext format and password separate.

Local processing

Loading tool workspace...

About this tool

When to use it

Experiment with password-derived AES-GCM encryption while keeping the ciphertext format and password separate.

How to use it

Enter test text and a password of at least eight characters, then encrypt. Copy the complete DM-AES1 payload. Switch to decryption, paste it, and use the exact same password. Keep the original until you have verified the round trip.

Guide updated 2026-09-15. Examples checked against this implementation.

Worked examples

Recover a short fixture

Input

Encrypt Hello with demo-password; decrypt the returned payload with the same password

Expected output

Hello

Ciphertext changes between runs because salt and IV are random. The example specifies the recovered text rather than a fixed ciphertext.

Errors and unsupported input

Decryption failed

Check the complete payload and password. A changed payload or incorrect password fails authentication; the tool cannot recover a lost password.

Continue this workflow

HMAC Generator: Authenticate a message without encrypting it when that matches your protocol.

Format rules and limitations

Plaintext is limited to 2 MiB. The custom payload includes salt, IV, and encrypted data; it is not an OpenSSL or arbitrary AES file format.

The implementation uses AES-256-GCM and PBKDF2-SHA-256 with 250,000 iterations. The eight-character minimum is an input guard, not a password-strength guarantee.

Privacy and security

The workspace processes data locally in your browser. Copy writes to the system clipboard; downloads persist on your device. Share, where offered, sends the selected result to your chosen app or copies it to the clipboard. The page also loads site assets and may contact configured analytics or consent services; tool input and output are not included in DevMate analytics. Review a report before sharing it, especially when it contains credentials or device details.

Review sensitive or production-critical output in the trusted system where it will be used.

Questions

Frequently asked questions

Why does encrypting the same text produce different output?

Fresh randomness is used for every encryption. Verify compatibility by decrypting successfully, not by expecting identical ciphertext.