Telegram logoTelegramOfficial Download Portal

Blog / Chat Migration

How to Transfer Telegram Chats to a New Phone Without Losing Media?

- Telegram Official TeamChat Migration

Transfer Telegram chats to a new phone without losing media: check cloud vs local data, set auto-download, verify, then wipe the old device.

how to transfer Telegram chats to a new phone, Telegram media transfer without data loss, Telegram chat history migration steps, Telegram cloud backup and restore, Telegram media missing after transfer fix, does Telegram transfer media automatically, Telegram local backup vs cloud sync, how to set up Telegram auto-download on new device

The cloud-first model: what actually travels with your account

People searching for a way to transfer Telegram chats to a new phone without losing media usually expect a multi-gigabyte copy job. In practice, Telegram is a cloud-first messenger: the message history you see is a rendering of server-side data tied to your account rather than to a handset. Swapping phones therefore moves a login session, not a database. The only thing that genuinely has to be rebuilt is the local cache — the downloaded copies of photos, videos and documents that made the old phone feel instant.

Framing the job this way immediately explains why some people lose media and others do not. Your data splits into two categories with opposite behaviour. Cloud chats — one-to-one conversations, groups, channels, and Saved Messages — follow the account and reappear on any device you sign into. Device-bound artifacts — Secret Chats, cached files, anything already saved into the phone's photo gallery, and every local preference such as notification sounds or the app passcode — stay where they were created. Nearly every reported media loss during a device swap traces back to treating the second category as if it were the first. The distinction is simple, but it is also the one most migration checklists skip.

There is a third category that trips up even experienced users: media that was never really cloud-stored in the first place. A photo sent in a Secret Chat, a video configured to self-destruct after viewing, a voice note opened once — none of these can be pulled down onto a new device, because no server-side copy survives in a retrievable form. Knowing this before you start is the difference between a routine migration and an unrecoverable surprise. In practice, that third category is less a storage location than a design choice: some content is meant to be ephemeral, and migration simply makes that intent visible.

The table below condenses the split into a practical reference, including what, if anything, you must do on the new phone.

Data typeFollows the account?What you must do on the new phone
Messages in normal chats, groups, channelsYesNothing beyond logging in
Photos, videos, files sent in cloud chatsYes, as server-side objectsRe-download, or pre-fetch in bulk
Chat folders, archived chats, pinned chats, draftsYesNothing; they reappear
Secret ChatsNo — bound to one deviceCannot be restored; plan ahead
Downloaded cache and thumbnailsNoRegenerated on demand from the cloud
App passcode, notification settings, theme tweaksNoReconfigure manually

Read the table as a division of responsibilities rather than a list of features: if an item follows the account, the new phone needs only a login; if it does not, the work has to happen before the old device is retired.

The cloud-first model: what actually travels with your account
The cloud-first model: what actually travels with your account

Prerequisites check before you touch the new phone

The most common way a smooth migration turns painful is skipping the ten-minute audit at the start. Three things must be true before you install anything: you can receive a login code, you can satisfy two-step verification, and you know which of your conversations are not cloud-backed. Verify each one on the old device while you still have it in your hand. That audit is short, but it is also the only part of the process that cannot be done retroactively.

Account access: the code and the password

Telegram sends the login confirmation to your other active sessions first and only falls back to SMS if no session can be reached. That behaviour is convenient during a planned upgrade and awkward if you have already logged out everywhere. Before wiping anything, open Settings → Privacy and Security → Devices (mobile) or Settings → Devices (desktop) and confirm at least one session is alive and reachable. If you have enabled two-step verification, locate the password now; the recovery email attached to it is your only self-service fallback. A user who forgets both typically faces a waiting period before the account can be recovered, which is exactly the scenario migration guides rarely mention. The goal is not to memorize the password, but to know where it is stored and that you can reach it from a device other than the one being retired.

Consider a realistic case: someone trades in a phone at a carrier store, hands over the old handset, then discovers two-step verification is on and the password lives in a notes app on that very device. The account is not lost, but the wait is measured in days rather than minutes. Writing the cloud password into a password manager before the swap converts a multi-day outage into a five-minute login.

