calculate.sh DE

This tool runs in your browser using JavaScript. If it does not appear, please enable JavaScript or reload the page. The description below explains how it works.

Hash Generator

A cryptographic hash is a fixed-size fingerprint computed from arbitrary input. This tool computes SHA-1, SHA-256, or SHA-512 digests of the text you type, entirely in your browser - nothing is sent anywhere.

How to use

  1. Type or paste your input - the hash updates live as you type.
  2. Pick an algorithm - SHA-1, SHA-256, or SHA-512 (see below).
  3. UPPERCASE - toggle whether the hex letters are displayed in capitals. Like UUID case, this is purely presentation and does not change the value.
  4. Copy - copies the digest to your clipboard.
  5. Download - saves the digest to a .txt file (useful for checksum sharing).

Choosing an algorithm

  • SHA-256 - the modern default. 256-bit output (64 hex chars). The right choice for file checksums, integrity checks, and content fingerprints. Fast and widely supported. Two common jobs need more than a bare digest: message authentication uses SHA-256 inside HMAC (HMAC-SHA-256) with a secret key, and password storage needs a slow, salted password-hashing scheme (see below).
  • SHA-512 - 512 bits (128 hex chars). Stronger margin if you want extra headroom, at roughly double the output size. Useful when you need a larger digest or have a very security-sensitive use case.
  • SHA-1 - 160 bits (40 hex chars). Do not use for new work. Collision attacks against SHA-1 are practical, so it should only ever be used to compare against already-stored legacy hashes (e.g. git's older object IDs).

Notes

  • A hash always returns the same output for the same input - that is what makes it a fingerprint. Even a tiny change (a different byte, an added space) produces a completely different, uncorrelated digest.
  • Hashing is one-way: you cannot recover the input from the digest. That is why comparing two hashes is a good way to prove two inputs are identical without revealing them.
  • These are raw SHA digests - unsalted and unkeyed. Use them for checksums and integrity verification. Do not use a raw SHA hash to store or check passwords; use a dedicated password-hashing scheme (Argon2, scrypt, bcrypt) instead. To authenticate messages, use HMAC with a secret key rather than hashing the message on its own.
  • Everything runs in the browser with the WebCrypto crypto.subtle API - your text never leaves the page.