← All Tools
Checksum Generator🔒 100% local
SHA-1, SHA-256, SHA-512. Privacy-first, no server uploads, no tracking.
Related Tools
Paste text and the page returns four digests of it: SHA-1, SHA-256, SHA-384 and SHA-512, printed one per line as the algorithm name followed by the hex digest. The hashing uses the browser's own crypto.subtle over the UTF-8 bytes of what you typed, so the string sits in the tab and nowhere else. There is no file picker and no upload step.
How to use it
- Type or paste the text into the input box.
- Press Process.
- Press Copy Output to take all four lines at once, or select a single digest.
Worked example
Hello WorldbecomesSHA-1: 0a4d55a8d778e5022fab701977c5d840bbc486d0
SHA-256: a591a6d40bf420404a011733cfb7b190d62c65bf0bcda32b57b277d9ad9f146e
SHA-384: 99514329186b2f6ae4a1329e7ee6c610a729636335174ac6b740f9028396fcc803d0e93863a7c3d90f86beee782f4f3f
SHA-512: 2c74fd17edafd80e8447b0d46741ee243b7eb74dd2149a0ab1b9246fb30382f27e853d8585719e0e67cbda0daa8f51671064615d645ae27acb15bfb1447f459bWhitespace is part of the input: hashing "Hello World " (trailing space) gives four completely different digests.
When to use it
- Checking that a build artefact, a config blob or an API payload matches the digest someone published.
- Producing a stable identifier for a cache key or a content-addressed filename.
- Confirming a string survived a copy/paste, an encoding step or a line-ending change.
What it does not do
- Input is text only - this does not hash a file's bytes, so a digest computed over a downloaded file will not match if it carries a BOM or different line endings.
- SHA-1 is shown for legacy interoperability; it is not safe for new work, and MD5 is not offered at all.
- A digest is not encryption and cannot be reversed, but hashing a weak password here still leaves it readable in the text box.
- All four digests are always produced; there is no per-algorithm choice.