Hash Generator

Generate MD5, SHA-1, SHA-256, and SHA-512 hashes from text or file input.

How to Use Hash Generator

1

Enter your text

Type or paste the text you want to hash.
2

Select algorithm

Choose MD5, SHA-1, SHA-256, SHA-512, or another hash function.
3

Copy the hash

Click copy to grab the generated hash digest string.

Tested tool guide Tested browser tools Checked August 16, 2026

What Hash Generator does, with a checked example

A hash is a fixed-length fingerprint of bytes: every input, from a single character to a gigabyte file, collapses to a short hexadecimal string, and any change to the input changes that string completely. This tool computes the fingerprint for text you paste or a file you select, across the MD5, SHA-1, SHA-256, and SHA-512 algorithms, all locally in the browser. The surprise most people hit: hashing is one-way and exact. There is no reverse operation, and a trailing newline, an extra space, or a CRLF-versus-LF line ending produces a totally different result.

Worked example

A concrete input and expected output from the current implementation.

Input

hello world

Expected output

MD5:    5eb63bbbe01eeed093cb22bb8f5acdc3
SHA-1:  2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
SHA-256: b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
SHA-512: 309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f

Each algorithm digests the same 11 bytes, so the four results differ only in length: 32, 40, 64, and 128 hex characters respectively. Change any character of the input, even add a trailing newline, and all four values change beyond recognition.

How the result is produced

Fixed-length digests

Each algorithm consumes the input's bytes and produces a digest of a length fixed by the algorithm: 128 bits for MD5, 160 for SHA-1, 256 for SHA-256, 512 for SHA-512, each rendered as hexadecimal. The digest is deterministic, so the same bytes always yield the same string, but the avalanche effect means that flipping a single bit changes roughly half of the output bits.

Exact bytes in, exact bytes out

The digest covers the exact bytes you provide. For pasted text, that is the literal characters; for a file, the raw bytes on disk. Anything that alters a single byte - a trailing newline, a trailing space, CRLF versus LF line endings, or a re-encoded file - yields a different digest, even when the content looks identical on screen. Processing happens locally in the browser, so the file never leaves your machine.

Good uses

Verify a download: hash the installer or ISO you just fetched and compare against the SHA-256 value published on the vendor's site; a match means the bytes arrived intact.
Prove a copy is byte-identical: hash a file before and after a transfer, backup, or archive round-trip and compare; equal digests mean no difference anywhere in the file.
Anchor a build artifact: record the SHA-256 of a release binary or config file in your release notes, then re-hash later to confirm nothing was modified or corrupted.

Limits and checks

One-way by design: hashing is not encryption. Nothing can reverse the digest into your text or file, and there is no undo. The only way to match a hash is to hash candidate inputs and compare.
No fuzzy matching: the digest reflects every byte. 'hello world' and 'hello world ' (trailing space) produce completely different hashes, and a mismatch does not say how much the inputs differ, only that they do.
MD5 and SHA-1 are cryptographically broken: both have publicly demonstrated collision attacks. They are fine for casual checksums but not where an adversary could exploit a collision; use SHA-256 or SHA-512 for anything security-relevant.

Common questions

Can this tool decrypt a hash or tell me what text produced it?

No. Hashing is one-way, and the tool has no reverse or decrypt mode. If the hidden input was short and guessable, someone can recover it by hashing candidate guesses and comparing digests, which is why MD5 and SHA-1 are not password hashing and why you should not paste password hashes into any hash tool.

Why does the same word give a different hash here than in another tool or website?

Almost always because the bytes differ, not because the tools disagree. Editors and websites often add a trailing newline, an extra space, or different line endings; any one of those changes the digest completely. Paste the exact same text, or hash the identical file, and every algorithm will produce matching values.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.