How Telegram Syncs Across All Your Devices

devices No main device, and why that matters daily

Several well-known messengers treat your handset as the authority. The desktop application is a window onto it: if the phone is off, out of signal, or flat, the computer in front of you stops working. People who have used one of those for years assume this is simply how messaging is.

Telegram never worked that way. Each installation signs in as its own session against your account and talks to the servers directly. Your laptop does not ask your phone for anything, which is why it keeps sending and receiving with the phone switched off in a drawer.

Three consequences follow, and they are the reason this is worth a step of its own. Buying a new phone is signing in rather than migrating. Losing a phone costs you a device, not a history. And a computer you use once a month is as current as the one you use hourly, because neither is holding the archive.

edit_note Drafts are the feature hiding in plain sight

Because an unfinished message is part of your account rather than part of a device, the message box becomes a small cross-device workspace. Most people never notice, and it solves a problem they solve badly in other ways.

The obvious use is finishing on a keyboard what you started with a thumb. The less obvious ones are better. A draft is a place to write something you are not sure you should send — it sits there, visible from anywhere, until you have decided. A draft in a chat you are about to open is a note to yourself about that conversation, in the one place you cannot miss it.

There is a matching caution, which Step 011 touched on from another angle: a forgotten draft is still there. Attach a photograph to a conversation with an old unsent line in the box and that line can go along as the caption. If a chat in your list shows a draft flag you do not recognise, read it before you type anything else into that room.

lock The security surface this design creates

Everything above has one structural consequence: a signed-in session is complete access to your account, and it does not need your phone's cooperation to keep working. Somebody with a session has your whole history, not just messages that arrive after they got in.

That makes Settings, then Devices, the most important screen in the app, and it is why it keeps appearing in this curriculum. The list shows every active session with the client it is running in, roughly where it connected from, and when it was last active. Terminating one takes effect immediately, wherever that device is and whether or not you can reach it.

Three habits cover it, and none takes more than a minute. Read the list once now and remove what you do not recognise — a legitimate device simply asks you to sign in again, so there is no cost to being wrong. Set sessions to expire automatically after a period of inactivity, which is the only part of this that maintains itself. And keep two-step verification on, so that a new session cannot be created with a code alone.

Step 028 goes through that screen in detail, including what its entries can and cannot tell you. The point here is the connection: the same property that makes a dead phone irrelevant also means a forgotten session is a live key.

public Where the history actually is

It is worth being plain about the trade this design makes, because the benefits above are not free.

Your cloud chats are encrypted between your devices and Telegram's infrastructure and stored there. That is what makes them available on every client you sign in to, searchable from any of them, and recoverable after a phone goes into a river. It also means the service holds them in a form it can access, which is a different arrangement from end-to-end encryption.

Neither arrangement is simply better. A history that only your handset can read cannot be restored when the handset is gone; a history the service can read is available everywhere and depends on the service. Telegram offers both and asks you to choose per conversation, which is the subject of the next step.

What follows practically is the point this curriculum keeps returning to: since the account is the archive, protecting the account is protecting the archive. Step 008 is the whole of that job, and everything in this step is a reason to have done it.

touch_app Try it now — five minutes

Three of these demonstrate the architecture and one secures it. Do the last one even if you skip the rest.

1. Type half a sentence on your phone and walk to a computer Do not send it. Open the same chat on the desktop or web client and the text is waiting. That one demonstration is what makes drafts stick as a habit.
2. Put your phone in flight mode and use the laptop Send something, search for something old, open a photograph from two years ago. All of it works, and seeing it work is what unlearns the habits from phone-tethered messengers.
3. Clear the storage on one device Settings, then storage. Then scroll back through an old conversation and watch the media return. Nothing was lost, which is the whole point of calling it a cache.
4. Read your device list and set the inactivity timer Settings, then Devices. Terminate anything you do not recognise, and set old sessions to expire on their own. This is the one item with a consequence.

help Common questions at this stage