Input
Output
Formatted result will be displayed here
SHA-1 is a 160-bit cryptographic hash function that outputs a 40-character hexadecimal digest. It is considered broken for security purposes but is still widely used for content addressing inside git, cache keys, and legacy integrity checks. This tool hashes your UTF-8 text locally in the browser, so the input never leaves your machine. Use it for checksums and file fingerprints, not for password storage or signatures.
git addresses objects by their SHA-1. Compute one by hand to understand how a blob or commit hash is derived.
Hashing a normalized request key into SHA-1 gives a compact identifier safe to use as a Redis or disk cache filename.
Verify a downloaded payload against a vendor-provided SHA-1 digest to confirm it matches what was published.
Reproducing a legacy system hash helps confirm you have understood its input normalization before replacing it with something modern.
It is not safe against deliberate collisions. For checksums over trusted data, it is acceptable; for any security property, migrate to SHA-256.
40 lowercase hex characters representing the 160-bit digest. The length does not depend on input size.
Yes. Any byte change, including a trailing newline, produces a completely different hash. Normalize input explicitly if needed.
No. The hash is computed using the browser crypto API entirely client-side.