Before you start
- Use test or non-production text unless you fully understand the handling and retention rules for the operation.
- Keep keys, passwords, parameters, and the original plaintext in a controlled location; never share a private key.
Security tool
AES Encrypt and Decrypt Online
Encrypt or decrypt text with AES-GCM or AES-CBC using PBKDF2, IV, salt, tag length, and Base64 or JSON output.
AES here is server-side processing, not local encryption
Use a harmless interoperability sample to confirm the exact payload contract before considering any sensitive workflow.
- The page sends plaintext and password to the `/api/aes` service. Do not enter production secrets, private keys, customer records, or credentials.
- Default encryption uses AES-GCM with a 256-bit key, PBKDF2-HMAC-SHA256 at 210,000 iterations, a random 16-byte salt, 12-byte IV, and 128-bit tag.
- The output is Base64 around a JSON envelope containing algorithm, KDF settings, salt, IV, tag length where applicable, and ciphertext. Base64 makes bytes transportable; it is not additional encryption.
The AES operation is performed by the server for the current request, unlike browser-local converters. Retention and encryption do not replace your organization’s approved secret-handling and key-management controls.
How to Use AES Encryption and Base64 Payloads Without Confusing Their Security BoundariesVerify a cryptographic operation before relying on it
Check the result
- Decrypt a test result or verify a signature with the intended public key before using it in a workflow.
- Record the algorithm, padding or mode, and encoding so another authorized user can reproduce the result.
Know the limit: Encryption and signatures protect only when keys, algorithms, endpoints, and access controls are used correctly.
Tool details
AES Encrypt and Decrypt Online
Encrypt or decrypt text with AES-GCM or AES-CBC using PBKDF2, IV, salt, GCM tag settings, and Base64 or JSON payloads.
What This Tool Does
The backend performs AES operations with the selected mode, key length, PBKDF2 iterations, IV length, salt length, and output format. It is useful for testing AES parameters and payload formats.
Common Use Cases
- Testing AES-GCM or AES-CBC encryption parameters
- Encrypting short text snippets with password-derived keys for development checks
- Decrypting Base64 or JSON payloads generated by this AES tool
How Data Is Handled
Encryption and decryption run on the backend, but plaintext, passwords, keys, and payloads are processed for the current request only and are not stored or written to logs.
FAQ
Which AES mode should I use?
AES-GCM is generally recommended for authenticated encryption when compatible with your workflow.
Does MV Tools store my password?
No. Passwords are used for the current operation only and are not stored.
Can I decrypt data from other tools?
Only if the payload format, password derivation settings, IV, salt, tag, and AES mode match what this tool expects.