How to Change Your Telegram Phone Number Safely

Most guides treat this as a settings chore, three taps and a code. The taps are real, but the interesting part is everything the platform does around them, because the number is not a contact detail on your profile. It is the thing your account is made of.

Here is the short version. Changing the number keeps everything, including chats, media and secret chats on every device. The change cannot be done from desktop or web, and the client says so in plain language. A session that is less than a day old cannot start the change at all. And in one specific emergency, changing your number is not a convenience, it is the documented way to cancel an attack already running against your account.

This article covers what the number really is, the two calls sitting behind the button, where the setting lives, why the desktop refuses, the twenty four hour wall, what happens when the new number is already taken, every refusal the operation can return, what travels with you, who gets told, how to hide the number instead of replacing it, the defensive use nobody writes about, the prompt that asks whether this is still your number, accounts with no SIM card at all, why an email cannot replace the number, and what teams running many accounts consistently get wrong. Every rule and every refusal quoted below was pulled from Telegram's own documentation and client source on 13 August 2026 rather than remembered.

What the Number Actually Is

Getting this straight first makes every rule further down look obvious instead of arbitrary.

One number, one account

The platform's own wording is blunt. Each phone number is a separate account. There is no shared identity underneath that several numbers point at, and there is no way to attach a second number to one account as an alternate address.

That is why the operation is called a change rather than an addition. You are moving the account from one address to another, and afterwards the old address holds nothing. If you want two numbers live at once, you are running two accounts, which most clients support side by side in one app.

The number is the identity, not a contact detail

Telegram states the consequence directly in its own help pages: the phone number is the only way it can identify a user, no additional information is collected, and so whoever has the number has the account. That sentence is worth reading twice before deciding what to do with a number you are giving up.

It also explains why the change flow is guarded so heavily. Every refusal described below exists because a successful change moves the whole account, and a change requested by the wrong person would move it to them.

Why the account does not live on the SIM

Nothing is stored on the card. The account lives on the server, and the number is a label the server uses to find it, which is why your history reappears the moment you sign in somewhere new. Our guide on moving a Telegram account to a new phone covers the device side of that in full.

The practical result is that changing the handset and changing the number are two separate jobs with two separate procedures. People arrive here having done one and expecting the other to have happened automatically. It does not.

The Two Calls Behind the Change Number Button

The button is one tap, but underneath it is a two step handshake, and knowing which step you are on tells you what a failure means.

The request that sends the code

The first call takes the new number and asks the server to send a verification code to it. It returns a code hash that ties the rest of the process together. This is the step where most refusals happen, because the server checks the number before it sends anything.

Four documented errors can come back here, and each one is a different problem with a different fix. They are covered one by one further down, because reading the refusal correctly saves the guesswork that usually follows.

The confirmation that moves the account

The second call submits the new number, the hash from the first call and the code you received. If it succeeds, the server returns your own user record with the new number on it, and the change is done at that instant. There is no pending state and no review queue.

This step has its own error list, which overlaps the first one but is not identical. Three of its failures are about the code itself, and two repeat checks from the first step, which is a detail with consequences we come back to.

The code goes to the new number

This trips people up more than anything else in the flow. The verification code is sent to the number you are moving to, not the one you are on. You need the new line reachable at the moment you start, on a device you can read.

Where exactly the code arrives depends on the same delivery ladder as a normal sign in, which has more rungs than most people expect. Our breakdown of the Telegram verification code covers each delivery method and why some of them silently fail.

Where the Setting Lives

The path is short and it has not moved in years, which is unusual for this app.

The path on a phone

Telegram's help pages give it precisely: open Settings, tap on your phone number, which sits just above the username, then choose Change Number. Nothing is hidden behind a submenu and nothing requires a support ticket.

The placement is itself a hint about how the platform thinks of the field. It sits with your name and username, in the block that describes who you are, rather than in a privacy or security area where a contact detail would live.

What you see before you commit

The client shows a plain warning before it does anything, restating that all of your data moves to the new number and your contacts will see the new one. Read it rather than swiping past, because it is describing the two effects people most often forget about afterwards.

After that you type the new number, submit it, and enter the code. The whole exchange takes under a minute when both numbers work. The failures are what take time, and they are almost always one of the documented refusals rather than a mystery.

Have both numbers reachable

