Ads Leaderboard

Hash Generator

Compute SHA-256, SHA-384 or SHA-512 digests of text directly in your browser using the native Web Crypto API — fast, offline and private.

Algorithm

Encoded as UTF-8 before hashing · Ctrl+Enter computes.

 

Hashing is one-way — a hash cannot be reversed to recover the input, and this tool is not encryption. Identical input always produces the same hash, so hashes are used to check integrity, not to hide data.

Ads In-Content

How to use Hash Generator

  1. Choose an algorithm: SHA-256, SHA-384 or SHA-512.
  2. Type or paste the text to hash (UTF-8 encoding is applied automatically).
  3. Click Generate hash (or press Ctrl+Enter).
  4. Copy the hexadecimal digest.

Features

  • SHA-256, SHA-384 and SHA-512 via the browser's Web Crypto API
  • Hex output with byte and character counts
  • UTF-8 input — hashes match what servers compute for the same text
  • Copy to clipboard, clear, Ctrl+Enter shortcut
  • No libraries, no network requests, no uploads

Important information

Hashing is one-way and is not encryption: a hash cannot be reversed to recover the input, but that also means a hash does not hide data — anyone with the input can recompute it. Use hashes to verify integrity (downloads, payloads, deduplication), never to store passwords directly; password storage needs a slow hash like bcrypt or argon2 with a salt. Identical input always produces the same digest, which is exactly what makes hashes useful for comparisons.

Frequently asked questions

Is hashing the same as encryption?

No. Encryption is two-way — data can be decrypted with a key. Hashing is one-way: it compresses input into a fixed-size digest that cannot practically be reversed. A hash is also not a secret, because the same input always produces the same output.

Why does my SHA-256 not match the server's?

Check the encoding: this tool hashes UTF-8 bytes. Servers hashing Latin-1, stripping whitespace, or hashing a file instead of its text content will produce different digests.

Is my input uploaded?

No. Digests are computed locally with crypto.subtle — no request is made.