Inventory: find the conversations that will not survive

Scroll your chat list with one question in mind: does this conversation have a lock icon? Secret Chats — Telegram's end-to-end encrypted conversations, marked with a padlock and available only on mobile clients — are anchored to the device that created them. They do not appear on other sessions and cannot be restored after the session ends. If a Secret Chat contains something you need, export or forward the material into a normal cloud chat now; forwarding, note, breaks the end-to-end property for that content, so only do it when the trade-off is acceptable to you.

The same audit should catch chats with a self-destruct timer and any view-once media, both of which are designed to leave no retrievable copy. Neither is a bug in the migration; both are working as intended. Finally, check whether any chat is pinned inside the Archived folder — archived conversations do sync, but a user who only glances at the main list may believe an archived chat was lost when it simply moved. The inventory step is less about scrolling every message than about spotting the exceptions before they become surprises.

Storage reality check on the destination device

A fresh install of the app is small, but the cache is not. If you regularly work in media-heavy groups, the cache can grow into the tens of gigabytes after a few weeks of browsing. Before you enable aggressive auto-download on a phone with limited free space, look at how much headroom you actually have. The setting is reversible at any time, which means the sensible default is conservative, with manual pre-fetching for the few chats that matter.

The core workflow, step by step

What follows is the shortest reliable path from an old handset to a new one. It assumes both devices are available simultaneously, which is the easy case; the harder variants are handled in the edge-case section further down. The order matters because each step depends on the previous one still being reversible.

Step 1 — Stabilise the old device

Keep the old phone online and signed in until the new one is fully verified. Its live session is your fastest route to the login code and your safety net if something goes wrong. While you are there, note the cloud password status and skim the device list for sessions you no longer recognise; revoking stale sessions now saves confusion later when the list contains three phones you have forgotten about.

Step 2 — Install and log in on the new phone

Install Telegram from the Play Store on Android or the App Store on iOS, then enter the phone number in international format. The confirmation code arrives as a message inside Telegram on your existing sessions; the SMS fallback appears only when no session is reachable. After entering the code, the app asks for the two-step verification password if one is set — this is the moment the preparation from the previous section pays off.

On iOS the install path is the same, but expect the system photo-library permission prompt immediately after first login. Granting it lets you save received media to the gallery and attach existing photos; declining is fine and can be revisited in system settings, but it does change how you export media off the device later. On desktop, the equivalent shortcut is QR login: the desktop client displays a code that the mobile app can scan from its Devices screen, and the exact label for the scanner varies by platform and release.

Step 3 — Confirm the cloud restore before touching media

Within a short time after login, the chat list repopulates. Resist the urge to start opening old conversations immediately; first confirm structure. Check that folders appear in the same order, that the Archived folder holds what it used to, and that pinned chats sit where you left them. If the list looks thinner than expected, open the archive and search for a known keyword before concluding anything is missing — in most support threads the missing chat was archived, not deleted.

Step 4 — Rebuild media availability with auto-download rules

This is the step that decides whether the new phone feels like the old one. Telegram downloads media on demand and caches it; the auto-download rules determine what arrives without a tap. On Android and iOS the path is Settings → Data and Storage → Automatic Media Download, with separate profiles for mobile data, Wi-Fi and roaming, and per-type toggles for photos, videos and files, each with a maximum size threshold. On desktop the equivalent lives under the advanced settings area and uses similar per-type size limits.

A practical configuration for a phone with a generous data plan: enable photos on every network, enable videos up to a moderate size on Wi-Fi only, and leave large files manual. The reasoning is that photos are the bulk of the visual record and cost little, while a single large video can consume the same bandwidth as hundreds of photos. Users who set a very high video threshold on mobile data frequently report surprise data charges in the first week after a device swap — an avoidable outcome of an avoidable setting.

Tip: If the goal is purely to preserve access rather than to browse offline, leave auto-download conservative. Every cloud photo is one tap away regardless; the cache only matters when you are offline or on a slow link.

Step 5 — Pre-fetch only the chats that matter

