Type anything and get its SHA-1, SHA-256, SHA-384 and SHA-512 digests at once. Hashing runs in the browser through the Web Crypto API.
A cryptographic hash maps any input to a fixed-length digest. SHA-256 always produces 256 bits, whether you feed it one character or a whole book. Change a single bit of the input and the output changes completely and unpredictably, which is the property that makes hashes useful for integrity checks.
All four algorithms are computed simultaneously so you can compare them. Digests are shown as lowercase hex; the uppercase toggle changes presentation only.
Use SHA-256 by default. It is unbroken and universally supported. SHA-512 is stronger still and faster on 64-bit hardware, but its 512-bit output is awkward in places where space matters. SHA-384 is a truncated SHA-512 that some compliance regimes name explicitly.
SHA-1 is only suitable for non-adversarial checksums now. Chosen-prefix collisions cost well under a hundred thousand dollars of GPU time, so it is fine for a file listing and not fine for signing.
There is no key, so nothing is decryptable — you go forward only. That one-wayness is what makes a hash a fingerprint rather than a container.
It also means plain SHA-256 is a poor password store. It is deliberately fast, so a GPU tries billions of candidates a second. Passwords belong in a memory-hard, tunable function: bcrypt, scrypt or Argon2. The salt is what stops two identical passwords from producing identical digests.
SHA-256, unless something specific requires otherwise. Avoid SHA-1 for security.
Not by computation. You guess inputs and hash them until one matches.
No. Use bcrypt, scrypt or Argon2 with a per-user salt.
No. The browser hashes it locally.