How to log in to a purchased Telegram account

How to log in with TDATA on a computer

TDATA lets a compatible version of Telegram Desktop open a saved authorization. You don't upload the folder through the app: Telegram reads it at startup. Use a separate portable copy for the purchased account so you don't replace your personal Telegram data.

On Windows, follow these steps:

1. Download the client. Open the official Telegram Desktop website, choose Portable version, and extract it into a new, separate folder.
2. Launch it once. Open Telegram.exe from that folder. Leave the welcome screen without entering a number or signing in to your personal account.
3. Quit Telegram completely. If closing the window leaves it running in the system tray, quit it from the tray icon's menu.
4. Remove the newly created folder. If tdata has appeared next to Telegram.exe, delete it. This must only be the folder created by the new copy you haven't signed in to. Never delete your personal Telegram folder.
5. Copy the order files. Extract the order archive and put the supplied tdata folder in the deleted folder's place, next to Telegram.exe. Copy the whole folder; don't merge the two folders' contents.
6. Launch the same client again. Open that same Telegram.exe. If it can read the files and the saved authorization is valid, the purchased account will open.
7. Check the profile. Compare its phone number with the order and wait for a connection to Telegram. Cached chats alone don't confirm working access.

After copying the files, the new client's folder should look like this: Telegram.exe and tdata are at the same level.

If you have account-01/tdata/tdata/, move the inner folder up to the correct level.

Don't rename files inside the supplied TDATA, and keep the original order archive.

If the login screen appears again, check that you quit the app before replacing the folder, copied all its contents, and launched the correct Telegram.exe. An old shortcut or pinned icon may open a different copy. If your personal account opens, don't log out of it: check the launch path and client storage first.

If Desktop asks for a local passcode, it protects the saved data and isn't the cloud 2FA password. The password in 2fa.txt won't necessarily work. Check whether the order includes a separate local passcode; don't delete protection files to bypass the prompt.

If the profile opens but stays on “Connecting”, check the network and proxy separately. That message alone doesn't prove the authorization was revoked. Copying TDATA again won't restore a terminated session. Save the error text and client version for support, without posting the files publicly.

These steps are for Windows Portable. Data locations differ on macOS and Linux; don't assume their files belong beside Telegram.exe.

How to log in with Session + JSON

In a compatible application, choose the option to import an existing Session, select its file and matching JSON, then connect. Session holds the saved authorization; JSON describes client settings. Check both parts: the app may read Session but ignore JSON and apply its own settings.

Start with one pair. Some applications match files by their base name: account-01.session and account-01.json. Others let you select them separately. Keep the original pair together and don't mix accounts. After connecting, compare the actual profile and phone number with the order. “Account added” may only mean a local record was created.

Which JSON settings are actually used

app_id and app_hash identify the Telegram application; other schemas use api_id and api_hash. They don't select the account: Session's authorization determines the profile. If the wrong account opens, changing its number or these parameters in JSON won't switch it. Check which Session file the application loaded and which working folder it used.

device, sdk and app_version commonly describe the device model, OS version and application version. An importer may use different field names or substitute its own values. Windows in sdk doesn't bind the account to one computer; the application itself determines OS requirements. Check whether it reads the JSON settings and what it actually applied, rather than editing fields at random.

lang_code describes the client's language, not the account's registration country or IP address. A proxy listed in JSON also has to be supported and applied by the application. Its presence in the file doesn't prove traffic uses it; check the effective connection settings.

Why the files may fail to import

There is no single JSON sidecar format that every application accepts. A missing-field error calls for checking the importer's required keys and schema. Don't automatically replace app_id with api_id, or rewrite the file to resemble another example.

If the error names a Session table or column, check the supported file type and version. Two files ending in .session can have different internal structures. Adding columns manually or renaming the file isn't a proper conversion.

When import succeeds but the account won't connect

Read the exact error first. Timeouts and proxy errors need network checks. AUTH_KEY_UNREGISTERED and SESSION_REVOKED concern authorization; editing JSON won't restore revoked access. Stop the previous application before moving the files, and don't run the same supplied Session in two independent clients at once.

Session and JSON may contain access credentials. Share the error text and application name with support, not the files with a public bot or unknown converter. Our TDATA and Session + JSON guide explains the format differences and compatibility.

How to log in to the purchased account on a phone

