How Does Telegram Transfer Chats and Media to a New Phone?

Telegram Data Transfer in 2026: The Account Is the Transfer Unit

Moving Telegram chats and media to a new phone is less a file-copy exercise than an account sign-in. Telegram is cloud-first: your chats, groups, channels, Saved Messages, and most account-level settings live with your phone number, not with the handset. When you install Telegram on a new phone and log in with the same number, the cloud side of the account reappears; media is pulled back on demand rather than pushed in one large bundle. That distinction explains most of the confusion people encounter after an upgrade, a carrier switch, or a lost device.

For the latest version as of this writing, the practical rule is simple: if the new phone logs into the same Telegram account, the cloud chats follow. If it logs into a different number, it is a different account, and no amount of local copying will merge the two. The rest of this guide works through the comparison of migration approaches, a decision tree, platform-specific steps, media behavior, browser-like boundaries around Secret Chats, and reproducible troubleshooting. The aim is to give beginners a path they can follow and advanced users the reasoning to know when a path is inappropriate.

Three layers matter throughout. The first is the account cloud, which holds ordinary chats and media within Telegram's service limits. The second is the local cache, a device-side copy that makes reopening chats faster and can be cleared without deleting the cloud original. The third is device-bound material, most notably Secret Chats, which are end-to-end encrypted and tied to the devices that created them. Migration advice that ignores the third layer tends to overpromise; advice that ignores the second tends to produce unnecessary data charges. Keeping these layers separate is what makes the rest of the guide predictable.

Tip: Before changing phones, open Settings > Devices on the old phone and confirm which sessions are active. If you are handing the old device to someone else, terminate the session after the new phone is verified, not before.

What Changed in Recent Releases, and What Did Not

Across the releases available in recent years, Telegram's migration model has remained stable because the account is cloud-anchored. What has changed is the level of control visible in the client. Newer builds expose storage usage per chat, automatic media download rules with exception lists, QR-code linking for desktop sessions, and a desktop export tool that can produce a readable archive. These are improvements in observability and control, not a replacement for the cloud account model; the underlying question is still which account the new phone is signed into.

If your mental model was formed when phones had small amounts of storage and media downloaded aggressively, it is worth revising. In empirical observation, the modern client behaves more like a cache manager than a synchronization client: it shows you what is taking space, lets you clear it, and downloads full media when you open a chat or tap a file. That is good for storage, but it means a new phone is not a clone of the old phone's cache. It is a fresh client attached to the same cloud account, and it will build its own local copy over time.

The stable part is the identity rule. Telegram treats the phone number as the account key. Changing the handset does not change the key; changing the number does. The in-app Change Number flow exists precisely so that an account can move to a new number without becoming a new account. If you skip that flow and simply register a new number, you have created a separate account with an empty cloud, even if the old phone is still sitting on your desk. This is why the order of operations matters more than the speed of the transfer.

Comparison and Choice: Five Migration Approaches and What They Actually Move

Most migration decisions are not about speed; they are about what you expect to move. The table below compares the approaches people commonly consider, including the ones that are often misunderstood. The right choice depends on whether you are keeping the account, whether you need a readable archive, and whether any conversations are device-bound. Read it as a map of trade-offs rather than a ranking.

The table makes the central trade-off visible. Same-account login is the only approach that reconstructs the working account on the new phone. Desktop export is the only approach that produces an archive you can read without Telegram, but it is a one-way street. Change Number is an account-preservation tool, not a device-transfer tool. OS migration assistants may be useful for photos and contacts, but Telegram's login session is anchored to verification and encryption, so a copied app container is not a guarantee. Treat that last point as a working hypothesis for your specific phone pair: verify by opening Telegram after the OS transfer; if it asks for phone verification, the session did not survive.

There is also a privacy dimension. The cloud login path keeps data inside Telegram's account boundary. An export or a third-party bot moves a copy outside that boundary. That is sometimes necessary for compliance or personal archiving, but it should be a deliberate choice rather than the default. If you only need to move to a new phone, the cloud path is the shortest and least exposed route; the archive is a separate decision with its own storage and access rules.

