You mostly can't prove it with the photo alone. A phone photo carries a date in its metadata, and that date can be changed, stripped by the platform you sent it through, or reset the moment the phone's clock is wrong. An adjuster who has seen a few contested claims knows this. So does opposing counsel if the claim ends up in a dispute. The photo by itself rarely settles the question of when the damage happened. What settles it is everything around the photo: when you sent it, who else saw the property before the loss, and whether anyone independent of you can confirm the timing.
Why this becomes a fight in the first place
Pre-existing damage disputes come down to one question: was this already broken before the covered event, or did the event cause it? A roof with wind damage after a storm looks a lot like a roof with wear damage that predates the storm. A water stain from a slow leak looks like a water stain from a sudden pipe burst. The photo shows the damage. It does not show when the damage started.
Carriers know this, and some adjusters are trained to look for it. If your claim involves a large loss, an older property, or damage that could plausibly have existed for months, expect the timing question to come up. It's not always bad faith. Sometimes it's a legitimate question the carrier is obligated to ask before paying out.
What doesn't actually help much
EXIF metadata. Most phones write a timestamp into the photo file when it's taken. That field is easy to edit with free software, and courts and adjusters both know it. An unverified EXIF date is weak evidence on its own, especially once a photo has been through a text message, an email attachment, or a social media upload. Many of those platforms strip metadata entirely during the upload, so the field may not even survive to the point where anyone wants to check it.
Filenames. "IMG_20240312" means nothing if the file itself has no independent record of when it was created. Anyone can rename a file.
"I remember taking it that day." True, probably. Also not something a carrier or a court can verify.
None of this means photos are worthless. It means the photo alone, unsupported by anything else, is a weak timing witness.
What actually helps
Photograph before repairs start, not after. This sounds obvious, but it's the single biggest factor in these disputes. Once repair work begins, the pre-loss condition is gone. If you're a contractor or property owner and you know work is coming, get photos of the site before anyone touches it. This is true whether the damage already exists or you're documenting a clean baseline before a project, so you have something to compare against later if a dispute ever comes up.
Keep originals somewhere other than just your phone's camera roll. Cloud photo sync services sometimes preserve metadata and sometimes don't, depending on settings you may not control. Back up the original files to a location you control, and don't rely on a screenshot of a photo. A screenshot has its own new timestamp and drops whatever metadata the original had.
Send the photos to your carrier promptly, and keep the correspondence. An email or claim-portal upload with a date on it is a record independent of the photo file itself. If you emailed damage photos to your adjuster two days after a storm, that email's timestamp is evidence the photos existed by then, even if the file metadata is contested. Don't wait weeks to submit documentation you already have.
Get a third party to see the property too. A contractor's estimate, a public adjuster's inspection report, a neighbor's account, a building inspection tied to a permit, even a delivery or service record that puts someone on the property on a specific date, all of these are corroboration that doesn't depend on trusting your camera roll. The more independent sources point to the same timeline, the harder it is to argue the damage was already there.
Check for outside records that happen to place a date on the condition. Weather service records for a storm, a prior insurance inspection, real estate listing photos if the property was recently sold or appraised. These aren't things you create for the claim. They already exist, and they can back up your timeline without anyone questioning your motives.
Where a blockchain anchor fits, and where it doesn't
This is the part worth being honest about, even though it doesn't help most people reading this after a loss has already happened: a blockchain anchor is not something you can apply retroactively to rescue an old, undated photo. If the damage already happened and the only photos you have are already sitting on your phone with disputed metadata, anchoring them today doesn't create a record of when they were originally taken. It creates a record of today.
Where it does something real is going forward. ProofLedger takes a SHA-256 hash of a file, a fingerprint unique to that exact file, and anchors it to the Polygon and Bitcoin blockchains. The file itself never leaves your device. Only the hash goes on the public record. Anyone, including a carrier, an opposing attorney, or a court, can independently check that the hash was anchored on a given date without having to trust ProofLedger, without having to trust you, and without ProofLedger being able to alter the record afterward.
That matters because it solves a specific gap the other methods don't fully close. An email to your carrier shows your correspondence had a certain timestamp, but that timestamp comes from your carrier's mail server, and you're trusting their system. A blockchain anchor is checkable by a party who has no stake in either side of the claim.
So the practical use is forward-looking: if you're a contractor documenting a site before a job starts, a landlord photographing a unit before a new tenant moves in, or a property owner who wants a baseline record of current condition before hurricane season, anchor those photos the day you take them. Then if a dispute ever comes up about whether that damage predated a loss, you have a record that exists independent of your phone, your cloud account, or your word.
What none of this guarantees
A timestamp, anchored or not, does not prove who took a photo, what camera it came from, or that nothing in the frame was altered before the shutter clicked. It proves the file existed in that exact form by a certain date. That's a real, useful fact in a timing dispute. It is not a substitute for a full case, and no carrier is obligated to settle a claim in your favor because one piece of evidence checks out. What it does is remove one argument from the other side's table: they can dispute whether your damage was caused by the covered event, but they can't credibly claim you fabricated the photo last week.
If you're dealing with a dispute right now over photos you already have, your strongest move is corroboration, not technology: get the correspondence records, get a second party's account, and be straightforward about what you can and can't independently verify. If you're trying to avoid this fight on your next project or policy period, the fix is boring but effective. Document before you need to, keep the originals somewhere durable, and if you want a record nobody can quietly edit later, anchor the hash the day you take it.