HubTools

Hash Generator

Generate cryptographic hashes using MD5, SHA-1, SHA-256, SHA-384, and SHA-512 algorithms.

What is a Cryptographic Hash?

A cryptographic hash function takes any input — a string, a file, a multi-gigabyte disk image — and produces a fixed-size fingerprint (the digest) that is fast to compute, deterministic, and effectively impossible to invert or collide. Hash functions are everywhere: git uses SHA-1 to identify every commit, package managers use SHA-256 to verify downloads, blockchains use them in proof-of-work, and password storage layers them under bcrypt or argon2 for credential hashing. The SHA-2 family (SHA-256, SHA-384, SHA-512) is the current standard for security work; MD5 and SHA-1 still appear in legacy tooling but should not be trusted for anything an attacker could exploit. This generator runs all five algorithms locally via the browser's Web Crypto API. Need reversible secrecy instead of a one-way fingerprint? Use the AES Encryptor. Working with JSON Web Tokens? Decode them with the JWT Decoder.
Text Input
0 chars
0 B
Hash Results
Enter text above to generate hashes for all algorithms.

How to use this tool

  1. 1
    Pick an algorithm
    Choose SHA-256 for general work, SHA-512 for performance on 64-bit machines, or MD5/SHA-1 only for non-security checksums.
  2. 2
    Paste text or drop a file
    Type or paste a string into the text field, or drag a file onto the drop zone. Files are read locally — nothing is uploaded.
  3. 3
    Pick output encoding
    Hex (lowercase, the default for git and most CLI tools) or Base64 (more compact, used in JWTs and HTTP headers).
  4. 4
    Compare with a reference hash
    Paste a known-good hash into the compare field — the tool flags a green check or red mismatch instantly.

Frequently asked questions

When should I use which algorithm?
Use SHA-256 or SHA-512 for security-critical work like file integrity, password hashing inputs, and digital signatures. Use MD5 or SHA-1 only for non-security checksums (like cache keys or rsync) — they are cryptographically broken for collision resistance and must never be used for signatures, certificates, or password storage.