The help pages attach a warning to this whole subject that is easy to skim past. Make sure you have access to the number connected to your account, otherwise you risk losing access to the account itself. That applies before the change and after it.

In practice that means doing this while the old line still works, not after it has been cancelled. If the old number is already dead and you are still signed in somewhere, you can still complete the change, because the process only needs the new number. If you are not signed in anywhere, the old line was your last route in.

Desktop and Web Will Not Do It

This is the single most searched variation of the question, and the answer is a flat no rather than a hidden menu.

The refusal, in the desktop client's own words

The desktop application ships a message for exactly this attempt, and it reads: you can only change your phone number using mobile Telegram apps, please use an official Telegram app on your phone to update your number. That string sits in the client's own language file, so it is not a bug report or a rumour.

The desktop client does carry the pieces of the flow, a submit control and a code entry screen, which is why the option sometimes appears reachable. It ends at that message, so the interface promising more than it delivers is the source of most of the confusion here.

Why the limit exists

The change hands the whole account to a new address, and desktop installations are the sessions most likely to be sitting unattended on a shared machine. Restricting the operation to the phone keeps it on the device that is hardest to borrow quietly.

It also lines up with how the code request is built. The request carries a flag stating whether the number belongs to the device making the call, a signal that only means something on a handset with a SIM in it.

What to do if the phone is the problem

If you are on a computer because the phone is broken or gone, the change is not your first move. Sign in on any phone you can reach with the number that still works, then change the number from there once the session settles.

If nobody can sign in anywhere, the priority is the sessions you already hold, not the number. Our guide on logging out of Telegram on all devices covers what you can still do from a session you control and what falls out of reach without one.

The Twenty Four Hour Wall

There is a delay built into this operation, and it is placed at the exact moment people least expect it.

The exact refusal

The code request answers a fresh session with a refusal whose text is unusually human. It says you cannot change your phone number right after logging in, and asks you to wait at least twenty four hours. It arrives as a not acceptable response rather than a bad request, which is the server's way of saying the call was well formed and simply not allowed yet.

The clock runs from the sign in of the session making the request, not from when the account was created and not from the last change. A session that has been signed in for a week can start the change immediately.

The order that fails

The common plan is to put the new SIM in the new phone, sign in with the old number, then change to the new number and be finished in one sitting. That plan fails at the second step, after you have already committed to the first.

It is worth noticing how the failure lands. Nothing is broken and nothing is lost, but you are now on a fresh session, holding a number you intended to abandon, with a day to wait. People in that position often reinstall or sign out and back in, which resets the clock and makes the wait longer.

The order that works

Change the number first from a session that is already older than a day, then move the account to the new handset. The device move has no waiting period attached, so doing it second costs nothing.

If the phone must be replaced first for practical reasons, do it, sign in, and then simply leave the change until the next day. The wait is not a penalty for doing something wrong, and there is no way to shorten it from the client.

When the New Number Already Has an Account

This is the second most common wall, and unlike the first one it does not clear by waiting.

The refusal you get

Both calls in the flow can answer that the phone number is already in use. The platform's guidance is equally short: if you already have a different Telegram account on the target number, you will need to delete that account first.

Deleting is a separate operation with its own timing, and it is not always immediate. If that account has a cloud password set, the removal can be held for a week before it completes. Our guide on deleting a Telegram account covers the hold, how to see the countdown, and how to cancel it.

Two accounts do not merge

There is no combine operation anywhere in the platform. Moving your account onto a number that holds another account does not merge the two histories, it is simply refused. The old account has to stop existing before the address is free.

That means the question worth asking first is which of the two accounts you actually want to keep. Whichever one you delete takes its chats, its channels, its owned groups and its purchase history with it, and none of that transfers to the survivor.

The gap between the two calls

The occupancy check runs on the request and again on the confirmation, which is a design detail with a real consequence. A number that was free when you asked for the code can be taken before you submit it, and the second call is where you would find out.

The window is small and the situation is rare, but it is the reason to complete the change promptly once you start rather than leaving the screen open. If the second call refuses on those grounds, nothing has moved and the account is exactly where it was.

Every Other Refusal the Change Can Return

The full list is short, and knowing it turns a vague failure into a specific one.

A number the platform has banned

The code request can answer that the number is banned from Telegram. This is not about your account, it is about the line, and it usually means that number carried an account that was removed for abuse at some point in its life.