For a handful of conversations — a project group, a family chat, an archive channel — bulk pre-loading is worth the bandwidth. Open the chat, scroll back to the period you care about, and let the media load while on Wi-Fi. There is no official one-button command to download an entire chat's history on mobile, so this is deliberately manual. If you need a complete offline copy of one conversation, the desktop client's export function is the documented tool, covered later.

Step 6 — Verify from an independent session

Before you wipe anything, prove the media is really server-side. Open Telegram Web in a browser on a different machine, sign in, and open an old photo from three months ago. If it renders, that object exists in the cloud and will render on any future device. If it fails there too, the problem is upstream of your new phone and no amount of reinstallation will fix it. This single check separates device-side caching issues from account-side problems faster than any other method.

Step 7 — Retire the old device cleanly

Once verification passes, terminate the old session from the new phone's device list rather than simply uninstalling the app. An uninstall leaves the session registered, and a registered session can still receive login codes and message previews. Terminating it removes the entry, ends push delivery, and — importantly for anyone with Secret Chats — closes those conversations at the source. After that, a factory reset of the old handset leaves nothing behind.

Media that genuinely never migrates

A migration guide that promises everything transfers is misleading. Four categories do not, and each has its own mitigation.

  • Secret Chats. End-to-end encrypted, mobile-only, device-bound. Once the originating session ends, the conversation is gone from every device. Mitigation: copy or forward essentials into a cloud chat before the swap.
  • Self-destructing and view-once media. Designed to leave no retrievable copy; a timer removes the content for all participants. Mitigation: none after the fact — treat such chats as ephemeral by design.
  • Local cache and thumbnails. Regenerated on demand, but only for objects that still exist server-side. Mitigation: none needed, provided the source objects are intact.
  • Files you saved into the phone's own storage. A video saved to the gallery or a document downloaded to a Downloads folder is your file, outside the app. Mitigation: copy it off the old phone with a cable or cloud drive before resetting.

The fourth item is the one people forget, because it sits at the boundary between the app and the operating system. Clearing the app cache removes cached media but leaves gallery-saved copies untouched; conversely, a factory reset destroys gallery copies while leaving the cloud intact. Different operations, different consequences.

Large libraries and slow connections: a worked example

Suppose a hypothetical user administers a work group that has accumulated years of design references, and their old phone holds roughly 40 GB of cached media. Copying that cache to a new phone is neither possible nor desirable — it is a cache, not a library. The correct move is to accept an empty cache, log in, and then let the specific chat re-download what is needed on demand.

The practical sequence for this scenario: log in over Wi-Fi, set auto-download to photos only on Wi-Fi, open the work group and scroll back through the last few months while the device is charging, then repeat for the two other chats that matter. Everything older stays in the cloud and appears the moment it is viewed. The apparent cost is a few minutes of scrolling; the real saving is tens of gigabytes of storage that would otherwise be filled with content the user will never open again.

Compare that with the opposite approach — setting auto-download to include all videos at maximum size on both Wi-Fi and mobile data, then leaving the phone to sync overnight. Empirically, this is where new-device complaints cluster: storage alerts within a week, a warm handset during the initial sync, and in some cases a data overage if the phone switched off Wi-Fi mid-download. Neither approach is morally superior; the point is that the aggressive setting should be a deliberate choice for a specific chat, not a global default set in a hurry.

Using the desktop client as a staging and verification station

Telegram Desktop has one documented capability the mobile clients lack: exporting data. Under Settings → Advanced → Export Telegram data, the client can produce an HTML or JSON archive of your account, and the context menu of an individual chat offers a scoped export for that conversation alone. You can select which media types to include and cap the maximum file size, which keeps the archive from ballooning.

Two boundaries are worth stating plainly. First, export is a one-way door: there is no documented import function that would push an exported archive back into an account, so it is an archival and compliance tool, not a backup-and-restore mechanism. Second, the exported archive is unencrypted by default — a folder of photos and JSON on your disk that anyone with file access can read. If the material is sensitive, move the archive to encrypted storage or delete it after the need passes.

