TDATA is the local session folder Telegram Desktop creates to store your logged-in account data — encryption keys, session tokens, and cached settings. Copying that folder to another computer can log that machine into the same account without a code. It is the format most Telegram account sellers deliver, and the one buyers must verify carefully.
What TDATA Actually Contains
When you install Telegram Desktop and log in, the app writes a folder named tdata into its working directory. Inside are files with names like key_datas, D877F783D5D3EF8C, and numbered map files. You are not meant to read them; Telegram Desktop reads them at launch to restore your session.
Practically, the folder holds three things:
- Authorization keys — the cryptographic material that proves to Telegram's servers that this device is already logged in.
- Session state — account identity, data-center routing, and update state.
- Local cache and settings — chat metadata, draft state, and UI preferences, depending on version.
Because the authorization keys are inside, a valid TDATA folder is functionally a password. Anyone who loads it into a compatible Telegram Desktop build can operate the account. That is exactly why it is the delivery format in account sales — and exactly why it is dangerous to handle carelessly.
How TDATA Is Used in Telegram Account Sales
Sellers deliver Telegram accounts in a few formats. TDATA is the most common for Desktop-oriented buyers because it is a single folder: drop it in, launch Telegram Desktop, and the account opens without an SMS code or password prompt.
The typical delivery flow looks like this:
- The seller packages the tdata folder (often zipped, sometimes with a password).
- The buyer receives it through the marketplace's delivery channel after payment clears escrow.
- The buyer places the folder in a clean Telegram Desktop installation directory and launches the app.
- The buyer immediately changes the account's two-step password, reviews active sessions, and terminates any sessions they do not recognize.
That fourth step is not optional. A TDATA folder can be copied before delivery, so the buyer's first job is to lock out anyone else who might hold a copy. If you are acquiring accounts at scale — for channel administration, for example — pair the handover with a proper review of what you are buying; our guide to buying Telegram channels covers the ownership and transfer checks that apply alongside the account itself.
On EPICSWP, account and channel transactions run through escrow with a 6% fee, and the platform resolves disputes if the delivered TDATA does not work as described. Escrow does not make a bad folder good, but it does mean you are not sending money to a stranger on trust alone.
TDATA vs. Session + JSON
The other common delivery format is a pair: a .session file (used by Telethon and similar Python libraries) plus a json file holding the API ID, API hash, and phone number. The two formats serve different purposes.
| Attribute | TDATA | Session + JSON |
|---|---|---|
| Works with | Telegram Desktop app | Telethon / Pyrogram scripts |
| Human usable | Yes — open the app and chat | No — needs code to run |
| Contains API credentials | No separate file needed | Yes, in the json |
| Typical buyer | Operators, channel owners, marketers | Developers, automation users |
| Main risk | Copied folder = silent access | Leaked API hash = account abuse |
Choose TDATA if a person will log in and use the account normally. Choose session+json if you are building automation and can run the libraries. Some sellers offer both; ask before paying, because converting between them is not always clean and a seller who claims both should be able to demonstrate each.
The Real Risks of Buying a TDATA Folder
Be specific about what can go wrong, because the failure modes are well known in this market:
- Duplicate copies. The seller may keep a copy and log in later. Changing the two-step password and terminating unknown sessions is your defense, but a seller who acts before you do can still cause damage.
- Version mismatch. TDATA folders are tied to Telegram Desktop builds. A folder from an old version may fail to load on a current install. Ask which version produced it.
- Frozen or restricted accounts. A folder can load perfectly and still belong to an account under spam restrictions or pending deletion. Test functionality, not just login.
- Recovery via phone number. If the seller retains the phone number tied to the account, they may be able to recover it. Confirm number control is transferred or that the number is detached.
- Malware in the package. Zipped deliveries sometimes carry more than tdata. Scan before extracting, and never run bundled executables.
No marketplace, EPICSWP included, can promise an account will never be recovered by a previous holder. What escrow does is give you a defined window to test and dispute. Use that window fully before releasing funds.
How to Verify a TDATA Delivery Safely
Do the check on a clean machine or a fresh virtual machine, not your main workstation.
- Scan the archive, then extract to an isolated folder.
- Install a Telegram Desktop build matching the seller's stated version.
- Place the tdata folder where the app expects it and launch.
- Confirm the account opens, check the profile, and review active sessions.
- Set a new two-step password immediately and terminate every other session.
- Test the functions you actually bought the account for — posting, admin rights, channel access.
Only then release escrow. If any step fails, document it with screenshots and open a dispute rather than negotiating privately.
FAQ
Is TDATA the same as a Telegram password?
No, but it functions like one. The folder contains authorization keys that grant access without a code, so treat it with the same care as a password and never share it after delivery.
Can I use a TDATA folder on mobile?
Not directly. TDATA is specific to Telegram Desktop. On mobile you log in normally, which is why buyers should confirm the phone number situation before purchase.
What should I do if the TDATA folder will not load?
First check the Telegram Desktop version — mismatches are the most common cause. If a matching build still fails, treat it as a failed delivery and raise it through escrow rather than accepting a partial refund off-platform.