Five Ways People Fake Proof Photos

Every photo- or video-proof accountability system has the same theoretical weak point: a file only proves that a picture was taken, not that the person who was supposed to take it actually took it. People exploit that gap constantly. Most fakes fall apart within a week, and the ones that survive longer usually aren’t beating the technology — they’re beating a partner who isn’t paying close attention.

Here are the five tactics that show up most often, roughly ordered from “gets caught almost immediately” to “no app on Earth can stop this one.”

1. Recycling an old photo

The laziest move, and the first one everyone tries. You woke up on time exactly once last month, took a great photo of your coffee and your alarm clock reading 6:02, and now you just… resend it. Every day it looks slightly different is a day someone might ask a question, so most people who try this only manage it two or three times before the pattern is obvious even to themselves.

What kills it: metadata and moving targets. An app that reads the timestamp baked into the image file catches a same-day resend outright — the photo says it was taken Tuesday, and today is Thursday. Apps that don’t bother with metadata can still close the gap by asking for something that changes daily: that morning’s newspaper front page, a coffee mug moved to a different counter the night before, a sticky note with a number generated fresh each morning. An old photo can’t contain tomorrow’s newspaper. That’s the whole trick.

2. Forwarding someone else’s photo

Slightly more sophisticated: you text a friend who’s already up, ask for their proof shot, and forward it as your own. This works exactly once, because the giveaway isn’t in the photo — it’s in the room. Your friend’s bedspread isn’t your bedspread. Their window faces a parking lot; yours faces a tree. A partner who’s seen ten of your real photos will clock the eleventh as wrong before they can articulate why.

On the technical side, this fails against any app that ties verification to that device’s camera at the moment of capture rather than accepting an uploaded file from a camera roll. If the app never lets a photo exist anywhere except inside its own capture flow, there’s no image to forward in the first place — your friend’s shot lives on their phone, not as a file either of you can hand off.

3. Pre-recording the night before

This one takes actual effort, which is almost a compliment. Same pajamas, lights dimmed to look pre-dawn, phone camera aimed at a spot that could plausibly be “6 AM bedroom” at 11 PM the night before. Some people even set a fake alarm sound playing in the background for authenticity.

It falls apart on light. Sunrise has a specific color temperature and a specific angle, and a lamp doing its best impression of dawn light rarely nails both. A partner who’s been burned before starts checking the window in the background — is that gray predawn light or orange lamp light? — and once they ask that question out loud, the game’s over.

Technically, this dies against any prompt generated at send-time rather than fixed in advance: hold up a word the app displays only the instant you open the camera, not a phrase you could’ve known about eight hours earlier. You can’t pre-record a response to a prompt that doesn’t exist yet.

Where DontSnooze sits on this: photos are timestamped server-side the moment they’re received, not by trusting whatever time your phone claims, and capture happens inside the app’s own flow rather than from an existing file. That closes tactics 1, 2, 3, and 5 below. It does not, and cannot, close tactic 4 — nothing does.

4. Getting someone else to actually do it

Here’s the honest one. You ask your roommate, your partner, your sibling — whoever’s already awake — to physically go make the coffee, take the photo, hold up the sign, and send it in your name. No editing. No old files. No clock tricks. The task genuinely gets done, just not by you.

There’s no technical fix for this, and it’s worth saying plainly rather than pretending otherwise: any system that verifies through a photo is verifying that a photo of the task exists, not that you took it. A camera has no way to check whose finger pressed the shutter.

The defense here isn’t code, it’s a person. A partner who knows your voice, your morning habits, your usual angle for these photos will eventually notice the proof feels like someone else’s rhythm. And there’s a simpler check that has nothing to do with detection: you know who you asked to lie for you, and you know you’d have to look them in the eye about it later. That’s a heavier deterrent than most people expect going in — turning your morning routine into a small daily promise to a specific person tends to work more like a social contract than a surveillance system, and social contracts are held up by people, not sensors.

5. Rolling back the clock

The technical cousin of tactic 3. Set your phone’s system time back an hour, snap your very-late proof photo, send it, then set the time back to normal. To the device, the photo was taken right on schedule.

This only works against apps dumb enough to trust the device’s self-reported clock. Any app that stamps the photo using server time — the time its own servers logged the upload arriving — makes your phone’s clock irrelevant. You can lie to your phone all you want; you can’t lie to the server about what time it is.

The pattern underneath all five

Notice that four of these five die to the same idea: verify at the moment something independent of the user’s control happens — a server receiving a file, a prompt generated on the spot, a camera shutter firing inside a locked flow — rather than trusting anything the user’s own device reports about itself. The fifth one dies to a person, not a system, because it was never a technical problem to begin with.

If you want the fuller framework for why some fakes are cheap to pull off and others are expensive even to attempt, there’s a broader way to think about it in the fakeability matrix — it maps effort against detectability across more than just photo proof. But for photo proof specifically, this is the whole list. Five tactics, four technical answers, and one answer that was always going to be human.