The mobile Telegram app doesn't import TDATA or Session + JSON through “Add Account.” A new connection needs the order's phone number and login confirmation. Some products let you get the code directly from your Datamoll order. If your account includes this feature:

1. Open the order. Press “Get sign-in code” and select the account if the order has several numbers.
2. Prepare retrieval. In the window that opens, press “Get the code” and wait for “Request is ready”. This isn't the code yet: the service is ready to receive it.
3. Start the Telegram login. Choose “Add Account” and enter the order's number. If the country code is selected separately, enter the remaining digits without repeating the prefix.
4. Retrieve the confirmation. When Telegram shows the code entry screen, return to the order and press “Telegram is asking for the code — show it”. Enter that code in Telegram for this number and current login attempt.
5. Finish signing in. If Telegram asks for the cloud 2FA password, use the supplied password or the available retrieval feature. Then compare the opened profile's number with the order.

Prepare retrieval before entering the number in Telegram; collect the code after Telegram requests it.

Keep the code window open until you've used it: another retrieval depends on the service terms. If those terms prohibit parallel connections, don't open TDATA, Session or another login during this process.

If the order supplies a personal code link, start the Telegram login first, then open that account's link and follow its instructions. Don't automatically apply the Datamoll window's preparation sequence to the link.

The two-step verification password is separate from the one-time code, the app's PIN and Desktop's local passcode. If supplied, 2fa.txt contains a password, not another code. “2FA enabled” doesn't itself provide that password. Resetting an unknown password isn't a routine login step. See Telegram's authentication documentation for this stage.

How to log in to Telegram with a QR code

Telegram Web and some Desktop versions offer QR login. The new client displays a QR code, and an account that's already logged in approves the connection. The image alone isn't enough: the approval has to come from the account you want to open.

A purchased account may include a separate QR-approval service. If this method is explicitly supported for your product:

1. Open QR login in your own new Telegram client.
2. Send the current QR through the approval service provided for that account.
3. Return to the client and finish signing in. Enter the cloud password if Telegram asks for 2FA.
4. Check the phone number of the account that opens.

If the image refreshes, send the new QR. A saved image can't be reused for future logins or a whole batch of accounts. The Telegram QR-login documentation explains approval and expiry.

Do not close the Telegram window where you got the QR code until login is complete. Once the code is approved, wait for the account to open in that same window and check that the phone number in the profile matches your order.

Signing in with a phone number and personal link in an application

Moving each code by hand becomes awkward when you're connecting several accounts. Some applications handle that step for you: add the phone number and its personal code-retrieval link, and the application signs in.

It requests a Telegram code, retrieves it through the link and enters it in its client. It also uses the supplied 2FA password when needed. After login, it saves a new session for later use. This connects a new client rather than importing the old session files.

Before connecting a batch, make sure the application can retrieve a code through your particular link. Downloading an archive from that page and importing Session files are different features; neither replaces automated phone-number login.

How to automate code retrieval with Datamoll API

If the application supports Datamoll API integration, you don't need to copy codes from the order manually. It prepares code retrieval for the account, starts the Telegram login, then retrieves the code and 2FA password if required. The Datamoll API documentation describes the integration; the application itself must support this process.

The code belongs to the current login attempt. The product's terms also determine the retrieval window and number of uses. Manual retrieval, the personal link and API share one service, not a separate allowance each. If you plan to sign in through the application, don't use up code retrieval manually beforehand.

How to connect a batch of accounts

Try your chosen method on a small part of the batch first. Check the phone numbers and connection to Telegram, then restart the application normally. Once you've confirmed that access is retained, use batch connection if the application supports it.

Keep each account's files, link and password together. Don't mix packages or run copies of one session in different applications as independent connections. Converting the files doesn't create another device either; it changes the format of the same data.

Configure proxies and network settings in the client you're using. An account's registration country doesn't mean a proxy is already included or connected. For organizing connected profiles and assigning them to tasks, see our guide to managing multiple Telegram accounts.

What to check if you cannot log in to Telegram

Start with the screen where login stopped. It's easier to identify the cause than to try every method again.

Before buying, decide where you'll use the account: Telegram Desktop, your phone or a compatible application. In the Telegram account catalog, check the data supplied with the product and whether its login method works with your application. If you plan to use a code or QR, make sure that specific feature is included in the product's terms.