What Hash Generator helps you do

Generate MD5, SHA-256, SHA-3, BLAKE, RIPEMD, CRC, and other digests from pasted text or uploaded files. Compare checksums, verify downloads, or document expected hashes for build artifacts. It is a workbench for the awkward moment when one system publishes a SHA-256 and another still asks for an MD5.

Hashing runs locally in your browser using Web Crypto and bundled digest libraries. Files are not uploaded.

How it works

Text is converted to UTF-8 bytes and hashed; a file is read as bytes and streamed through the same algorithm. Web Crypto covers the standard SHA family, while bundled implementations provide the legacy and extended algorithms. Variable-length functions such as SHAKE take the output length you enter, and cSHAKE/KMAC expose their customization inputs.

How to use Hash Generator

Enter text or select a file, then pick the hash algorithms you need.
Set the output length for SHAKE, or the customization values for cSHAKE and KMAC.
Copy individual digests or compare against a known reference hash.
Re-run the hash after a download to confirm the bytes match.

When to use it

Verify that a downloaded installer matches a published SHA-256 checksum.
Generate fingerprints for configuration or cache-busting keys during development.
Document multiple hash types when auditing legacy systems that still reference MD5 or SHA-1.
Check a file's integrity after a transfer.
Produce a stable key for a cache or a content-addressed store.
Compare a Git blob or a build artifact digest.

When not to use it

Do not use MD5 or SHA-1 for new security-sensitive designs; prefer SHA-256 or stronger.
Do not treat a hash as encryption or as a way to hide a password.
Do not compare only the first few characters of a digest.

Example

A vendor publishes a SHA-256 for a 240 MB installer. Dropping the file into the hash tool produces a digest that matches the published value exactly, so the installer is kept. A second file from a mirror fails the same check and is deleted.

What you can do with Hash Generator

Hash text or a dropped file locally.
Cover MD, SHA-1, SHA-2, SHA-3, Keccak and RIPEMD families.
Generate BLAKE2b, BLAKE2s, BLAKE3 and CRC32 digests.
Choose a variable output length for SHAKE.
Use cSHAKE or KMAC advanced options.
Copy each digest or compare it with a published value.

Example: verify a downloaded installer

Drop the installer and select SHA-256. Copy the digest and compare it with the vendor's published checksum character by character; a single different character means the file is not the one that was signed off.

If the vendor also publishes a SHA-512 or a BLAKE2 value, generate that too. Matching only one legacy algorithm is weaker evidence than matching a modern one.

Keep the digest in the release notes or build log so the next person can verify the same artifact without re-downloading it from an unknown mirror.

What to know before you start

A hash verifies integrity, not authenticity or safety.
Legacy algorithms such as MD2, MD4 and MD5 are provided for compatibility, not for new designs.
Very large files are limited by browser memory and read speed.
The tool does not verify signatures or certificates.
Variable-length and keyed modes require you to supply the correct parameters.

Common mistakes

Comparing a truncated checksum from a web page that wrapped the text.
Using MD5 for a new integrity check because it is shorter.
Hashing the extracted file instead of the downloaded archive.
Assuming a matching hash proves the file is safe; it proves the bytes match the expected source.
Forgetting that a text hash depends on the exact encoding and line endings.

Troubleshooting

If the digest does not match, confirm that the expected value belongs to this file and not a different release or platform build.

If a text hash differs, check for a trailing newline, Windows versus Unix line endings, or a different character encoding.

If a large file takes a while, that is normal; the browser reads every byte locally.

If an algorithm is unavailable, the page may not have loaded its bundled implementation yet. Reload and try again.

If a variable-length digest looks wrong, check the output length in bytes; SHAKE output depends on that value.

If two implementations disagree on a BLAKE or SHA-3 digest, check whether the output is rendered as lowercase hex, uppercase hex or base64; this tool shows hex by default.

If a file hash changes after a copy, verify that the copy completed and that no line-ending conversion was applied to a binary file.

Hash Generator