Hash Generator
MD5, SHA-1, and SHA-256/384/512 of text or a file, computed locally.
By opening this website or using its tools, you agree to our Terms and Privacy Policy.
Your file never leaves your browser during processing
How it works
To hash something, switch between Text and File above and provide the input — all five hashes (MD5, SHA-1, SHA-256, SHA-384, SHA-512) compute instantly in your browser and nothing is ever uploaded.
A hash function turns any input, of any length, into a fixed-size fingerprint — the same input always produces the same hash, and changing even one byte produces a completely different one. That makes hashes useful for verifying a download matches what the publisher intended, or for comparing two files without transmitting either of them.
SHA-1, SHA-256, SHA-384, and SHA-512 are computed with the browser’s native SubtleCrypto API — the same cryptographic engine used elsewhere on the web for real security work. MD5 is not: it was removed from SubtleCrypto years ago because it is broken for anything security-sensitive (collisions — two different inputs producing the same hash — can be engineered deliberately), so it is implemented here by hand, in JavaScript, purely because MD5 checksums are still what a lot of older download pages and file utilities publish for a basic integrity check.
File hashing reads the file into memory and processes it locally the same way as text — nothing about the file is uploaded at any point, which the network monitor below confirms directly rather than asking you to trust a privacy policy.
FAQ
Is my file uploaded to compute the hash?
No. The file is read and hashed entirely in your browser using the Web Crypto API (and a local MD5 implementation). The live network monitor on this page confirms zero bytes are sent.
Why is MD5 included if it’s considered broken?
MD5 is cryptographically broken for security purposes — an attacker can craft two different files with the same MD5 hash. It remains useful here purely as a basic corruption/integrity check against checksums that download pages still publish in MD5.
Which hash should I use to verify a download?
Whichever one the publisher provided next to the download — comparing hash algorithms only works if you compute the same one they did. Prefer SHA-256 or better if you have a choice.
Do large files slow this down?
SHA-1/256/384/512 use the browser’s native engine and stay fast even on large files. The hand-written MD5 implementation is pure JavaScript and will be noticeably slower on very large files.