1. Add your files
Choose or drag in one or two files. They are read by your browser and never uploaded.
Check whether two files are identical, or verify a download against a published checksum, using SHA-256, SHA-384, SHA-512 or SHA-1. Files are never uploaded.
Choose or drag in one or two files. They are read by your browser and never uploaded.
SHA-256 is the standard choice. Match whatever algorithm the publisher of a download used.
A clear match or mismatch, with each full hash ready to copy for your records.
| Algorithm | Length | Use it for |
|---|---|---|
| SHA-256 | 64 hex characters | The everyday standard for verifying downloads and comparing files |
| SHA-384 | 96 hex characters | Stronger variant, used in some security and certificate workflows |
| SHA-512 | 128 hex characters | Longest output, popular for Linux distribution checksums |
| SHA-1 | 40 hex characters | Legacy only. Fine for spotting accidental changes, not for security |
No. Files are read and hashed by your own browser using its built-in Web Crypto API. Nothing is sent to Dueter or anywhere else, so it is safe for private documents.
A hash is a short fingerprint calculated from every byte of a file. Change a single byte and the hash changes completely, so two files with the same SHA-256 hash are, for practical purposes, identical.
Copy the checksum published by the software maker, paste it into "Expected checksum", choose the same algorithm (usually SHA-256) and add the downloaded file. A match means the file arrived complete and unaltered.
Browsers do not include MD5 in the Web Crypto API because it is no longer considered secure. If a site only publishes an MD5 checksum, ask for SHA-256 or use a desktop tool.
Files are read into memory, so the practical limit depends on your device. Files up to about 1 GB work well on most computers; larger files may be slow or fail on phones.
No. Only the contents are hashed. Two copies of the same file with different names or dates have the same hash.