Compare checksums
Compare a local file hash with the SHA-256 value published in release notes or download pages.
File Hash Calculator
브라우저 내부 처리
Calculate SHA hashes for uploaded files locally in the browser.
File hash verification workflow
Comparing hashes is the reliable way to confirm a build artefact or received file was not corrupted in transit. Check the value computed here against the published checksum. The whole file is read in the browser and never uploaded, which makes it usable for internal files too.
No upload required
The browser reads the file and computes the hash locally; the selected file is not uploaded by this tool.
Record multiple hashes
When needed, keep SHA-256 and SHA-512 values together in verification notes.
Errors you will hit
Case differences look like a mismatch
Hex digests are case insensitive. 9B2E and 9b2e are the same value — normalize the case before comparing.
The browser stalls on large files
Hashing happens in memory, so multi-gigabyte files can overwhelm the tab. Use an OS command such as shasum or certutil for those.
Can you trust a SHA-1 result?
SHA-1 has demonstrated collision attacks and is unsuitable for security verification. Use SHA-256 or stronger.
Things to check
Hashing is not encryption
A hash identifies file content and helps with integrity checks. It does not restore the original file or provide secrecy.
Large files take time
Very large files can use more browser memory and processing time. Wait briefly before assuming the calculation failed.
Different hashes mean different files, not the reverse
Matching hashes effectively mean identical files, but a slightly corrupted download produces a completely different hash. So a hash cannot tell you how much changed — that is a diff tool's job.
Large files take time
The hash is computed in your browser, so the whole file must be read. Multi-gigabyte files can be slow or hit memory limits. In exchange nothing is uploaded, which is what makes it safe for internal files.
SHA-1 is for integrity only now
Collisions in SHA-1 can be constructed deliberately, so it is unsuitable for signatures or security verification. It is still fine for checking whether a transfer corrupted a file. Use SHA-256 or stronger where security matters.
More: step-by-step usage and worked examples
How to use it
- Select the file you want to verify.
- Compare the calculated SHA value with the reference value from a release note, download page, or internal document.
- Ignore casing and extra whitespace when comparing hexadecimal strings.
- If the value differs, download the file again or review the transfer path.
Real input and output
Verifying a download
Input
ubuntu-24.04.isoOutput
SHA-256
9b2e1f...c47a3dIf a single character differs from the published checksum, the file is corrupted or tampered with.
Tools that pair well
- PDF Merge/Split
- Image Optimizer — Before uploading an image you have to decide how far you can compress before the quality shows.
- Image Base64 — Converting a small icon or test image to a data URL lets you inline it in code.
- OCR Extractor — Text extraction returns nothing from a scanned PDF or a photographed document, because the page is a single im
- QR Code — Turn a URL or Wi-Fi details into a QR code for mobile testing or printed notices.