SHA256 OnlineMaintain an existing integration
Reproduce SHA1 only where the integration calls for it; use the correct message bytes.
Legacy SHA compatibility · Text
SHA1 Hash Generator
Calculate SHA1 from UTF-8, Hex or Base64 text. Compare a trusted expected digest locally.
Input No upload
Output Your result · SHA1
SHA1 calculated
0 decoded bytes · UTF-8 · input changes update automatically
Browser-local hashing. Inputs masked in Clarity.
No account. No uploads. Just your browser.
SHA1 versus SHA256
| Algorithm | What differs |
|---|---|
| SHA1 | 160-bit SHA-1 output; broken collision resistance. |
| SHA256 | 256-bit SHA-2 output; a different algorithm and digest length. |
Generate SHA1 from exact bytes
- 1
Enter or decode your message
Start empty, paste UTF-8 text, or choose Hex or Base64 for encoded bytes.
- 2
Inspect the full digest
SHA1 returns 40 lowercase hex characters. Copy digest preserves the whole output.
- 3
Compare or reproduce a keyed result
Paste a trusted reference, or enable HMAC only for a keyed protocol.
SHA1 text workflows
Check a historical release
Read the algorithm label on the publisher’s archive before comparing an old SHA1 value.
Distinguish IDs from raw hashes
A system may hash metadata together with content. A SHA1-looking identifier need not be the SHA1 of raw text.
Details that affect your SHA1 result
How SHA1 works
SHA1 produces a 160-bit result: 40 hexadecimal characters. It remains useful for reproducing legacy fingerprints, but its collision resistance is broken. Prefer SHA256 for new integrity workflows.
A SHA1 file checksum describes raw bytes, not the extracted content of an archive. Recompressing the same documents changes the archive checksum. Use the publisher’s original file and the SHA1 algorithm.
Generate a SHA1 hash from exact bytes
Type or paste text for an automatic result. UTF-8 preserves whitespace and line endings. Hex accepts pairs of digits with optional whitespace; Base64 requires the standard padded alphabet. Invalid encoding stops calculation instead of hashing a different input.
The default result is the digest of zero bytes. The abc example contains exactly 61 62 63 in hex with no newline. Adding Enter changes the bytes and therefore the result.
Compare a value or use a key
Paste a complete hexadecimal expected value to see Match or Mismatch. Outer whitespace and uppercase hex are accepted; incomplete digests, filenames and embedded spaces are not.
HMAC-SHA1 calculates a keyed hash. Enable HMAC and enter the secret in its own encoding. An empty key is a valid key and differs from turning HMAC off. Keys are never saved or included in exported reports.
Switch to files without changing the algorithm
The SHA1 file checksum tool reads raw bytes in chunks and supports batch manifests. Text mode is limited to 8 MiB decoded input; use file mode for larger data.
No input is uploaded. Only a light/dark theme preference is stored. Copy and report downloads remain on your device.
Known SHA1 result: empty input
SHA1 · 0 bytes · no HMAC. Empty input is not the same as no file selected.
da39a3ee5e6b4b0d3255bfef95601890afd80709SHA1 hash generator FAQ
Is SHA1 the same as SHA-1?
Yes. This interface writes SHA1; the standard name is SHA-1. Both refer here to the 160-bit algorithm.
Should I use SHA1 for a new security design?
No. SHA-1 has broken collision resistance. Use a modern construction selected for your protocol rather than introducing SHA1 for compatibility-free new work.
Why will a Git object ID not equal my text SHA1?
Git object hashing includes an object header as well as content. This tool hashes only the bytes you supply; it does not construct Git objects.
Can HMAC-SHA1 match a plain SHA1 digest?
They are different operations. HMAC-SHA1 requires the agreed key and message bytes; turning HMAC on is not a way to verify a plain SHA1 checksum.
How do I hash encoded bytes with SHA1?
UTF-8 hashes literal text. Hex and standard padded Base64 decode to bytes first. abc, Hex 616263 and Base64 YWJj represent the same bytes; invalid encodings stop calculation.
Will spaces or Enter change my SHA1?
Yes. Text is not trimmed. A trailing newline, carriage return, byte-order mark or extra space changes the byte sequence and usually the result.
How do I compare a SHA1 expected value?
Paste exactly 40 hexadecimal characters. Uppercase and outer whitespace are accepted. Match means equality with your reference, not proof of a trustworthy source.
Where does this SHA1 generator store my input?
Text and keys stay in browser memory, not URLs or localStorage. The tool saves only your theme preference; Clarity may use its own identifiers, as explained in Privacy. Text mode accepts up to 8 MiB of decoded bytes; use file mode for larger inputs.