How to change your phone number on X (or remove it)

#Quick answer

To change your phone number on X (formerly Twitter), open Settings and privacy, go to Your account, then Account information, then Phone. On the web, click Update phone number, enter your password, type the new number, and enter the code X texts you. In the mobile apps the screen sits under Settings and privacy, then Account, then Phone number, where Update number and Delete number are both options. The change only takes effect once you enter the SMS code.

Last updated: September 2026

#TL;DR

The taps take a minute. Everything expensive about this sits around them: your phone number is one of only two ways back into a locked account, X allows exactly one number per account, and the platform will quietly detach a number it thinks you no longer own. Every video tutorial covers the taps. Below are the steps plus the five things that actually go wrong, all of them documented on X's own help pages.

#How to change your phone number on X, step by step

On the web

1. Click More in the left sidebar, then Settings and privacy.
2. Open Your account, then Account information.
3. Click Phone.
4. Under your current number, click Update phone number.
5. Enter your password and click Next.
6. Type the new number and click Next. No country code or leading zero is needed, because X handles those.
7. X texts a code. Enter it in the Verification code box and click Verify.

On iPhone

1. From the navigation menu, tap Settings and privacy.
2. Tap Account.
3. Tap Phone number, then select Update number.
4. Follow the keypad prompt to enter the new number, then confirm the code X sends.

On Android

1. Tap the navigation menu icon or your profile icon, then Settings and privacy.
2. Tap Account, then Phone number.
3. Follow the prompt to enter the new number and verify it by SMS.

Adding a number for the first time uses the same screen. If your account has never had one, the button reads Add instead of Update, and X asks for your password before it shows you anything (X Help, read 2026-09-27).

One quirk worth knowing: if the SMS never lands, the web flow can sometimes offer a voice call to read the code out instead. X documents this as situational rather than guaranteed, but it is the first thing to try when a carrier is eating the text.

#How to remove your phone number, and what stops working

On the same Phone number screen, tap Phone number, choose Delete number, then confirm with Yes, delete. That is the whole flow, and it is faster than most people expect, which is exactly the problem.

Four things depend on that number:

So the order matters. Check that the email on the account is one you still control before you delete the phone number, not after. Removing both recovery routes in the same week is how accounts become unrecoverable, and X is blunt that without access to either one it cannot keep troubleshooting.

If your reason for pulling the number is privacy rather than security, there is a middle option. Under Settings and privacy, Privacy and safety, Discoverability and contacts, you can keep the number on the account for recovery while switching off the toggle that lets people who have it find you. That separates "X can reach me" from "my contacts can identify me," which is usually the actual goal.

#One number per account, ten accounts per number

This pair of rules confuses people running more than one account, so it is worth being exact about both.

An X account holds exactly one phone number. X's FAQ says there is no option to attach two or more, and it calls out dual SIM devices specifically: you still pick one number (X Help, read 2026-09-27).

A phone number can sit on up to 10 X accounts. X documents the cap, and adds that every account holding your number still receives its own SMS messages for password resets and login verification.

For anyone running a brand account next to a personal one, that second rule is the useful one: you do not need a burner SIM per account. It also has a side effect nobody mentions. Ten accounts sharing one number means ten sets of security texts arriving at one handset, and any of those messages can trigger a reset on an account you forgot you had. If you are at that scale, switching between X accounts covers the 10-account limit on the app side, and the two limits together are the real ceiling on how many accounts one person can sensibly run.

#When the verification code never arrives

This is the single biggest reason a phone number change stalls, and the fixes are boringly mechanical.

• Unblock 40404. X has run a notice on its own phone number FAQ saying that people who previously blocked SMS from the 40404 shortcode need to unblock it before requesting a code again. Anyone who ever silenced X's texts by blocking the sender is now invisible to the verification system.
• Wait two minutes before retrying. X's own 2FA guidance asks for at least that before trying again, because requesting a second code often invalidates the first and resets the clock.
• Check the phone is actually online. Airplane mode, no signal, or a data-only eSIM will all fail silently.
• Try the voice call on the web flow if SMS keeps failing.
• Carrier filters. Some carriers and prepaid plans block shortcode traffic entirely on cheaper plans. A number that has never received a shortcode message from anyone is the suspect.

If the code arrives but the account still rejects it, you are usually looking at a clock problem on an authenticator app rather than the SMS path, which is a different fix.

#"Already associated with another X account"

You type a new number, and X says it belongs to somebody else. Almost always that is true, and it does not matter.

Phone numbers get recycled by carriers. The person who had yours before may have used it on X, and X's FAQ says the leftover record only means outdated information still exists in the system. It explicitly states that the previous owner does not get any access to an account you create with that number. When the error blocks a new signup rather than an update, X's suggestion is to register with an email address instead and attach the phone later.

#The notification nobody expects: a reclaimed number

Here is the one that arrives out of nowhere and reads like a hack.

X sends a phone number reclaimed notification when it gets signals that the number on your account may now belong to someone else. It detaches the number and tells you. Per X's FAQ, the trigger is a combination: the account has been inactive for 45 or more days, and that number is added to a new account whose owner verifies it.

Read that carefully, because it is a real risk for anyone running dormant accounts. A parked handle you have not opened in two months can silently lose its phone number to whoever the carrier gave your old digits to. If the email on that account is also stale, the account has just lost both recovery routes without a single login attempt from anyone. Dormant accounts are worth a quarterly pass for exactly this reason, and if one of yours has already gone sideways, recovering a hacked X account covers the escalation routes that remain.

#Before you swap phones

X's own advice for changing your number or device goes beyond the settings screen, and it is sensible: wipe the old handset, pull or wipe any SD card, and revoke access for apps you connected using the old phone.

That last one is the one people skip. Tokens issued to a third-party app keep working after you change your number, your password, or your handset, because they are not tied to any of those. The list lives under Apps and sessions, and reviewing your X connected apps walks through what each permission actually allows. Do it on the same visit as the number change, while you can still remember which tool you granted access to in 2023.

#Bottom line

Settings and privacy, Your account, Account information, Phone, password, new number, SMS code. The mechanic is identical on every surface and takes under two minutes.

The part worth slowing down for is the accounting around it. One number per account and up to ten accounts per number set your real limits. Deleting a number closes a recovery door, so confirm the email first. Missing codes are nearly always a blocked shortcode or an impatient retry. And a dormant account can lose its number to the 45-day reclaim rule without anyone doing anything wrong.

One habit ties all of this together: make account-level changes yourself, in a browser you control, rather than through a tool that holds your session. That is the design X-Autopilot starts from. It runs in your own logged-in browser on your Mac, so the session cookie never leaves the machine and there is no delegate account or shared cloud IP pool in the path, which is a smaller detection surface than cloud schedulers rather than a guarantee of any kind. Browser-driven automation is not a sanctioned route under X's automation rules, and that is worth knowing before you point any tool at an account whose recovery number you just changed.