Hash Generator: MD5 and SHA in Your Browser
Get MD5, SHA-1, SHA-256 and SHA-512 for any text or file, and paste a checksum to verify a download. Everything is hashed on your device.
Rate this toolChecksum Studio
Text or file · four algorithms · verify a match
Your input
Hashes update as you type. Spaces and line breaks count: they change the hash.
Compare / verify hash
If it matches any of the generated hashes, we tell you which algorithm it matches.
Your hashes
Type or paste text. MD5, SHA-1, SHA-256 and SHA-512 appear here.
MD5 runs in plain JavaScript and is skipped for files over 50 MB. The SHA hashes use your browser's built-in Web Crypto.
- Hash algorithms
- 4Hash algorithms
- Largest file
- 500 MBLargest file
- SHA-256 hex characters
- 64SHA-256 hex characters
- Files uploaded
- 0Files uploaded
Keep working with your data
Tools that pick up where this one leaves off.
Hash text or a file in three steps
From a file or a line of text to four checksums you can copy or compare, without uploading anything.
- STEP 01
Type or drop
Type text, or switch to File and drop any file up to 500 MB.
Text hashes as you type - STEP 02
Read the hashes
MD5, SHA-1, SHA-256 and SHA-512 appear together, each with a copy button.
All four at once - STEP 03
Compare
Paste the checksum a website published to see if your file matches.
Case doesn't matter
How to use this hash generator
The most common job is checking a download: hash the file, paste the published checksum, read the verdict.
- 1
Pick text or file
Text mode hashes exactly what you type, spaces and line breaks included. File mode hashes the file's bytes.
- 2
Find the published hash
Software sites list a checksum, usually SHA-256, next to the download. Copy it from the official page.
- 3
Paste it to compare
The tool checks it against all four hashes and names the algorithm that matched.
- 4
No match? Stop
A mismatch means the file changed or the download broke. Download again from the official source.
What makes a checksum check worth doing
Four habits that turn a hash into real proof that a file is the one you meant to get.
Prefer SHA-256
MD5 and SHA-1 have known collision attacks. Use SHA-256 or SHA-512 when you have the choice.
- SHA-256 for downloads
- MD5 only for legacy
- Never MD5 for signatures
Get the hash elsewhere
A checksum on the same hacked page as the file proves little. Use the official site or a signed file.
- Official project page
- Signed checksum files
- Not a mirror's copy
Compare every character
Eyeballing the first few characters isn't enough. Paste the full hash and let the tool compare.
- Paste the whole hash
- Case is ignored
- Spaces are trimmed
Hash locally
Private files shouldn't be uploaded to be hashed. Here they're read by your browser and never sent.
- No upload
- Works offline once loaded
- Nothing stored
MD5, SHA-1, SHA-256 and SHA-512 compared
Same idea, different digest lengths and very different safety today.
| Algorithm | Digest | Hex length | Status | Typical use |
|---|---|---|---|---|
| MD5 | 128 bits | 32 characters | ✗ Broken for security | Old checksums, cache keys |
| SHA-1 | 160 bits | 40 characters | Retire by 2030 (NIST) | Legacy systems, old Git IDs |
| SHA-256 | 256 bits | 64 characters | ✓ Current standard | Download checksums, signatures |
| SHA-512 | 512 bits | 128 characters | ✓ Current standard | Where a longer digest is wanted |
Browsers' Web Crypto API has no MD5, so this tool computes MD5 in plain JavaScript. To keep the page responsive it skips MD5 for files over 50 MB; the three SHA hashes still work up to 500 MB.
Where checksums turn up
The same four hashes, used for very different jobs.
Software downloads
Projects publish a SHA-256 next to each installer or disk image so you can check it arrived intact.
Developers and DevOps
Checking that a build, a container layer or a package matches what the pipeline produced.
Backups and archives
A hash taken at backup time shows later whether a stored file has changed.
Security and forensics
Recording a file's hash proves it wasn't changed between collection and review.
Three things every hash does
These properties are why a short string can stand in for a whole file.
Same input, same hash
Hash the same bytes anywhere, on any device, and you get the same result every time.
- Repeatable everywhere
- Fixed length output
- Any size of input
One change, new hash
Change one character or one byte and the hash looks completely different.
- “hello” vs “Hello” differ
- A trailing space counts
- Line endings count
Common mistakes
These give a “no match” even when the file is fine, or a false sense of safety.
- Comparing an MD5 to a SHA-256
- A stray space or newline in text
- Trusting a hash from the same page
- Using MD5 for passwords
Keeping checksums useful over time
A hash is only as good as the record you keep of it.
- 1
Store hashes with files
Keep a SHA256SUMS-style text file next to your archives, listing each file and its hash.
- 2
Move off MD5 and SHA-1
NIST says to phase SHA-1 out by 31 December 2030. Re-hash old records with SHA-256 when you touch them.
- 3
Re-check before restoring
Before relying on a backup, hash it again and compare with the stored value.
- 4
Note where it came from
Write down where each expected hash came from, so you can trust it later.
This tool vs command-line tools vs upload sites
All three compute the same hashes. They differ in where your file goes and how easy it is.
| Feature | CleverTools hash generator | sha256sum, certutil, shasum | Sites that upload the file |
|---|---|---|---|
| File leaves your device | ✓ Never | ✓ Never | ✗ Yes |
| Four algorithms at once | ✓ Yes | One command each | Varies |
| Compare with a pasted hash | ✓ Built in | By eye or script | Varies |
| Very large files | Up to 500 MB | ✓ Any size | ✗ Upload limits |
| Install or terminal needed | ✓ No | Terminal | ✓ No |
| Cost | ✓ Free | ✓ Free | Varies |
Need a strong password rather than a hash? Use the Password Generator.
Pro tips for checksums
Small things that cause most “it doesn't match” moments.
Watch the newline
Text copied from a file often ends with a line break. It changes the hash.
Count the characters
32 hex characters is MD5, 40 SHA-1, 64 SHA-256, 128 SHA-512.
Hash the file, not its name
Renaming a file doesn't change its hash. Editing a single byte does.
Paste, don't retype
One wrong character makes a match fail. Paste the published hash.
Not for passwords
Fast hashes like SHA-256 are the wrong tool for storing passwords. Use Argon2id or bcrypt.
Hash is not encryption
You can't get the text back from a hash, and a hash doesn't hide short, guessable inputs.
Pin versions
In scripts, pin the expected SHA-256 of what you download and fail if it differs.
Signed is better
A checksum file signed by the project proves who published it, not just that it's intact.
If the published hash is 64 characters, it's SHA-256, so compare it with the SHA-256 line. The compare box does this for you and names the algorithm that matched.
Hashing or encrypting? Know which one you need
Both scramble data, but only one can be undone. Picking the wrong one is a common security mistake.
Did this data change?
A fixed-length fingerprint of the data. Good for checking integrity and spotting duplicates. There is no key and no way back.
Best for checksums and file integrity
Keep this data secret
Scrambles data so only someone with the key can read it again. Use it when you need the original back later.
Best for files and messages you must read later
Who uses this hash generator
Six everyday jobs for a checksum.
Anyone downloading software
Checking an installer or ISO against the SHA-256 on the official site.
Developers
Generating a quick SHA-256 of a string for a test, a cache key or an API example.
DevOps engineers
Confirming a build artefact matches the one the pipeline recorded.
Archivists
Recording hashes of stored files so later changes can be spotted.
Security analysts
Hashing a suspicious file to look it up, without uploading the file itself.
Students
Seeing how a one-letter change produces a completely different hash.
Frequently asked questions
Quick answers about the algorithms, file limits and what a hash can prove.
What is a hash?
Which hash should I use?
Is this free?
Can I hash files?
What people say
Reviews from people who used this tool.
Loading reviews…
Popular presets
Jump to a version of this tool already set up for a specific need.
More free developer tools
Free, with no sign-up, just like this one.
- Free toolFavicon GeneratorTurn any image into the full favicon set - six standard sizes plus the HTML meta tags ready to paste, generated locally in your browser.Try it now
- Free toolCron Expression GeneratorBuild, preview, and copy cron expressions visually with presets and next run time previewTry it now
- Free toolCSS Gradient GeneratorCreate beautiful CSS gradients visually - linear, radial, conic with live preview and code outputTry it now
- Free toolBase64 Encoder / DecoderEncode text to Base64 or decode Base64 strings instantly in your browserTry it now
- Free toolJWT DecoderDecode and inspect JSON Web Tokens - view header, payload, expiry, and claims instantlyTry it now
- Free toolUnix Timestamp ConverterConvert Unix timestamps to human dates and vice versa with live clockTry it now