Download Hash Verifier

Downloaded Tor Browser, Tails, a Linux image or a crypto wallet? Before you open it, check it’s the exact file the developers released. Choose the file below and paste the checksum from the official website. Your file is read on your device and never uploaded, even if it’s several gigabytes.

Runs in your browser. Your file is read on your device and never uploaded; nothing is sent or stored.

Next stepMetadata RemoverSee and strip hidden GPS, device and author data from files.

What a checksum tells you

A checksum (or hash) is a short fingerprint calculated from every byte of a file. Change a single byte and the fingerprint changes completely. Publishers list the fingerprint of each release, so if yours matches, you have exactly the file they published: not a damaged download, not a half-finished one, and not a copy someone has tampered with.

That matters most for privacy and security software. Fake Tor Browser and wallet downloads are a common way to spread malware that steals passwords and crypto, and they look identical to the real thing. Checking takes a minute and catches them.

How to use it

  1. Download the file from the project’s official website.
  2. On that same official site, find the checksum: usually a 64-character SHA-256 next to the download link, or a file called SHA256SUMS.
  3. Choose your file above and paste the checksum. You can paste a whole SHA256SUMS file; the tool picks the line for your file’s name.
  4. Wait for the result. A green Match means the file is genuine. A red No match means don’t open it: delete it and download it again.

Use SHA-256 or SHA-512 wherever the publisher offers them. SHA-1 and MD5 are old: they still catch a damaged download, but a determined attacker can create a fake file with the same MD5 or SHA-1 fingerprint.

Checksums vs signatures

A checksum is only as trustworthy as the page you copied it from. If attackers control the download site, they can swap both the file and the checksum. That’s why projects like Tor Browser and Tails also publish a digital signature (an .asc file) made with the developers’ own key. Checking the signature proves the release came from them, whichever website it came through.

This tool checks checksums. For signatures, follow the project’s own guide (linked under “Where to find official checksums and signatures” above): the Tor Project’s signature guide and the Tails expert verification. The Tails download page also checks your download for you.

Using it in Tor Browser

The tool works at Tor Browser’s Standard and Safer security levels. At Safer, WebAssembly is switched off, so the tool falls back to the browser’s built-in hashing. That works for files up to 1 GB. For larger files, such as some Linux images, switch this page to Standard or check the file with your computer’s own tools (shasum -a 256 on macOS and Linux, certutil -hashfile file SHA256 on Windows). At Safest, JavaScript is off and the tool can’t run.

New to Tor? Read our Tor Browser review and how to access the dark web safely.

Hash verifier FAQ

Is my file uploaded?

No. Your browser reads the file in pieces and calculates the checksum on your device. Nothing about the file, not even its name, is sent to us or anyone else. The page is locked so it can't send data anywhere.

Where do I find the official checksum?

On the project's official website, usually next to the download link or in a file named SHA256SUMS or similar. Copy it from the official site over HTTPS, not from a forum, a video description or the mirror you downloaded from. Our list under the tool links to the right pages for popular privacy software.

The checksums don't match. What now?

Don't open or install the file. Delete it, download it again from the official website and check again. A mismatch usually means the download was interrupted or damaged, but it can mean the file was replaced. If it still doesn't match, use a different network or ask the project.

Does a match mean the file is safe?

It means the file is exactly what the publisher released, as long as the checksum came from the publisher. It doesn't judge whether the software itself is trustworthy, so stick to well-known projects. For the strongest check, also verify the developers' digital signature.

Which algorithm should I use?

SHA-256 (or SHA-512) whenever the publisher offers it. The tool picks the algorithm automatically from the length of the checksum you paste. SHA-1 and MD5 only rule out accidental damage, because attackers can fake them.

Why does it say "Couldn't verify"?

The check didn't finish: you cancelled it, the file couldn't be read (for example it was still downloading), or the browser can't hash a file that size with WebAssembly switched off. We never show a match unless the whole file was checked.