Drop a file here, or use Choose file. The checksum uses the file bytes. Clear the file to hash the text box instead.
Nothing to hash yet
Paste text or choose a file to generate checksums.
100% private processing
Checksums are calculated in your browser. The text or file is not uploaded. This is for verifying bytes, not for storing passwords.
Generate SHA-256, SHA-384, SHA-512, and SHA-1 checksums in your browser. Paste text or choose a file, and SnapBit hashes it on your device. Nothing is uploaded, and you do not need an account. A checksum is a short fingerprint of exact bytes. If one character, or one bit in a file, changes, the hash changes. Developers use that to confirm a download matches the publisher's SHA-256, to compare two builds, or to see whether a config file is still the copy they expect. The same check is useful for a snippet of text: a license key file, a token you do not want to send to a website, or a script you just edited. SnapBit uses the Web Crypto digest built into the browser. SHA-256 is the one to copy when a project publishes a checksum. SHA-384 and SHA-512 are longer digests from the same family. SHA-1 is included because older docs still print it, not because it is a good choice for new work. This page does not compute MD5, and it is not a password hasher. Password storage needs a slow algorithm such as scrypt or Argon2, which is a different job from a checksum. Text is hashed as the exact UTF-8 characters in the box. A trailing newline changes the result. The command echo hello | sha256sum hashes the word hello plus a newline, so it will not match a paste of hello with nothing after it. File mode hashes the raw bytes of the file you choose, which is what sha256sum prints for that file. The tool reads the file in the tab. Clearing the file switches the checksums back to the text box. Paste an expected checksum under the results to check a match. Spaces and a trailing filename, the way sha256sum prints them, are ignored. The comparison uses the lowercase hex digest. You can copy each line. Very large files depend on the memory in your browser, because the whole file is read locally before it is hashed.
Yes. Text and files are hashed with the browser's built-in Web Crypto API. The input stays on your device, and SnapBit does not receive a copy.
Use SHA-256 unless the publisher of a file asked for something else. SHA-384 and SHA-512 are longer digests from the same family. SHA-1 is here for older documents. This tool does not compute MD5.
Text mode hashes the exact characters you paste, as UTF-8, and does not add a newline. echo hello | sha256sum hashes hello plus a newline, so the digests differ. File mode hashes the raw bytes, which matches sha256sum for that file.
No. These are checksums. They are fast on purpose, which makes them a poor way to store passwords. Use them to verify a download, a file, or a snippet.
It proves the bytes match the digest you compared. It does not, by itself, prove who created the file. Trust the checksum only when it comes from the same place you trust the download.
Hashing runs entirely in your browser. Text and files are not uploaded or stored.
