Delimiter.live
Encoding & Security Tools Runs in your browser Free · no account

SHA-1 Hash Generator

The SHA-1 generator produces the 160-bit SHA-1 digest of your text as a 40-character hexadecimal string. SHA-1 is deprecated for security purposes and is provided for compatibility with systems that still require it.

Options
Text to hash 0 characters
SHA-1 digest

Your result will appear here.

Not sure where to start? Use Load example.

Results update automatically and are calculated on your device. Nothing you type is sent to a server.

Runs in your browser. Processing happens entirely in your browser. Nothing you enter is sent to Delimiter.live.

How to use the SHA-1 Hash Generator

  1. Type or paste the text you want to hash.
  2. The digest appears immediately and updates as you type.
  3. Choose uppercase or Base64 output if the system you are feeding expects that format.
  4. Copy the result.

Example

Input
hello
Output
aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d

Common use cases

  • Matching a Git object identifier or a legacy API signature.
  • Interoperating with a system that has not yet migrated to SHA-256.
  • Checking a SHA-1 checksum published with an older release.

Limitations and things to watch for

  • SHA-1 collision attacks have been demonstrated publicly since 2017 and are now inexpensive. Certificate authorities and browsers stopped accepting SHA-1 certificates years ago.
  • Do not use SHA-1 for signatures, integrity against an adversary, or passwords. Use SHA-256 instead for anything new.

Frequently asked questions

Is my input sent to a server?
No. Hashing uses the Web Crypto API built into your browser, so the value you type is never transmitted, logged or stored.
Can a hash be reversed?
Not directly — a cryptographic hash is one-way. But short or common inputs can be recovered instantly from precomputed tables, which is why passwords must be hashed with a slow, salted algorithm such as bcrypt or Argon2 rather than a plain digest.
Why do I get a different hash from another tool?
Almost always because of the input, not the algorithm. A trailing newline, different line endings or a different text encoding changes the bytes and therefore the digest. This tool hashes exactly what you type, encoded as UTF-8.

Share this tool