How to Decrypt OpenSSL AES Ciphertext
OpenSSL AES values can look simple in Base64, but successful decryption depends on the exact command and options that created them. A key mismatch is often a key-derivation mismatch.
Try it locally
Use the AES workspace to test documented values in your browser. Do not paste long-lived production secrets into a tool unless you understand and accept your device and browser risks.
Open the AES toolRecord the original command
Before decrypting, identify the cipher name, such as aes-256-cbc or aes-256-gcm, whether a password or raw key was used, the salt setting, digest, iteration count, and output encoding. These choices are part of the encrypted format, not optional settings.
Raw keys are different from passphrases
This tool accepts an already derived AES key and its IV or nonce. If an OpenSSL command used a password-based derivation, first reproduce that derivation in a trusted environment. Pasting the original password into a raw-key field will not normally work.
Check the transport format
OpenSSL output is often Base64-wrapped, may include line breaks, and may contain salt metadata. Decode and inspect it only after confirming the original format. For production data, use a reviewed application-specific implementation rather than an ad-hoc browser workflow.
Quick checklist
- Find the exact OpenSSL cipher and command options.
- Determine whether the source used a raw key or a password-derived key.
- Match key bytes, IV or nonce, mode, padding, and Base64 or Hex representation.
Common questions
Why does my OpenSSL password not work as an AES key?
OpenSSL may derive a key and IV from the password, salt, digest, and iteration settings. The raw AES key is a different value.
Can every OpenSSL AES value be pasted here?
No. This utility supports raw-key AES-GCM, AES-CBC, and AES-ECB compatibility. Values that depend on a password derivation need that derivation reproduced first.
Further reading: OpenSSL enc command documentation