Skip to main content

Hash Generator

Hash text and files locally, verify published checksums, and switch between hexadecimal and Base64 output.

Text hashes

Input size: 0 (UTF-8)

SHA-1

Legacy
Calculating…

SHA-256

Calculating…

SHA-384

Calculating…

SHA-512

Calculating…

File checksum

Only the selected algorithm is computed. 256 MiB limit. Files never leave your device.

Verify a checksum

The algorithm is inferred from a 40/64/96/128-character hex value. Lines such as “SHA256 (file) = …” are accepted.

All calculations stay in your browser; text and files are never uploaded. A fast hash is not a safe password-storage scheme. Use a salted password-hashing function such as Argon2id or bcrypt for stored passwords.

How to Use

  1. 1

    Enter text or choose a file. Select one algorithm for file hashing.

  2. 2

    Copy the result as hexadecimal or Base64. The known digest of an empty string is handled correctly.

  3. 3

    Paste a published checksum into the verification field and confirm that it matches.

Features

  • ✓Four simultaneous text digests and one selected file digest
  • ✓Hex and Base64 output with one-click copy
  • ✓Checksum verification with automatic algorithm detection
  • ✓Browser-only processing, race protection, and an explicit 256 MiB limit

FAQ

Q. Is my input sent to your server?

A. No. Hashing is processed entirely inside your browser.

Q. Can I hash files with this tool?

A. Yes. Drop a file and select the algorithm. Web Crypto reads files into memory in one pass, so this tool uses a 256 MiB limit for stability.

Technical Notes

The tool uses the Web Crypto API via crypto.subtle.digest for secure hash computation.

Text is converted to UTF-8 bytes with TextEncoder before hashing.

Security & Privacy

Input text never leaves your device and is not transmitted over the network.

This design is suitable for private verification workflows.

Examples, Security Cautions, and Common Mistakes

Examples

  • Compare a downloaded file's SHA-256 hash with the value published by the distributor.
  • Check whether a string or configuration value changed by comparing hashes before and after.
  • Create fixed-length identifiers for test data without displaying the original value directly.

Cautions

  • Prefer SHA-256 or stronger for integrity checks; MD5 and SHA-1 are weak against collisions.
  • Hashing is not encryption. Short inputs may still be guessed by brute force.
  • For password storage, use a dedicated salted password hashing algorithm instead of a simple hash.

Common Mistakes

  • Assuming an MD5 match proves security instead of only matching one weak digest.
  • Ignoring case, line breaks, or trailing spaces that change the resulting hash.
  • Storing passwords with a single unsalted SHA-256 hash.

Related Tools