# tdata vs session file in Telegram: what they are, how to upload > How a tdata folder differs from a .session file with .json, which formats TeleTraff accepts, how to upload accounts and what to do about import errors. TeleTraff editorial team · October 21, 2026 · 7 min read - tdata is the Telegram Desktop folder, .session with .json is the session file set. They are two packages of the same account login. - TeleTraff accepts tdata folders, .session and .json pairs, and ZIP and RAR archives. Pyrogram sessions are not accepted. - After the upload the panel checks the accounts through Telegram. Those Telegram does not accept still land in the manager, with the reason for each. tdata is the folder where Telegram Desktop keeps the account login. A session is a session file created by Telethon-based programs; it comes with a .json describing the account. TeleTraff's [Account Manager](/en/modules/account-manager) accepts both: the «Import accounts» window reads folders, file pairs and archives. Which one to use depends on what your seller or your tool gave you. ## What is tdata and how is it different from a session? tdata is the working folder of the desktop Telegram app. It holds the keys the app uses to sign in without a login code. If you signed in to an account in Telegram Desktop, the folder appears on that computer. The panel needs the whole account folder, not single files from it. A session is a file with the .session extension. It is the same account login, in a format that scripts and services read. Next to it sits a .json with the account description. That is why a session is always taken as a pair: .session and .json together. In our experience both formats give the same login; only the packaging differs. - Bought a batch of accounts for a gambling offer — you usually get an archive of tdata folders or of .session and .json pairs. - Moved an account out of an old tool — usually a .session and .json pair. - Signed in to an account in Telegram Desktop yourself — you have a tdata folder. - Need the files back — the bulk action «Export sessions» in the manager returns .session with .json, or tdata. ## Which formats does TeleTraff accept? - The account folder with tdata — the «Telegram Desktop» tile. - The .session and .json files together — the «Session + JSON» tile. The names may differ by an export suffix: a file with a suffix at the end of its name and a file without it are read as one pair. - A ZIP or RAR archive — the «ZIP or RAR archive» button. Many accounts can sit inside; the panel also unpacks nested ZIPs. - Drag and drop: you can simply drop a folder or files into the window. A Pyrogram session is not accepted: the panel says «This is a Pyrogram session» and suggests converting it to Telethon or uploading tdata. Files of the Telegram program itself that landed in the folder are dropped: the panel only needs the account login. ## How do I upload tdata or a session to the panel? 1. **Open the import.** In the [Account Manager](/en/modules/account-manager) click «Import accounts». Everything happens in one window: files, accounts, proxies and a footer with the buttons. 2. **Choose the source.** Click «Telegram Desktop» for a tdata folder, «Session + JSON» for file pairs, or «ZIP or RAR archive» for an archive. You can also drop files into the window. 3. **Click «Read the files».** The panel parses the upload and lists the accounts. Each gets a verdict: «Ready» or «Skipped», with a reason for the skipped ones. The «Files read» line confirms the parsing is done. 4. **Assign proxies.** In the «Proxies» block pick a mode: «Automatically» from the pool, «Pick proxies» by hand, or «Add new». If an account has its own proxy in the archive, it is marked «Own proxy from the archive»; the rest get proxies by the chosen scheme. Proxies are checked through Telegram before the import, and the import goes only through working ones. The [Proxy Center](/en/modules/proxy-center) is the handy place to store and change proxies. 5. **Add two-factor passwords if you know them.** The «More» block is collapsed. In it you can save a password per session, choose a pool for the new accounts and turn on profile generation. The field may stay empty: it shows «Not provided». 6. **Click «Import».** The footer button shows how many accounts go into the import. If the proxy check is still running, the import waits for it on its own. > **No files yet?** > > Where to buy accounts and proxies and how to pay is covered in Where to get accounts and proxies. More on uploading folders and archives is on the tdata upload page. ![Account manager with the import button](https://teletraff.com/modules/shots/en/account-manager-table.webp) *The account manager: the «Import accounts» button at the top left, labelled with the .session, tdata and archive formats, next to adding by phone number, buying and proxies, with the account table below. Demonstration data.* ## What happens after the import? Right after the import the panel checks each account through Telegram and shows a summary. It has an «Added to the manager» block and a «Failed the Telegram check» block. The «Check on import» label shows what Telegram answered. - «Session opened» and «No restrictions» — the account is ready to work. - «The session works; Telegram restricted its actions» — the login works but a spam block is set: «Temporary spam block», «Permanent spam block» or «Geo spam block». Such accounts count as imported. What to do with them is in the guide on spam blocks. - «Frozen» — Telegram froze the account. - «Telegram did not accept the session» — the login failed. The account is still added to the manager, but cannot be used; the reason is shown next to it. - «Not checked» — you can run the check again with the «Check again» button. ![The «Check summary» window after an account check](https://teletraff.com/modules/shots/en/account-check-results.webp) *«Check summary»: each account has a status, «Lifts» and «What Telegram said». The frame shows a temporary spam block, a permanent spam block, a geo spam block and working accounts; there are no frozen accounts in this example. Demonstration data.* ## What import errors are there and what to do about them? - «The tdata root was not found» or «The selected folder has no tdata»: the wrong folder was chosen. Upload the whole account folder with tdata inside. - «Required files are missing from tdata»: the folder was copied incompletely. Copy it again. - «There is no .json beside this session» and «Sessions with no .json»: the .session file lacks its pair. Add the .json to the same upload. - «This is a Pyrogram session»: the format does not fit. Convert the session to Telethon or use tdata. - «The archive is empty», «The archive is cut off» or «This is not an archive»: the file did not finish downloading, or it is named .zip but holds something else. Download the original archive again. - «One of the files is too large to import»: upload only the tdata folder, not the whole Telegram Desktop folder. - No proxy passed the check: the import does not start until the list has working ones. Replace the proxies and check again. ## FAQ **Do I need a two-factor password to upload an account?** No, the import does not require it. If you know it, you can save it in the «More» block per session. If the field is empty, the account shows «Not provided». **Can I upload many accounts in one archive?** Yes. Put tdata folders or .session and .json pairs of several accounts into one ZIP or RAR. The panel finds the accounts inside and gives each a verdict. It also unpacks nested ZIPs. **What if a session has no .json file?** Add it to the same upload. The panel warns «Sessions with no .json», and the import refuses such sessions. If there is no .json at all, ask the seller or your tool for the tdata folder. **Is a proxy bound to the account during the import?** Yes. In the «Proxies» block the panel assigns proxies automatically from the pool, from ones you picked, or from new ones you add. Before the import the proxies are checked through Telegram, and the import goes only through working ones. Own proxies from the archive stay with their accounts. **The account is in the manager but does not work. Why?** The panel also adds accounts Telegram did not accept, with a reason. Open the upload summary: it shows «Telegram did not accept the session», a spam block or «Frozen». Spam blocks have their own guide; for the rest you need a different account. **Can I get tdata or .session back out of the panel?** Yes. Select the accounts in the manager and choose the bulk action «Export sessions»: the panel returns .session with .json, or tdata.