Hash a local file with SHA-256 (default), SHA-512, or legacy SHA-1 and optionally compare an expected digest — entirely in your browser. Files are never uploaded. Distinct from Hash Generator (text-only) and HMAC Generator (keyed message MAC).
No. Hashing uses the local File API and Web Crypto in your browser. The file never leaves your device for ConvertWiseHub servers.
Hash Generator hashes pasted strings. This tool hashes file bytes with progress for larger files and an optional expected-hash verify UI. Need a keyed MAC of a message? Use HMAC Generator.
Checksumming stays in browser memory. The 50 MB hard cap keeps mid-tier devices responsive while covering typical downloads and build artifacts. Larger files need a desktop or CLI hasher.
When you paste an expected hash, Match means the computed digest equals that string (after normalizing hex/Base64). Mismatch means they differ. A match does not prove the publisher is trustworthy — only that the bytes match the digest you pasted.
SHA-1 is collision-weak for new trust decisions. It remains only so you can compare older vendor-published SHA-1 checksums. Prefer SHA-256 or SHA-512 when you control the pipeline.
Paste whichever form the publisher printed. Hex is usual in checksum files; Base64 appears in some APIs. Length must match the selected algorithm. Spaces and optional 0x prefixes are ignored for hex.