Guide
How to spot a fake screenshot
Fake chat and social-media screenshots spread fast — but most give themselves away. Here are the 12 tells that catch them, from the status bar to the pixels, plus a quick self-check.
A screenshot feels like proof. That is exactly why fabricated ones spread so easily — a fake text exchange, a doctored DM or an invented tweet can go viral before anyone checks. The good news: making a screenshot that survives real scrutiny is harder than it looks, and almost all fakes leave tells. This guide is the checklist we use ourselves.
The single most reliable test isn’t in the image at all: ask to see the live conversation in the app. A real thread can be scrolled and screen-recorded; a fake usually can’t.
Start with the status bar
The strip at the top of a phone screenshot — time, signal, Wi-Fi, battery — is the most common point of failure, because people focus on the message bubbles and forget the chrome. Check that the battery, signal and time are internally consistent and plausible, and look for the tell-tale placeholder word “Carrier”, which only appears in simulators. A status-bar time that contradicts the timestamps in the conversation is a giveaway.
Check the timestamp logic
Read the conversation as a timeline. Do replies come after the messages they answer? Does a “Delivered” or “Read” marker sit under a message that has already been replied to? Do day dividers appear where the app would insert them? Fakes are usually built message-by-message and rarely keep the chronology airtight.
Look at the type and the bubbles
Real apps render in the system font and with exact geometry. Watch for a substituted font,off kerning, emoji drawn in the wrong platform’s style, a bubble whose corner radius or tail is subtly wrong, or a colour that is close to — but not exactly — iMessage blue, WhatsApp green or the Instagram gradient. These millimetre errors are where hand-made fakes fall down.
The 12 tells at a glance
Status bar that does not add up
A dead battery next to a full signal, a time in the bar that contradicts the message times, or 5G on a carrier that has none. The status bar is copied last and fixed rarely.
The word "Carrier"
A placeholder network name like “Carrier” only appears in simulators and mockups — never on a real phone with a SIM.
Impossible timestamps
Replies that arrive before the message they answer, a “Delivered” under a message the other person already replied to, or a conversation that jumps across days with no date divider.
Wrong font or kerning
Real apps use the system font (SF on iOS, Roboto on Android). Slightly-off letter spacing, a substituted font, or emoji from the wrong platform are strong tells.
Bubble geometry that is subtly off
Corner radius, tail shape, padding and max-width are exact in the real app. Fakes often get the bubble a few pixels wrong or drop the tail on the last message.
Colours that are close but not exact
iMessage blue, WhatsApp green and the Instagram gradient have precise values. A bubble that is “nearly” the right colour was likely re-drawn.
Read receipts that contradict each other
Two blue ticks on WhatsApp while the status says “last seen yesterday”, or a “Read” on iMessage mixed with SMS green bubbles that never show read state.
Alignment and avatar mistakes
The wrong person on the left/right, an avatar that appears on outgoing messages, or a group name where a 1:1 chat should be.
Compression and resolution mismatch
Crisp UI chrome around soft, re-compressed text — or a screenshot whose pixel dimensions do not match any real device — suggests editing.
Cropped edges
A screenshot cropped to hide the status bar or the input field is hiding the parts that are hardest to fake. Ask for the full, uncropped image.
No matching notification or thread
The most reliable check is outside the image: does the supposed sender have the message in their app? Can they screen-record scrolling the live thread?
It is too convenient
A screenshot that appears exactly when someone needs proof, from a conversation nobody else saw, deserves more scrutiny, not less.
Try it: quick authenticity self-check
Tick each check the screenshot passes. This is a prompt for judgement, not a verdict — context still rules.
0 / 6 checks passed
What to do if a fake targets you
Documenting beats denying. Save the fake and where it appeared, then gather your own evidence: open the real thread, screen-record yourself scrolling it, and export any platform history you can. Report the content to the platform it’s on. If it’s defamatory or used to defraud, it can be a legal matter — and you canreport misuse of our tools so we can act on our side.
Why we publish this
We build realistic screenshot generators for parody, education, design and fiction — and we watermark every free export precisely so honest use stays honest. Teaching people to spot fakes is the other half of that responsibility. Media literacy is the real defence against fabricated screenshots, and it starts with knowing where to look.
Frequently asked questions
What is the fastest way to check a screenshot?
Look at the status bar first (battery, signal, time, the word “Carrier”), then the timestamp logic. Those two catch most fakes in seconds. The definitive check is asking to see the live thread in the app.
Can you always tell a fake screenshot?
No. A carefully made fake can pass a visual inspection, which is exactly why the reliable checks are contextual — the live thread, the sender’s copy, platform logs — not just the pixels. Treat a lone screenshot as a claim, not proof.
Do fake screenshots contain metadata I can check?
Rarely usefully. Screenshots are freshly rendered images, so they carry no message metadata, and re-saving strips EXIF. Metadata absence is normal and not itself proof of anything.
Someone is using a fake screenshot of me — what do I do?
Document it (save the image and where it appeared), gather your own evidence (your real thread, screen recordings), and report it to the platform. If it is defamatory or used for fraud, it may be a legal matter. You can also report misuse of our tools.