Hash Generator Online – MD5, SHA-256 Free
Checksums and digests, locally.
At a glance
- Processing:
- Runs locally in your browser
- Privacy:
- Nothing you type is sent to a server
Last updated: 2026-10-03
Common use cases
- Checking a downloaded text file against its published digest
- Verifying a copied invoice block was not altered
- Comparing draft texts during review for silent edits
- Creating test vectors for a checksum parser
About this tool
Hash any text with SHA-256, SHA-384, SHA-512, SHA-1 or MD5 (via a tiny local fallback for the legacy case). Compare digests to verify file or message integrity.
How to use it
- Paste the text.
- Pick the algorithm.
- Copy the hex digest.
Practical tips
- Pick SHA-256 for routine checks. Reserve SHA-1 and MD5 for legacy matches only. They are flagged as broken in the panel.
- Paste input first, select the algorithm, then press Compute hash. The digest box stays empty before that.
- Use Copy on the hex digest to avoid transcription slips. Long digests are easy to mistype.
Common mistakes
- Expecting output as you type. Nothing appears until you press Compute hash.
- Using MD5 for security decisions. It suits legacy checks only — use SHA-256 or SHA-512 instead.
- Running in an insecure frame and seeing a failure note. Web Crypto needs a secure context.
How this compares
Server hash APIs send your text out for digesting, which exposes private input. This tool uses Web Crypto in your tab, plus a local MD5 fallback, so text stays put. You give up shared job logs and cloud batch runs. You keep private one-off digests with no upload.
Good to know
- Input is text only. There is no file drop in this panel.
- MD5 runs via a local script for legacy checks. It is not fit for security use.
- Web Crypto needs a secure context or hashing fails with a notice.
Frequently asked questions
Is my input uploaded?
No. Hashing uses the Web Crypto API inside your browser — input never leaves your device.
Which algorithm should I use?
SHA-256 for general integrity, SHA-512 for stronger digests, SHA-1/MD5 only for legacy compatibility (both are broken for security use).
Can a hash be reversed?
No — hashes are one-way by design. You verify data by re-hashing it and comparing digests, never by decoding.
Why do small text tweaks change the whole digest?
Hash functions spread input bits across the result. Change one letter and a fresh SHA-256 digest looks unrelated, which is how you spot edits. Empty input still hashes. The digest then covers zero bytes.

