Utils365

SHA-1 hash generator

Get the 40-character SHA-1 of any text or file, for checksums and legacy systems.

  • 100% free
  • No sign-up
  • Runs in your browser

Type text, open any file, or drop one here. Text is hashed as UTF-8

Hashes

  • SHA-1

    —

  • MD5

    —

  • SHA-256

    —

  • SHA-384

    —

  • SHA-512

    —

SHA-1 is still used by Git and older checksums, but it’s broken for security since the 2017 SHAttered collision. Use SHA-256 for anything that has to resist tampering, and never a plain hash for passwords.

Paste the checksum from the download page to check your file. Case and spaces don’t matter.

Next: Base64 encode / decode · UUID generator

Report a problem with this tool

How to use SHA-1 hash generator

  1. Add text or a file

    Type or paste text, or open or drop a file. Nothing is uploaded; hashing happens on your device.

  2. Copy the SHA-1

    The SHA-1 hash is shown first and highlighted, ready to copy in hex or Base64. MD5 and SHA-2 hashes are below it.

  3. Compare if you need to

    Paste an expected SHA-1 checksum to check your file, or to confirm two copies are identical.

Why use Utils365

  • For older checksums

    Many older downloads, package mirrors and backup tools still publish SHA-1. Check them without installing anything.

  • See the stronger hashes too

    SHA-256 and SHA-512 are worked out at the same time, so moving to a safer hash costs nothing.

  • Private by design

    Your text and files never leave the browser, so it’s safe to hash confidential documents.

Frequently asked questions

What is SHA-1?

A 160-bit hash function from 1995, written as 40 hex characters. The SHA-1 of hello is aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d.

Is SHA-1 still secure?

No. In 2017 the SHAttered project produced two different PDFs with the same SHA-1, and attacks have only got cheaper since. Browsers stopped trusting SHA-1 certificates the same year.

Is it OK to use SHA-1 for checksums?

For catching accidental corruption, yes, it’s still reliable. For anything where someone might deliberately swap a file, use SHA-256 instead.

Does Git use SHA-1?

Yes, Git names commits and files by SHA-1 by default, with extra checks against the known collision attack. Newer Git can use SHA-256 repositories instead.

Can SHA-1 be used for passwords?

No. Plain SHA-1 hashes of leaked passwords are cracked in bulk. Use a password hash such as Argon2 or bcrypt, which is salted and deliberately slow.

Why does my Git object ID differ from this hash?

Git hashes a header such as blob 5 and a null byte before the file’s contents, so a Git blob ID isn’t the plain SHA-1 of the file.