Why does this tool show four different hashes at once?
Different systems require different hash algorithms, and seeing them side by side saves time when you need to compare or generate fingerprints for multiple consumers. MD5 is still common for cache keys and legacy interop, SHA-1 appears in Git and older APIs, SHA-256 is the modern default, and SHA-512 covers cases that need extra security margin. Generating all four in one place avoids running four separate utilities.
Which hash should I pick if I am building something new?
Start with SHA-256. It is supported everywhere, has no known practical attacks, and produces hashes short enough to store comfortably. Move up to SHA-512 if you need a higher security margin or are running on 64-bit hardware where it is actually faster. Avoid MD5 and SHA-1 in new designs - they are documented as broken for any application where collisions matter.
Are any of these hashes safe for storing passwords?
No. MD5, SHA-1, SHA-256, and SHA-512 are all general-purpose hashes designed to be fast. Modern GPUs can compute billions of any of them per second, making brute-force attacks against stolen password databases trivial. For passwords, always use a slow, salted, memory-hard function such as bcrypt, scrypt, or Argon2. The bcrypt generator on this site is the right tool for that job.
What do hash lengths look like across the algorithms?
MD5 is 32 hex characters, SHA-1 is 40, SHA-256 is 64, and SHA-512 is 128. Length doubles roughly with security level. The hash length is fixed for each algorithm regardless of how big or small your input is. You can spot which algorithm a hash came from at a glance just by counting characters, which helps when reverse-engineering legacy systems or third-party APIs.
Is the input I paste sent over the network?
No. All four hashes are generated locally in your browser, so the input never leaves your device. There are no server-side logs, analytics on content, or background uploads. This makes the tool safe for sensitive inputs like internal identifiers, API tokens being rotated, or test fixtures from production-like data. Closing the tab discards everything from memory.
Can I rely on hash comparison alone to verify a download?
Only if you obtained the expected hash from a trusted channel separate from the file. If both the file and the hash come from the same compromised mirror, the comparison proves nothing. Pair the hash check with a digital signature when possible, and prefer SHA-256 or stronger over MD5/SHA-1 for any download where an active attacker is part of your threat model.