Get MD5, SHA-1, SHA-256, SHA-384 and SHA-512 hashes for typed text or a dropped file, all on one screen. Hashing runs in your browser and files are never uploaded.
Your files are processed in your browser, on your own device. Nothing is uploaded to a server.
The Hash Generator works out MD5, SHA-1, SHA-256, SHA-384 and SHA-512 hashes for text or a file, all five on one screen. Type or paste text, or drop a file in, and each result lands with its own copy button. It is free, runs in your browser, and your files are never uploaded.
Type or paste text and it is hashed as its UTF-8 bytes, so the same words give the same result here as in any tool that follows the standards. Drop a file in and the tool reads it on your device in chunks of 1 MB, which keeps the tab responsive while a large file goes through. The SHA values come from the Web Crypto API built into your browser, and MD5 comes from a small library, because Web Crypto does not offer MD5.
Hashes are fingerprints. Change one character in the input and every hash changes completely, which is why a match carries weight. The uppercase switch changes only how a result is written, capitals instead of small letters, because publishers print checksums both ways. The value underneath stays exactly the same either way.
Checking a download is the classic job. A publisher prints a checksum next to an installer, an ISO or a firmware file, and hashing your copy tells you whether the file that arrived is the file they sent. One different character in the hash and something changed on the way.
Transfers are the second job. A file crosses a shaky connection, a borrowed drive or a chain of laptops, and nobody wants to trust a progress bar. Hash the file at both ends and compare the rows. It takes a moment and settles the question for good.
Support tickets and backup logs make the third. A fingerprint attached to a ticket, a release note or a backup record lets a future copy be proven identical months later. If two hashes match, you are holding the same file, and if they differ by one letter, you are not. There is no middle state to argue about.
Two of the five algorithms are weak, and the page says so rather than letting the tidy table imply otherwise. MD5 and SHA-1 have known collisions, meaning different inputs can be crafted to share a hash. Both are fine for spotting accidental damage and for casual checksum work. Neither belongs in signatures or any security decision.
Hashing is not password storage. Every algorithm here is built for speed, and password storage needs slow hashing made for that job, such as bcrypt, scrypt or Argon2. Do not store passwords with anything on this page, no matter how long the output looks.
Files answer to your device. Reading in 1 MB chunks keeps the tab responsive, but a file of several gigabytes still takes real time and memory on your machine, and performance depends on the hardware you have. The SHA digests also need the Web Crypto API, which browsers only open on secure pages. This site is served over HTTPS, so the tools work here as intended.
The hashing runs on your device. Text you type and files you drop are not sent to a server, not stored by ToolPeko and not read by anyone here. There is no account and no daily cap. Close the tab and your inputs and results go with it.
Five: MD5, SHA-1, SHA-256, SHA-384 and SHA-512. All five are worked out in one pass for text and for files, each with its own copy button.
Yes. The file is read on your device in chunks of 1 MB and hashed inside your browser. Nothing about the file leaves your machine.
Either the file differs from the published one, even by a single byte, or the comparison tripped on letter case. Letter case is display only, so compare with the uppercase switch set to match how the checksum was printed.
No. MD5 is weak and fast, and both qualities are wrong for passwords. Password storage needs slow hashing built for the job, such as bcrypt, scrypt or Argon2.
Only the letters in the output, capitals instead of small ones, so a result lines up with a checksum printed in capitals. The hash value itself does not change.
No. Hashing happens in your browser, and nothing is sent to or kept on a ToolPeko server.
Same rules as this one: free, in your browser, with nothing uploaded.
Paste messy JSON, get it neat and valid.
Check JSON and find the exact line that breaks it.
Squeeze JSON down to one tight line.
Open JSON as a tree you can fold and explore.
JSON rows turned into a CSV a spreadsheet can open.
A CSV file turned into clean JSON objects.
JSON rewritten as YAML for config files.
YAML config turned into JSON you can use in code.