Home › All Tools ›

File Integrity Checker

Use File Integrity Checker online for free at FreeToolZones — no sign-up, no watermark.

Loading tool...

When you download a program, an update, or an important document, how do you know the file you received is the file the publisher intended? Downloads can be corrupted by a network error, truncated by an interrupted connection, or, in the worst case, replaced by a modified file. The File Integrity Checker answers that question by computing a hash of a file on your device and comparing it with the hash published by the provider. The file is read and hashed entirely in your browser and is never uploaded, so you can verify even large or sensitive files without sending them anywhere. A matching hash means the file appears intact; a mismatch means you should not trust the file until you obtain a fresh copy from a trusted source.

What Is the File Integrity Checker?

The File Integrity Checker is a free browser-based tool that computes a cryptographic hash of a file you select. A hash is a fixed-length fingerprint computed from the file bytes. The same file always produces the same hash, and any change to the file, even a single changed byte, produces a completely different hash. The tool offers four algorithms: SHA-256, labeled recommended, SHA-512, SHA-1, labeled legacy and not secure, and MD5, labeled legacy checksum only and not secure. SHA-256 and SHA-512 are computed with the browser WebCrypto library, while MD5 is computed locally in the page. After hashing, the tool shows the hash, the file name, the file size in bytes, and the algorithm used. If you paste an expected hash, the tool compares the two values, ignoring case, and reports whether they match, with wording that explains the meaning: a match means the file appears intact, and a mismatch means the file may be corrupted or tampered with.

The most important design feature is that the file never leaves your device. The tool reads the file into memory in your browser, hashes the bytes, and discards them. There is no upload, no server-side processing, and no copy retained by the site. That makes the tool suitable for verifying private documents, installers, and archives that you would not want to upload to an online service. The tool requires WebCrypto over HTTPS in a modern browser, and it shows a notice explaining the requirement if the API is unavailable.

The distinction between the algorithms matters. SHA-256 and SHA-512 are strong hash functions suitable for integrity verification against a deliberate attacker, provided the expected hash comes from a trustworthy source. SHA-1 and MD5 are broken for security purposes and should be used only to match a legacy checksum published by a provider, to detect accidental corruption. A matching MD5 checksum does not prove a file was not deliberately modified, because collisions can be constructed for MD5.

How to Use the File Integrity Checker

  1. Choose the file. Click the file input and select the file you want to verify from your device. The field notes that the file is read and hashed in your browser and never uploaded. Only one file is hashed at a time.
  2. Choose the hash algorithm. Select the algorithm that matches the hash published by the file provider. If no hash was published, choose SHA-256, the recommended default, to create a fingerprint you can record for later comparison.
  3. Optionally paste the expected hash. Copy the hash from the provider download page or release notes and paste it into the Expected hash field. The comparison ignores uppercase and lowercase differences.
  4. Click Compute File Hash. Press the button. The tool shows a message naming the file while it reads and hashes it, then displays the result. Larger files take longer, because every byte must be read.
  5. Read the result. Check the hash, file name, size, and algorithm. If you provided an expected hash, read the match or no-match message carefully. A match means the file appears intact. A mismatch means you should delete the file and download a fresh copy from the official source.
  6. Copy the hash if needed. Use the Copy Hash button to copy the computed hash for your records, for sharing with support, or for comparing with a value published later.

Key Features of the File Integrity Checker

  • Local file hashing. The file is read and hashed in the browser with no upload, protecting privacy and avoiding the bandwidth cost of sending large files to a server.
  • Four hash algorithms. SHA-256, SHA-512, SHA-1, and MD5 cover modern verification and legacy checksum compatibility, with honest security labels on the legacy options.
  • Expected-hash comparison. Paste a published hash and receive a clear match or no-match verdict with an explanation of what each outcome means for the file.
  • File details in the result. The file name, size in bytes, and algorithm are shown alongside the hash, so you can confirm you hashed the intended file and record the details accurately.
  • Case-insensitive comparison. The expected hash is normalized before comparison, so a hash published in uppercase matches a computed hash shown in lowercase.
  • One-click copying. The Copy Hash button copies the full hash without transcription errors.
  • Progress feedback. A message naming the file appears while hashing is in progress, so you know the tool is working on large files.

Practical Use Cases With Concrete Examples

Verifying a downloaded installer. You download an operating system image or a software installer, and the download page publishes a SHA-256 checksum. Hash the downloaded file here and compare. A match confirms the download is complete and unaltered. A mismatch tells you to delete the file and download again, rather than running a potentially corrupted or modified installer.

Checking a file after a transfer. You copy a large archive to a USB drive or receive it through a file-sharing service. Hash the file before and after the transfer, and compare the two values. Identical hashes confirm the transfer preserved every byte; different hashes reveal corruption that might otherwise go unnoticed until you try to open the archive.

Confirming a backup is unchanged. Hash a backup file when you create it and record the hash. Months later, hash the stored backup again. If the hash matches, the backup has not been altered or degraded. If it differs, the backup may be damaged, and you should rely on a different copy.

