Skip to main content
DevCodivo

Hash Generator

Compute SHA-1, SHA-256, SHA-384 and SHA-512 hashes of any text, locally in your browser.

Runs in your browser — your data never leaves your deviceFree, no sign-up

How it works

Your text is encoded as UTF-8 and hashed with the browser’s Web Crypto API — the same cryptographic primitives the browser itself uses for TLS. All four algorithms (SHA-1, SHA-256, SHA-384, SHA-512) are computed in one pass, and each digest is shown as lowercase or uppercase hex, ready to copy.

Hashing is one-way: the digest uniquely fingerprints the input, but the input cannot be recovered from it.

Features

  • SHA-1, SHA-256, SHA-384 and SHA-512 in one click
  • Built on the platform Web Crypto API — no libraries
  • Lowercase or uppercase hex output
  • Copy each digest individually
  • 100% client-side — nothing leaves your browser

How to use

  1. Type or paste the text (or upload a .txt file).
  2. Press Compute hashes.
  3. Toggle uppercase if needed, then copy the digest for your algorithm.

Example

Input:    The quick brown fox jumps over the lazy dog
SHA-256:  d7a8fbb307d7809469ca9abcb0082e4f8d5651e46d3cdb762d02d0bf37c9e592

Frequently asked questions

Why is there no MD5?
MD5 is cryptographically broken (collisions can be produced in seconds) and is not implemented by the Web Crypto API this tool is built on. Hand-rolling a broken hash would create the false impression of security. If you need a checksum, use SHA-256; if you were told to use MD5 for a legacy system, this is not the tool for that.
Are these hashes suitable for passwords?
No. Plain SHA-256 is far too fast for password storage — modern GPUs try billions of guesses per second. Passwords need a deliberately slow, salted algorithm like bcrypt, scrypt or Argon2. Use this tool for file checksums, data integrity and fingerprinting, not passwords.
What is the difference between SHA-256, SHA-384 and SHA-512?
They are members of the same SHA-2 family, differing in output size (256, 384 and 512 bits) and internal block size. For most applications SHA-256 is the default choice; SHA-512 is not 'more secure' in a meaningful way for typical data — pick the one your system specifies.
Is SHA-1 still safe?
No — practical collision attacks exist against SHA-1, which is why browsers and certificate authorities dropped it. It is included here only because legacy checksums in the wild still need to be verified. Use SHA-256 or better for anything new.
Is my text sent to a server?
No. Hashing uses the browser's built-in Web Crypto API and happens entirely on your device. Nothing you type is transmitted anywhere — you can verify this in your browser's network inspector.

Related tools