Hash Generator

How it works

A cryptographic hash reduces input of any length to a fixed-length digest. The same input always produces the same digest, and changing a single character changes the output completely. Hashes are used to check that a file or message has not been altered, to store password verifiers, and to build signatures.

Every algorithm is computed at once, so you can copy whichever the other system expects without switching modes. SHA-1, SHA-256, SHA-384, and SHA-512 come from the browser's built-in Web Crypto API; MD5 is computed by the page itself, because browsers do not expose it. Digests are shown as lowercase hex or as Base64.

Input is treated as UTF-8 text. The Web Crypto API is only exposed in a secure context, so the page has to be served over HTTPS for hashing to work.

Frequently asked questions

Which hash algorithms are supported?

MD5, SHA-1, SHA-256, SHA-384, and SHA-512. The SHA family comes from the Web Crypto API. MD5 is implemented in the page, since browsers deliberately omit a function that is broken for security purposes, and it is offered here only for legacy checksums such as file manifests and ETags.

Can I reverse a hash back to the original text?

No. Hashing is one-way by design. What is sometimes described as reversing a hash is really a lookup of precomputed digests for common inputs, not an inversion of the function.

Is SHA-1 still safe to use?

Not for signatures or anywhere collision resistance matters, since practical collisions have been demonstrated. It remains in use for non-security checks such as Git object identifiers. Prefer SHA-256 for anything new.

Why is a SHA-256 hash 64 characters long?

SHA-256 produces 256 bits, or 32 bytes, and each byte is printed as two hex digits. By the same rule SHA-1 gives 40 characters, SHA-384 gives 96, and SHA-512 gives 128.

Is the text I hash sent anywhere?

No. The digest is computed inside your browser and the tool makes no network requests, so your input never leaves your device.