Free tool
MD5 Hash Generator (plus SHA-1, SHA-256 and SHA-512)
Hash text or a file with MD5, SHA-1, SHA-256 and SHA-512 at once, and check whether a hash matches. Files are hashed in your browser, never uploaded.
- MD5
- –
- SHA-1
- –
- SHA-256
- –
- SHA-512
- –
An MD5 hash generator turns any text or file into a short fingerprint of 32 hex characters, so you can check whether a download arrived intact or two files are identical. This one shows MD5, SHA-1, SHA-256 and SHA-512 at the same time and can tell you which of them matches a hash you paste in. Everything runs in your browser: text and files are hashed on your device and never uploaded.
How to use the MD5 hash generator
- Type or paste text into the text box. It is hashed as UTF-8, exactly as typed.
- Or select Or choose a file… to hash a file on your computer instead.
- Read the four hashes: MD5, SHA-1, SHA-256 and SHA-512, in lowercase hex. Tick Uppercase to show them in capital letters.
- Select Copy next to a hash to put it on your clipboard.
- To check a hash, paste it into Compare with. The tool says which algorithm matches, or that none of the four does. Upper and lower case are treated the same.
How does the MD5 hash generator work?
It hashes your text or file inside your browser. MD5 comes from the page’s own RFC 1321 code, and SHA-1, SHA-256 and SHA-512 come from the browser’s Web Crypto API.
A hash function reads any amount of data and produces a fixed-length digest. NIST’s Secure Hash Standard (FIPS 180-4) describes the key property: any change to the message will, with a very high probability, result in a different digest. That’s what makes hashes useful for spotting corrupted or altered files.
| Algorithm | Digest size | Hex characters | Computed by | Use for security? |
|---|---|---|---|---|
| MD5 | 128 bits | 32 | The page’s own MD5 code (RFC 1321) | No |
| SHA-1 | 160 bits | 40 | Browser’s Web Crypto | No |
| SHA-256 | 256 bits | 64 | Browser’s Web Crypto | Yes, for integrity |
| SHA-512 | 512 bits | 128 | Browser’s Web Crypto | Yes, for integrity |
The SHA family comes from crypto.subtle.digest, the browser’s built-in Web Crypto API, which supports SHA-1, SHA-256, SHA-384 and SHA-512. It has no MD5, so the page computes MD5 with its own implementation of the RFC 1321 algorithm. All four results are shown as hex, two characters per byte.
Text is converted to UTF-8 bytes before hashing, the same way MDN’s digest() example does it, so letters with accents or emoji give the same hash as in other UTF-8 tools. A file is read whole into memory and hashed locally. That works for any file your browser can load, but a very large file takes longer and uses roughly its own size in memory.
MD5 and SHA-1 are not for passwords or security
RFC 1321, published in 1992, intended MD5 for digital signatures, but that use is long over. RFC 6151 says MD5 “is no longer acceptable where collision resistance is required” and must not be used for digital signatures. MDN warns that SHA-1 is also considered vulnerable for cryptographic use, and Microsoft’s Get-FileHash documentation says MD5 and SHA-1 should only be used for simple change validation.
What they are still fine for:
- Checksums that catch accidental corruption, such as a broken download or a bad copy. RFC 6151 accepts MD5 used solely to protect against errors.
- IDs and cache keys, where you need a short, stable fingerprint of some data and nobody gains anything by forging a match.
Important: Never store passwords as MD5, SHA-1 or plain SHA-256 hashes. NIST SP 800-63B requires passwords to be “salted and hashed using a suitable password hashing scheme”, which takes a password, a salt and a cost factor. Use the password hashing function your framework or language provides instead of a general-purpose hash.
Worked examples
The hashes of “hello” (5 characters, no line break):
| Algorithm | Hash |
|---|---|
| MD5 | 5d41402abc4b2a76b9719d911017c592 |
| SHA-1 | aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d |
| SHA-256 | 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824 |
| SHA-512 | 9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca72323c3d99ba5c11d7c7acc6e14b8c5da0c4663475c2e5c3adef46f73bcdec043 |
With Uppercase ticked, the MD5 reads 5D41402ABC4B2A76B9719D911017C592: the same value.
One capital letter changes everything. The MD5 of “Hello” is 8b1a9953c4611296a827abf8c47804d7, which shares nothing visible with the hash of “hello”.
A hidden line break. A file that contains “hello” followed by a line break holds 6 bytes, not 5, and its MD5 is b1946ac92492d2347c6235b4d2611184. If your hash doesn’t match someone else’s, a trailing line break is the first thing to check.
Accented letters. “café” is 4 characters but 5 bytes in UTF-8 (63 61 66 c3 a9), because é takes two bytes. Its MD5 is 07117fe4a1ebd544965dc19573183da2.
RFC 1321’s own test value. The MD5 standard lists MD5(“abc”) = 900150983cd24fb0d6963f7d28e17f72, which is a quick way to check any MD5 implementation.
Check a download. Choose the downloaded file with Or choose a file…, then paste the hash from the publisher’s download page into Compare with. “Match: this is the SHA-256 hash of your file.” means the file is the one the publisher hashed. On Windows you can get the same SHA-256 without a browser in PowerShell:
Get-FileHash "$env:USERPROFILE\Downloads\setup.iso" -Algorithm SHA256
This prints the algorithm, the hash in uppercase hex and the file path. Replace setup.iso with your file’s name; -Algorithm also accepts SHA1, SHA384, SHA512 and MD5, and SHA256 is the default.
Related guides
- Name-based UUIDs are built from MD5 (version 3) or SHA-1 (version 5) hashes: identify any UUID’s version with the UUID generator.
- A JWT signed with HS256 carries an HMAC built on SHA-256: decode the token’s header to see which algorithm it names.
- A matching hash shows a file wasn’t changed, not that it’s safe. Our guide to the Windows SmartScreen warning shows how to check a download’s source and publisher.
- SHA-1 is being phased out in SSH too: see why OpenSSH stopped offering its old SHA-1 key exchange methods by default in SSH KexAlgorithms.
Frequently asked questions
Is MD5 safe for storing passwords?
No. MD5 and SHA-1 are fast and no longer collision resistant, and even SHA-256 on its own is not a password hash. NIST requires passwords to be salted and hashed with a suitable password hashing scheme that has a cost factor; use the one your framework or language provides.
Can an MD5 hash be decrypted?
No. A hash is not encryption, and there is no key that turns it back into the input. Short or common inputs can still be found by guessing and comparing hashes, which is why fast hashes are unsuitable for passwords.
Why is my hash different from another tool's?
The input bytes differ. The usual causes are a line break at the end of the text, different capital letters, or a different text encoding. This tool hashes text as UTF-8, exactly as typed.
Are my files uploaded?
No. A file you choose is read and hashed inside your browser. Nothing is sent to a server, but very large files take longer and need enough free memory to load them.
Which hash should I use to check a download?
Use the one the publisher lists. If it offers several, prefer SHA-256 or SHA-512: Microsoft's documentation says MD5 and SHA-1 should only be used for simple change validation, not where tampering matters.
Does uppercase or lowercase matter?
No. Hex hashes are the same value in either case, and the Compare with field ignores case. Windows PowerShell's Get-FileHash, for example, prints hashes in uppercase.
Related guides

Free tool
UUID Generator (Version 4 and Version 7)
Generate up to 1,000 random version 4 or time-ordered version 7 UUIDs, and check the version, variant and timestamp of any UUID you paste.
Free calculator
Free Developer and PC Tools
Free formatters, decoders and converters for developers and PC users. Everything runs in your browser, and nothing you type is sent anywhere.
3 min read