· encryption
Generate BLAKE3 hashes from text or files, or check a hash you already have against them. 256-bit by default, any length up to 1,048,576 bytes, optional key.
Encryption
A hash turns any input into a short, fixed-length fingerprint. The same input always gives the same digest, and changing a single byte gives a different one. That makes hashes the standard way to check a download, compare two files or store a password without keeping the password itself.
This category covers the SHA-2 and SHA-3 families, BLAKE2 and BLAKE3, Keccak and SHAKE, and the legacy MD4, MD5 and SHA-1 for older systems that still expect them. For error detection there are CRC-32, CRC-64, Adler-32 and FNV checksums. Keyed and password hashing come with matching verifiers: HMAC, and Argon2id. ROT13 and ROT47 sit here too, as simple letter rotation ciphers.
For accounts and logins there is a random password generator and a JWT decoder for reading the header and claims of a token.
23 public tools
Generate BLAKE3 hashes from text or files, or check a hash you already have against them. 256-bit by default, any length up to 1,048,576 bytes, optional key.
Calculate CRC-64 checksums of text or files up to 2 GiB each with the XZ, ECMA-182, Go-ISO, MS, NVMe, Redis or WE variant.
Hash text or files up to 2 GiB with SHA-256 and copy the 64-character hex digest, or paste a published checksum to verify a download.
Decode or encode ROT13 text in one step, or switch to ROT5 for digits, ROT18 for letters and digits, or ROT47 for all printable ASCII.
Generate an HMAC authentication code for text or a file using a hexadecimal secret key.
Generate SHA-1 digests from text or uploaded files: 160 bits, 40 hexadecimal characters. SHA-1 is not suitable for new security-sensitive uses.
Generate MD4 digests from text or files up to 2 GiB each for legacy compatibility. MD4 is cryptographically broken.
Generate MD5 digests from text or uploaded files: 128 bits, 32 hexadecimal characters. MD5 is cryptographically broken and is for legacy use only.
Generate SHA-512/224, SHA-512/256 or full SHA-512 digests from text or files up to 2 GiB each.
Generate SHA-384 digests from text or files up to 2 GiB each: 384 bits, 48 bytes, 96 hexadecimal characters.
Generate SHA-224 digests from text or files up to 2 GiB each: 224 bits, 28 bytes, 56 hexadecimal characters.
Generate SHAKE128 or SHAKE256 extendable-output hashes of 1 to 1,048,576 bytes from text or files up to 2 GiB each.
Generate Keccak-224, Keccak-256, Keccak-384 or Keccak-512 hashes from text or files up to 2 GiB each.
Generate SHA3-224, SHA3-256, SHA3-384 or SHA3-512 digests from text or files up to 2 GiB each.
Generate BLAKE2b digests at 128, 256, 384 or 512 bits, or any length from 1 to 64 bytes, from text or files up to 2 GiB each.
Generate BLAKE2s digests at 128, 160 or 256 bits, or any length from 1 to 32 bytes, from text or files up to 2 GiB each.
Create a salted Argon2id password hash using memory-hard, interoperable defaults.
Generate FNV-1a or FNV-1 32-bit and 64-bit non-cryptographic hashes from text or files up to 2 GiB each, with the offset basis and prime for each width.
Generate CRC-32 checksums from text or files up to 2 GiB each using ISO-HDLC, CRC-32C, BZIP2, MPEG-2, cksum and six more named variants.
Generate Adler-32 checksums from text or files up to 2 GiB each. Adler-32 is built for speed rather than security.
Decode a JWT to read its header, claims and signature. Nothing is verified, so use it to inspect a token, not to trust one.
Verify an HMAC authentication code against a message or file, using a hexadecimal secret key and SHA-2 or SHA-3.
Verify a password against an Argon2 PHC hash using the parameters embedded in the hash.