No. Hashing happens in your browser — SHA algorithms through the native WebCrypto API, MD5 and CRC32 in local JavaScript. Nothing is transmitted or stored.

Which algorithm should I use?

SHA-256 for anything security-related. MD5 and CRC32 only to detect accidental corruption, because both can be deliberately forged. SHA-1 is also broken and should not be trusted for security.

Can I use this to hash passwords?

No. Password storage needs a deliberately slow algorithm with a salt, such as bcrypt, scrypt or Argon2. A fast hash like SHA-256 can be brute-forced at enormous rates and is the wrong tool for that job.

Hash Generator

Runs in your browser

Compute MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC32 for text or a file — all at once, all in your browser.

Text

Choose a file

About this tool

A hash is a fixed-length fingerprint of some data: change one byte and the output changes completely. That makes hashes ideal for checking that a download arrived intact or that two files are identical, and it is why projects publish a SHA-256 next to their release archives. This tool computes every common algorithm at once so you can match whichever one the source published. SHA-2 comes from WebCrypto, the browser's native implementation; MD5 and CRC32 are computed locally because the platform deliberately omits them.

How to use

Type or paste text, or choose a file — hashes update as you go.
Compare the value against the checksum published by the source.
Copy whichever algorithm you need.

When to use this tool

Verifying a downloaded ISO or installer against a published checksum.
Checking whether two files are byte-for-byte identical.
Generating a cache key or content fingerprint.
Producing a digest to compare against a value from a database.

Tips

For file verification, use whichever algorithm the source published — a matching SHA-256 is strong evidence; a matching MD5 only rules out accidental corruption.
Hashing runs over exact bytes, so a trailing newline changes the result.
Large files are read into memory, so very large images may be slow on modest devices.

Limitations

MD5, SHA-1 and CRC32 are broken or non-cryptographic. Use them to verify accidental corruption, never to protect against a deliberate attacker.
Hashing is not password storage — real password hashing needs a slow algorithm such as bcrypt or Argon2.

FAQ

Is my file uploaded?: No. Hashing happens in your browser — SHA algorithms through the native WebCrypto API, MD5 and CRC32 in local JavaScript. Nothing is transmitted or stored.
Which algorithm should I use?: SHA-256 for anything security-related. MD5 and CRC32 only to detect accidental corruption, because both can be deliberately forged. SHA-1 is also broken and should not be trusted for security.
Can I use this to hash passwords?: No. Password storage needs a deliberately slow algorithm with a salt, such as bcrypt, scrypt or Argon2. A fast hash like SHA-256 can be brute-forced at enormous rates and is the wrong tool for that job.