Танҳо дар браузер

SHA-256 Hash Generator (Text/File Checksums)

Compute SHA-256 instantly in the browser. Generate hashes for text or files, copy in one click, and verify checksums without uploading.

Computed in your browser No file upload Copy & verify
Runs locally in your browser. No data is sent.

SHA-256 Calculation (Text)

Perimeter × Height
Hex
Input bytes: -
Verification status appears here
Recent hashes (last 5)
Ҳанӯз таърих нест
Омода

Танзимот

Иловагӣ

Тарзи истифода

SHA-256 Calculation (Text)
  1. Paste your text.
  2. SHA-256 appears automatically.
  3. Copy it or paste the expected hash to verify.
sha256 checksum (file)
  1. Drop or choose a file.
  2. Click Calculate SHA-256.
  3. Copy the checksum or verify it.

Why hashes differ even when text looks the same

If your sha256 checksum doesn't match, these are the usual causes.

Line endings

LF (\n) and CRLF (\r\n) are different bytes.

Trailing newlines or spaces

A single newline or space changes the bytes even if it looks identical.

Character encoding

UTF-8 hashes won't match hashes created from other encodings.

Unicode normalization

Visually identical characters can be different byte sequences (NFC/NFD).

Text vs file

Files can include BOMs or different line endings even with the same text.

Examples (verify correctness)
Empty string e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
abc ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad

Use these to confirm your result quickly.

Uncovered excess

Can you add MD5?

It's a candidate. Web Crypto API doesn't provide MD5, so we'd need a separate implementation. The first release focuses on SHA-256.

Does it work with files?

Yes. The browser reads your local file and calculates SHA-256 without uploading anything.

Why is my hash different for the same content?

Line endings (LF/CRLF), trailing spaces/newlines, non-UTF-8 encodings, and Unicode normalization differences all change the byte sequence.