Hash Generator
Type or paste text to get its SHA-256, SHA-1, and SHA-512 hashes.
Developer tool
Generate SHA-256, SHA-1, and SHA-512 hashes from any text, instantly and privately.
Type or paste text to get its SHA-256, SHA-1, and SHA-512 hashes.
Continue with nearby developer and data utilities.
Type or paste any text into the input box. The tool computes the SHA-256, SHA-1, and SHA-512 digests at the same time and shows each one as a string of hexadecimal characters. Use the Copy button next to a result to put that digest on your clipboard so you can paste it into a release note, a verification script, or a chat message. Because the same input always produces the same output, you can re-hash a value later and compare it character by character to confirm the data has not changed.
A cryptographic hash function takes input of any size and returns a fixed-length value called a digest, hash, or fingerprint. Three properties make it useful: the same input always yields the same digest, even a one-character change produces a completely different digest, and it is computationally infeasible to work backwards from the digest to the input. Unlike encryption there is no key and no way to decrypt, which is exactly why hashing is the right tool for verifying integrity and comparing values, but the wrong tool when you actually need to recover the original data.
Each algorithm produces a digest of a fixed length, shown below as the number of hexadecimal characters. The right choice depends on whether you need a fast non-security checksum or a collision-resistant digest for security work.
| Algorithm | Digest length | Typical use |
|---|---|---|
| MD5 | 128-bit / 32 hex | Legacy checksums and cache keys only - not safe for security |
| SHA-1 | 160-bit / 40 hex | Legacy Git object IDs - not safe for new security work |
| SHA-256 | 256-bit / 64 hex | Recommended default: file integrity, signatures, certificates |
| SHA-512 | 512-bit / 128 hex | Same security family as SHA-256, faster on some 64-bit systems |
MD5 and SHA-1 are kept here for compatibility with old systems. Practical collision attacks exist against both, so never rely on them to prove that data is authentic.
Suppose a project lists the SHA-256 hash of its installer as e3b0c442.... You download the file, run it through this tool (or a command-line tool such as sha256sum), and read off the digest. If your value matches the published one exactly, the file is intact; if even one byte was corrupted or tampered with in transit, the two hashes diverge completely and the mismatch warns you not to trust the file.
Hashing turns any input into a compact, fixed-length fingerprint that is easy to store, index, and compare. Developers use it to verify downloads, generate checksums for backups, deduplicate files, build stable cache keys, sign and validate data, and check whether two large inputs are identical without comparing them byte by byte. Having all three SHA variants computed side by side lets you match whatever format a tool, API, or specification expects without switching applications.
Every digest is computed locally with the browser's built-in Web Crypto API, the same vetted implementation your operating system relies on, so the results match what command-line tools and server libraries produce. Nothing you type is uploaded, logged, or stored - the text never leaves your device. Remember that hashing is not encryption: a hash proves integrity and enables comparison, but it does not keep the original content secret on its own, which is why passwords need a dedicated, salted algorithm rather than a plain SHA digest.
No. A cryptographic hash is a one-way function: it maps any input to a fixed-length digest, and there is no mathematical way to compute the input from the digest. The only way to find the original text is to guess candidate inputs and hash each one until a match appears, which is why short or common inputs are still vulnerable to dictionary and brute-force attacks.
They differ in digest length and security. MD5 produces 128 bits and SHA-1 produces 160 bits, but both are broken: researchers can create two different inputs with the same hash, called a collision, so neither should be used for security. SHA-256 produces 256 bits and has no known practical collisions, which makes it the recommended default for integrity checks and digital signatures.
General-purpose hashes like SHA-256 are designed to be fast, which lets an attacker who steals your database try billions of password guesses per second. For passwords use a slow, salted algorithm built for the job, such as bcrypt, scrypt or Argon2. These add a unique salt and a deliberate work factor so each guess is expensive, even on specialised hardware.
A download page publishes the SHA-256 hash of a file. After downloading, you hash your copy and compare it with the published value. If even a single byte changed during transfer or storage, the hashes will be completely different, so a match gives you strong confidence the file is intact and unmodified.
No. All hashing happens locally in your browser using the built-in Web Crypto API. The text you type is never uploaded, logged or stored, so you can safely hash sensitive strings without them leaving your device.