Encrypt text locally with AES-256-GCM, random salt and IV, authenticated metadata, and legacy-payload compatibility
The password is never stored in the payload. Use a long passphrase and keep it safe; it cannot be recovered.
Higher values resist guessing better but take longer on slower devices. The value is stored with the payload.
AAD is not encrypted, but is authenticated and stored in the payload; any change makes decryption fail.
AES-256-GCM provides confidentiality and tamper detection with a fresh 16-byte salt and 12-byte IV. This tool is for text and developer-data exchange, not login-password storage; use Argon2id, scrypt, or a dedicated password hash for that.
Encrypt text locally with AES-256-GCM, random salt and IV, authenticated metadata, and legacy-payload compatibility. It requires no desktop installation and supports common developer workflows directly in a modern browser.
Core processing runs locally in your browser. Tool input is not uploaded; downloads and clipboard actions are handled by the browser.
Continue with the next step in the same workflow.
Calculate chunked local MD5 checksums for text or files, verify GNU/BSD manifests, and export compatible checksum files
Calculate SHA-1 hashes for text, files, or HMAC workflows
Calculate SHA-256/384/512 hashes for text, files, or HMAC workflows
Generate local HMAC test tokens, strictly validate JWT claims, and verify signatures with HMAC, PEM, JWK, or JWKS keys