Tools & 3D Studio
← All tools

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.

0 bytes uploaded 0 external requests crypto.subtle signature checked locally

Hash a file or some text

read in memory · never sent

Drop the file you want to check

Any type, any size. Read into this tab's memory and hashed there.

—

Algorithm
SHA-256
—
No expected checksum entered

What the number means

three things people conflate

01A 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 · privacy
Is a SHA-1 checksum still worth using?
For accidental corruption, yes — it still catches a changed byte. For anything an attacker controls, no: a chosen-prefix collision costs well under a hundred thousand dollars of GPU time, so two different files can share a SHA-1 value. Use SHA-256 for anything you publish and keep SHA-1 only to read old manifests.
The expected checksum has spaces or an asterisk — will it still compare?
Yes. The field accepts the whole 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?
Two usual reasons: the token in your clipboard was refreshed and the copy is old, or 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.
Does the tool keep my file or my token?
No. Nothing is written to storage, nothing is posted anywhere, and the page makes no request after it loads. Close the tab and the bytes are gone with it. The footer counts cross-origin requests with a PerformanceObserver and it stays at 0 — the one honest way to show that claim instead of just asserting it.