Learn
History for this tool
The most recent data you entered in this tool, stored only in this browser.
Save what you type here, in this browser? Your work would go into this browser's local storage, so a refresh or a trip to another tool does not wipe it. You also get a short list of previous entries under the form, each one restorable with a click. Nothing is ever uploaded, and there is no account.
Being straight about the trade-off: anything kept there can be read by anyone who can use this browser profile, and by any script that later runs on this site. A tool page can hold a private key, a password or a signed token. Saving is convenient; it is not private.
Saved on this device
Your inputs and history are stored locally.
Not saved
This page forgets your work when you leave it.
About this tool
Encrypt and decrypt text with AES-GCM using a passphrase, with the key derived by PBKDF2. The output is a self-contained Base64 blob carrying the salt and the initialisation vector, so it can be decrypted later with the passphrase alone.Questions
- Is this strong enough for real data?
- AES-GCM and PBKDF2 are sound primitives and the construction is standard. What it cannot protect you from is a weak passphrase, or forgetting it — there is no recovery path.
- Why does the ciphertext change every time?
- Because a fresh random salt and IV are generated for each encryption. The same plaintext and passphrase therefore produce a different blob, which is the intended behaviour.
- Is the passphrase sent anywhere?
- No. Deriving the key and encrypting both happen in the browser.