Our own photo of a pier in Melbourne, taken on an Android phone. We made a copy and removed one lamp post, then checked both files.
Before: our photo, straight off the phone.
After: the lamp post removed. Nothing else changed.
What changed
- One lamp post. At normal size, few people would notice it had gone.
- What saved the file. The original's compression matches no known editing software, as you'd expect from a phone. The copy's matches a common software encoder, with signs of a second save.
- The thumbnail. The phone stored a small preview that matched the photo. Saving the edit threw it away.
What the report said: Authenticity A for the original, B for the edited copy, with Origin as its weakest area.

The report didn't point at the lamp post. It showed the file had been re-saved by software, and a photo that's meant to be straight off the phone shouldn't have been.
Updated 14 November 2026
Reports now include evidence maps. We ran both files again. The grades are the same: A for the original, B for the copy.
-
Original: colour on the buildings and the pier.
-
Edited copy: the same areas.
-
The Compression map colours the same areas on both files. Sharp edges often react to being saved again, on an untouched photo too.
-
Only the copy has a Save history map, because it was saved twice. It measures the middle of the photo and marks a band along the far shore.
-
The lamp post stood near the right edge, outside the part that map measures. So the maps don't point at it either.

The new map says the file was saved again. It doesn't say what changed.
Go deeper
- How to check one yourself: Has this photo been edited?
- Why it works: How to tell if a photo has been edited, by Kenneth Springer
- Try it on your own photo








