Hash Generator

SHA-256, SHA-1, SHA-384 and SHA-512 digests of any text or file — computed locally, with a checksum compare box.

…or drop a file here any type, any size — hashed on your device
—
Hashing runs on your device via the browser's Web Crypto engine — nothing is uploaded.

About this tool

A hash is a fingerprint of data: feed in the same text or file and you always get the same digest; change a single byte and the digest changes completely. This tool computes SHA-256, SHA-1, SHA-384 and SHA-512 hashes of anything you type or any file you drop — using the cryptography engine built into your browser, so even multi-gigabyte files never leave your machine.

The most common everyday use is verifying downloads: many sites publish a SHA-256 checksum next to their installer. Drop the file here, paste the published value into the compare box, and you'll see instantly whether they match.

How to generate a hash

  1. Choose an algorithm (SHA-256 is the standard choice).
  2. Type text — the hash updates live — or drop a file.
  3. Copy the digest, or paste an expected checksum to verify a match.

Frequently asked questions

Is my text or file uploaded?

No. Hashes are computed by your browser's built-in Web Crypto engine, entirely on your device — safe even for confidential files.

What is a hash used for?

A hash is a short fingerprint of data: the same input always produces the same hash, and any change produces a completely different one. Common uses are verifying that a downloaded file matches the checksum a website published, deduplicating files, and integrity checks in software builds.

How do I verify a downloaded file's checksum?

Drop the downloaded file here, pick the algorithm the website lists (usually SHA-256), and compare the result with the published value. Use the compare box — it checks the two for you and tells you if they match.

Which algorithm should I use?

SHA-256 is the modern default and what most checksums use. SHA-512 offers a longer digest, and SHA-1 is provided only for compatibility with older systems — it is considered cryptographically broken and shouldn't be used for security decisions.

Why is there no MD5?

Browsers' built-in crypto deliberately omits MD5 because it has been broken for decades. If a site only publishes an MD5 checksum, treat it as an integrity hint, not a security guarantee — and prefer sources that publish SHA-256.