Is a hash the same as encryption?

No. A hash is a one-way fingerprint; you cannot decode it back to the original text. Encryption is reversible with a key. Prefer SHA-256 or stronger for new integrity checks.

Can I store passwords with MD5 or SHA-256?

No. Fast hashes are wrong for password storage. Use a slow, salted KDF such as Argon2, bcrypt, scrypt, or PBKDF2 in your auth stack—not a checksum from this page.

Why do MD5 and SHA-1 still appear here?

Many legacy checksums and fixtures still expect them. They are not collision-resistant enough for modern security decisions; use them only for compatibility comparisons.

No. Digests are computed locally in your browser.

Utill.net

Hash Generator

MD5, SHA-1, SHA-256 & SHA-512

Compute MD5, SHA-1, SHA-256, and SHA-512 hashes from text input. Use deterministic digests for checksums, comparisons, and fixtures.

Fast digests for checksums — not for password storage. Hashing runs only in your browser.

Uppercase hex

Characters0
OptionsAll algorithms
HexLowercase

Input

MD5
SHA-1
SHA-256
SHA-512

What is this tool?

This hash generator turns UTF-8 text into deterministic digests with MD5, SHA-1, SHA-256, and SHA-512. The same input and algorithm always produce the same hex fingerprint; a tiny input change produces a very different digest.

Hashes are for integrity checks, cache keys, fixtures, and comparisons. They are not encryption and must not be used alone for password storage—use a slow, salted KDF (Argon2, bcrypt, scrypt, PBKDF2) in your auth system.

By default the page shows all algorithms live as you type. Switch to one algorithm when you only need a single digest, and toggle uppercase hex to match case-sensitive consumers.

Common use cases

Compare a published checksum or fixture digest against pasteable text
Generate cache keys or content fingerprints for configs and snippets
Cross-check legacy MD5/SHA-1 values while preferring SHA-256 for new work

How to use

Paste the text to hash. Digests update live (no Generate click).
Stay on All algorithms for side-by-side rows, or One algorithm to focus on a single Select.
Optionally enable Uppercase hex. Use Sample for hello, then Copy a row or Copy all digests.
Prefer SHA-256+ for new integrity workflows; treat MD5/SHA-1 as legacy compatibility only.

Examples

Input / setting	Output	Notes
`hello` + MD5	`5d41402abc4b2a76b9719d911017c592`	Legacy 128-bit digest.
`hello` + SHA-256	`2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824`	Modern integrity fingerprint.
Empty string + MD5	`d41d8cd98f00b204e9800998ecf8427e`	Well-known empty digest—handy fixture edge.
`hello` + uppercase hex	Same bytes, `A–F` uppercase	Case-only change for picky APIs.

Practical pitfalls

Checksum ≠ password storage: Fast digests (even SHA-512) are cheap to brute-force offline. Password systems need slow, salted KDFs—not this tool’s output as a “hash password” field.
Web Crypto limits: Browser SubtleCrypto.digest does not expose MD5 (and treats SHA-1 as legacy). This page uses a local CryptoJS path so MD5/SHA-1 still work for fixture matching—do not assume every browser API can reproduce MD5 the same way.
Encoding mismatches (BOM, non-UTF-8 sources) change the digest even when the characters look identical on screen.

References

Last reviewed: 2026-07-27

Frequently asked questions

Is a hash the same as encryption?: No. A hash is a one-way fingerprint; you cannot decode it back to the original text. Encryption is reversible with a key. Prefer SHA-256 or stronger for new integrity checks.
Can I store passwords with MD5 or SHA-256?: No. Fast hashes are wrong for password storage. Use a slow, salted KDF such as Argon2, bcrypt, scrypt, or PBKDF2 in your auth stack—not a checksum from this page.
Why do MD5 and SHA-1 still appear here?: Many legacy checksums and fixtures still expect them. They are not collision-resistant enough for modern security decisions; use them only for compatibility comparisons.
Is my text uploaded?: No. Digests are computed locally in your browser.