The desktop client's most underrated role during migration is verification. Because it runs on a machine that is not the old or new phone, it gives an unbiased third view of what the account actually contains. If a photo opens on desktop but not on the new phone, the issue is local; if it fails on both, the issue is account-side. That single comparison collapses a lot of guesswork.

Using the desktop client as a staging and verification station
Using the desktop client as a staging and verification station

Edge cases and failure branches

Planned migrations follow the seven steps above. Unplanned ones — a lost phone, a broken screen, a number change — take different routes, and the correct route depends on which asset you still control.

The old phone is gone or unreachable

Install on the new device and request the code. With no reachable session, the app falls back to SMS to the registered number, so access to that number becomes the whole game. If the number itself is gone, the number-change flow matters: Telegram supports moving an account to a new number, and the option sits either in profile editing or under Privacy and Security depending on client and version. Do this while you still control the old number if at all possible; afterwards it becomes a support conversation rather than a menu action.

The cloud password is forgotten

If a recovery email was configured, use it — the reset link is the clean path. Without one, the account enters a recovery waiting period before two-step verification can be removed. Nothing in this article can shorten that; the practical advice is to start the process immediately rather than reinstalling repeatedly, which achieves nothing. Once recovered, store the password in a manager before the next device change.

Long periods of inactivity

Telegram accounts can be configured to self-destruct after a period of inactivity, with the window set under Privacy and Security. A phone that sits in a drawer for months while you use a tablet is not inactive in the account sense, but a number you abandon entirely might be. If an account has already been deleted, no migration step recovers it; the chat history ceases to exist server-side. This is the single strongest argument for logging in on the new device before decommissioning the old one.

Multiple accounts and shared devices

If you run several accounts in one client, each migrates independently — logging into one does not restore another. On a shared family device, remember that logging out is a per-session action and does not delete cloud data, which is usually what you want but occasionally is not.

Automation: what you can and cannot script

There is no official scheduled backup, and no supported way to push an archive back into an account. What you can automate is the shape of your working set, which in practice removes most of the manual effort.

Chat folders are the highest-leverage tool here. Build a folder containing only the conversations whose media you actually need offline, then treat that folder as your pre-fetch queue after a device swap. Folders sync with the account, so the folder you built on the old phone is waiting on the new one — a small feature with an outsized effect on migration time. Pair it with network-specific auto-download rules and the new device becomes usable within minutes rather than hours.

Third-party archiving bots exist, but apply the principle of least privilege. A bot added to a group or channel receives messages from the moment it is added and only in chats where it is a member; it does not retroactively gain your history. That makes bots an archive of the future, not a rescue tool for the past, and it means granting one admin rights to your channels deserves the same scrutiny as adding a human administrator. Prefer bots you can remove without residue, and never hand over a session or login code to a third-party service — that is the one action that can genuinely cost you the account.

Warning: Any tool that asks for your login code, cloud password, or a QR session is asking for full account control. No migration task requires handing those over.

Troubleshooting: symptom, cause, verification, fix

The table below maps common symptoms to their likely causes, the quickest verification step, and the usual resolution. Most entries resolve without reinstalling the app.

SymptomLikely causeVerificationResolution
Chat list restored but old photos show placeholdersMedia downloaded on demand, not yet cachedTap one; it loads within secondsNormal behaviour — adjust auto-download if you need offline access
A conversation seems to have vanishedIt lives in the Archived folderSearch a known keyword across all chatsOpen the archive and unarchive if desired
A chat is absent everywhere, including searchSecret Chat tied to the old deviceCheck the old phone for a padlock iconNot recoverable; recover content only if the old device still works
No login code arrivesCode is delivered in-app to existing sessions firstCheck every signed-in device for a service messageWait for the SMS fallback, or request again after the timer
Password prompt blocks loginTwo-step verification enabledTry the recovery email pathReset via email, or begin the recovery wait
Messages in one chat keep disappearingSelf-destruct timer active in that chatOpen chat info; the timer is listedExpected behaviour — disable the timer for future messages
Videos will not play while offlineSize exceeded the auto-download thresholdCompare file size against the configured capRaise the cap on Wi-Fi and re-open the chat on Wi-Fi

