Guide · Evidence
What is a SHA-256 checksum, and how do you check a file’s hash?
SHA-256 is a hash function: it reads a file and produces a 64-character fingerprint of its exact bytes. Change one byte and the fingerprint changes completely, so matching fingerprints mean the file is the same as when the first one was taken. To check one on a Mac, open Terminal and run shasum -a 256 followed by the file; on Windows, certutil -hashfile followed by the file and SHA256. A hash proves sameness, not who made the file or when ([NIST’s standard](https://csrc.nist.gov/pubs/fips/180-4/upd1/final) defines the function).
On this page
A fingerprint for a file
A hash function reads any amount of data and returns a short, fixed-length result. SHA-256 is one of the functions in NIST’s Secure Hash Standard, and its result is 256 bits, usually written as 64 characters of 0 to 9 and a to f.
Three properties make it useful:
- Same input, same output. Hash a file today and next year, and you get the same string.
- Tiny change, total change. Flip one bit and about half of the output changes. There is no “close match”.
- One way. You can’t rebuild the file from the hash, and you can’t easily make a different file that matches it.
So a hash is a way to say “this is exactly that file” without sending the file.
What a matching hash proves
If you wrote down a file’s hash on Monday and it matches on Friday, the file hasn’t changed in between. Not a pixel, not a date in its metadata, not a byte. That is all it proves, and it is a lot.
What it does not prove:
- Who made the file. Anyone can hash anything.
- When it was made. A hash has no clock in it. You need a record of when the hash was written down.
- That the content is true. A hash of a staged photo matches that staged photo.
To prove “unchanged since a date”, the hash has to be written somewhere you can’t quietly edit: sent to someone, printed, or kept in a tamper-evident record.
Check a hash on a Mac
- Open Terminal (in Applications, then Utilities).
- Type
shasum -a 256with a space at the end. The 256 picks the SHA-256 function. - Drag the file into the window, so its path appears, and press Return.
- Compare the long string it prints with the one you were given. Check the first and last eight characters at least.
Check a hash on Windows
- Open Command Prompt or PowerShell.
- Type
certutil -hashfileand drag the file in, then typeSHA256(the same function) and press Enter. - Compare the result. Capital or small letters don’t matter.
Why a photo’s hash changes when you share it
Send a photo through a chat app and the copy that arrives often has a different hash. That is not tampering. Many apps resize, recompress or strip metadata as they send. Even saving a photo again can change bytes. If you need a copy to keep its fingerprint, share it as a file, not as a picture, and check the hash on arrival. For what that metadata holds, see what photo metadata reveals.
Hashes and encryption are different tools
A hash shows that a file is unchanged. Encryption keeps it unread. Many systems use both: an authenticated cipher has a check built in, as the AES guide explains, and an encrypted file can be hashed like any other.
Where Sealed helps, and where it doesn’t
It helps in an evidence stack, which records a fingerprint for each file. In an evidence stack, every photo, video, voice memo and document you add gets the time, a fingerprint that changes if the file does and, if you choose, where your iPhone was, and each entry is tied to the one before, so a changed file or one slipped in shows.
It helps you check those fingerprints without the app. An evidence stack makes a PDF report with each file’s SHA-256 fingerprint, and explains how to check a file yourself with shasum on a Mac or certutil on Windows. Each link of an evidence chain is written as plain text, so anyone can recompute its hash with standard tools. The evidence stacks page shows how.
It doesn’t make a file trustworthy on its own say-so. An evidence stack shows whether anything changed after it was added, as far as the vault can tell. It is not a legal guarantee.
It doesn’t fix a fingerprint until a report leaves your phone. An evidence stack is not tamper-proof: whoever holds the vault key could rebuild a whole chain, so a report that has left the phone is the fixed point, and a file whose fingerprint matches that report has not changed since.
Questions and answers
Is SHA-256 encryption?
No. A hash goes one way: there is no key and no way to get the file back from the fingerprint. Encryption is two-way, with a key.
Can two different files have the same hash?
In theory, yes. In practice, nobody has found two files with the same fingerprint for this function, and a forger would need to make one on purpose.
Why does a copied photo sometimes have a different hash?
Because it isn’t byte for byte the same. Many apps recompress photos, strip metadata or convert formats when they share them, and any of those changes the fingerprint.
Sources
What this page says about Sealed was checked against the app on .
- NIST, FIPS 180-4, Secure Hash Standard — published August 2015; specifies hash algorithms, SHA-256 among them, that generate digests of messages. Read 13 Nov 2026
- Sealed on the App Store — the listing for the app used as the example
Get Sealed
Sealed is free to download, and Sealed Pro is an optional in-app purchase.