Generate SHA-1 and CRC32 checksums from text, in hex and decimal. For legacy verification only — both are unsuitable for security. Free, runs locally.
First time here? Type or paste your text Your input is processed locally and disappears when you close the tab.
This is a deliberately unfashionable tool. SHA-1 has been broken for collisions since 2017 and CRC32 was never a security function at all — yet both remain unavoidable, which is why a sha1 hash generator still earns its place.\n\nGit identifies every object by SHA-1. Zip archives and PNG chunks carry CRC32 checksums. A great many vendors still publish SHA-1 hashes beside their downloads. When you need to verify against one of those systems, you need the algorithm they used, not the one you would have chosen.\n\nThe tool computes both live as you type, shows CRC32 in hexadecimal and decimal because different systems report it differently, and offers an uppercase toggle for matching output from tools that use it. Byte count is shown too, since UTF-8 encoding means character count and byte count diverge the moment non-ASCII text is involved.\n\nWhat it will not do is pretend either algorithm is something it is not. SHA-1 must not be used for signatures, certificates or password storage. CRC32 catches accidental corruption and nothing more — forging a collision is trivial. For anything where security matters, use the SHA-256 or SHA-512 generators instead.
Type or paste your text
Read the SHA-1 and CRC32 values
Switch to uppercase if the system you are comparing against uses it
Copy the value you need
0 bytes · hashed as UTF-8
So why are they here? Because they are still everywhere and you still have to work with them. Git object IDs are SHA-1. Zip archives and PNG chunks carry CRC32. Plenty of vendors publish SHA-1 checksums alongside downloads. Verifying against those is a legitimate, everyday need.
For anything where security matters, use the SHA-256 or SHA-512 generators instead.