Skip to content

SHA-1 hash generator

SHA-1 of any text or file, computed locally with WebCrypto.

Runs in your browser — files never leave your device
Text to hash
SHA-1—
MD5—
SHA-256—
SHA-384—
SHA-512—

Generate a SHA-1 hash locally

SHA-1 still turns up in plenty of places: checksums published for older software, legacy APIs that sign requests with HMAC-SHA1, certificate thumbprints in Windows, and Git's original object IDs. This page computes the SHA-1 of text or of any file with your browser's WebCrypto, with the other common digests alongside.

SHA-1's status today

SHA-1 produces a 160-bit digest — 40 hex characters. Its collision resistance is broken: in 2017 the SHAttered project published two different PDFs with the same SHA-1, and by 2020 a chosen-prefix collision cost only tens of thousands of dollars of cloud computing. Browsers stopped trusting SHA-1 certificates in 2017.

That rules SHA-1 out for signatures and anything security-related that is new. Matching a checksum someone already published is still a fine use, and SHA-256 is the replacement wherever you have a choice.

A note for Git users: a blob ID is the SHA-1 of a short header plus the content, not of the raw file, so git hash-object and a plain SHA-1 of the same file differ.

Other conversions with this tool

How to generate a SHA-1 hash

  1. 1

    Type or paste text, or pick a file.

  2. 2

    The SHA-1 hash appears in the highlighted row.

  3. 3

    Copy it with one click.

SHA-1 Generator — frequently asked questions

Is my file uploaded anywhere?

No. The conversion runs in your browser, and this site has no server that could receive your file. A Content-Security-Policy blocks requests to other domains; you can confirm in DevTools → Network or by going offline.

Is SHA-1 broken?

For collision resistance, yes — two different PDFs with the same SHA-1 were published in 2017. It is still fine for matching legacy checksums, but use SHA-256 for anything new.

Why doesn't my file's SHA-1 match its Git hash?

Git hashes a header ("blob <size>\0") plus the content, not the raw file, so a git blob ID differs from the plain SHA-1 of the same file.

SHA-1 Generator guides