For teachers & students
Fake chat generators for teachers & digital literacy
Make realistic message examples for media-literacy, digital-citizenship and scam-awareness lessons — and teach students how fakes are spotted.
The most effective way to teach students that a screenshot is not proof is to show them how convincing a fake can be — and then how to spot it. Mock Screenshots lets you build realistic fictional message examples for class, from a phishing-style DM to a rumour thread. Pair it with our guide to spotting fakes for a complete lesson on why screenshots need scrutiny.
Why teachers & students use it
Concrete, relatable examples
Students engage more with a realistic WhatsApp or Instagram example than with an abstract description.
Teach the tells
Show a fake, then walk through the status-bar, timestamp and tick giveaways using our spot-a-fake guide.
Safe and clearly fictional
Frame classroom material as fictional examples and never use real student or staff identities.
No account required
Normal classroom editing and downloads stay in the browser. Do not put student data in shared-state links or render-API requests.
A simple workflow
- Build a realistic example — a rumour, a scam DM, a pressured group chat.
- Show it to the class and ask: real or fake?
- Walk through the tells with the "how to spot a fake screenshot" guide.
- Have students try to build one, then critique each other's for realism and red flags.
Turning a fake into a media-literacy lesson
The lesson that sticks is not "screenshots can be faked" in the abstract, it is watching a convincing fake get built and then learning to take it apart. Make two or three realistic examples before class, show them without comment and ask the room to vote real or fake, then walk through the tells together using the spot-a-fake guide: the status-bar icons, the timestamp logic, the kerning and the tick states. Finish by having students build their own example and critique each other's for red flags. That show-then-spot arc turns a passive warning into an active skill, and it maps cleanly onto digital-citizenship and misinformation units already in most curricula.
Keeping classroom examples safe
Everything you make for a lesson should stay unmistakably a fictional example. Normal editing and downloads stay in the browser. Shared-state links and render-API requests can enter browser history, logs, and caches, so never put student data there. Avoid using the names or likenesses of real students or staff, and frame scam-awareness examples around the technique rather than any real person. Used this way the tool supports the exact skill you are teaching — healthy scepticism about screenshots — without ever modelling the deceptive behaviour you are warning against.
Recommended generators
Frequently asked questions
Is this appropriate for a classroom?
Yes, when framed as media literacy and clearly identified as fictional. Our ethics policy prohibits deceptive use. Pair it with the spot-a-fake guide for a full lesson.
Do students need accounts?
No sign-up is required. Normal editing and downloads stay in the browser; shared-state links and render-API requests may be logged or cached and should not contain student data.
Every export is fictional mock output — for creative and educational use, not deception. See our Acceptable Use policy.