Hash Generator — SHA-1, SHA-256, SHA-384, SHA-512
How to Use
- Type or paste text into the input area.
- Select an algorithm (SHA-1, SHA-256, SHA-384, or SHA-512).
- The hash value is generated in real time as you type.
- Click the copy button to copy the hash to your clipboard.
Hash Algorithms
SHA (Secure Hash Algorithm) is a family of cryptographic hash functions. Each algorithm produces a fixed-length output regardless of input size.
- SHA-1 (40 characters): Legacy algorithm. Still used for checksums and Git commit hashes, but not recommended for security purposes due to known collision vulnerabilities.
- SHA-256 (64 characters): The most widely used. Standard for digital signatures (TLS/SSL), blockchain (Bitcoin), data integrity verification, and password hashing.
- SHA-384 (96 characters): A truncated version of SHA-512. Used in government and military applications (NSA Suite B).
- SHA-512 (128 characters): Highest security. Suitable for scenarios requiring maximum collision resistance, such as high-security certificates and large-scale data verification.
Which Algorithm Should I Use?
- General purpose / data integrity: SHA-256
- File checksums / quick verification: SHA-256
- Maximum security requirements: SHA-512
- Legacy system compatibility: SHA-1 (avoid for new security applications)
What is a Cryptographic Hash?
A cryptographic hash function takes an input of any size and produces a fixed-length output (the hash or digest). The same input always produces the same hash, but even a tiny change in the input produces a completely different output. Hash functions are one-way — you cannot reverse-engineer the original input from the hash. These properties make hashes essential for data integrity verification, password storage, digital signatures, and blockchain technology.
Use Cases
- File integrity: Generate a hash of a file before and after transfer to verify it was not corrupted or tampered with.
- Password storage: Hash passwords before storing them in a database (always use a dedicated password hashing function like bcrypt or Argon2 in production).
- Checksums: Verify downloads by comparing the published hash with the hash of the file you received.
- Deduplication: Identify duplicate content by comparing hashes instead of comparing full file contents.
- Version control: Git uses SHA-1 hashes to identify commits, trees, and blobs uniquely.
Privacy
All hashing is performed entirely in your browser using the Web Crypto API (crypto.subtle). Your data is never sent to a server.
FAQ
What is the difference between hashing and encryption?
Encryption is two-way — with the key, you can recover the original data. Hashing is one-way: you cannot reverse a hash back into its input. This tool generates hashes used for matching and integrity verification, not encryption.
Is it safe to enter sensitive data like API keys or passwords?
Yes. All hashing happens in your browser via the Web Crypto API (crypto.subtle), and your input is never sent to a server, stored, or logged. You can safely hash sensitive text.
Which algorithm should I choose?
SHA-256 is the standard choice for general data integrity and checksums. Use SHA-512 when you need higher collision resistance, and reserve SHA-1 for legacy compatibility only — avoid it for new security purposes.
Can I use this to hash passwords for production?
No. Plain SHA hashes are unsuitable for storing passwords. In production, use a dedicated password hashing function like bcrypt or Argon2, which include salting and cost parameters. This tool is for verification and learning.
Does the same text always produce the same hash, and do case and whitespace matter?
Yes, identical input always yields the same hash. Conversely, even a tiny difference — letter case, a trailing space, or a newline — produces a completely different hash, so inputs must match exactly when comparing checksums.