Add your file
Choose or drop a .* file. You can paste the contents instead.
File Hash & Checksum Verifier
Pick one file — or paste text — and the page reads it in 1 MB slices and hashes it locally. The full lowercase hexadecimal digest is shown together with the algorithm name and the exact number of bytes hashed, and it is never shortened, grouped or reformatted for display: a SHA-256 result is always the complete 64 characters. To verify a download, paste the value the publisher listed into the expected-checksum box; surrounding whitespace is trimmed and upper case is accepted, and the outcome is reported as match, mismatch, or invalid expected value — never as "almost the same". Large files show progress while they are read and the tab keeps responding, because the file is hashed slice by slice instead of being loaded whole. You can copy the digest on its own or as a checksum line that puts the digest in front of the file name, and download it as a .sha256, .sha384 or .sha512 text file. Every input is treated as an opaque byte stream: the extension is ignored and nothing is decoded as text, so installers, archives, disk images, photos and documents are all hashed the same way. Pasted text is the one exception — it is encoded as UTF-8 first, and the result records that.
File types: .*Processing: This browser
How to use File Hash & Checksum Verifier
Let it read the file
The file is read and parsed in this browser — nothing is uploaded.
Check the result
Look over what came back, then copy it, download it, or move on.
Want to know how files are handled? Read the privacy notice →
Common questions
How do I get the SHA-256 hash of a file in the browser?
Choose the file and the complete SHA-256 digest appears on the page — there is no upload step, no account and no button chain to work through. The file is read in 1 MB slices, so the tab stays usable while it works, and the result is shown with the algorithm name and the exact byte count next to the 64-character value. Switching to SHA-384 or SHA-512 recomputes the digest from the same file.
How do I verify a download's hash against the checksum the publisher lists?
Hash the downloaded file, then paste the publisher's value into the expected-checksum box: the comparison trims stray spaces and accepts upper or lower case, and reports match or mismatch. It compares the whole string without uploading the file anywhere. A match means your copy is byte-for-byte identical to the copy the published checksum describes; make sure the value you paste was produced with the same algorithm you selected.
Is my file uploaded to a server when I calculate its hash?
No. The bytes are read from your disk by the page itself and hashed inside the tab, and no network request is made while hashing — not for the file, not for its name, not for the resulting digest. Pasted text behaves the same way. Nothing about the file leaves the browser, so there is no copy on any server to delete afterwards.
Does the file hash tool still work offline with no internet connection?
Yes — once the page has loaded, hashing needs nothing from the network, so it works on a disconnected laptop, in airplane mode, or on an isolated machine. The digest is produced by the page's own SHA-2 implementation rather than a remote service, which also means it does not stop working if a network filter blocks outbound requests.
How do I check a file's SHA-256 hash on Windows 11 without using PowerShell?
Open the page in Edge or Chrome on Windows 11, pick the file, and read the digest — no Get-FileHash, no certutil, no admin rights and no software install. The value is the same one Get-FileHash would print, shown in lower case, so you can compare it with a publisher's checksum directly.
Can I get a file hash on a Mac or an iPhone without the Terminal?
Yes. In Safari or Chrome on macOS, choose the file and the digest matches what `shasum -a 256` prints in the Terminal. On an iPhone or Android browser you can pick the file from Files or Downloads and hash it the same way; phone-sized files are quick, while a 100 MB file takes noticeably longer on a phone than on a laptop.
Why does my file's hash not match the checksum on the download page?
A mismatch nearly always means the download is incomplete or corrupted, or that the two values are not comparable — re-download the file and confirm the published value is for the algorithm you selected. A value with the right characters but the wrong length is also reported as a mismatch, which is what a truncated value or an SHA-1 checksum looks like beside a SHA-256 digest.
Why is my expected hash value reported as invalid instead of simply wrong?
An expected value is only compared when it consists of hexadecimal characters, 0-9 and a-f, after trimming; anything else is flagged as an invalid entry rather than quietly counted as a mismatch. Common causes are a pasted "sha256:" prefix, the file name pasted along with the value, or a base64-encoded digest. Paste the bare hexadecimal string and it compares normally.
Why can't I hash a folder or several files at once?
This tool hashes exactly one file per run, so dropping a folder or selecting several files stops with a message asking you to pick a single file. Folders are detected and refused rather than partly processed. There is no combined digest for a set of files here — hash them one at a time and compare each against its own published value.
What is the maximum file size this hash tool accepts?
The limit is 100 MB — exactly 100,000,000 bytes — and a larger file is refused before a single byte is read, so nothing is loaded and then abandoned. The ceiling cannot be raised from the page. A file right at the limit hashes without freezing the tab because it is processed in 1 MB slices with progress reported as it goes.
Which hash algorithms are supported, and can I use MD5 or SHA-1?
SHA-256, SHA-384 and SHA-512 are supported; MD5 and SHA-1 are not offered, and asking for one returns an explicit note that they are not fit for security verification. Use SHA-256 instead whenever a publisher lists both. CRC32, BLAKE2 and xxHash are not implemented, so values in those formats cannot be checked here.
What is the difference between the SHA-256 and SHA-512 hash when verifying a file?
They are different functions over the same bytes and produce different-length results: 64 hexadecimal characters for SHA-256, 96 for SHA-384 and 128 for SHA-512. Neither is more "correct" — use whichever the publisher used, because one digest can never be converted into another. If you picked the wrong one, just switch the algorithm and the file is hashed again.
Is it safe to hash a confidential file with an online checksum tool?
Hashing a confidential file here does not disclose it, because the file is read locally and never transmitted — no upload, no temporary storage, no third-party service in the path. The digest is not sent anywhere either, so it is never submitted to a lookup database. The usual caution applies to the machine itself: anyone with access to your computer still has access to the file.
Does a matching SHA-256 hash prove the file is safe to run?
No. A match proves only that your copy is byte-for-byte identical to the file the checksum describes, which says nothing about whether that file is trustworthy. If the checksum came from the same page as a tampered download, or the publisher itself was compromised, the match is worthless. This tool cannot detect malware and never looks a digest up in any database.
Can I compute a SHA-512 file hash for free without installation or registration?
Yes — nothing to install, no registration, no extension and no per-day quota; the page runs in the browser you already have. Because the hashing happens on your own machine there is no server cost to meter, so there is no sign-in wall and no limit on how many files you check, one at a time, up to 100 MB each.