Decision Tree: Which Path Fits Your Situation

Use the following sequence before you wipe, sell, or lose access to the old phone. It is ordered by the questions that most often change the answer, not by the order of the settings menus. Each step is meant to rule out a failure mode before it becomes difficult to reverse.

1. Are you keeping the same Telegram account? If yes, continue. If no, stop: a different phone number is a different cloud account. If the number is changing but the account should remain, use Change Number before you lose the old number.
2. Can you still receive a login code? Check whether Telegram is open on another device, because the code may arrive there instead of by SMS. If you have no access to the number and no logged-in device, account recovery is limited; prevention is the reliable strategy.
3. Do you know the two-step verification password? If it is enabled and you do not know it, resolve that before migration. A recovery email helps, but it is not a substitute for the password.
4. Are Secret Chats part of the picture? If yes, accept that they will not appear on the new phone. Plan a separate channel for anything that must survive the device change.
5. Do you need an offline or compliance archive? If yes, use Telegram Desktop export after the new phone is working, or before you delete material. Do not confuse the export with a restore.
6. Is cellular data limited? If yes, set automatic media download to Wi-Fi only before opening media-heavy chats on the new phone.
7. Are you handing over the old device? If yes, verify the new phone first, then terminate the old session from Settings > Devices.

The tree is deliberately conservative. It treats the old phone as a temporary authentication asset, not as the data source. That framing prevents the common mistake of wiping the old device before the new login is confirmed. It also prevents the opposite mistake: keeping an old session alive indefinitely because the user is afraid to terminate it, which leaves an unnecessary access path to the account.

For a simple upgrade with the same number, the tree collapses to two actions: log in on the new phone, then review devices. For a number change, it expands to three: Change Number, verify the new login, then terminate old sessions. For a lost or broken phone, it becomes an account recovery problem rather than a transfer problem, and the available options depend on whether the number, the two-step password, and another logged-in device are still under your control. Knowing which of these situations you are in is more useful than memorizing every menu path.

Operation Paths by Platform: Android, iOS, and Desktop

The shortest path is the same on every platform, but the labels and the fallback options differ. The paths below use the latest version as of this writing; exact labels can vary slightly by build and by operating system language. If a menu label does not match, search within Settings for the feature name rather than assuming the feature is missing. The platform differences are mostly about storage habits and fallback controls, not about the account model.

Android: Install, Verify, Then Tune Media Behavior

On the old Android phone, confirm the account number under Settings > Edit Profile and confirm that two-step verification is either disabled or that you know the password. Keep the old phone charged and connected to a network. On the new Android phone, install Telegram from Google Play, open it, and choose Start Messaging. Enter the phone number in international format, confirm it, and wait for the code. If Telegram is still active on the old phone or another device, the code may appear there rather than in an SMS. Enter the code, then the two-step password if prompted. At this point the account is live on the new phone; the remaining work is about cache and data use, not about copying chats.

After the initial sync, do not open every large chat on cellular data. Go to Settings > Data and Storage > Automatic Media Download and set photos, videos, and files to Wi-Fi only, or use the exception list for the chats you actually need. Then open Settings > Data and Storage > Storage Usage to see which chats are consuming cache. On a new phone the cache starts small and grows as you open media; that is normal. If you need to free space later, clear the cache for selected chats rather than deleting the chats themselves.

The Android fallback path is useful when the code does not arrive. Check whether the number was entered in the correct international format, wait before requesting another code, and look at other logged-in devices. If you are moving from Android to iOS, the Telegram side is the same account login; the difference is in how the operating system handles local storage and gallery saving. Telegram's cloud does not care which mobile OS you use, but the local cache does, so the new phone will build its own storage profile.

iOS: Same Account, Different Storage Habits

