Tool
Are these two files exactly the same?
Pick two files from this device to see their sizes and SHA-256 fingerprints, with an immediate identical-or-different verdict. No uploads — hashing happens in your browser.
Last updated
Compare two files
Drop a file in each slot. Everything is read and hashed on this device — nothing is sent anywhere.
How the comparison works
Select two files from your device. Your browser uses its built-in Web Crypto API to calculate each file's SHA-256 hash — a 64-character hexadecimal fingerprint of the bytes. Because the calculation happens entirely on your machine, the photos are never uploaded or sent across the internet.
You see the file size and full hash for both, followed by a clear verdict. If the two fingerprints match, every single byte in the files is the same.
What a match proves — and what it does not
A hash match proves byte-identity: the two files hold the exact same photo data — no recompression, no resizing, no metadata stripped. Any alteration at all, even re-saving a JPEG at the same quality, changes the bytes and produces a completely different hash.
That is all it proves. A match says nothing about who created a file, where it came from, or when it was made — anyone can copy a file, and the copy hashes the same. Treat the verdict as a sameness check, not a certificate of origin.
When photographers reach for this
Typical moments: confirming a copy on a second drive is intact, checking a client received the exact file you exported, or verifying a downloaded gallery file against the original on disk.
shoots.page stores originals byte-for-byte, so an original downloaded from your gallery hashes identically to the file you uploaded — a quick way to prove the delivery chain kept your work untouched. More on that in share photos without losing quality.