Recycled mobile numbers are reissued by carriers constantly, so the history attached to a number is not necessarily yours. There is no client side fix for this one. The number is either appealed through support or replaced.

A number the platform will not accept

A separate refusal says the number is invalid, and it also arrives as a not acceptable response rather than a plain bad request. In most cases this is formatting, a missing country code or a national trunk digit left in front of the subscriber part.

The safe habit is to enter the number the way the platform stores it, in full international form, and to let the client handle the country prefix rather than typing it twice. A number that looks correct on a bill can still be wrong in this field.

The three ways a code fails

The confirmation step can refuse because the code is missing, because it has expired, or because it is invalid. Missing and invalid are usually the same human error, and expired means the exchange sat open too long and needs restarting from the request.

Restarting is cheap. Nothing about the account changes on a failed confirmation, so a fresh request and a fresh code is the correct response rather than repeated attempts with the old one.

What Moves With You and What Stays Behind

The promise here is broader than people expect, and the exceptions are narrower.

Everything in the cloud moves

The help pages put it plainly: you can change your number and keep everything, including all your contacts, messages and media from the Telegram cloud. Chats do not restart, groups do not drop you, and channels you own stay yours.

Because the account itself never changes, nothing has to be copied anywhere. The server relabels the account, and the same data is still sitting behind the same identifier. That is why the operation completes in seconds regardless of how large your history is.

Secret chats move too

This one surprises people who have read about secret chats being tied to devices. Telegram's own wording covers them explicitly, stating that a number change keeps your secret chats on all devices. The device you are on does not change, so the end to end keys stay where they were.

The case where secret chats are genuinely lost is a different one, signing out or moving to new hardware. Confusing the two is why the warning gets repeated in the wrong place, and it is worth separating them before you act.

Sessions, username and password are untouched

Your active sessions survive the change, your username stays exactly as it was, and a cloud password remains in force. Nothing about the change logs anyone out, including whoever else might be signed in, which matters if the change was prompted by a security scare.

If ending other sessions is part of your plan, treat it as a separate task with its own rules, including its own twenty four hour restriction. Our guide on the session file and TDATA explains why a stored session keeps working after the number on the account has changed.

Who Finds Out, and How

The change is not silent, and the audience is wider than the people you have messaged.

The update your contacts receive

The protocol carries a dedicated notification meaning that a user's phone number was changed, delivered with the user identifier and the new number. Clients apply it directly, so people who can see your number see the new one without doing anything.

Nobody receives a message about it and nothing appears in a chat. It is a quiet field update rather than an announcement, which is why most people never notice when a contact does this.

People who saved the old number

Your address book entries on other people's phones do not update. Someone who saved your old number keeps that entry, and depending on their settings and yours they may see a contact whose number no longer matches the one on file.

By default your number is visible only to people who added you to their address book as contacts, and the setting is in the privacy area. The client attaches a warning under it worth quoting: users who have your number saved in their contacts will also see it on Telegram.

The old number afterwards

Once the change completes, the old number is not attached to any account. The platform's lookup for a number that nobody holds answers that no user is associated with it, which is the same state a number never used on Telegram would be in.

That has an obvious implication if the line is going back to a carrier. Whoever receives that number next can register a new account on it, and while they get nothing of yours, they do inherit the position in everybody's address book that used to point at you.

Hiding the Number Instead of Changing It

A large share of people asking how to change the number actually want it hidden, which is a different setting and a much smaller job.

Two separate switches

The platform keeps two independent controls here and they are easy to mix up. One governs whether people can see your number, the other governs whether people can add you to their contact list by your number. They are separate keys in the protocol and separate rows in settings.

Setting the first to nobody hides the field. Setting the second is what stops a stranger who already knows the digits from turning them into a chat with you. Changing one and assuming the other followed is the usual mistake.

The warning under the setting

The help pages are honest about the limit of all this: people will always see your number if they know it already and saved it in their address book. No privacy setting reaches into somebody else's phone.

The client repeats the same point in its own words next to the contacts option, noting that users who add your number will see it on Telegram only if they are your contacts. Our walkthrough of Telegram privacy settings goes through each of these rows and what it actually changes.

Hand out a username instead

The permanent fix for handing out a number is not handing it out. A username is the address you can give to strangers, it works in links, and you can change or drop it whenever you like without touching the account.

The rules are simple: letters, digits and underscores, between five and thirty two characters. Our guide on the Telegram username covers claiming one, what happens when you release it, and why it is the correct thing to print on anything public.

