Telegram Desktop
Telegram Desktop stores cached chat messages, media, and session metadata in tdata/ — multimedia cache often survives server-side deletion.
Where to find it
Default filesystem paths and registry locations. Collect these with your preferred live-response or disk-image tooling.
- $%APPDATA%\Telegram Desktop\tdata\
- $~/Library/Application Support/Telegram Desktop/tdata/ (macOS)
Forensic significance
Common scenarios in which this artifact becomes decisive evidence.
- Recovering multimedia after sender used self-destruct timer
- Group chat membership history
- Session login locations (IP in session data)
Tools that parse it
unJaena AI and other DFIR tools commonly used to extract evidence from this artifact.
Related artifacts
KakaoTalk PC
The Windows desktop client of KakaoTalk stores chat history, contacts, and profile metadata in the user's AppData directory, each per account profile.
LINE PC
LINE Desktop (Japan's dominant messenger) stores cached chat history, stickers, and call logs in user AppData — critical for cases involving Japanese-language evidence.
iOS SMS / iMessage (sms.db)
iOS stores SMS, MMS, and iMessage conversations in a single SQLite database including timestamps, read receipts, attachments, and reply threading.
iOS Call History
CallHistory.storedata logs every cellular, VoIP, FaceTime, and third-party call (WhatsApp, KakaoTalk) with duration, direction, and contact information.
Stop parsing artifacts by hand
unJaena AI ingests disk images, live-response output, and mobile backups, then automatically correlates every artifact on this page — and 200+ more — into an investigator-ready timeline.
Try unJaena AI →