Terminal First Testing With Kane CLI
Natural language browser & mobile app tests right from terminal

Compute SHA-1 and HMAC-SHA1 hashes of text or files in your browser, with hex and Base64 output and built-in checksum verification.
0 characters
A SHA1 hash calculator is a tool that converts any text or file into a fixed 160 bit digest, shown as 40 hexadecimal characters. The SHA-1 algorithm is defined in NIST FIPS PUB 180-4. The same input always produces the same digest, so comparing digests confirms two copies of data are identical.
This TestMu AI calculator runs entirely in your browser and also covers the keyed variant, HMAC-SHA1. If you need a stronger modern digest for the same workflow, use the SHA256 Hash Calculator.
SHA-1 first pads your input and splits it into 512 bit blocks, appending the message length to the final block. Each block then passes through 80 rounds of bitwise operations that keep updating five 32 bit working values. After the last block, those five values are joined into the 160 bit digest.
You can check this calculator against the canonical test vector from FIPS PUB 180-4: hashing the three characters abc must produce the digest below.
SHA1("abc") = a9993e364706816aba3e25717850c26c9cd0d89dNo. NIST formally retired SHA-1 in December 2022 and plans to remove it from federal use by the end of 2030, after researchers demonstrated the first practical collision (the SHAttered attack) in 2017.
SHA-1 remains fine for non adversarial jobs: spotting accidental file corruption, building cache keys, or interoperating with legacy systems that require it. For anything security sensitive, move to the SHA-2 family, for example the SHA512 Hash Calculator.
A SHA1 hash is always 160 bits (20 bytes) long, no matter how large the input is. In hexadecimal form it appears as 40 characters, and in Base64 form it appears as 28 characters. Hashing a single letter or a 2 GB file produces the same fixed digest length.
A SHA1 hash cannot be decrypted, because hashing is a one way function that discards the original data. Attackers can still guess simple inputs by hashing millions of candidate strings and comparing results, which is why short or common passwords are easy to match against precomputed lookup tables.
SHA1 produces a 160 bit digest and is retired for security use, while SHA256, part of the SHA-2 family, produces a 256 bit digest and remains approved by NIST. SHA256 output is 64 hexadecimal characters instead of 40. Choose SHA256 for signatures, certificates, and any security sensitive integrity check.
SHA1 generates a 160 bit digest while MD5 generates a 128 bit digest, shown as 40 and 32 hexadecimal characters respectively. Both are broken for collision resistance, but MD5 fell much earlier. SHA1 is slightly slower and slightly stronger, yet neither should protect passwords, signatures, or certificates today.
Two different files can share the same SHA1 hash, which is called a collision. Google and CWI Amsterdam demonstrated the first practical SHA1 collision, the SHAttered attack, in 2017 using two different PDF files. Collisions must be deliberately engineered and remain expensive, but they are proven feasible.
HMAC-SHA1 combines the SHA-1 digest with a secret key to produce a keyed message authentication code. It verifies that a message came from someone holding the key and was not modified in transit. Legacy APIs such as OAuth 1.0a and many webhook signatures still rely on HMAC-SHA1.
This SHA1 calculator never uploads your text or files. All hashing runs inside your browser through the Web Crypto API built into Chrome, Firefox, Safari, and Edge. Nothing you type or select leaves your device, so you can safely hash private data, internal documents, and unreleased builds.
A SHA1 checksum is a digest published alongside a download so anyone can verify the file arrived intact. You hash the file you received and compare the result with the published value. Matching checksums confirm the copy is byte for byte identical, while a mismatch signals corruption or tampering.
The same input always produces the same SHA1 hash on every system, because SHA-1 is a deterministic algorithm with no randomness involved. This consistency is what makes hashes useful for verification: any two parties can hash the same data independently and expect byte for byte identical digests.
A SHA1 mismatch usually comes from invisible input differences rather than the algorithm. Common causes include a trailing space or newline, Windows versus Unix line endings, different character encodings, or comparing an HMAC result against a plain hash. Check for hidden whitespace first, then confirm both sides hash identical bytes.
You can generate a SHA1 hash of a file directly on this page: click the upload icon, choose the file, and read the digest instantly. No command line tools such as sha1sum or CertUtil are required, and the file is read locally without being uploaded.
SHA1 is not safe for storing passwords. It computes far too quickly, which lets attackers test billions of guesses per second, and it offers no salting by itself. Use a dedicated slow password hashing algorithm such as bcrypt, scrypt, or Argon2 for credentials instead of any plain digest.
Did you find this page helpful?
TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance