TDATA vs Session+JSON: Which Telegram Account Format Should You Choose?
You need Telegram accounts for a project. Someone tells you to get TDATA. Someone else says Session+JSON. Both work, but for completely different use cases. Pick the wrong one and you spend hours trying to make a desktop folder work with a Python script that expects a session file.
This guide breaks down the differences so you pick the right format the first time.
Quick comparison table
| Feature | TDATA | Session+JSON |
|---|---|---|
| Best for | Telegram Desktop GUI, manual use | Python scripts, bots, automation |
| Protocol | Local desktop cache | MTProto API (direct protocol) |
| Concurrent sessions | Limited by desktop resources | Unlimited per VPS |
| Setup time | 2 minutes | 30 seconds |
| API access | Desktop only | Full MTProto API |
| Phone needed | No | No |
What is TDATA?
TDATA is the session folder used by Telegram Desktop. It stores encrypted tokens, settings, and cache. You place it next to a portable Telegram.exe and the account opens automatically. No phone number, no SMS. Read the full TDATA guide.
What is Session+JSON?
Session+JSON is a two-file format for API-level automation. The .session file is a SQLite database with authorization keys. The .json file provides app_id, app_hash, and phone number. Telethon and Pyrogram use these files to authenticate. Read the full Session+JSON guide.
When to choose TDATA
- You want to log into Telegram Desktop and use it like a normal account
- You are running accounts with Telegram automation tools that load TDATA folders
- You prefer not to write code
- You need to manage accounts visually
When to choose Session+JSON
- You are writing Python scripts with Telethon or Pyrogram
- You need to run hundreds of concurrent sessions on a single server
- You want full MTProto API access (messages, channels, contacts)
- You integrate accounts into a custom software stack
Can you convert between formats?
Yes. Open-source tools like opentele can convert TDATA folders to Session+JSON files. But buying the right format from the start saves time. On accs.tg, you can order either format directly.
Which format should you pick?
If you use Telegram manually or through desktop-based tools, pick TDATA. If you automate with Python or run accounts at scale on a VPS, pick Session+JSON. Many buyers use both formats for different parts of their setup.
Still not sure? Order a small batch in each format and test with your setup. Most buyers on accs.tg start with one format and add the other once they scale up.
Browse the catalog at accs.tg/services and choose your format. For bulk automation, check the API docs.