Hash text and files locally in your browser with MD5, SHA-1, SHA-256, SHA-512, SHA-3, CRC32, HMAC, copyable output, and checksum comparison.
Runs locally in your browser
No input or files are uploaded
Uses Web Crypto API where supported
MD5/SHA-1 are legacy algorithms
Input and Options
0 characters · 0 words · 0 lines
Algorithms
MD5, SHA-1, and SHA-256 are selected by default. SHA-3 and RIPEMD-160 use the page's optional client-side crypto library when it is available.
Drop a file here or choose a file
Files are processed locally in your browser and are not uploaded.
No file selected.
HMAC mode for keyed hashes
HMAC supports SHA-1, SHA-256, SHA-384, and SHA-512 through the Web Crypto API.
Results
Enter text or choose a file, then generate hashes.
Whitespace, colons, and hyphens are ignored for hex comparisons.
Tip: Ctrl/Cmd + Enter regenerates hashes. Ctrl/Cmd + K focuses the text box.
Which hash should I use?
For modern integrity checks, choose SHA-256 or SHA-512. They are widely supported by command-line tools, APIs, package managers, and checksum files.
MD5 and SHA-1 are legacy algorithms. Use them only when you need compatibility with an existing checksum, and not for adversarial security decisions.
A hash is not encryption. It cannot be decrypted, and plain hashes are not appropriate password storage. For passwords, use a dedicated password hashing function such as bcrypt, Argon2, or scrypt.
Password storage without bcrypt, Argon2, or scrypt
SHA-512
512-bit
128
Modern and strong
High-assurance integrity, 64-bit systems
Short fixed-width fields that require SHA-256 compatibility
SHA-3
224-512-bit
56-128
Modern SHA-3 family
Systems that specify Keccak/SHA-3 outputs
When the receiving system expects SHA-2
CRC32
32-bit
8
Checksum only, not cryptographic
Archives, accidental corruption checks
Any adversarial or security-sensitive check
HMAC
Depends on selected SHA algorithm
Depends on selected SHA algorithm
Secure when key and SHA choice are strong
Webhook signatures, API authentication, message integrity
Public checksums where no secret key is shared
Understanding cryptographic hashes
A cryptographic hash function maps text or bytes to a fixed-size digest. The same input produces the same output, but a strong hash should make it impractical to reconstruct the input or find a different input with the same digest.
This page hashes text and files in the browser. SHA-1, SHA-256, SHA-384, SHA-512, and HMAC use the browser Web Crypto API where supported. MD5, SHA-224, SHA-3, and RIPEMD-160 use the client-side library loaded by the page when available. CRC32 and Adler32 are checksum calculations implemented locally in JavaScript.
Hash Generator: FAQs
Is a hash the same as encryption?
No. Encryption is designed to be reversible with a key. A hash is a one-way digest used for fingerprints, checksums, and integrity checks.
Can I decrypt or reverse a hash?
No. Hashes are designed to be one-way. Weak or common inputs can sometimes be guessed with dictionaries, but the digest itself is not decrypted.
Why do I get a different hash than another tool?
Different input encoding, invisible whitespace, line endings, Unicode normalization, uppercase versus lowercase output, HMAC mode, or hashing the text of a file path instead of the file bytes can all change the result.
Should I use MD5?
Use MD5 only for legacy compatibility or non-adversarial checksums. Do not use MD5 for signatures, security decisions, password storage, or tamper-resistant integrity checks.
How do I verify a downloaded file checksum?
Drop the downloaded file into the file hashing area, choose the algorithm listed by the publisher, paste the expected checksum into the compare field, and check for a match.
What is HMAC?
HMAC combines a cryptographic hash with a secret key. It is used to verify that a message came from someone who knows the key and was not changed.
What is the difference between SHA-256 and SHA-512?
SHA-256 produces a 256-bit digest and SHA-512 produces a 512-bit digest. Both are modern SHA-2 algorithms; SHA-512 has a longer output and can be faster on some 64-bit systems.
Are files uploaded?
No. Files are read and hashed locally in your browser. The file bytes are not uploaded to Starlight Tools.
