Skip to content
English
All tools

Categories

Developer ToolsEncoding & DecodingJSON & DataHash & ChecksumText ToolsDate & TimeNetwork ToolsFile ToolsMarkdown & Diagrams

SHA-1 Hash Generator

Compute the 160-bit SHA-1 digest of any text or hex bytes instantly.

Processed locally in your browser

Options
0 chars · 0 lines
The result will appear here.

What is SHA-1 Hash Generator?

SHA-1 maps any input to a 160-bit digest, shown as 40 hexadecimal characters. It was the workhorse of TLS certificates and code signing until practical collisions were demonstrated in 2017. It still appears in Git object IDs, older APIs, HMAC-SHA1 signatures and legacy checksums.

This generator converts your text to UTF-8 (or reads hex bytes), hashes it with a WebAssembly SHA-1 and returns the digest in hex or Base64 with the input length in bytes.

How does it work?

  1. Enter or paste text in the input box.
  2. Pick UTF-8 text or hex bytes as the input type, then hex or Base64 for the output.
  3. Copy the result; "abc" should give a9993e364706816aba3e25717850c26c9cd0d89d.

Common use cases

  • Checking a legacy checksum published as SHA-1 next to an old download.
  • Understanding how Git derives an object ID (Git hashes a header plus the content).
  • Verifying an OAuth 1.0 or webhook signature scheme that still relies on SHA-1.
  • Generating the fingerprint format expected by an older system.

Examples

Try this input in the tool above:

Input
The quick brown fox jumps over the lazy dog
Output
2fd4e1c67a2d28fced849ee1bb76e7391b93eb12

Privacy

SHA-1 Hash Generator runs entirely in your browser. The text or files you provide are processed on your device and are not uploaded, logged or stored on our servers.

Limitations

SHA-1 is deprecated for signatures and certificates because collisions are practical. It is acceptable only for non-adversarial checksums; use SHA-256 for anything security related.

Frequently asked questions

Is SHA-1 still secure?

Not against a determined attacker. Chosen-prefix collisions were shown in 2017 (SHAttered) and made cheaper since. Browsers and certificate authorities dropped it; use SHA-256 or SHA-3.

Why is a Git commit ID not simply the SHA-1 of my file?

Git hashes the text "blob <size>" plus a null byte before the content. So the SHA-1 of the bare file differs from its Git object ID.

How long is a SHA-1 hash?

160 bits: 20 bytes, 40 hex characters or 28 Base64 characters with padding.

Related tools

More tools in Hash & Checksum →