Data Encryptor
NewEncrypt and decrypt text using AES-256-GCM with PBKDF2 key derivation — all client-side.
AES-256-GCM with PBKDF2 (SHA-256, 100,000 iterations). The IV is prepended to the ciphertext before Base64 encoding.
Frequently Asked Questions
What exact encryption format does this tool use?
It encrypts text with AES-256-GCM and derives the key with PBKDF2 using SHA-256 and 100,000 iterations. The output is Base64 of the 12-byte IV prepended to the ciphertext.
Can I decrypt ciphertext from another AES tool here?
Only if that tool used the same overall format: PBKDF2-derived AES-GCM, a 12-byte IV, and a payload encoded as Base64 of IV + ciphertext. This page does not accept separate salt or IV fields.
Why does decryption fail when the password is wrong or the text was altered?
AES-GCM authenticates the ciphertext as well as decrypting it. If the password is wrong or the bytes were changed, Web Crypto rejects the decrypt step and the tool shows an error.
Does this use a separate salt, or just the IV?
In this implementation, the IV is also reused as the PBKDF2 salt. That means the only bytes stored alongside the ciphertext are the prepended 12-byte IV.
Can I encrypt files or binary data with it?
Not directly. The UI is text-only, so it works on textarea content and returns either Base64 ciphertext or decoded plaintext text.