Verify a File's Checksum
Drop any file and get its checksums in all five common algorithms at once — the fastest way to verify that a download matches the checksum published on the source's website. The file is read and hashed locally; nothing is uploaded to Filesvo.
or drag and drop any file here — checksums are computed instantly
Processed on your device — files are never uploaded to Filesvo.
How to use Filesvo
- Select or drop the file to check.
- Wait a moment while the digests are computed.
- Compare the digest against the published checksum — they must match exactly.
Why verify checksums?
Software downloads often publish a SHA-256 checksum next to the download link. Computing the same digest locally and comparing proves your copy is byte-for-byte identical to what was published — catching corrupted downloads and tampered files alike. Even one changed byte produces a completely different digest.
Match the algorithm to whatever the source published: SHA-256 is today's standard, while older projects may list MD5 or SHA-1 — fine for spotting accidental corruption, though only the SHA-2 family protects against deliberate tampering.
Private by design
Your files are processed directly in your browser using the browser's built-in APIs and are not uploaded to Filesvo. Nothing is stored on our servers, because nothing ever reaches them.
Frequently asked questions
- Is there a file size limit?
- Yes — 100 MB, because the file is read into browser memory to hash. For larger files, use your system's built-in command: sha256sum on Linux, shasum -a 256 on macOS, or certutil -hashfile on Windows.
- The checksums don't match — what now?
- First re-download the file — most mismatches are interrupted or corrupted downloads. If a fresh download still doesn't match the published value, don't run the file: it isn't the file the publisher released.
- Which algorithm should I compare?
- Whichever the download page publishes — you need the same algorithm on both sides. If several are listed, compare SHA-256 (or SHA-512); MD5 and SHA-1 no longer prove authenticity against tampering.
- Is my file uploaded to a server?
- No. The file is read and hashed entirely in your browser — it never leaves your device, which is exactly what you want when checking an installer.