Hash Generator - MD5, SHA-1, SHA-256, SHA-512
Create MD5, SHA-1, SHA-256, SHA-384 and SHA-512 hashes from text you paste or from a file on your device, and compare a hash against one you already have.
Hash Generator
MD5, SHA-1, SHA-256, SHA-384 and SHA-512 for text or files, with HMAC.
The key is never saved.
Recent hashes
Only a label, the length and the SHA-256 are kept. Your text and key are never stored.
Saved data
Found a Bug or Missing a Feature?
Report any problems or suggest new features you want. You can write in English, Urdu, Hindi, or any language! Our AI will analyze your feedback and upgrade the tool.
About This Tool
Create MD5, SHA-1, SHA-256, SHA-384 and SHA-512 hashes from text you paste or from a file on your device, and compare a hash against one you already have.
Hash Generator for MD5, SHA-1, SHA-256, SHA-384, SHA-512 and HMAC
A hash is a fixed-length fingerprint of some data. Change one letter of the input and the fingerprint changes completely; feed in the same input tomorrow and you get the same fingerprint. That makes a hash the fastest honest answer to the question "are these two things identical?" The generator above produces five of them at once for pasted text or a file from your disk, and it can add an HMAC secret when you need to sign instead of just fingerprint.
Check a download in three steps
This is the job most people come for. A project publishes an installer along with a SHA-256 value, and you want to be sure the file you got is the file they built. Switch to the File tab, drop the installer in, and wait a moment while it is hashed locally. Then paste the published value into the compare box on the right. If it matches, that row turns green and the page names the algorithm. If it does not, the file was damaged on the way, or it is a different version, or someone swapped it. Either way, do not run it until you know which.
Picking an algorithm
The five options differ in length and in how much you should trust them. Written as hex, MD5 is 32 characters, SHA-1 is 40, SHA-256 is 64, SHA-384 is 96 and SHA-512 is 128. MD5 and SHA-1 have known collision attacks, so keep them for catching accidental damage and for matching old systems that still ask for them. SHA-256 is the sensible default for checksums, signatures and content addressing. SHA-384 and SHA-512 are from the same family with longer output, useful when a specification names them. You can switch algorithms off with the chips, and the output can be lowercase hex, uppercase hex, Base64 or URL-safe Base64.
Why your result differs from the one in the tutorial
When two hashes of "the same" text disagree, the text is rarely the same. A trailing newline is the classic culprit: many command-line examples hash a line that ends with one, and a text box does not add it. Windows line endings (CRLF) against Unix ones (LF) change every byte count too, which is why the tool has switches to trim the ends and to treat CRLF as LF. Text is encoded as UTF-8, so accented letters take more than one byte; a system using a different encoding will disagree. Letter case in hex does not matter, but Base64 against hex does. If you are hashing a JSON body, make sure both sides format it the same way first, and the JSON Formatter and Validator is a quick way to see what is really in the payload.
HMAC, for when two parties share a secret
A plain hash can be computed by anyone. An HMAC mixes in a secret key, so only someone holding that key can produce or check the value. Webhook providers use it to prove a request came from them: they send the body and a signature, and you recompute the HMAC with your shared secret and compare. Tick "Use HMAC", type the key, and each algorithm row is labelled HMAC-SHA256 and so on. The key is kept in the field only while the page is open. While testing, you can hash throwaway identifiers from the Random UUID Generator, although a UUID is not a substitute for a properly random secret.
A hash is not a password store
It is tempting to hash a password with SHA-256 and call it done. Do not. These algorithms are built to be fast, which is exactly what helps someone guessing millions of passwords per second. Real password storage uses slow, salted schemes such as bcrypt, scrypt or Argon2 on the server. Use this page for checksums, fingerprints and signatures, and for learning what the output looks like.
What stays on your device
Hashing happens in your browser, and files up to 256 MB can be handled before memory becomes a concern. SHA algorithms use the browser's built-in Web Crypto support, which needs a secure (HTTPS) page; MD5 is computed by the page itself. If you turn on history, only a label such as the file name and one hash are stored, never the text or the key, and you can switch it off in the History window.
Hash questions, answered
What is the MD5 hash of the word hello?
It is 5d41402abc4b2a76b9719d911017c592 in lowercase hex. A handy value for checking that any MD5 tool you use is working.
What is the SHA-256 hash of hello?
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824.
Why does empty text still produce a long hash?
Every input, including nothing at all, has a hash. The SHA-256 of empty text is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
Can a hash be turned back into the original text?
No. A hash is one-way. People recover weak passwords by guessing candidates and hashing them, not by reversing the hash.
Is MD5 still safe to use?
For spotting accidental corruption it is fine. For anything where someone could tamper with the data on purpose, use SHA-256 or longer.
Are my text, files and secret key uploaded?
No. Hashing runs in your browser. History keeps only a label and a single hash, and the HMAC key is never stored.
