Is my input sent to a server?

No. Hashing uses the browser's built-in Web Crypto API (crypto.subtle.digest) and runs entirely in your browser. Your text is never uploaded or stored.

Why isn't MD5 available?

MD5 is cryptographically broken and is not implemented by the Web Crypto API, so this tool deliberately omits it. For integrity checks or anything security-sensitive, use SHA-256 or stronger.

Can I reverse a hash back to the original text?

No. Cryptographic hashes are one-way functions. The only way to "reverse" one is to guess candidate inputs and hash them until one matches, which is infeasible for strong hashes and unpredictable inputs.

Gerador de Hash

Overview

A cryptographic hash maps input of any length to a fixed-size digest. The same input always produces the same digest, while a one-character change produces a completely different one. This tool computes SHA-1, SHA-256, SHA-384, and SHA-512 simultaneously as you type, using the Web Crypto API (crypto.subtle.digest).

How to use

Type or paste your text into Input.
All four digest fields — SHA-1, SHA-256, SHA-384, SHA-512 — update automatically as hexadecimal strings.
Copy the digest you need from its read-only field.

Examples

SHA-256 of hello → 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
SHA-1 of hello → aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d
Digest lengths in hex: SHA-1 = 40 chars, SHA-256 = 64, SHA-384 = 96, SHA-512 = 128.

Notes

SHA-1 is deprecated for security use — practical collision attacks exist; prefer SHA-256 or SHA-512. Hashing is not encryption: it provides integrity, not confidentiality. For passwords, never store a bare hash — use a salted, slow KDF such as bcrypt, scrypt, or Argon2. Input is hashed as UTF-8 bytes, so the digests match echo -n "text" | shasum -a 256 on the command line.