Hash Generator: SHA-256, SHA-512, SHA-1, MD5

Type some text or choose a file: the hash generator instantly calculates the SHA-256, SHA-384, SHA-512 and SHA-1 checksums, and MD5 on request. Paste an expected hash (for example from a download page) to compare it directly. Everything runs in your browser – files are never uploaded.

MD5 is insecure and only meant for simple checksums.
Exactly this text is hashed as UTF-8 – an extra space or a trailing line break gives a completely different hash.

Your text stays in your browser – it is not sent, not stored and not added to the address bar.

The file is only read locally and never uploaded (up to 512 MB).

Result

SHA-256
64ec88ca00b268e5ba1a35678a1b5316d212f4f366b2477232534a8aeca37f3c
SHA-1
7b502c3a1f48c8609ae212cdfb639dee39673f5e
SHA-384
9203b0c4439fd1e6ae5878866337b7c532acd6d9260150c80318e8ab8c27ce330189f8df94fb890df1d298ff360627e1
SHA-512
b7f783baed8297f0db917462184ff4f08e69c2d5e5f79a942600f9725f58ce1f29c18139bf80b06c0fff2bdd34738452ecf40c488c22a7e3d80cdf6f9c1c0d47
Hashed
Text, 11 bytes (UTF-8)

How it is calculated

A hash function maps data of any length to a value of fixed length – the hash, digest or checksum. The same input always gives the same hash; changing a single character produces a completely different one. You can’t work back from the hash to the input.

The algorithms

Verifying a download

Many projects publish a SHA-256 checksum next to the file. Select the file here and paste the published value into “Compare with expected hash” – if it matches, the file arrived unchanged. Case, spaces and colons in the expected value don’t matter. On Windows you can do the same with certutil -hashfile file SHA256, on macOS and Linux with shasum -a 256 file or sha256sum file.

Why does my hash differ?

Usually because of invisible characters: echo text | sha256sum hashes the text with a line break, echo -n without. Windows line endings (CR LF instead of LF), a byte order mark or an encoding other than UTF-8 also change the hash.

Hashes and passwords

Fast hashes such as SHA-256 or MD5 are unsuitable for storing passwords – attackers can try billions of guesses per second. Use slow, salted algorithms such as Argon2, scrypt or bcrypt instead.

Hashes are calculated with your browser’s Web Crypto API. Your text, file and comparison value are not sent, not stored and not written into the address bar.

Frequently asked questions

How do I get the SHA-256 hash of a file?

Choose the file under “Or hash a file” – the SHA-256 value appears straight away at the top of the result. The file is only read inside your browser and is never uploaded.

Can a hash be decrypted?

No. A hash isn’t encryption but a one-way function. For short or common inputs (such as weak passwords), however, attackers can find a matching input by trial and error or with precomputed tables.

Is MD5 still secure?

No. MD5 has been broken since 2004; collisions can be generated on an ordinary computer in seconds. For security, use SHA-256 or stronger. As a checksum against accidental transmission errors, MD5 still does the job.

Why doesn’t my hash match the one from the command line?

The most common cause is a line break: echo "text" | sha256sum appends a \n. Use echo -n or printf. Different line endings (Windows CR LF) or character encodings also change the hash.

What is the difference between hex and Base64 output?

It is the same hash written differently: hexadecimal uses 2 characters per byte (SHA-256 = 64 characters), Base64 is shorter (44 characters). Base64 is used, for example, in Subresource Integrity (integrity="sha256-…").

Sources and legal basis

As of:

Related tools