Verify downloads
Compare a file hash against a checksum published by a trusted source.
Hash Generator
Generate hashes for text and files
Enter text or choose a file to generate SHA hashes with browser Web Crypto. Content is processed locally and is not uploaded.
Results
Common uses
Hashes are useful for file verification, cache keys, integrity checks, and comparing content without sharing the original text or file.
Hash generator FAQ
Does this support MD5?
No. Browser Web Crypto does not provide MD5. This tool uses SHA algorithms available in modern browsers.
Are files uploaded?
No. Files are read locally by browser JavaScript.
Hash generation guide
Hash Generator creates SHA digests for text and files in the browser. Hashes help compare content, verify downloads, create cache keys, and confirm whether two files are identical without reading the full content again.
Detect changes
Hash two versions of a file or text value to see whether the content changed.
Share fingerprints
Provide a digest for integrity checks without exposing the original file contents.
Sample review notes for hash checks
A hash check compares exact input bytes or text against a trusted reference. It is an integrity check, not encryption and not a full security scan.
Expected result
The selected algorithm matches the published reference and the generated digest is compared character by character against the trusted source.
Failure signals
The reference uses a different algorithm, the file was edited or recompressed, or the user hashes copied text when the reference was created from file bytes.
Reviewer action
Get the reference digest from the publisher's official channel and regenerate the hash after any download retry or file change.
Real workflow note: download integrity checks
Hashes are useful when a publisher provides a checksum for an archive, installer, report, or export. The check confirms whether the local file matches the published reference value.
Use the trusted checksum
Copy the reference hash from the publisher's official page, release notes, or secure channel.
Hash the file itself
When the checksum is for a file, hash the downloaded bytes rather than copied text from inside the file.
Understand the limit
A matching hash confirms integrity against the reference; it does not prove the publisher or file is safe by itself.
Case study: checking a downloaded archive
A user downloads a release archive and copies the SHA-256 checksum from the official publisher page. They hash the downloaded file locally, compare every character, and avoid using the file if the value differs.
- Use the same algorithm as the published checksum.
- Hash the file bytes, not copied text from inside the file.
- Get the reference checksum from a trusted source.
Recommended workflow
- Choose text or a file as the input source.
- Select SHA-256 or stronger for modern integrity checks.
- Generate the digest and copy it exactly.
- Compare hashes only when both values use the same algorithm and input encoding.
Quality checks before using the result
- Compare hashes only when the algorithm, file, and exact input encoding are the same.
- Copy the digest from a trusted publisher source before trusting a downloaded file.
- Regenerate the hash after any edit, recompression, line-ending change, or download retry.
Questions about this tool
Can I recover the original file from a hash?
No. A cryptographic hash is one-way for practical purposes.
Why did two similar files produce different hashes?
Even a one-byte change creates a completely different digest.
Does a matching hash guarantee safety?
It confirms integrity against a known value, but the known value must come from a trusted source.