BLAKE3 Hash Generator
Generate a BLAKE3 hash of any text, as hex, Base64 or binary. Free, and runs entirely in your browser — nothing you enter is uploaded or stored.
About Hash Generator
A digest of whatever you paste, in fifteen algorithms: the SHA-2 family, all of SHA-3 and Keccak, BLAKE2b, BLAKE2s and BLAKE3, RIPEMD-160, and the broken ones — SHA-1 and MD5 — for the systems that still send them. CRC-32 is there too, labelled as the checksum it is.
The result comes back in whichever encoding the receiving system wants — hex in either case, Base64, Base64url or raw binary — with hex and Base64 always shown alongside, because the same digest in the wrong encoding is the commonest reason two systems disagree.
Paste a digest into *Compare with* and it says whether the two match, without your eyes having to walk sixty-four hex characters. Tick *Show every algorithm* and the same input is hashed by all of them at once, which is how you work out which algorithm produced a hash you were given.
A hash is one-way and unkeyed: it proves that two pieces of data are the same, not that either came from anyone in particular. For that, sign it — and never call a hash encryption.
Where it helps
- Digests are computed with Web Crypto in your browser, so the input is never transmitted.
- Hex or Base64 output, matching whichever format the system you are checking against expects.
- Deterministic and fast: the same text always produces the same digest anywhere.
- UTF-8 handling is explicit, so non-ASCII text hashes consistently.
Limits
- Hashing is not encryption — the original cannot be recovered, by you or anyone else.
- A plain hash is a poor password store: attackers test billions of guesses per second. Use a password hash such as Argon2 or bcrypt on the server.
- SHA-1 is included for compatibility only; it must not be used where collision resistance matters.
- This hashes text. For a file, use the File Checksum tool, which reads the bytes directly.
Frequently asked questions
Can I reverse a hash back to the original text?
No. Hashes are one-way. Sites that appear to reverse them are looking answers up in a table of previously seen inputs.
Which algorithm should I use?
SHA-256 unless something forces your hand. It is fast, widely supported and has no practical attacks.
Why does my digest differ from the server's?
Usually a trailing newline, different line endings, or a different text encoding. Hashes are computed over exact bytes.
Is a hash enough to authenticate a message?
No — anyone can recompute it. Authentication needs a key, which is what the HMAC Generator provides.
Related tools
- HMAC Generator — Keyed message authentication codes
- File Checksum — Verify a download, and work out which algorithm made the checksum
- Text Encryption — AES-256-GCM with a PBKDF2 passphrase
- Password Generator — Strong random passwords with an entropy estimate
- MD5 Generator — MD5 digests, with a plain account of what they are still good for
- Key Derivation — Stretch a passphrase into key material with PBKDF2, scrypt or Argon2id
More Security & Cryptography tools
- Hash Generator — SHA-2, SHA-3, BLAKE and legacy digests, in any encoding
- MD5 Generator — MD5 digests, with a plain account of what they are still good for
- HMAC Generator — Keyed message authentication codes
- Key Derivation — Stretch a passphrase into key material with PBKDF2, scrypt or Argon2id
- Password Generator — Strong random passwords with an entropy estimate
- Password Strength — Judge a password by what an attacker would actually try
- JWK Generator — A JSON Web Key for a JOSE algorithm, with its key set and thumbprint id
- Key Pair Generator — RSA and elliptic-curve key pairs, generated in this tab and never sent
- TOTP / HOTP Generator — Two-factor codes, the QR code to enrol with, and why one did not match
- Text Encryption — AES-256-GCM with a PBKDF2 passphrase
- Bcrypt Generator — Hash a password with bcrypt, verify one against a hash, or read what a hash is made of