Stillcode › Two-factor authentication › X (Twitter)
What X (Twitter) supports, the caveat it records against its own setup, and what happens to those codes when the phone they live on stops existing.
These are the second factors X (Twitter) offers on x.com. Which ones you
see can depend on your plan and your country;
what each of the seven actually costs you is set out once.
| Method | What it is | |
|---|---|---|
| Authenticator app (TOTP) | Supported | Computed on your own device; nothing is sent to produce it. |
| Hardware security key | Supported | A physical key you tap; the one option phishing does not beat. |
| SMS text message | Supported | Texted to your number, so your carrier is part of the lock. |
X (Twitter)'s own caveat, as recorded in the directory: SMS only available on select providers and for X Premium members only.
Data sourced from 2FA Directory by 2factorauth. Snapshot 2026-09-24.
X (Twitter) offers both SMS and an authenticator app. They are not equivalent — a texted code depends on your mobile carrier and survives no longer than control of your phone number, while a generated code never travels. If both are enabled, the account is only as strong as the weaker one, because an attacker picks.
A hardware security key is also accepted. It is stronger than any code, because a code can be typed into a convincing fake page and a key cannot. The usual arrangement is a key as the primary factor and an authenticator app as the backup that fits in a pocket.
Of the fifty services on this site, eighteen carry a caveat of the service’s own in the directory,
and X (Twitter) is one of them. Eleven of the fifty accept exactly this combination, so the same
decision comes up on ten other
services here. Among the eight services filed under social,
three accept a hardware security key —
X (Twitter) among them.
The directory files X (Twitter) under social, records three of the seven second
factors it tracks, and points at instructions published at
help.x.com/en/managing-your-account/two-factor-authentication. A second document on the same host, …/issues-with-login-authentication,
covers not being able to complete sign-in.
X (Twitter) is x.com, and the same account also signs you in at
twitter.com. Two-factor authentication
is a property of the account, not of the address you happened to type — switch it on once
and every one of those is covered. That also means losing the second factor loses all of them at
once.
X (Twitter)'s own instructions: X (Twitter) — two-factor authentication — linked, never copied, because a stale menu path here locks people out.
X (Twitter) publishes a page for exactly this situation: what to do when you cannot complete two-factor sign-in. ⭐ Read it before you need it — the steps almost always require something you have to set up in advance.
Background: how the codes work · what still works when the phone is gone.
An iPhone, iPad and Mac authenticator for these codes that makes no network calls at all. What is free and what Pro adds. Get it on the App Store