HashForge · checksums & tokens · zero upload
The checksum that never leaves the file.
SHA-1 to SHA-512, HMAC, JWTs.
Computed in this tab.
A download page gives you a hash and you need to know whether the file matches. Drop it here: the browser's own
crypto.subtle reads it in memory, the digest appears with the time it took, and the checksum you were given
is compared character by character. The same tab opens a JWT and counts a token's expiry in KST and UTC,
and fixes Base64 that broke your Korean.
Hash a file or some text
read in memory · never sentDrop the file you want to check
Any type, any size. Read into this tab's memory and hashed there.
Decode a JWT
header · payload · expiryBase64 · Base64url · URL
UTF-8 safe · Korean intactBase64 is an encoding, not encryption — anyone can reverse it, so it hides nothing. This page converts to UTF-8 bytes before encoding, which is why Korean survives; most in-browser btoa snippets mangle anything above U+00FF.
What the number means
three things people conflate01A hash is not encryption
A hash runs one way: there is no key and no undo, and the output is a fixed length whatever the input. Encryption is reversible with a key; encoding such as Base64 is not even secret. A checksum answers one question — are these the same bytes — and it is the right tool for that and the wrong tool for everything else.
02What a match proves
That the file arrived intact — no dropped packet, no partial download, no accidental edit. It does not prove who made it: anyone can compute a hash of anything. Certificates and signatures exist for that. If the checksum came down the same pipe as the file, treat it as a corruption check, not as authentication.
03Where HMAC fits
HMAC mixes a shared secret into the hash, so only someone holding the key can produce the value. That turns a checksum into a proof of possession — which is exactly what an HS256 JWT signature is: HMAC over the header and payload. The secret never travels with the token, so a token with a strong secret cannot be forged.
Questions
checksums · tokens · privacyIs a SHA-1 checksum still worth using?
The expected checksum has spaces or an asterisk — will it still compare?
sha256sum line, so 2cf24dba… *file.zip works: the page pulls out the run of hex characters that matches the algorithm's length and compares only that. Whitespace, uppercase and the leading backslash a Windows tool adds are all tolerated.Why is my JWT shown as expired when the app says I am signed in?
exp is in seconds and something converted it to milliseconds twice. The page reads exp and iat as Unix seconds, shows both in KST and UTC, and prints how long ago it expired — so you can see which one it is.