Airbnb changed the evidence rules.
Here is what it means for your claims.

Airbnb's April 2026 Terms of Service update changed how damage claims are judged. Two things matter for hosts: claims must now meet a Legitimate and Verifiable Evidence standard, and AI-generated or AI-altered images are banned from claims.

Legitimate and Verifiable Evidence means original, unedited, independently checkable documentation. Provenance now counts as much as the picture: a photo you can prove is original and unaltered beats a prettier one you cannot.

The change rewards honest, timestamped capture and puts edited or reconstructed photos at risk. It did not change what AirCover covers or the 14-day window, only what counts as proof once you file. Always review the current terms on your own account.

Legitimate and Verifiable Evidence is Airbnb's name for documentation a reviewer can trust: original files that have not been edited or reconstructed, carrying details that can be independently checked, such as when and where they were captured. It is the formal version of what strong hosts were already doing.

The practical effect is that provenance now matters as much as the picture. A clear photo with no verifiable origin is weaker than a slightly less pretty one that can be proven original and unedited. This is the same idea as tamper-evident evidence, now written into the rules. In effect, Airbnb has moved the question a reviewer asks from "does this photo look like damage?" to "can I trust that this photo is what it claims to be?" The second question is answered by metadata and integrity, not by image quality.

Banning AI-generated evidence is aimed at fabricated claims, and for honest hosts it is good news: it discredits the invented photos that used to muddy disputes. The trap is accidental non-compliance.

Run a genuine damage photo through an app that auto-enhances, upscales, or cleans it up, and you can turn real evidence into something that looks altered. The safest habit in 2026 is simple: capture the original and submit the original, untouched.

The subtle danger is that many phones and gallery apps now enhance images by default, and some cloud services re-compress or "improve" photos automatically. An honest host can end up submitting an altered file without ever choosing to edit anything. The defence is to keep the true original, captured and stored somewhere that does not silently process it, and to submit that. If a guest ever turns this around and accuses you of faking evidence, verifiable originals are your defense. That scenario is covered in accused of faking evidence, and the flip side, why Airbnb rejects photos, is in why Airbnb rejects your photos.

Most hosts do not need a new philosophy; they need to find the one place their existing habit quietly breaks the standard. Run this quick audit against how you document today:

• Where do your photos live? If they pass through a chat app or auto-enhancing gallery, the version you would submit may already be altered. Keep the untouched original.
• Can you prove when they were taken? A file with no verifiable timestamp is weak now. Capture needs to record time in a way a reviewer can check.
• Can you prove where? Location data ties the damage to your property. Without it, an image is harder to trust.
• Can you prove nothing changed after capture? An integrity hash or tamper-evident record answers this before it is asked.

If any answer is "no," that is the gap to close first. The Damage Documentation Score runs exactly this audit and scores where your workflow falls short of the 2026 bar.

The update did not arrive as a dramatic announcement so much as a revision to the terms every host had already agreed to. That is worth understanding, because it shapes how it applies to you:

• The Terms of Service were updated in April 2026, folding the evidence standard and the AI-image ban into the rules that govern every claim.
• It applies going forward, to claims judged under the current terms, which means the workflow you use on your next checkout is the one that matters, not the one you used last year.
• Enforcement lives in the review, where a claim is assessed against the standard. There is no separate approval step to pass in advance; the first time it is tested is the first time you file.

The quiet nature of the rollout is exactly why so many hosts are operating on out-of-date assumptions. The rules changed under them, and the first sign will be a claim that behaves differently than they expected. Reading the current terms on your own account is the only way to be sure you are working from the live version.

Before 2026, verifiable capture was an edge. After 2026, it is the baseline, and improvised documentation is the liability. If you take nothing else from the change, build these into every stay:

• Capture, do not curate. Photograph the real condition in place and leave it untouched. The instinct to tidy an image up is now a risk.
• Record provenance automatically. Time and location should be captured for you, not typed in later, so a reviewer never has to take your word for them.
• Store the true original. Keep the unprocessed file somewhere that will not silently enhance or re-compress it, and submit that.
• Prove integrity. A hash or tamper-evident record means any later change is detectable, which turns "trust me" into "check for yourself."

None of this is more work than what many hosts already do; it is the same work, captured in a way that survives the new standard. The checkout inspection guide turns these habits into a repeatable routine.