Hash Generator
Hash text or hex bytes with SHA algorithms, compare an expected digest and download results.
This tool runs entirely in your browser. Your data is never uploaded, never stored, and never leaves your device.
Generate SHA digests from UTF-8 text or hex bytes and compare a selected result with an expected digest.
How to use it
- 1Choose text or hex bytes; enable legacy algorithms only if needed.
- 2Enter the exact input, including any intentional whitespace, and generate.
- 3Compare a trusted expected digest, then copy or download the results.
What happens to your data
Hashing stays in your browser. A digest is not encryption or password storage; MD5 and SHA-1 are legacy compatibility options.
Last updated October 2026
Generate a cryptographic digest from UTF-8 text or hexadecimal bytes, then compare it with an expected hash. SHA-256, SHA-384 and SHA-512 provide modern digest choices; legacy MD5 and SHA-1 are for compatibility checks, not new security designs. The input is processed locally and the result can be copied or downloaded.
Hashing operates on bytes, not on how text looks. A space, an invisible newline, a different Unicode representation or the difference between LF and CRLF can produce a completely different digest. UTF-8 text mode hashes the text as entered. Hex-byte mode hashes decoded bytes: the text 616263 and the bytes 61 62 63 are different inputs unless you deliberately choose the appropriate mode.
An empty input is also a real byte sequence with a well-defined digest. This tool can generate that value explicitly, which is useful when checking an integration or distinguishing an empty file from a missing value. To hash an entire local file, use the dedicated File Hash tool so you compare the original file bytes rather than a pasted text interpretation.
How it works
Choose UTF-8 text or hex bytes, then generate the SHA-256, SHA-384 and SHA-512 digests together. Legacy MD5 and SHA-1 require a deliberate compatibility opt-in. The browser's cryptographic API computes the SHA family; the MD5 helper is loaded only when required. Input is limited to 400,000 characters and 128 KiB of decoded bytes. Hex mode accepts complete byte pairs, compact or separated by whitespace, without prefixes or punctuation. Invalid bytes and malformed expected digests are reported, not partly accepted.
The expected-hash comparison checks equality for the chosen algorithm. It does not prove who supplied the expected value. For a meaningful download integrity check, obtain the reference digest through a trusted source. A malicious replacement of both a file and its displayed digest would still match.
An ordinary hash is not encryption: it has no decryption key. It is also not a password-storage scheme. Password databases need a purpose-built password hashing design with salts and an appropriate work factor. For a keyed message authenticator, use HMAC rather than appending a secret to this tool's text input. Changing source or compatibility settings clears obsolete output so a previous digest cannot be mistaken for the new data.
Worked example: a standard SHA-256 test vector
- Input
- abc (UTF-8, with no newline)
- Result
- ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
Hex-byte input 61 62 63 represents the same three bytes and must produce the same digest.
Common use cases
- Checking a published digest against known input bytes
- Debugging UTF-8 versus raw-byte hashing
- Testing the empty-input and abc reference cases
- Comparing digests without uploading the source text
Frequently asked questions
Why is my SHA-256 different from another tool?＋
Compare the exact bytes, input mode and algorithm. Trailing newlines, spaces, UTF-8 versus another encoding and LF versus CRLF are common causes. The text abc and abc followed by a newline are not the same input.
Can empty text have a hash?＋
Yes. The empty byte sequence has a standard digest for each supported algorithm. Generate it intentionally; empty input is not automatically treated as an error or as an instruction to reuse a previous result.
Does a matching checksum prove a file is safe?＋
No. It shows that the hashed bytes match the supplied digest under the selected algorithm. It does not establish the source's trustworthiness, detect all malicious content or verify a digital signature.
Should I choose MD5 or SHA-1?＋
Use them only when checking a legacy format that explicitly requires them. They have known collision weaknesses and should not be selected for new security-sensitive integrity designs. SHA-256 is the default modern choice here.
Can I encrypt or store passwords with this tool?＋
No. Digests are not reversible encryption, and fast general-purpose hashes are not suitable standalone password storage. Use a reviewed encryption or password-hashing system for those tasks.
Standards and limitations
Used in these workflows
Related tools
File Hash Checker
Get SHA-1, SHA-256 and SHA-512 checksums for a file, then paste the expected value to confirm a match.
HMAC Generator
Generate and verify HMAC digests with five algorithms and hex, Base64 or Base64URL output.
Hex / Binary / Text Converter
Convert UTF-8 text, hex and binary in six directions, validate input and download original bytes.
Base64 Encoder & Decoder
Encode and decode text or files with Base64, Base64URL, data URI detection, preview and download.