What is it?
The Hash Generator makes a hash (a short fingerprint code) of any text or file. It gives MD5, SHA-1, SHA-256, SHA-384 and SHA-512, which you can use to check that a file has not changed.
Who is it for?
People downloading software or ISO files who want to check them, developers and IT staff verifying files, and students learning how hashing works.
How to use it
- Type text, or choose a file.
- Read the MD5 and SHA hashes.
- To verify, paste the expected value in Compare with.
Check that a download is genuine
- Find the checksum on the official download page, usually labelled SHA-256.
- Tap Or choose a file and pick the file you downloaded.
- Paste the official value in Compare with (Paste a hash to check (optional)). A match means your file is exactly the same as the original, not damaged or changed.
The hash doesn’t match
- The download was incomplete or damaged: download it again.
- You are comparing different algorithms (an MD5 value against SHA-256). Compare like with like.
- You downloaded a different version or language of the file than the one the checksum is for.
- If it still doesn’t match from the official site, don’t open the file.
Text hashes
For text, every character counts: a space or line break at the end gives a completely different hash. Uppercase and lowercase hex results mean the same thing.
Good to know
- MD5 and SHA-1 are fine for spotting damaged files but are not secure against deliberate tampering. Prefer SHA-256.
- Hashes are one-way: you can’t get the text back from a hash. Don’t use plain hashes to store passwords.
- If you see This browser cannot make SHA hashes here, open the page over https in a recent browser.
Files are hashed inside your browser and never uploaded, so this works for private documents too.
Open the tool: Hash Generator (MD5, SHA-256)
Still stuck?
Contact support. Tell us which tool or page you were using, what you tapped, what you saw, and your phone or computer and browser (for example: Android phone, Chrome). We reply by email.






























Questions, or an error not listed here?
Tell us in the comments: what you were doing, the exact message you saw, and your device and browser. We read every comment and add new fixes to this article.