On iPhone, install Telegram from the App Store and follow the same number-based login. The iOS client exposes Settings > Data and Storage > Storage Usage and automatic media download controls in a layout that may feel more compact than Android's. If you use iCloud backup for the device, remember that it backs up the app's local data according to Apple's rules; it is not a substitute for Telegram's cloud account. The reliable migration remains the Telegram login, not the phone backup.

A practical iOS scenario: a user upgrades from an older iPhone with limited storage to a larger model and expects all videos to be present immediately. In empirical observation, thumbnails and recent items appear quickly, while full videos download when opened. That is not a failed transfer; it is the cache being rebuilt on demand. If cellular data is limited, set auto-download to Wi-Fi only before scrolling through video-heavy channels.

If you are switching from Android to iOS, do not expect the old local cache to appear in the iOS app. The cloud chats will return, but the new phone builds its own cache. Saved Messages, folders, and pinned chats are generally account-level and normally reappear; verify them rather than assuming every client-side preference will be identical. Notification tones and some display preferences are examples of settings that may be device-local, so a short review after login is worthwhile.

Desktop: A Second Device, an Export Station, and a Safety Net

Telegram Desktop is not a phone-to-phone transfer tool, but it is useful in two ways. First, it can be linked as an additional device so that you can receive login codes and inspect chats while the new phone is being set up. On mobile, open Settings > Devices > Link Desktop Device and scan the QR code shown on the desktop login screen. Second, it provides the export path under Settings > Advanced > Export Telegram data, which is the closest thing to a local archive.

The desktop export is not a restore. It produces a readable archive, typically an HTML index, a JSON file, and media folders, depending on the options you select. You can choose which chats and media types to include, but you cannot import that archive back into Telegram as a new account. That boundary is important for compliance work: the export is a record, not a migration shortcut. It is also unencrypted by design, so store it on an encrypted volume or a protected location if it contains sensitive material.

If both phones are unavailable, a desktop session can be a safety net for receiving a login code and for exporting critical chats. It should not be the only session you keep alive, however. Review Settings > Devices periodically and terminate sessions you no longer recognize or need. A desktop session is most useful when it is intentional, current, and limited to devices you control.

Media Mechanics: Why Photos and Videos Reappear on Demand

Telegram media in ordinary cloud chats has three states that users often conflate. The first is cloud-only: the file exists in Telegram's service and is not on the new phone yet. The second is cached: the phone has a local copy, which makes reopening faster and counts toward storage usage. The third is saved to the device gallery or filesystem, which is outside Telegram's cache and may be backed up by iCloud, Google Photos, or a computer. Migration affects the first two states; the third is your own copy and follows your device backup strategy, not Telegram's login.

When you log in on a new phone, Telegram does not push the entire media history to the device. It reconstructs the chat list from the cloud and downloads media when you open a chat or tap a file, subject to your automatic download settings. In empirical observation, thumbnails and small previews tend to appear first, while full videos and large files wait for a tap or a Wi-Fi connection. Actual timing varies by network, device, and file size; treat any single timing claim with suspicion.

This behavior is a feature, not a defect. A user with a large Saved Messages archive can move to a phone with less storage without immediately filling it. The trade-off is that the new phone is not a complete offline clone. If you need offline access to a specific set of files, download them explicitly and consider saving the important ones to the gallery or to a separate storage location. That keeps the cloud account as the source and the device as a working copy.

A Hypothetical Data-Usage Scenario

Suppose a user keeps a 12 GB archive of design references and travel videos in Saved Messages, and the new phone has a 5 GB monthly cellular allowance. If automatic video download is enabled on cellular, scrolling through Saved Messages can begin pulling full files and consume the allowance quickly. The safer path is to set automatic media download to Wi-Fi only, open Saved Messages on Wi-Fi, and download only the files needed for the next trip. This is a hypothetical but realistic example; the exact size and allowance are placeholders, not measurements of Telegram's service.

The same logic applies to large group chats. A chat with many active members may contain years of media. Opening it on a new phone with aggressive auto-download settings can trigger a wave of downloads. Use per-chat exceptions if you want automatic downloads for family chats but not for large public groups. The control exists in Settings > Data and Storage; the discipline is in deciding which chats deserve the exception.