Changing the Number as a Defensive Move

This is the part almost nothing on the subject mentions, and it is the reason the operation is worth understanding before you need it.

The attack this cancels

Anyone holding your number can start a request to delete your account and reset its cloud password. That is not a flaw in a client, it follows directly from the number being the identity. The platform's answer is to warn you and to give you two ways to stop it.

One way is entering the confirmation code sent to your line, which proves the number is still yours. The other is more interesting and much less known.

The notice, word for word

The client's own text for this situation reads: somebody with access to your phone number has requested to delete your Telegram account and reset your two step verification password, and if this was not you, enter the code just sent by text. It then adds the second route directly, saying you can also cancel this by changing your phone number to a number you control.

Read that carefully, because it changes what the change number screen is for. If someone else holds the line and you cannot receive the confirmation code on it, moving the account to a number you do control ends their claim on it entirely.

The order under pressure

The sequence that survives this is not obvious in the moment. Set a cloud password first if there is not one, because that alone stops the number from being sufficient to sign in. Then move the account to a number you hold. Then deal with sessions.

The wall from earlier bites here too, so a session you signed in on minutes ago cannot start the change. Keep an old session alive during any scare rather than reinstalling, which is the instinct most people have. Our guide on how Telegram scams work covers the social side of how people are talked out of that code in the first place.

The Prompt Asking If This Is Still Your Number

Some accounts get asked about this without ever going looking, and the prompt is not random.

Where it comes from

The server maintains a list of pending suggestions for each account, and clients display them as prompts. One of the documented values covers this exactly: users should check whether their authorization phone number is correct, and change it if it is inaccessible.

The client wording is friendlier. It asks whether the number shown is still yours, and explains that keeping it up to date makes sure you can always sign in. It links to the platform's own page on having a new number.

What the platform means by it

Inaccessible is the operative word. The concern is not that the number is old, it is that you may no longer be able to receive anything on it, which turns the account into something you cannot recover if a session is ever lost.

This is also why the passkey documentation carries the same warning from a different angle, noting that you can still request a text code to sign in, so the account should always use an up to date number that you control. Newer sign in methods sit on top of the number rather than replacing it.

Dismissing it is a decision

Prompts can be dismissed, and the dismissal is recorded so it stops appearing. There is nothing wrong with that when the number is genuinely fine, and the prompt cannot tell the difference.

The failure mode is dismissing it out of habit on an account whose number lapsed years ago. If you cannot say for certain that a text message sent to that line would reach you today, the prompt is correct and worth acting on.

An Account Without a SIM Card

The most common tail on this question is how to change to no number at all, and there is a real answer that is not quite the one people hope for.

What the platform announced

The official position is public. Telegram announced that you can have an account without a SIM card and sign in using blockchain based anonymous numbers available on the Fragment platform. That is the supported route, and there is no other.

Note what it does not say. The account still has a number, and the change flow is still the change flow. What changes is where the number comes from and who can trace it back to a person.

What a collectible number looks like

Clients treat these as a distinct object. The interface describes such a line as a collectible phone number belonging to an account, and shows when it was purchased and for how much. That information is public by design, because the ownership record lives on a public ledger.

So the anonymity is specific rather than total. The number is not tied to an identity document at a carrier, which is the point, but the fact that it is a collectible and the price paid for it are visible to anyone who taps it.

The honest limits

These numbers cost money, sometimes a lot of it, and the price is set by an open market rather than a tariff. They also put you in charge of a wallet, which is a new way to lose an account for anyone who has not managed one before.

They are also not a way around a ban, and they do not remove the requirement to receive a code. If the goal is simply that acquaintances cannot see your digits, the privacy switches above do that for free and without adding a custody problem.

Changing to an Email Is Not a Thing

The idea of replacing the number with an email address comes up constantly, so it is worth stating exactly what the email feature is.

What the login email actually replaces

Telegram supports a login email, and the protocol has a code type meaning the code was sent via the previously configured login email. That is the whole scope of it. The email is a delivery channel for the sign in code, not an identifier for the account.

Your account is still found by number, still displayed by number, and still changed with the flow described above. Setting a login email does not remove the number and does not let you delete it.

You cannot set one first

The setup order is enforced by the server. Configuring an email has two purposes, an initial setup and a later change, and attempting the change without an existing one is refused with a message saying an email must already be set up first.

