Skip to tool content
Toolioz logoToolioz
Cryptographic Hashing

Hash Generator

A hash is a fixed fingerprint of text or file bytes. SHA-1, SHA-256, SHA-384, and SHA-512 are computed here with the Web Crypto API.

Input

Algorithms

Hash Output

Hash results will appear here

Private hashing

The digest is computed in the browser with the Web Crypto API. The text or file is not uploaded.

Immediate digest

Each selected algorithm returns a hex digest as soon as the input is hashed.

File checksums

Any file the browser can read can be hashed and compared with a published checksum.

Frequently Asked Questions

No. Hashing runs in the browser through the Web Crypto API. The text or file is not uploaded.

SHA-1, SHA-256, SHA-384, and SHA-512. SHA-256, SHA-384, and SHA-512 come from the SHA-2 family. The browser Web Crypto API computes them.

Yes. Text can be pasted, or any file the browser can read can be hashed from its raw bytes.

SHA-1 is cryptographically weak and is not suitable for certificates or new security designs. SHA-256 or SHA-512 is the appropriate choice for those uses.

Publisher notes · reviewed 10 September 2026

Hashes identify bytes; they do not encrypt them

SHA-256 and similar functions map input bytes to a fixed-size digest. The same input always yields the same digest. You cannot get the input back. That is not encryption, and it is not a password-storage recipe by itself.

Use and misuse

Hash a file to check it survived a download. Hash a string to compare equality without storing the string. Rainbow tables exist for common passwords, so use Argon2 or bcrypt for credentials, not raw SHA-256.

HMAC needs a key. If this page only exposes unkeyed hashes, do not treat the output as an HMAC. Encoding (Base64, hex) is not hashing.

Worked examples

  • Empty SHA-256

    SHA-256 of an empty input is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855. If the tool shows something else for empty input, the implementation is wrong or it hashed a newline.

Limits of this page

  • Not a certificate fingerprint UI for TLS inspection.
  • MD5/SHA-1 remain available in some tools only for legacy checksums; they are not collision-resistant for security.

Sources