A Reproducible Check for Cloud vs Cache

To see the distinction for yourself, open a chat on the old phone and note a photo that is visible. Go to Settings > Data and Storage > Storage Usage and clear the cache for that chat. Reopen the chat: the photo should still be available from the cloud and will download again when tapped. That simple test demonstrates that the cache is a copy, not the master. It also explains why a new phone can show the chat without showing every file immediately.

Secret Chats and Other Boundaries: What Will Not Follow You

Secret Chats are the most important exception. They are end-to-end encrypted and tied to the devices that created them; they are not part of the cloud chat history that reappears after login. A new phone will not show them, and there is no supported migration path that turns them into ordinary cloud chats. If a conversation must survive a device change, it should not be conducted solely in a Secret Chat. This is a boundary of the feature, not a bug in the transfer process.

The same caution applies to self-destructing messages and any media designed to disappear. Even if a local cache or a screenshot exists, the official model is device-bound and ephemeral. Migration planning should treat these conversations as outside the transferable set. For sensitive work, decide in advance which channel is allowed to carry information that must be retained, and which channel is intentionally disposable.

Other boundaries are less dramatic but still worth naming. A different phone number is a different account, so logging in with a new number will not reveal the old chats. A deleted chat is deleted from the account, not merely hidden on one device. A media file that the sender deletes for everyone may no longer be available from the cloud, even if it was cached on the old phone. These are account-level realities; no local transfer trick changes them.

Exports, Bots, and Third-Party Tools: Use Them for Archives, Not Migration

Telegram Desktop's export is the most reproducible official way to create a local record. It is useful when you need to read old chats without Telegram, hand material to a compliance process, or keep a personal archive. It is not a migration tool. The export does not log the new phone in, does not restore Secret Chats, and does not replace the cloud account. Think of it as a printout of selected conversations, not as a backup that can be re-imported.

Third-party bots occupy a different risk category. A bot cannot read your existing chat history; it only receives messages that are sent to it or messages in groups where it is a member, subject to its privacy settings. An archiving bot therefore only archives what you forward to it or what it sees after joining. That makes it suitable for selective, ongoing archiving, not for transferring a history that predates the bot. The principle of least privilege applies: do not give a bot admin rights it does not need, and treat a bot token as a credential.

There is no official Telegram bot that migrates an account from one phone to another. The account migration is the login. If a tool promises to move your entire history into a new account or a new number, verify what it actually does before trusting it with sensitive material. A reproducible test is to use a small, non-sensitive chat first and observe whether the tool reads old messages or only new ones. If it claims to read history it never received, that claim is a warning sign.

Troubleshooting: Symptom, Cause, Verification, Resolution

Most migration problems are not failures of the transfer itself. They are mismatches between what the user expects and what the account model does. The following entries follow a simple structure so that you can verify before you act. Start with the symptom, confirm the cause where possible, and only then change a setting or log out.

Chats Are Missing Entirely

Possible cause: the new phone is logged into a different phone number or a different account. Verification: compare Settings > Edit Profile on both phones; the number should match. Resolution: log out of the wrong account and log in with the correct number. If the number itself has changed and you did not use Change Number, the old account still belongs to the old number; you will need access to that number to recover it.

Chats Appear but Photos and Videos Do Not Download

Possible cause: automatic media download is disabled or restricted to Wi-Fi, or the device is low on storage. Verification: open Settings > Data and Storage > Automatic Media Download and check the rules; then check Storage Usage and free space. Resolution: connect to Wi-Fi, tap the file to download it manually, or adjust the auto-download rules for that chat. If storage is full, clear cache for large chats rather than deleting the chats.

The Login Code Does Not Arrive

Possible cause: SMS delay, carrier filtering, or the code being delivered to another logged-in Telegram session. Verification: check other devices where Telegram is open; check the number format; wait before requesting again. Resolution: use the code from the other device if it appears, confirm the number, and avoid repeated requests that may trigger rate limits. If you have no access to the number and no active session, account recovery options are limited.

