What Is TData? Telegram's Session Format Explained

If you have ever bought a Telegram account, you were handed a folder or a pair of files rather than a password. That trips people up the first time. This is what those files actually are.

TData in one sentence

TData is the folder Telegram Desktop uses to remember that you are logged in.

When you sign into Telegram Desktop, the app writes an encrypted folder called tdata next to the program. Inside it sits your authorisation key — the token that proves to Telegram's servers that this device is allowed to act as your account. Copy that folder onto another machine, point Telegram Desktop at it, and you are logged in without a phone number or a code.

That is the whole idea. TData is not a password. It is a session that has already been authorised.

What a session file is

A session file does the same job for code rather than for the desktop app. Libraries like Telethon store the authorisation key in a small .session file, which is really a SQLite database holding the key, the data centre it belongs to, and some connection state.

The account is identical. The difference is which program is meant to read the file.

TData is for the Telegram Desktop app. A session file is for automation code. Both hold an already-authorised login for the same account.

Where the JSON comes in

The JSON file is not part of the login at all. It is the account's paperwork — the metadata a seller records so you know what you received:

• the phone number the account was registered with
• the registration date, which is what makes an account "aged"
• the device and app version the session was created under
• the two-factor password, if one is set
• sometimes the proxy the account was last used behind

None of that is required to log in. It matters because it tells you what you are holding, and because reusing the same device fingerprint the session was created with attracts less attention than logging in as a completely different device.

Why we ship Session+JSON+TData together

There are sellers who make you choose a format up front, then charge to convert. That never made sense to us. The three artefacts describe one account, and converting between them after the fact is fiddly and error-prone.

Every account we sell arrives as Session+JSON+TData, in every age tier. Use the TData folder if you are working in Telegram Desktop. Use the session file if you are working in Telethon. Read the JSON either way, so you know the account's registration date and whether a 2FA password is set.

Practical notes before you log in

A few things that save people trouble:

1. Keep one copy untouched. Once a session is used, its state changes. Archive the original folder before you do anything with it.
2. Do not run the same session in two places at once. Telegram sees concurrent sessions from different IPs and treats that as suspicious.
3. Match the proxy to the account. An account registered on a Nigerian number that suddenly appears from a German data-centre IP is a pattern Telegram notices.
4. Check the JSON for a 2FA password before you try to change any security settings.
5. Test one account from a batch first. If something is wrong with the batch, you want to find out on account one, not account two hundred.

Which one do you actually need?

You are using	Read this
Telegram Desktop	the tdata folder
Telethon	the .session file
Telegram mobile	neither — log in with the number and a code
Checking what you bought	the JSON

If you are not sure which applies to your workflow, tell us what you are building and we will point you at the right one before you order.