Check a Sealed Photo yourself
Check a Sealed Photo right here, and it stays on your device. For a second opinion from a tool we don't run, use an independent check. Then see what a result shows, and what to do with a Proof Report.
Check a photo here
This check needs JavaScript and a recent browser. If this message is still here once the page has loaded, this browser can't run it. Use the independent check below instead.
Your photo never leaves this device.
The checker downloads to your browser, then checks your photo right here. Your photo, and anything read from it, isn't sent anywhere.
or drop it here
JPEG, PNG, HEIC, WebP, AVIF or TIFF, up to 50 MB.
On iPhone, choose the file from Files. Picking it from Photos can convert it and remove the seal.
Got a Proof Report? This page checks photos, not reports. Here's how to check a report.
Checked: ()
How this check works
This page runs the Content Authenticity Initiative's open-source C2PA library in your browser (c2pa-web 0.15.4, built on c2pa-rs 0.91.3). The PicLatch app seals photos with c2pa-rs 0.77. The parts that read your photo run with no permission to connect to anything.
The library checks that the picture and the sealed details haven't changed. The timestamp row comes from our own code instead, because the library can't tell whose timestamp it is.
The seal is intact
The picture and the details sealed with it haven't changed since it was sealed. An edit to either would have broken the seal.
- Signer
Not recognized
This page doesn't check who signed. PicLatch makes each photo's certificate on the renter's phone, so a genuine PicLatch photo shows this too. Anyone can make a certificate with any name, so the name on it doesn't show who sealed the file.
Name on the certificate:
- Capture time recorded in the file
Not recorded
Recorded, but not as a date this page can read
- Device recorded in the file
Not recorded
Whoever made the file recorded these. The seal shows they haven't changed, not that they're right.
- Location
Recorded in the file. This page doesn't show it.
Not recorded
- Trusted timestamp
From FreeTSA, the timestamp service PicLatch uses. It shows the seal existed by then. It says nothing about what the room looked like.
None - timestamp from an unrecognized service
This photo carries a timestamp from a service PicLatch does not recognize, so its time is not treated as independent proof. The seal itself is intact.
None - timestamp could not be verified
This photo carries a timestamp that could not be verified, so it is not treated as independent proof. The seal itself is intact.
Not checked
This page couldn't check this photo's timestamp. The seal itself is intact.
Not reported
This photo doesn't carry an independent timestamp, for example because the timestamp service wasn't available when it was sealed. That alone doesn't mean the file changed.
Not checked
This page checks timestamps on JPEG photos only. PicLatch photos are JPEGs.
A seal shows the picture and the sealed details haven't changed. It can't show who took the photo or what's outside the frame. Someone could also edit a photo and seal it again, so ask for the original straight from the phone.What sealing does not prove
This file doesn't match its sealThis seal didn't pass every check
The file may have changed after it was sealed, or it may be damaged. Treat this as a failed check, and ask for the original file again.
Part of the seal didn't pass its check. That doesn't show the picture changed, but this page can't vouch for the seal. Treat this as a failed check, and ask for the original file again.
What didn't pass:
- The file's contents don't match what was sealed. Rewriting a photo's details can do this, even if the picture looks the same.
- Details recorded in the seal didn't pass their check.
- The seal's signature didn't pass its check.
- The signing certificate didn't pass its check.
- The timestamp didn't pass its check.
- Another check didn't pass.
Want a second look? Check the same file with an independent tool.
Technical details
This file's Content Credentials couldn't be read
This page found what looks like Content Credentials but couldn't read them, so it can't say whether the file changed. Treat this as a failed check, and ask for the original file again.
This page couldn't read that file
This page couldn't read this file, so it can't say whether it changed. Treat this as a failed check, and ask for the original file again.
No Content Credentials found
This file doesn't carry a seal. It may not be an original Sealed Photo, or an app along the way may have removed the seal: some apps shrink or convert photos, and that strips it. Ask for the original file.
This file's Content Credentials are stored online
This page doesn't connect to anything while it checks, so it can't fetch them. Ask for the original Sealed Photo. PicLatch keeps the seal inside the file.
This page can't check that file
It checks photos: JPEG, PNG, HEIC, WebP, AVIF or TIFF.
That doesn't look like a photo. It may be a Proof Report
A Proof Report isn't sealed, so there's nothing here for this page to check.Here's how to check the photos in a report.
That file is too big to check here
This page checks files up to 50 MB.
The check couldn't finish
Try again. If it keeps happening, this browser may not be able to run the check, and you can useContent Credentials Verify instead.
What verification proves
PicLatch signs each photo on the phone right after it's taken, and that signature is the seal.
Checking the seal shows whether the picture and the details sealed with it have changed, because an edit to either breaks it.
The seal also covers details PicLatch recorded, such as the capture time, the phone's make and a location if one was added, but the seal shows they haven't changed, not that they were right.
It can't show who took the photo, who caused what it shows, or what's outside the frame, and our page onwhat sealing does not prove goes through each limit.
Independent, not ours — on purpose
A free tool we don't run can read the seal for you. It's built on C2PA, the open standard PicLatch's seal follows, so checking a photo there doesn't depend on us. It can tell you whether the file changed after it was sealed. It can't tell you who sealed it.
Content Credentials Verify (contentcredentials.org/verify)
- Get the original file. If you're the renter, open the Move-In Record tab in PicLatch, tap the photo to open Photo Details, then tap the share icon at the top of the screen. PicLatch sends the original Sealed Photo file, not a copy. AirDrop, Files and email at actual size usually keep the file as it is. Some apps shrink or convert photos, and that can strip the seal, so check that the tool finds one. Screenshots and the pictures in a Proof Report don't carry the seal. If someone else is sharing a photo with you, ask them for the original file this way. The original also carries the exact location if one was added, so share it only with people you mean to.
- Add it to the tool. Open Content Credentials Verify with the link above and add the file. It's a separate site with its own terms, so read them first.
- Read the result. Unrecognized and invalid mean different things, so read them closely.
- Unrecognized. An unchanged PicLatch original is expected to show this. The signer isn't on the tool's trust list, because each photo is signed with a certificate made on the renter's phone. The tool may show the name ProvenancePhotos. Unrecognized means the tool can't vouch for who signed. It isn't a sign the file changed. But anyone can make a certificate with any name, so neither unrecognized nor the name ProvenancePhotos shows who sealed the file. That's why getting the original straight from the renter's phone is part of the check.
- Invalid. The check failed. The file may have changed after it was sealed, or it may be damaged. Don't wave an invalid result away: treat it as a failed check, and ask for the original file again.
- No credentials found. The file isn't an original Sealed Photo, or something along the way stripped the seal. Ask for the original.
- No signing time. The tool may not show a signing time, for example when a photo was sealed without an independent timestamp. That alone doesn't mean the file changed.
The tool's wording can change. If what you see doesn't match this, email us.
Got a Proof Report?
A Proof Report is one web page file, made from Sealed Photos and shared from the renter's app. You open it in a browser. The app may also call it a PicLatch Landlord Report: the file is named piclatch-landlord-report followed by the date, and its page title reads PicLatch Landlord Report.
The report itself isn't sealed. Its text (the times, rooms and Manifest ID lines) and its smaller preview pictures can be changed, and those pictures don't carry the seal.
A report has no QR code and no link that checks it online. Its footer points to the original sealed files as the source records for independent checking.
To check a photo, ask the renter for that photo's original file, check it withthe steps above, and compare the details the tool shows with what the report says.
A report is a readable summary. The original files are the record.
Keep reading
- What sealing does not prove
Where a seal stops, in plain language.
- Verification Details, screen by screen
What each screen in the app shows about a photo.