UlvixorFile Hash Generator
Upload any file and instantly get its SHA-1, SHA-256, SHA-384, and SHA-512 hashes, calculated with the browser's native Web Crypto API. Useful for verifying a file's integrity or authenticity without uploading it to any server.
How it works
- Select any file from your device using the file picker.
- Your browser reads the file as binary data (ArrayBuffer).
- The SHA-1, SHA-256, SHA-384, and SHA-512 hashes are calculated simultaneously using crypto.subtle.digest(), the browser's native cryptographic API.
- Each hash is displayed in hexadecimal, with its own button to copy it to the clipboard.
Use cases
- Verify that a downloaded file exactly matches the checksum published by its source.
- Check that two copies of a file are byte-for-byte identical.
- Generate a unique, reproducible identifier for a file (for example, to detect duplicates).
- Audit file integrity before distributing or digitally signing them.
Use cases
- Verify that a downloaded file exactly matches the checksum published by its source.
- Check that two copies of a file are byte-for-byte identical.
- Generate a unique, reproducible identifier for a file (for example, to detect duplicates).
- Audit file integrity before distributing or digitally signing them.
Common mistakes
- Looking for an option to generate an MD5 hash.MD5 isn't supported by the browser's Web Crypto API and is considered weak today, so this tool offers SHA-1, SHA-256, SHA-384, and SHA-512 instead. For most verification uses, SHA-256 is a good replacement.
- Renaming a file and expecting its hash to change.The hash is calculated solely from the file's binary content, not its name or metadata, so renaming it doesn't change the result.
- Comparing a SHA-256 hash generated here with a SHA-1 checksum published elsewhere and concluding the file is corrupted.Two hashes are only comparable if they were calculated with the same algorithm. Check which algorithm the original source published and compare against this tool's matching hash.
Frequently asked questions
No. The file is read and processed entirely in your browser using the Web Crypto API (crypto.subtle.digest). It's never sent to an external server.
MD5 isn't natively supported by browsers' Web Crypto API, and today it's considered a cryptographically weak algorithm. Implementing it manually in JavaScript would add weight and complexity without a real benefit, so this tool only offers SHA-1, SHA-256, SHA-384, and SHA-512, which are native, fast, and more robust.
For most integrity-verification cases, SHA-256 is the most widely used and recommended standard today. SHA-1 is kept mainly for compatibility with older systems, since it's considered weak for sensitive cryptographic uses.
Yes, the Web Crypto API can process files of several hundred megabytes without issues, though the calculation time increases with file size and depends on your device's performance.
No. The hash is calculated solely from the file's binary content, not its name or metadata, so renaming it doesn't change the result.
Alternatives
In the terminal, commands like certutil -hashfile (Windows), shasum (macOS/Linux), or sha256sum do the same thing without leaving the command line. This tool is handy if you'd rather not open a terminal: select the file and get all four hashes at once, with the file never uploaded to any server.