Free mini-course: five short steps in your browser
Verify a leaked-looking chat or email screenshot in 5 stepsthe claim and source, a pause, the original and the people involved, clues, and a dated record
TimeBinder adds a layer of protection against AI and human fraud and disputes. A five-step routine for a “leaked” chat or email screenshot that may be edited, cropped, generated or missing context. Progress stays in this browser.
No checker on this page can reliably tell a genuine screenshot from an edited or generated one. A TimeBind does not show that a message was really sent or that a screenshot is unedited. The steps are a routine, not a verdict on any one screenshot.
Start the five steps
Each step is short and ends with one or two checks. Your progress is saved in this browser only. Nothing you choose is sent to TimeBinder. The course uses no real person’s messages or likeness, only own-made diagrams.
Your progress is saved in this browser only. Choices stay on this device and are not sent to TimeBinder or tied to your name.
Step 1 of 5. 0 of 5 complete.
Step 1. Name the claim, the screenshot and the source
A screenshot of a chat or email arrives with a claim attached: this person said this, to that person, on that day. Before you react to the wording, write the claim in one line (who is said to have written it, to whom, when, and what you are meant to conclude), and note the source: who passed the screenshot to you, and who posted it first that you can find. A screenshot is a picture of a message, not the message. It can be a faithful picture, a cropped one, an edited one or one made from scratch. Keep what the screenshot shows, what it is said to prove and where it came from apart.
Check 1. Match each part to what it means
Tap a part, then tap the meaning that fits it best.
Check 2. A “leaked” chat screenshot is spreading fast
What is the best first move?
Step 2. Pause: a screenshot of a message is not proof
Text can be typed into a chat or email template, changed on a web page before it is captured, or drawn as an image, and generators of fake message screenshots are easy to find. AI tools can also render convincing chat screens. Equally, a real screenshot can be cropped, low quality or oddly formatted. “Leaked”, “they deleted it” and “you will not believe what they said” are pressure, not evidence. If the message would be explosive, that is a reason to slow down, because that is the kind of message people have a motive to fabricate. Do not share it as fact yet, and move to Step 3.
Check 1. Which statement is the honest one?
Check 2. The screenshot has a small typo and uneven spacing
What does that tell you?
Step 3. Go to the original message and the people involved
The strongest check is the original. If you are one of the people in the conversation, open the thread in the app itself and compare, and for an email open the original message rather than a picture of it. If you are not, ask the people named, directly, by a channel you already know and trust: type the address or open the existing contact yourself, and do not reply to the account or number shown in the screenshot or in the post that carried it. Then trace who shared the screenshot first and whether anyone with direct knowledge has confirmed or denied it. If you cannot get to the original, say so and treat the screenshot as unconfirmed. A denial or a confirmation from someone with an interest is still only one input. If real people are named, think about the harm of passing it on.
Check 1. Which of these are sound verification moves?
Tick all that apply.
Check 2. The person named says they never wrote it, and nobody can show the original
What does that suggest?
Step 4. Clues and context: names, addresses, times and layout
With the original out of reach, look for clues, and treat them as clues. For an email: does the display name match the address, and is the domain an exact match or a look-alike? Is the reply address different from the sender? Where a link is shown, does the text match where it points? For a chat: do the times, dates, time zone and date format fit the app and the place? Do names, spelling and message order fit the conversation as described, and is the part that matters conveniently cropped? Full email headers can help you read the route a message took, but headers can also be forged, and a pass on sender checks only concerns the sending domain, not whether the content is true. Online “fake screenshot detectors” are not a verdict in either direction, and this site cannot tell you reliably whether a screenshot was edited or generated.
Check 1. The email headers show the sender domain passed its checks
Check 2. What carries the most weight about a chat or email screenshot?
Step 5. Decide, label, and keep a dated record
Honest outcomes include “confirmed by the people involved or the original”, “could not be confirmed, so I did not share it as fact”, and “this looks fabricated or misleading, reported”. If you share it at all, say plainly what is and is not confirmed, and use the platform’s report tools for content that looks deceptive or impersonates someone. If a message is yours and may matter later (a dispute, a complaint, a workplace or contract matter), keep the original in its app, export it where the app allows (for an email, save the original message with its headers), and keep your notes of when and where you saw it. A TimeBind records that an exact file, such as that export or a screenshot, existed no later than a recorded time, and that a later copy still matches its SHA-256 fingerprint, anchored to Bitcoin. It does not show that a message was really sent, who wrote it, or that a screenshot is unedited or not AI-generated. First Pooled TimeBind is free, then from US$5. An ASAP TimeBind is US$15.
Check 1. What can a TimeBind show about a screenshot or export file?
Check 2. You could not confirm the screenshot. What now?
You have finished all five steps
Progress stays in this browser. You can revisit any step above. If a message is yours and may matter later, keep the original and date the exact file.
How do you verify a leaked-looking chat or email screenshot? The short answer
Work through five steps: write down the claim (who is said to have written what, to whom, when) and who passed the screenshot to you; pause, because a screenshot of a message is easy to fabricate and “leaked” framing is pressure, not evidence; go to the original (the thread or email itself) and ask the people named directly through a channel you already trust, not the contact shown in the screenshot; weigh clues such as sender name versus address, look-alike domains, times, dates and cropping as clues only; then decide honestly, say what is unconfirmed, and keep your notes. If a message is yours and may matter later, keep the original and an export.
None of this tells you for certain whether a screenshot was edited or generated, and an online detector score is a clue at most. A TimeBind of an exact file can show that it existed no later than a recorded time and still matches. It does not show that a message was really sent, who wrote it, or that a screenshot is unedited.
Why this course, in November 2026
Search suggestions checked on 13 November 2026 return full lists for “fake email screenshot” (including “fake email screenshot maker”, “fake email screenshot template” and “fake email conversation screenshot”), for “fake text message generator” (including iPhone, WhatsApp, iMessage and group-chat variants) and for “how to tell if a text message screenshot is fake”. Suggestion lists show what people type, not how many type it, and we have not measured volumes beyond that. They do tell us that making and checking message screenshots is something people search for. None of this says that a screenshot can be settled by looking at it.
This is the seventh course in the series. The first, Spot AI fakes in 5 short lessons, is a general introduction. The second, Verify a viral video in 5 steps, is a workflow for any single clip. The third, Check a suspicious voice message in 5 steps, covers voice messages and calls. The fourth, Verify a screenshot or fake document in 5 steps, is the general screenshot and document course. The fifth, Verify an AI-generated photo of an event in 5 steps, covers event photos, and the sixth, Verify a viral news clip in 5 steps, covers clips dressed as news. This one is narrower than the fourth: a chat or email screenshot said to be leaked, where the key move is getting to the original message and the people involved. An eighth course, Verify a fake product review or testimonial in 5 steps, covers product reviews and testimonials. A ninth course, Verify an AI-generated receipt or invoice in 5 steps, covers AI-generated receipts and invoices, and a tenth, Check a suspicious profile photo or dating profile in 5 steps, covers suspicious profile photos and dating profiles. An eleventh course, Verify an AI-edited rental or property listing photo in 5 steps, covers rental and property listing photos, and a twelfth, Check a suspicious celebrity or expert video ad in 5 steps, covers celebrity and expert video ads. A thirteenth course, Check a photo, video or audio file offered as evidence in 5 steps, covers photo, video or audio files offered as evidence, and a fourteenth, Check a suspicious video call or remote job interview in 5 steps, covers suspicious video calls and remote job interviews. A fifteenth, Check a suspicious website or login page in 5 steps, covers suspicious websites and login pages, and a sixteenth, Check a map or satellite image that may be AI-made or edited in 5 steps, covers maps and satellite images that may be AI-made or edited. All sixteen sit under the public guide to protecting yourself from AI forgeries.
What each step can show, and what it cannot
The honest job of this routine is to slow a snap judgement and leave you with notes you can show. See also synthetic media and existed no later than in the glossary.
| Step | What it can show | What it cannot show |
|---|---|---|
| 1. Claim and source | What the screenshot is said to prove, who is said to have written it, and who passed it to you or posted it first. | That the message is genuine. |
| 2. Pause | Whether urgency or “leaked” framing is part of the pattern. | Whether a screenshot was edited or generated. Polish proves nothing, and neither does roughness. |
| 3. Original and people involved | Whether the original thread or email matches, and whether the people named, or anyone with direct knowledge, confirm or deny it. | That a screenshot is fake because someone denies it, or real because someone confirms it. Each is one input. |
| 4. Clues and context | What sender name and address, domain spelling, link destinations, times, dates and cropping suggest. Metadata can be edited or lost. | Truth or authorship. A passed sender check, missing details or a detector score settles nothing. |
| 5. Decide and keep | What you checked and found, and that an exact saved file existed no later than a recorded time, with a later copy still matching its SHA-256 fingerprint. | That a message was really sent, who wrote it, or that a screenshot is unedited or not AI-generated. |
If a message is yours and may matter later
If a conversation or email could become part of a dispute, a dated record of the exact files you keep helps:
- Keep the original in its app and export it where the app allows. For an email, save the original message with its headers, not only a screenshot. Add notes on when and where you saw it.
- Make a TimeBind of the export or screenshot file. The fingerprint is made in your browser and the file stays on your device. You can later download a Proof of Time Certificate.
- Store the file, the certificate and your notes together. Use the file date and metadata inspector or the file-changed answer to compare a copy later.
First Pooled TimeBind free, no card, then from US$5. An ASAP TimeBind is US$15. A TimeBind does not show that a message was really sent or that a screenshot is unedited.
First Pooled TimeBind free, no card, then from US$5. An ASAP TimeBind is US$15.
What a TimeBind shows, and what it does not. It shows that an exact file existed no later than a recorded time and that a copy shown later still matches its fingerprint. It does not show who made the file, who owns it, that its contents are true, or whether AI was used to make or edit it. This is general information, not legal advice.
Verify a chat or email screenshot: FAQ
Can this course tell me whether a chat or email screenshot is real?
No. No checker on this page, and no tool on this site, can reliably tell a genuine screenshot from an edited or generated one. The steps help you check the claim, go to the original message and the people involved, trace who shared it first and weigh clues. “Could not confirm, so I did not share it as fact” is a valid result.
Can I spot a fake message screenshot by looking at the bubbles, fonts or spacing?
Not reliably. Text can be typed into a template, changed on a web page before capture or generated, and real screenshots can be cropped and messy. Mismatched times, look-alike domains or an oddly cropped line are clues worth noting, not proof. Verify with something other than how it looks.
Do email headers prove an email screenshot is genuine?
No. Headers can help you read the route a message took, but they can also be forged, and a pass on sender checks only concerns the sending domain, not whether the content is true or whether a picture of it was edited. You cannot read headers from a plain screenshot anyway; you need the original message.
Does a TimeBind show that a message was really sent or a screenshot is unedited?
No. A TimeBind shows that an exact file, such as a screenshot or an exported message, existed no later than a recorded time and that a later copy still matches its fingerprint. It does not show who wrote a message, that it was really sent, or that a screenshot is unedited or not AI-generated.
Should I share a screenshot I cannot confirm?
Better not as fact. If you do mention it, say plainly what is and is not confirmed, and use the platform’s report tools for content that looks deceptive. Where real people are named, think about the harm of passing it on.
Where is my progress saved?
In this browser only, using localStorage. Choices are not sent to TimeBinder and are not tied to your name. Clearing site data, or using another browser, starts the steps again.
Is the course free?
Yes. The five steps and the checks run in your browser at no charge. If you later make a TimeBind, the first Pooled TimeBind is free, then from US$5. An ASAP TimeBind is US$15.
Related guides and tools
- Verify a screenshot or fake document in 5 stepsThe fourth mini-course: screenshots and documents
- Spot AI fakes in 5 short lessonsThe first mini-course: labels, reverse image search, voice scams and more
- Verify a viral video in 5 stepsThe second mini-course: a workflow for a single clip
- Check a suspicious voice message in 5 stepsThe third mini-course: voice messages and calls
- Verify a viral news clip in 5 stepsThe sixth mini-course: clips dressed as news
- Can photo metadata be faked?What file details can and cannot show
- Real or AI? quizPractise on own-made and public-domain images
- File date and metadata inspectorSee what a file’s own details say
Date the exact files you keep
Add a layer of protection against AI and human fraud and disputes: a dated, checkable record of the exact file, kept while you still have it.
- Open the app and sign in with email or Google.
- Add your files. They stay on your computer.
- Seal them and download your Proof of Time certificates.
First Pooled TimeBind free, no card, then from US$5. See pricing.