AES Encryptor

Enter text and a password of at least 4 characters.

Use this tool

Result

The result appears in this panel after you run the tool.

About this tool

The output is Base64 of salt, IV, and ciphertext. Decrypt it with the AES decryptor and the same password.

The password is not stored and is not sent to analytics.

How to use it

  1. Open this page and provide the input it asks for.
  2. Set the options that are visible, then use Encrypt.
  3. Read the result in the panel. Copy it or download it when a file is offered. The input stays in this browser.

Limitations

A fresh salt and a fresh 12-byte nonce

What is generated for each encryption

The password must be at least four characters. Shorter input throws before any cipher runs. Each run draws a 16-byte salt with crypto.getRandomValues and a 12-byte IV with another call. The salt and password go through PBKDF2 with SHA-256 and 100000 iterations to derive a 256-bit AES-GCM key. The textarea is UTF-8 and encrypted under that key and that IV. Web Crypto appends the authentication tag to the ciphertext. The bytes are packed as salt, then IV, then ciphertext, and the pack is base64. Base64 is only the spelling of those bytes. It is not the encryption. The encryption is AES-GCM under the derived key.

GCM requires that a nonce never repeat under the same key. A repeat lets an observer relate the two messages and can break the authentication guarantees. This page does not ask you for an IV, and it does not reuse the last one. Every encryption draws a new 12-byte IV. It also draws a new salt, so the derived key changes even when the password stays the same. The decryptor reads the IV back from the package. It does not invent a second nonce.

What you must store

You need the password and the entire base64 string. The salt is not a separate field you have to copy. It is the first 16 bytes inside the package. Losing the base64 loses the salt, the nonce, and the ciphertext together. The password is not inside the package. The page does not store either one. A later decryption has to be given both again. The iteration count is fixed at 100000 on this path, not taken from the PBKDF2 page’s control.

Other layouts and other jobs

Another product’s file format will not line up. OpenSSL’s salted layout, a raw hex ciphertext, or a caller-chosen nonce will not match this packing. Hashing would repeat for identical input. This package will not: the salt and IV are new on every run, so the base64 changes even when the password and the paragraph stay put. It is not a signature you can check without the plaintext. The tag is checked on decrypt. If you only have the package, you cannot read it without the password, which is the point of the cipher. If you need someone to verify a public message, use a MAC or a signature scheme and accept that the message stays visible.

Privacy

Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.