All hashing runs in your browser. Your text and files never leave your device, and the tool works offline.
Which algorithm should I use?
A hash is a fixed-length fingerprint of some data. The same input always gives the same hash, and any change to the input changes the hash completely. That makes hashes useful for checking that a file downloaded correctly or hasn't been altered.
| Algorithm | Length | Good for |
|---|---|---|
| MD5 | 32 hex chars | Fast checksums, matching against legacy MD5 values. Not for security. |
| SHA-1 | 40 hex chars | Compatibility with older systems and Git object IDs. Not for security. |
| SHA-256 | 64 hex chars | Modern integrity checks and anything security-sensitive. The safe default. |
| CRC32 | 8 hex chars | Quick error-detection checksums, like those in ZIP and PNG files. |
For verifying a download against a published checksum, use whichever algorithm the source published. For anything where someone might try to fake a match on purpose, use SHA-256. MD5 and SHA-1 are both considered broken for security, because it's possible to craft two different files with the same hash.
Verifying a download
Software projects often publish a checksum next to a download. To verify it, pick the matching algorithm above, drop the downloaded file into the File box, and paste the published value into "Compare with a known hash." A green match means the file is intact. A mismatch means the file is corrupted, incomplete or has been tampered with — download it again.
Questions
Is there a file size limit?
There's no fixed limit. Files are read in chunks and hashed as they stream through, so even large files won't exhaust memory. A multi-gigabyte file simply takes longer, and a progress bar shows how far along it is.
Does uppercase or spacing in the compare box matter?
No. When comparing, the tool ignores letter case and trims surrounding spaces, so a hash pasted as uppercase or with a trailing newline still matches. It also ignores a leading 0x and a trailing filename if you paste a full checksum line.
Why does the same text give a different hash elsewhere?
Usually a difference in line endings or a hidden trailing newline. This tool hashes exactly the bytes you enter, encoded as UTF-8. A file created by a text editor often ends with a newline that you don't see, which changes the hash.
Can I hash with HMAC or a salt?
Not in this tool — it produces plain hashes. For keyed hashes, FlipperFile has a separate HMAC generator, and for password hashing use the bcrypt tester instead.
Is anything uploaded?
No. Every algorithm is built into this page and runs in your browser. Your text and files are never sent anywhere, and the page keeps working with no network connection.