SHA1 Hash Generator

Q: Why does the same text give me a different SHA-1 hash?

The underlying bytes may differ. Check Input Encoding, extra spaces, line breaks, capitalization, and Unicode characters. For a valid comparison, the original data and the selected encoding must match exactly.

Q: What is the difference between SHA-1 and HMAC-SHA1?

Plain SHA-1 hashes the message alone. HMAC-SHA1 uses SHA-1 within a keyed authentication method, so calculating or verifying the result requires a secret key as well as the message.

Q: Does changing Hex to Base64 change the SHA-1 hash?

No. Hex (lower), Hex (UPPER), and Base64 only change how the same 20-byte digest is displayed. Uppercase and lowercase hexadecimal digits represent identical byte values.

Q: What happens if I select Hex or Base64 for input?

Those options are for input represented as encoded data rather than ordinary text. For example, the hexadecimal bytes 616263 represent abc; selecting Hex is different from hashing the six literal characters 616263 as UTF-8 text.

Q: Can a SHA-1 hash be decrypted or reversed?

No. SHA-1 is a one-way hash function, not an encryption algorithm. A known digest may be compared against hashes of possible inputs, but the digest itself does not contain a reversible copy of the original data.

Q: Is SHA-1 secure for passwords or digital signatures?

No. Practical collision attacks make SHA-1 inappropriate for new digital signatures and other collision-sensitive uses. Store passwords using a dedicated password-hashing algorithm such as Argon2id, bcrypt, or scrypt, and prefer SHA-256 or a stronger approved hash for new general-purpose cryptographic designs.

Generate SHA-1 hashes from text for legacy checksum comparisons or testing older integrations. The tool also offers Auto / Live updates, multiple input encodings, and an optional HMAC-SHA1 mode.

Input Encoding:

Auto / Live

Input text

SHA-1 Hash Result

Live

Output Format:

Hex (lower)

Hex (UPPER)

Base64

Enable HMAC-SHA1

How to Generate a SHA-1 Hash

Use this online SHA1 calculator to hash text as entered or to interpret an encoded byte sequence before hashing. The steps below match the controls shown in the tool.

Type or paste your content in the Input text editor.
Open Input Encoding and choose the representation of your input, such as UTF-8, UTF-16, Hex, or Base64 where available. Leave UTF-8 selected for ordinary text.
Keep Auto / Live enabled to update the hash while editing, or switch it off and press Run to calculate manually.
Under Separator, select Hex (lower), Hex (UPPER), or Base64. Read the value in SHA-1 Hash Result, then use Copy to copy it or Clear to reset your input.

For a quick test, enter abc with UTF-8 and Hex (lower). The SHA-1 result is a9993e364706816aba3e25717850c26c9cd0d89d.

Input Encoding vs. Hash Output

Input Encoding determines which bytes are hashed. UTF-8 and UTF-16 represent text differently; Hex and Base64 can represent byte data in text form. Choose the encoding used by the original system when checking an existing digest.

The Separator choices control the display format of the same digest, despite that label in the interface. Switching between Hex (lower), Hex (UPPER), and Base64 changes how the 20 result bytes are written, not the SHA-1 value itself.

Generate an HMAC-SHA1 Value

Turn on Enable HMAC-SHA1 when you need a keyed message authentication code rather than an ordinary SHA-1 digest. HMAC combines the message with a secret key, so the same text produces a different result when a different key is used.

Enter your message in Input text. HMAC requires a shared secret key, which must match the key used by the system you are checking. Configure it in the HMAC settings, choose the input and output formats, and use Run if live calculation is off.

What Is a SHA-1 Hash?

SHA-1 (Secure Hash Algorithm 1) computes a fixed 160-bit message digest from input bytes. A digest contains 20 bytes; it takes 40 hexadecimal characters to write those bytes in Hex. Base64 provides another representation of the same result.

When a SHA-1 Calculator Is Still Useful

SHA-1 remains relevant when matching old checksums, investigating legacy software, or reproducing expected results in a test. Exact bytes matter: even a trailing space, a different line ending, or another input encoding changes the hash.

SHA-1 vs. SHA-256: Security Considerations

SHA-1 is vulnerable to practical collision attacks and is not suitable for new digital signatures or systems that rely on collision resistance. For new applications, use SHA-256 or an appropriately selected modern alternative. HMAC-SHA1 is a separate keyed construction and may still appear in established protocols; follow the security requirements of the system you are integrating with.

A SHA-1 hash is not encryption. It cannot be decrypted back into the input, and plain SHA-1 should not be used to store passwords.