Hash Generator
Checksum text or a file — MD5, SHA-1, SHA-256, SHA-512. Private, client-side, click to copy.
Checksums and digests only — not encryption, and not for storing passwords (use a password hasher like Argon2/bcrypt in your app).
Hashed as UTF-8. Stays in your browser.
Digests are of the file bytes (or UTF-8 text), not the filename. Prefer SHA-256 for new work; MD5 and SHA-1 are for legacy matches only.
Sponsored
Ad space
How to use this tool
- Choose Text or File.
- Paste text, or drop a file (max 100 MB).
- Read the hex digests — SHA-256 is highlighted as the usual pick.
- Click a card to copy. Compare with the checksum you were given.
Checksums, not crypto theater
Real use in 2026 is still simple: verify a download, fingerprint a string for a cache key, or match a digest from docs. This page shows the four hashes people still search for — with SHA-256 as the default recommendation — and skips password hashing, HMAC builders, and rare algorithms most visitors never need.
Encoding binary or tokens for transport? Try Base64 Encode / Decode. Inspecting a signed token? Open the JWT Decoder. Generating a secret to hash later? Use the Password Generator.
FAQ
Is my text or file uploaded?
No. Hashing runs in your browser with the Web Crypto API (and a small MD5 routine). Nothing is sent to a server.
Which algorithm should I use?
SHA-256 for new checksums and digests. Use MD5 or SHA-1 only when you must match an existing value from old docs, APIs, or downloads.
Is a hash the same as encryption?
No. A hash is a one-way fingerprint. You cannot get the original text back from the digest. Encryption is reversible with a key.
Can I hash passwords with this?
Do not store password hashes from a general MD5/SHA tool. Password storage needs a slow, salted algorithm (Argon2, bcrypt, or scrypt) in your app — not a fast checksum.
Why does the same text always produce the same hash?
Hash functions are deterministic. Identical UTF-8 bytes always map to the same digest, which is why checksums work for verifying downloads and copies.
Do you hash the filename or the file contents?
The file contents — every byte inside the file. Renaming the file does not change the digests; changing even one byte inside it does.
What encoding is used for text?
UTF-8. That matches how most modern APIs and files treat string bytes.
Sponsored
Ad space