What EXIF metadata actually stores
EXIF is a standard block of data embedded in most photos. It can include the capture date and time, camera settings, and, if location services were on, GPS coordinates. In theory it answers the two questions a reviewer cares about: when was this taken, and where.
In practice the host controls the device clock and the location setting, and the data can be edited with free tools. So even when EXIF is present, it proves intent more than fact, because nothing stops it from being changed.
Why metadata vanishes before a reviewer sees it
The bigger problem is that metadata rarely survives the journey to the claim. Messaging apps and many upload flows compress images and strip EXIF by default. A screenshot of a photo keeps the picture and discards every original field. By the time the photo reaches Airbnb, the date and location it once carried are often gone.
This is why a host can swear a photo was taken at check-out and still have no way to show it. The proof was real at capture and lost in transit.
What reviewers trust instead
Because raw EXIF is both alterable and fragile, strong evidence does not depend on it. It captures the time and place into a record that lives outside the image file and cannot be silently rewritten, then publishes that record where a reviewer can confirm it.
The photo still matters, but it is anchored to a verifiable report rather than to metadata that may have been edited or erased. That anchor is the difference between a picture and a proof.
Go deeper
Related guides
Airbnb evidence guide
The full standard for damage evidence that survives the claim process.
ReadTamper-evident evidence
Documentation built so any change after capture becomes detectable.
ReadGPS-verified report
An inspection document where location and capture time are verified, not just embedded.
ReadEvidence quality
What separates evidence a reviewer trusts from evidence they discount.
Read