SmartKitio

Hash Generator

Compute MD5, SHA-1, SHA-256, and SHA-512 digests of text, for example to compare checksums or build test fixtures.

Your input stays in your browser. Nothing is uploaded.

About this tool

The text is encoded as UTF-8 and hashed. SHA-1, SHA-256, and SHA-512 use the browser's Web Crypto API; MD5 is computed by a JavaScript implementation because Web Crypto does not include it. Results are lowercase hexadecimal. MD5 and SHA-1 are broken for collision resistance and should not be used for signatures or certificates. None of these fast hashes is suitable for storing passwords; use a password-hashing function such as Argon2, scrypt, or bcrypt for that.

Limits

  • These are fast checksums, not password hashes. Do not store passwords as MD5, SHA-1, SHA-256, or SHA-512. Use Argon2, scrypt, or bcrypt for that.
  • MD5 and SHA-1 are not collision-resistant. Do not use them for signatures or certificates.
  • Only the text in the box is hashed, as UTF-8. A file with different line endings will not match.

How to use it

  1. Type or paste the text to hash.
  2. Choose the algorithm.
  3. Copy the hex digest, or compare it with the checksum you were given.

Examples

  • SHA-256 of an empty string

    e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.

  • MD5 of "hello"

    5d41402abc4b2a76b9719d911017c592.

  • Whitespace matters

    "hello" and "hello " (with a trailing space) produce completely different digests.

Digest lengths

AlgorithmBitsHex charactersStatus
MD512832Broken; checksums only
SHA-116040Broken for collisions
SHA-25625664Recommended
SHA-512512128Recommended

FAQ

Can I hash a file?
Not on this page; it hashes text only. Line endings matter too: a file saved with Windows line endings hashes differently from the same text pasted here.
Why doesn't my hash match another tool?
Usually because of a trailing newline, different line endings, or a different text encoding. This tool always uses UTF-8 and hashes exactly what is in the box.
Can a hash be reversed?
Not directly. But short or common inputs can be found by guessing, which is why fast hashes should not be used for passwords.