In other words the email is layered onto an account you already have, reached in the usual way. There is no path that starts with an email address and produces an account.

Resetting it has a waiting period

If you lose access to that email, the reset is not instant. The server tells the client how many seconds to wait before the reset can be requested, and it reports a pending reset date once one is scheduled. The waiting period is zero for accounts with a premium subscription.

That is worth knowing before you rely on it as your only route in. A code channel with a built in delay is a fine second option and a poor only option.

What Operators Get Wrong About Numbers

Once you pass one account the number stops being a personal detail and starts being inventory, and a few assumptions cost people real time. The three below come up in nearly every conversation we have about running a fleet, whether the work sits on standard tooling or on something built for a team under Custom Solutions.

The number and the session are different objects

A stored session authenticates with a key, not with the number printed on it. Changing the number on an account does not invalidate a session that was already signed in, and a session file named after an old number keeps working exactly as before.

This surprises people who expect a rename to break their tooling, and it also means a filename is a label rather than a fact. Knowing which account is signed in where is the actual job, and it is the one our Account Manager exists to do.

Recycled numbers carry a history

The banned number refusal is the clearest evidence that the platform tracks lines rather than only accounts. A number that was used badly by a previous holder can refuse to accept an account long after that holder is gone.

That is one of the reasons the age and provenance of a line matter when accounts are acquired rather than created. Our guide on acquiring Telegram accounts covers the questions worth asking about where a number has been, and our note on spam restrictions covers the limits that attach to accounts rather than lines.

Plan the wall into the schedule

Any migration plan that signs in and changes numbers in the same sitting fails on every account it touches, all at the same step. The day long wait is per session and there is no bulk exemption, so it has to be built into the schedule rather than discovered during it.

The same applies to the mobile only restriction, which quietly rules out doing this from a desktop toolchain. Teams that run outreach at volume with Mass DMs or grow rooms with Member Adder hit both limits the first time they try to rotate identities, and the fix is always sequencing rather than software. Holding the record of which line belongs to which account is the other half of it, and that is the job Account Manager takes over. Our note on avoiding bans in cold outreach covers the rest of that discipline, and managing multiple accounts covers keeping that map straight.

Frequently Asked Questions

Will I lose my chats if I change my phone number?

No. Telegram states that you keep everything, including all your contacts, messages and media from the cloud, as well as all your secret chats on all devices. The account itself does not move, only the label the server uses to find it.

Can I change my Telegram number on a computer?

No. The desktop client answers this attempt with a message saying you can only change your phone number using mobile Telegram apps, and asking you to use an official app on your phone. The web client is the same. Do it on a handset.

Why does it say I cannot change my number right after logging in?

Because a session must be older than twenty four hours before it can start the change. The refusal says so directly and asks you to wait at least a day. The clock runs from that session's sign in, so an older session on another device may be able to do it now.

What happens if the new number already has a Telegram account?

The change is refused with a message saying the number is already in use, and Telegram's guidance is that you would need to delete that account first. Accounts cannot be merged, so decide which history you are keeping before you delete anything.

Do I need the old number to still work?

Not for the change itself, since the verification code goes to the new number. You do need to be signed in somewhere, because the operation runs from an existing session. If you are not signed in anywhere and the old line is gone, the change is not the tool for that situation.

Will my contacts know that I changed my number?

They are not messaged about it, but the protocol pushes an update meaning a user's phone number was changed, so anyone who can see your number sees the new one. People who saved your old number in their address book keep that saved entry unchanged.

Does my username change when my number changes?

No. The username is a separate field and is untouched by the operation, as are your active sessions and your cloud password. That is why a username is the safer thing to hand out in the first place.

Can I use Telegram without a phone number?

Not without a number, but you can use one that is not a SIM card. Telegram announced support for accounts using blockchain based anonymous numbers from the Fragment platform. These are purchased, publicly recorded as collectibles, and still function as the account's number.

Can I replace my phone number with an email address?

No. A login email is only a delivery channel for the sign in code, and the server refuses to configure one as a change unless an email is already set up. The account is still identified by its number.

Why is Telegram asking me whether this is still my number?

Because the server sends clients a suggestion asking users to check that their authorization number is correct and to change it if it is inaccessible. It appears when the platform thinks you may be unable to receive a code, and it is worth answering honestly rather than dismissing.