Kodigo Labs ToolsHow to use the hash generator
Type or paste text, or switch to File and choose a file. MD5, SHA-1, SHA-256, SHA-384 and SHA-512 are all calculated at once. Choose hex, HEX (uppercase) or Base64 output, and use the copy button next to any hash.
To check a download, paste the checksum published by the vendor into Compare with expected hash. Extra spaces, a leading sha256: label and a trailing file name (as in sha256sum output) are ignored. For API or webhook signatures, tick HMAC and enter the secret key.
Example
The text abc gives these well-known test values:
- MD5:
900150983cd24fb0d6963f7d28e17f72 - SHA-1:
a9993e364706816aba3e25717850c26c9cd0d89d - SHA-256:
ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
Change it to abd and every hash changes completely. That is why a matching checksum is good evidence that a file arrived exactly as published.
Frequently asked questions
How do I check a downloaded file's checksum?
Open the File tab and choose the downloaded file. Then paste the checksum from the download page into "Compare with expected hash". The tool checks it against every algorithm at once and tells you which one matches. If none match, the file is incomplete, damaged or not the one the publisher released.
Is my file uploaded to calculate the hash?
No. The file is read and hashed inside your browser, so even very large or private files never leave your computer. SHA hashes use the browser's built-in Web Crypto; MD5 is calculated by code on this page.
Which hash should I use?
Use SHA-256 (or SHA-384/SHA-512) for anything security related. MD5 and SHA-1 are broken for security purposes because collisions can be created on purpose, but they are still fine for spotting accidental corruption and are often what older download pages list.
What is HMAC?
HMAC mixes a secret key into the hash. Only someone who knows the key can produce the same value, so it is used to sign API requests and webhooks (for example, many payment providers send an HMAC-SHA256 signature). Turn on HMAC, enter the key, and compare the result with the signature you received.
Why is my text hash different from another tool?
Hashes change completely if even one byte differs. Common causes are a trailing space or newline, Windows line endings (CRLF) instead of LF, or a different character encoding. This tool hashes your text exactly as typed, encoded as UTF-8, with line breaks as LF.