Telegram Desktop data is kept in a “tdata” folder inside your user profile, with paths that differ on Windows, macOS, and Linux.
New to Telegram on a computer and trying to find where files, cache, and session info live? You’re in the right place. This guide shows the exact folders used by the desktop app across operating systems, what lives inside them, how portable builds behave, and safe ways to clean up space without losing chats.
Quick Orientation: What Gets Stored Locally
Telegram syncs cloud chats across devices. The desktop app keeps a small local footprint: session keys, settings, and cached media so scrolling is snappy. Your main conversation history sits in the cloud, not in a local database on the desktop app. That’s why clearing cache won’t erase cloud chats—you can always fetch media again when needed.
Telegram Desktop Data Location On Each OS
Below are the default folders the app uses on the three major platforms. The folder that matters most is tdata—it holds session files and other client artifacts. If you installed a portable build, the entire working set (including tdata) lives next to the executable.
Windows (Regular Installer)
Path to open in File Explorer:
%APPDATA%\Telegram Desktop\tdataThat expands to something like C:\Users\<You>\AppData\Roaming\Telegram Desktop\tdata. Inside, you’ll see encrypted session files, settings, and cache directories. The regular installer keeps program files and user-specific data under your profile so updates and logins remain per-user.
Windows (Portable Build)
When you run the portable executable from a folder (for instance on a USB stick), the working directory becomes the data root. You’ll find tdata sitting beside Telegram.exe. Copying that folder preserves the session for that portable instance.
macOS (Standalone Download)
For the non–App Store build, the desktop client stores its data under your user Library:
~/Library/Application Support/Telegram Desktop/tdataUse Finder’s Go menu > Go to Folder and paste the path above. You’ll recognize the same structure: tdata with subfolders for cache and settings.
macOS (App Store Build)
Apps from the store run in a sandbox. Telegram’s Mac App Store edition uses a Group Container directory. You’ll often see media cached under a path that looks like:
~/Library/Group Containers/6N38VWS5BX.ru.keepcoder.Telegram/Under that root, look for stable and per-account folders where media cache files are assembled before moving to your chosen Downloads destination.
Linux (Tarball / Repo Builds)
Most conventional installs keep user data here:
~/.local/share/TelegramDesktop/tdataSome older setups used ~/.TelegramDesktop/tdata, and you may still encounter that path on long-lived systems.
Linux (Flatpak)
Flatpak apps write under the sandboxed per-app tree:
~/.var/app/org.telegram.desktop/data/TelegramDesktop/tdataIf you reset or move a Flatpak install, checking that directory is the quickest way to confirm where the client’s cache and session files live.
What Lives Inside “tdata”
tdata contains encrypted session material and client settings that keep you signed in. You may also see subfolders like user_data/cache and user_data/media_cache. Those hold thumbnails, videos, and other media the app has fetched so it can render chats instantly. Messages themselves aren’t stored here as a local archive; the desktop client re-requests content from the cloud when needed.
Downloads Folder vs. Cache
Two places matter for space:
- Cache inside
tdata— safe to purge; the app can fetch again. - Downloads — the folder you selected for “Save to…” files you explicitly downloaded. Those are yours to manage like any other files.
On macOS (App Store build), media may be cached first under the Group Container path above before the complete file lands in your chosen Downloads location. If you download lots of large files, check both areas when reclaiming space.
Open The Folder Fast (Copy-Paste Ready)
Use these quick commands to jump straight to the right directory.
Windows (Run Dialog)
Press Windows+R, paste, and press Enter:
%APPDATA%\Telegram Desktop\tdatamacOS (Terminal)
open ~/Library/Application\ Support/Telegram\ Desktop/tdataFor the App Store build’s cache root:
open ~/Library/Group\ Containers/6N38VWS5BX.ru.keepcoder.TelegramLinux (Terminal)
xdg-open ~/.local/share/TelegramDesktop/tdataFlatpak:
xdg-open ~/.var/app/org.telegram.desktop/data/TelegramDesktop/tdataSafe Cleanup: Free Space Without Losing Chats
The fastest way to reclaim disk space is inside the app. Open Telegram on your computer and head to Settings → Advanced → Manage Local Storage. There you can clear cached media, set size limits, and tell Telegram to auto-remove older cache after a period. Clearing cache removes local copies only; chats remain available from the cloud. If you’ve saved files to the Downloads folder, tidy those manually in your file manager.
Portable Builds And Data Copies
If you use a portable build on Windows, everything (including tdata) sits next to Telegram.exe. Copying that folder carries the active session to another USB or machine. On conventional installs, copying just tdata between different OS packages (like moving from Flatpak to a tarball) may not always work due to sandbox and path differences. When migrating across platforms, sign in normally for the most reliable result.
Why You Can’t “Recover Messages” From The Folder
It’s tempting to browse inside tdata looking for a local message database. Telegram’s desktop client doesn’t keep a full offline archive for cloud chats. Cache and thumbnails exist to accelerate scrolling, but the conversation history is fetched from the service whenever you need it. If you purge cache, you only remove those temporary local files.
Common Variations And Gotchas
- Older Linux paths: Some installs still use
~/.TelegramDesktop/tdata. Newer setups favor~/.local/share/TelegramDesktop/tdata. - Flatpak layout: Expect data under
~/.var/app/org.telegram.desktop/. Removing the Flatpak app alone doesn’t always delete the sandbox’s data folder; check it if you’re truly cleaning house. - macOS sandbox quirks: On the App Store build, large file downloads are assembled inside the Group Container first. If space is tight, clear cache in Telegram and empty Trash after large transfers.
- Portable on Windows: Launching from a custom folder means that folder becomes the working directory. Keep your portable tree on a drive with enough free space.
Reference Table: Default Folders By Platform
The table below condenses the most common locations. If you don’t see these paths, you may be running a portable build or a sandboxed package.
| Platform | Data Folder (tdata Root) | Notes |
|---|---|---|
| Windows | %APPDATA%\Telegram Desktop\tdata | Regular installer; per-user profile. |
| Windows (Portable) | <folder with Telegram.exe>\tdata | All data travels with the app. |
| macOS (Standalone) | ~/Library/Application Support/Telegram Desktop/tdata | Non–App Store build. |
| macOS (App Store) | ~/Library/Group Containers/6N38VWS5BX.ru.keepcoder.Telegram/… | Sandboxed; media cached here. |
| Linux (Tarball/Repo) | ~/.local/share/TelegramDesktop/tdata | Older systems may use ~/.TelegramDesktop/tdata. |
| Linux (Flatpak) | ~/.var/app/org.telegram.desktop/data/TelegramDesktop/tdata | Sandboxed per-app data tree. |
Two Helpful House Rules
- Use the built-in storage manager to clear cache and set limits. It’s quicker and safer than manual deletions in the file system.
- Treat Downloads separately. Anything you saved to your chosen folder is outside the cache. Move, archive, or delete those like any other files.
Trusted Pointers For Extra Clarity
Telegram’s official FAQ confirms that cloud chats live on the service and that you can clear local cache any time without losing conversations. The team’s desktop tips channel also points to the storage manager on desktop and reminds heavy downloaders to check their Telegram folder in Downloads. Both references align with the folder behavior described above.
Wrap-Up
You now know exactly where the desktop client keeps its local bits on Windows, macOS, and Linux, how portable builds differ, and which folders to clean when space runs low. If you’re troubleshooting storage, start in the app’s storage settings, then verify the correct tdata and Downloads paths for your install type.