Two-Step Verification Blocks the Login

Possible cause: the account has a two-step password that you do not remember. Verification: the login screen asks for a password after the code. Resolution: use the recovery email if configured; follow the in-app recovery flow. Do not expect support to bypass two-step verification, because that would defeat its purpose. The reliable prevention is to store the password and recovery email before migration.

QR Login on Desktop Fails

Possible cause: outdated client, camera permission issue, or network restriction. Verification: try the phone-number login on the same desktop; if that works, the network is not the blocker. Resolution: update the desktop client, grant camera permission, or use the phone-number fallback. On mobile, the link path is Settings > Devices > Link Desktop Device.

Secret Chats Are Gone

Possible cause: expected behavior. Secret Chats are device-bound and do not migrate. Verification: confirm that the missing conversation was a Secret Chat rather than an ordinary cloud chat. Resolution: there is no migration fix. Plan future sensitive conversations with the device boundary in mind, and do not rely on Secret Chats for material that must survive a phone change.

Applicable and Non-Applicable Scenarios

The cloud-login approach is suitable for most personal upgrades, carrier switches, and device replacements where the same account is retained. It is also suitable for moving between Android and iOS, because the account is platform-neutral. It is not suitable when the goal is to merge two different accounts, to recover a number you no longer control, or to preserve Secret Chats across devices. The table below summarizes the practical boundary.

For a team or business context, add a policy question: is Telegram the system of record, or a communication channel? If it is the system of record, the cloud account alone is not a retention strategy. Export the material that must be retained and store it under the organization's access controls. If it is a channel, the migration is simply the login, and the retention burden belongs elsewhere. Making that distinction explicit prevents migration advice from being mistaken for a records-management policy.

Best Practices: A Short Decision Checklist

The following rules are written as decisions rather than steps, so they can be applied to an unexpected device change as well as a planned upgrade. They are not a substitute for the platform-specific paths above; they are the principles that keep those paths from going wrong.

• Verify the account number and two-step password before you wipe or lose the old phone.
• Keep at least one other logged-in session available until the new phone is confirmed.
• Set automatic media download to Wi-Fi only before opening large chats on a new device.
• Use Storage Usage to identify cache-heavy chats; clear cache rather than deleting chats when you only need space.
• Use Change Number if the phone number changes and the account should remain.
• Treat Secret Chats as non-transferable and plan sensitive retention separately.
• Export only what you need, store the export securely, and remember that it is not a restore.
• After migration, review Settings > Devices and terminate sessions you no longer need.

The checklist is intentionally short. Longer checklists tend to be ignored during a stressful device change. If you follow only two items, make them these: confirm the login on the new phone before terminating the old session, and set media downloads to Wi-Fi only before opening a large archive. Those two decisions prevent most of the avoidable problems described in this guide, and the remaining items are refinements rather than prerequisites.

Frequently Asked Questions

Conclusion: Log In First, Tune Second, Archive Third

The reliable Telegram transfer chats and media to a new phone strategy is not a cable or a clone. It is a sequence: log in to the same account, let the cloud chat list rebuild, tune media downloads so the new phone does not consume unnecessary data, and export only what must live outside the account. The old phone is an authentication asset until the new login is verified; after that, it is a session to retire.

The boundaries are equally important. Secret Chats do not follow you. A different number is a different account. An export is an archive, not a restore. OS-level migration tools may copy some local data, but they do not replace Telegram's account login. If you plan around those boundaries instead of fighting them, the migration becomes predictable, and troubleshooting turns into a short checklist rather than a rescue operation.

A sensible next step is to open Settings > Devices on the old phone now, confirm the account number and two-step status, and decide whether any chats need a Desktop export. Then log in on the new phone over Wi-Fi, set automatic media download to Wi-Fi only, and verify a few media-heavy chats before terminating the old session. That order keeps the account accessible, the data usage controlled, and the archive deliberate. Client interfaces may continue to change, but the account boundary described here is the stable part to plan around.