Use the verification column before taking action; it prevents the most common mistake, which is reinstalling or resetting in response to a problem that is actually normal on-demand behaviour.

When this workflow is not the right choice

Cloud restore is the right default for individuals and small teams, but it is a poor fit in a few situations. If you need a legally defensible, tamper-evident record of a conversation, pulling media down onto a phone is not evidence handling — the desktop export produces a readable archive but no chain of custody, and no client-side function in Telegram provides one. In that case, involve whatever archival or compliance tool your organisation already mandates.

If the destination device is a shared or borrowed handset, logging into a full account exposes every conversation to whoever holds it next. The app passcode and the ability to terminate sessions help, but they are mitigations rather than isolation; using the web client for temporary access and terminating the session afterwards is usually the cleaner pattern. And if your real goal is to preserve a small number of files rather than an account, saving them individually off the old phone is simpler and carries no account risk at all.

Review checklist before you wipe the old phone

  1. The new device is fully signed in and two-step verification has been satisfied.
  2. Chat folders, archived chats, pinned chats and drafts all match the old device.
  3. An independent session (web or desktop) opens an old photo successfully, proving cloud availability.
  4. Auto-download rules are set deliberately for mobile data, Wi-Fi and roaming, with sensible size caps.
  5. The handful of chats you need offline have been scrolled back and pre-fetched on Wi-Fi.
  6. Any Secret Chat content worth keeping has been copied into a cloud chat.
  7. Gallery-saved and downloaded files have been copied off the old device if they matter.
  8. The old session has been terminated from the device list — not merely uninstalled.
  9. The cloud password is stored in a manager, not in a notes app on either phone.
  10. A desktop export exists if you need an archival copy, and it is stored encrypted or deleted after use.

Work through the checklist in order rather than treating it as a set of independent reminders; each item confirms a different layer of the migration, from account access to local files to session cleanup.

Frequently Asked Questions

Do I need to back up Telegram before changing phones?

Not for cloud chats — they are stored server-side and reappear after you log in. A backup is only relevant for content that is not cloud-backed, such as Secret Chats, or for files you saved into the phone's own storage. The desktop export function creates an archive, but it cannot be imported back into an account.

Why are old photos blurred or missing on the new phone?

Media is downloaded on demand and cached locally, so a new device starts with an empty cache. Tapping a photo fetches it from the cloud. To avoid tapping, adjust the automatic media download thresholds under Settings → Data and Storage.

Can Secret Chats be moved to a new phone?

No. Secret Chats are end-to-end encrypted and tied to the device that created them; they are not stored in the cloud and do not appear on other sessions. If the originating device is unavailable, the conversation cannot be restored. Copy anything essential into a normal chat before switching devices.

Does clearing the cache delete my media permanently?

No, for cloud chats. Clearing the cache removes local copies only; the source objects remain on the servers and re-download when opened. The exception is content that never had a server-side copy, such as Secret Chats or media that has already expired via a self-destruct timer.

Should I log out on the old phone or just uninstall the app?

Terminate the session from the device list on the new phone, then reset the old handset. Uninstalling alone can leave the session registered, which means it may still receive login codes and notifications. Ending the session also closes any Secret Chats tied to that device.

The short version

Transferring chats to a new phone is mostly an exercise in understanding what Telegram already does for you. Messages, folders and archives follow the account; media follows on demand from the cloud; only Secret Chats, expired content and files saved outside the app genuinely stay behind. Prepare the account credentials, log in, verify from a third session, tune the auto-download rules for the chats that matter, and retire the old device by ending its session rather than deleting the icon.

As a next step, do the ten-minute audit today rather than on the day you switch: confirm two-step verification is recoverable, check the device list for sessions you no longer use, and build one folder containing the chats whose media you would want offline. Those three actions convert a stressful migration into a routine login, and they cost nothing if the phone never changes at all. None of this requires a special tool; it requires knowing which category each piece of content belongs to.

Tags#Data Migration#Media Backup#Chat History#Device Transfer#Cloud Sync#Account Restore