Matching a legacy checksum on an old download page. An older software page publishes only an MD5 checksum. Compute the MD5 hash here to confirm the download matches. Remember that this checks accidental corruption only, not deliberate tampering, because MD5 is not secure.

Verifying a document received by email. A sender emails a contract and publishes its SHA-256 hash on a website. Hash the attachment and compare. A match confirms the attachment is the document the sender hashed, provided you obtained the hash from a trustworthy source separate from the email.

Detecting accidental edits. You keep a reference copy of a data file and want to know whether a working copy was accidentally modified. Hash both copies at different times and compare. Any edit, however small, changes the hash, making the check far more reliable than comparing file sizes or dates.

Supporting a support request. When reporting a corrupt download to a vendor, include the computed hash and the expected hash in your message. That evidence helps support confirm the problem quickly and rules out a misunderstanding about which file you downloaded.

Tips and Best Practices

  • Always get the expected hash from the official source. A hash published on the same page as a compromised download proves little if the attacker changed both. Use the official website, release notes, or a signed checksum file, and prefer a channel separate from the download itself.
  • Use SHA-256 when you have a choice. It is the recommended algorithm, widely published by software providers, and strong enough for integrity verification. Use SHA-512 if the provider publishes that format.
  • Do not run a file whose hash mismatches. A mismatch means the file is not the file that was hashed. Delete it and obtain a fresh copy. Running it risks executing corrupted or malicious code.
  • Record hashes for important files. When you create a backup or archive, record its SHA-256 hash in a separate note. That record lets you verify the file years later without needing the original publisher.
  • Hash the file you actually received. Do not hash a renamed or re-saved copy and expect it to match, if the re-saving process changed the bytes. Hash the exact file you downloaded or transferred.
  • Remember that a hash does not prove authenticity on its own. A matching hash proves the file matches the hash, not that the hash came from the real publisher. For strong authenticity, look for digital signatures in addition to checksums.
  • For text, use the text tool. To hash text you paste rather than a file, use the Hash Checker, which offers the same algorithms for text input.

Limitations

The File Integrity Checker has limits that affect how much trust a result deserves. It hashes one file at a time, and it reads the entire file into browser memory, so extremely large files may be slow or may exceed what the browser can handle comfortably. The check proves only that the file matches a given hash; it does not prove the file is safe to run, free of malware, or from the publisher you think it is from, unless the expected hash itself came from a trustworthy, authenticated source. MD5 and SHA-1 results must not be treated as security guarantees, because collisions can be constructed for both functions. The tool does not scan for malware, does not inspect file contents, and does not verify digital signatures. It requires WebCrypto over HTTPS in a modern browser. Finally, a hash cannot detect a file that was malicious from the start: if the publisher hashed a malicious file, the hash will match perfectly. Integrity verification and malware scanning answer different questions, and both may be needed.

Frequently Asked Questions

Is my file uploaded to a server?

No. The file is read and hashed in your browser and never uploaded. That is stated in the tool itself. You can verify files that you would not want to send to any online service.

What should I do if the hash does not match?

Do not use the file. Delete it and download a fresh copy from the official source, then hash the new copy. If the mismatch persists, contact the provider, because the published hash may be wrong or the download source may be compromised.

Which algorithm should I use?

Use the algorithm the provider published, so the values are comparable. If you are creating a hash for your own records, use SHA-256. Avoid relying on MD5 or SHA-1 for security decisions.

Can the tool check multiple files at once?

No. The tool hashes one file per run. To verify several files, hash each one separately and compare each result with its published hash.

Does a matching hash mean the file is safe?

No. A match means the file is identical to the file that was hashed. It does not mean the file is free of malware or safe to run. Use malware scanning and trusted sources in addition to hash verification.

Why is the hash different after I edit and save a file?

Because any change to the file bytes, even one byte, changes the hash completely. Saving a file in an editor often changes metadata or formatting bytes as well as content, so the hash of the saved file will differ from the hash of the original.

Building a Verification Habit

Hash verification only protects you if it becomes a habit rather than an occasional effort. The most effective way to build the habit is to tie it to a trigger: every time you download an installer, an update, or a disk image, check for a published checksum before you run the file, and make the check part of the download routine, like scanning an attachment before opening it. Keep a short personal checklist for downloads from unfamiliar sources, including confirming the official domain, downloading only from that domain, finding the published hash on the official page, and comparing it here before execution. For files you create and archive yourself, record the hash in the same note or inventory entry that describes the file, so that a future verification needs no detective work. Teams can formalize the habit by including checksum verification in onboarding guides and deployment runbooks, so that new members learn it as standard practice rather than discovering it after an incident. Over time, the few seconds each check takes become invisible, while the protection against corrupted or substituted files remains. A habit that is easy and tied to a clear trigger is far more durable than a policy that relies on memory and good intentions alone.

Related Tools

Related tools include the Hash Checker for text hashing, the MD5 Hash Generator and SHA256 Hash Generator for dedicated hash tools, the File Hash Checker for an alternative file hashing workflow, and the MD5 File Checksum Tool for MD5 file checksums. Browse all tools from the homepage.

Browse More Tools