🔑

Ħieles File Hash / Checksum

Compute SHA-256, SHA-1, SHA-384, and SHA-512 checksums of any file and verify a download against its published hash. The file is never uploaded.

Ebda limitu tad-daqs tal-fajlIl-fajls jibqgħu privatiEbda login meħtieġĦieles għal dejjem

Waqqa 'fajls hawn, jew ikklikkja biex tfittex

Any file ebda limitu tad-daqs tal-fajl

Fittex fajls

Il-fajls tiegħek qatt ma jħallu t-tagħmir tiegħek. L-ipproċessar kollu jseħħ lokalment fil-browser tiegħek.

Compute SHA-256, SHA-1, SHA-384, and SHA-512 checksums of any file — and verify a download against its published hash. The file is read locally and never uploaded.

Optimize for your platform

Kif Taħdem

A checksum is a fingerprint of a file. Publishers list one next to a download so you can confirm the file you got is exactly the one they released — not corrupted or tampered with. This computes them in your browser.

  1. 1
    You pick a file
    It's read into memory locally — never uploaded, no matter the size.
  2. 2
    Web Crypto hashes it
    The browser's native crypto.subtle computes SHA-256, SHA-1, SHA-384, and SHA-512 in a single pass over the bytes.
  3. 3
    You compare to the published hash
    Paste the checksum from the download page; it's matched against all four algorithms and a clear ✓/✗ tells you if the file is authentic.
  4. 4
    Copy any hash
    Grab a checksum to publish alongside your own files.

Verifying a sensitive download (an installer, a disk image, a backup) shouldn't require uploading it anywhere. The hash is computed entirely on your device with native browser crypto.

Għaliex nużaw tagħna?

Completely free — no hidden costs, ever
No account, email, or login required
Files stay on your device — processing happens in your browser
Works on any device — phone, tablet, desktop
No watermarks on any output
Browser memory limits may apply for very large files

Għodda Relatati

Din l-għodda kienet utli?

Mistoqsijiet Frekwenti