01
Choose an algorithm
Select SHA-256, SHA-384, or SHA-512 and optionally paste a trusted expected hash.
Calculate SHA-256, SHA-384, or SHA-512 checksums for files locally and compare an expected hash.
A matching hash can confirm that bytes match an expected value. It does not prove a file is safe, trustworthy, or free of malware.
Your data is processed locally in your browser whenever supported and is not uploaded to our servers.
How it works
01
Select SHA-256, SHA-384, or SHA-512 and optionally paste a trusted expected hash.
02
Select up to ten files. Their bytes are read and hashed locally in the browser.
03
Copy individual checksums or confirm whether one file matches an expected value.
Private integrity checks
A cryptographic digest acts as a compact fingerprint for exact file contents. Even a small byte change normally produces a different checksum.
Uses the browser Web Crypto implementation of SHA-256, SHA-384, and SHA-512.
Validates hexadecimal length for the selected algorithm before showing match or mismatch.
Generate checksums for as many as ten files in one sequential local operation.
Files are read into browser memory and are never sent to Got A Tool for hashing.
FAQ
A hash is a fixed-length digest calculated from a file's bytes. The same bytes and algorithm produce the same digest, while changed bytes normally produce a different one.
Use the algorithm published by the file provider so the values can be compared. SHA-256 is the most common general choice; SHA-384 and SHA-512 produce longer digests.
MD5 has known collision weaknesses and should not be chosen for modern security-sensitive integrity verification. This tool focuses on SHA-2 algorithms supported by Web Crypto.
No. It only confirms that the bytes match the expected digest. A malicious file can also have a correctly published hash, so this is not antivirus or trust verification.
No. Hashing runs locally in your browser. Files up to 100 MB are read into device memory and are not sent to Got A Tool.
Keep working
Convert Unix seconds or milliseconds to readable dates and timezone-explicit ISO dates back to timestamps.
Open tool →Encode UTF-8 text to Base64 or decode validated Base64 text locally in your browser.
Open tool →Generate one or many cryptographically secure UUID v4 identifiers directly in your browser.
Open tool →