Universal

AES-256-GCM text encryptionEN

Authenticated encryption keeps tampering and wrong-passphrase failures separate from plaintext output.

Options

AES-256-GCM · PBKDF2-HMAC-SHA-256 · 600,000 iterations

The passphrase is never stored. Losing it makes encrypted text unrecoverable.

Ready.

How to use it

Use this portable envelope for modest text that must be encrypted in the browser with an explicit passphrase.

  1. Choose Encrypt or Decrypt and enter a passphrase of at least 12 Unicode characters.
  2. For encryption, enter plaintext; for decryption, paste the complete Rigula JSON envelope.
  3. Run the operation and store the envelope and passphrase separately.

Worked example

Input
Plaintext: private note
Passphrase: a long unique passphrase
Output
{"v":1,"alg":"A256GCM","kdf":"PBKDF2-HS256",…}

Salt and IV are freshly generated, so encrypting the same input twice produces different envelopes.

Method and definitions

  • PBKDF2-HMAC-SHA-256 uses 600,000 iterations and a random 16-byte salt to derive a 256-bit AES key.
  • AES-GCM uses a new 12-byte IV, a 128-bit tag, and authenticates the versioned envelope metadata.

Limits and edge cases

  • This is not a password manager, key-recovery service, audited vault, or password-storage function; Argon2id is preferred for password storage.
  • Losing the passphrase loses the plaintext. The tool limits plaintext to 1 MiB and never remembers the passphrase.

Privacy

All input and output stays in this tab. Rigula does not upload, store, or include it in a share URL.