Which hash should I use?

For integrity checks and modern security use SHA-256 or SHA-512. SHA-1 and MD5 are cryptographically broken for collision resistance and should only be used for non-security checksums or compatibility with legacy systems.

Is my text sent to a server?

No. SHA hashes are computed with the browser's built-in SubtleCrypto, and MD5 with a JavaScript implementation that runs on your device. The text never leaves your browser, so it is safe even for sensitive strings.

How is the text encoded before hashing?

The string is encoded as UTF-8 bytes, the standard expected by virtually every hashing tool and library. That means a hash here matches what you would get from sha256sum or most programming-language hash functions on the same UTF-8 text.

Why is the same text always the same hash?

Hash functions are deterministic: identical input bytes always produce identical output. That is what makes them useful for verifying that two pieces of text or files are exactly the same, or that data has not changed.

Can I get the original text back from a hash?

No. Hashes are one-way — there is no way to reverse a digest back into the input. Attackers only recover short or common inputs by brute force or precomputed tables, which is why salting and slow hashes matter for passwords.

Text Hash Generator — Gera Tools

A hash is a fixed-length fingerprint of any input. Type a string here and this tool computes its MD5, SHA-1, SHA-256, SHA-384, and SHA-512 digests instantly, all in your browser. Developers use hashes to verify data integrity, generate cache keys and ETags, deduplicate content, and match checksums published alongside downloads.

How it works

The tool encodes your text as UTF-8 bytes and feeds them to two engines:

SHA-1, SHA-256, SHA-384, SHA-512 are computed with the browser’s native crypto.subtle.digest, the same audited implementation used for TLS and Web Crypto. The result is rendered as a lowercase hex string.
MD5 is not part of SubtleCrypto, so it is computed with a compact, correct JavaScript implementation of the RFC 1321 algorithm — the same 128-bit digest produced by md5sum.

Because every algorithm is deterministic, the same text always yields the same digest, which is exactly what makes hashes useful for comparison and verification.

Security notes

MD5 and SHA-1 are broken for collision resistance — never use them to verify untrusted data or to protect passwords. They remain fine for non-adversarial checksums and legacy interoperability.
For new work prefer SHA-256 or SHA-512.
Hashing a password directly is not secure storage — use a slow, salted algorithm (bcrypt, scrypt, or Argon2) on the server. This tool is for hashing arbitrary text, not for password storage.