All free tools

SHA-1 hash generator

Type text or choose a file to get its SHA-1 hash at once, in hex and Base64, and check it against a published checksum.

Runs in your browser. Your text and files are hashed on your device and never uploaded to EpiFive.

Hash

How to use it

  1. Choose Text and type, or A file and pick one. The SHA-1 hash appears straight away.
  2. Tick Uppercase hex if you are comparing against a checksum in capitals.
  3. Paste the expected SHA-1 into the compare box to check a download.
  4. Tap Show all algorithms for MD5, SHA-256, SHA-384 and SHA-512 of the same input.

Where you still meet SHA-1

  • Git commit and object IDs, the long hex strings in every repository.
  • Older download pages and package mirrors that publish .sha1 files.
  • HMAC-SHA1 in older APIs and one-time-password apps (TOTP), where the collision weakness does not apply in the same way.

Security caveats

SHA-1 is broken for collision resistance: attackers can make two different files that share a SHA-1 hash. That rules it out for digital signatures, certificates and any check where someone might swap the file on purpose. It was never suitable for passwords, because it is far too fast to slow down guessing; use bcrypt or Argon2 for those. For new checksums choose SHA-256.

Verifying a checksum

Choose the downloaded file, paste the SHA-1 from the publisher into the compare box and look for the match. A mismatch means the file is incomplete, corrupted or not the release you expected.

Test values

  • SHA-1 of abc: a9993e364706816aba3e25717850c26c9cd0d89d
  • SHA-1 of an empty input: da39a3ee5e6b4b0d3255bfef95601890afd80709

The hash generator shows all five algorithms side by side.

  • Hash generator: MD5, SHA-1, SHA-256 and SHA-512 hashes of text or files, and checksum verification.
  • MD5 hash generator: MD5 hash of text or a file, with checksum verification. For checksums only, not for passwords.
  • SHA-256 hash generator: SHA-256 hash of text or a file in hex and Base64, and verify a download against its published checksum.
  • SHA-512 hash generator: SHA-512 hash of text or a file in hex and Base64 (for SRI and npm integrity), with checksum verification.
  • Base64 encode and decode: Encode or decode Base64 text (UTF-8 safe) and convert files to and from Base64.

Questions people ask

What is a SHA-1 hash?

SHA-1 is a hash function published by the US NIST in 1995. It turns any input into a 160-bit value written as 40 hexadecimal characters. Identical inputs give identical hashes, and any change to the input gives a completely different one.

Is SHA-1 still safe to use?

Not for security. In 2017 the SHAttered project produced two different PDF files with the same SHA-1 hash, and collisions have become cheaper since. Browsers stopped trusting SHA-1 certificates in 2017, and NIST plans to retire SHA-1 by 2030. Do not use it for signatures, certificates or passwords; use SHA-256 or SHA-512.

Why does Git use SHA-1?

Git names every commit, file and folder by its SHA-1 hash, which was chosen to detect corruption rather than to resist attacks. Git now uses a hardened SHA-1 that detects known collision attacks, and it supports SHA-256 repositories as a newer option.

What is the difference between SHA-1 and SHA-256?

SHA-1 gives a 160-bit hash (40 hex characters) and is broken for collisions. SHA-256 belongs to the SHA-2 family, gives a 256-bit hash (64 hex characters) and has no known practical attacks, which is why it replaced SHA-1 for TLS certificates, software signing and checksums.

How do I get the SHA-1 of a file without this page?

On Windows, run certutil -hashfile file.iso SHA1. On macOS and Linux, run shasum -a 1 file.iso, or sha1sum file.iso on Linux. The result should match the 40 characters shown here.