Hashing Passwords: Why Plain SHA-256 Isn't Enough

A plain SHA-256 or SHA-1 hash of a password, on its own, is not safe for storing user credentials — even though both are available in the tool on this page. General-purpose hash functions are designed to be fast, which is exactly the wrong property for password storage: fast hashing means an attacker who steals your password table can try billions of guesses per second against it.

Password storage needs a function designed to be slow and resistant to hardware acceleration — bcrypt, scrypt, or Argon2 (the current recommendation). Those also handle salting automatically, which a bare SHA-256 call does not.

What SHA-256/SHA-1 on this page are useful for: checksums, cache keys, deduplication, and other cases where speed is a feature, not a vulnerability.