How Many X Accounts Can You Have in 2026 (The 10 Is a Phone Limit)

Search this question and almost every answer says the same thing: X allows up to ten accounts per person. That number is real, it comes from X's own documentation, and it does not mean what everyone says it means.

Here is the actual sentence, from X's help page on adding a phone number:

You can have the same phone number associated with up to 10 X accounts.

Ten accounts per phone number. X's own page about creating and managing multiple accounts contains no numeric limit at all: it explains how to add accounts on each platform and never caps them. So the honest answer to the question is the same one as on Reddit and Discord, with a twist that makes X the most permissive platform in this series on the thing that is usually hardest.

How many X accounts can you have?

No published cap on accounts per person. X's multi-account help page gives no number, and the Authenticity policy governs behaviour rather than counts.
Up to 10 per phone number, which is stated outright.
No merging, ever. X says plainly that it does not offer a way to merge accounts or migrate posts, following or followers between them, so the structure you choose is the structure you keep.

Compare that to the rest of the series, because the contrast is the useful part:

Platform	What the docs say about one phone number
X	Up to 10 accounts, stated outright
Discord	Exactly 1 account at a time, and no VOIP or landline numbers
TikTok	No published figure
Instagram	No published figure
Facebook	Moot, since one person gets one account

Two of those rows are documented and three are not, which is worth saying plainly rather than filling in with folklore. And the absence of a number is not permission: on Instagram and TikTok a shared phone number is one of the strongest links between two accounts, and it is also what recovers an account later, which makes reusing it expensive in both directions. We said exactly that in the Instagram guide and the TikTok one, and it still holds.

X is the one platform in the series where the phone number is genuinely not the bottleneck. That does not make sharing one across ten accounts a good idea, it just means the platform will not stop you.

And there is a practical catch buried in X's own phone FAQ: every account with that number attached still receives SMS for password resets and login verification. Put one number on ten accounts and every code lands on the same handset, unlabelled, which is both an operational mess and a single point of failure for ten recoveries at once. Full platform-by-platform detail is in how many accounts you can have on each platform.

So what is the real constraint on X?

Posting volume, and it is much lower than the internet thinks.

X's own limits page lists the current technical limits. It also, further down the same page, still contains a leftover line about a daily limit of 2,400 updates. That older number is the one most guides quote. These are the limits as the page states them at the top:

Action	Limit
Original posts, unverified account	50 per day
Replies, unverified account	200 per day
Direct messages	500 per day
Follows	400 per day, technical
Account email changes	4 per hour
Follow ratio kicks in	Once you follow 5,000 accounts

Three things to take from that table.

Fifty posts is the number that matters. If you plan a content operation on the 2,400 figure, you are planning against a limit that no longer describes a free account. Fifty original posts plus 200 replies is generous for a person and tight for an operation.

The limits are cumulative across everything. X states that they include actions from all devices: web, mobile, phone and API together. Using several third-party tools on one account burns the same allowance faster.

Posts are also broken into semi-hourly sub-limits, so 50 posts does not mean 50 posts in one sitting. Bursts get throttled even when the daily total is fine.

What does X actually prohibit?

The Authenticity policy, updated April 2025, is the document that matters, and it is aimed squarely at patterns rather than counts. Its headline requirement is that accounts must be authentic: you may not create, operate or mass-register accounts that are not legitimate, genuine and transparent as to their source, identity and popularity. Under that heading sit six named sub-clauses, and five of them bear directly on running a roster:

Unauthorized automation. Automated or scripted accounts that do not comply with the Developer Policy. X also notes you remain responsible for any third-party app you authorise on your account.
Fake personas. Named explicitly: stock, stolen or AI-generated profile photos, copied or stolen bios, misleading profile information used to deceive. That AI clause is the one recent addition most guides have not caught up with.
Impersonation, with a carve-out: Parody, Commentary and Fan accounts are allowed if the purpose is to discuss, satirise or share information, and if they are labelled to comply.
Multiple accounts and coordination. Coordinated inauthentic activity that artificially influences conversations is prohibited. Note the wording: the violation is the coordination, not the plurality.
Ban evasion. You may not circumvent enforcement actions.

The sixth, account compromise, is about someone else getting into your account rather than about how many you run.

X's automation rules add the precise line that defines the boundary:

You may not create and/or automate multiple accounts for duplicative or substantially similar use cases. However, automating multiple accounts for related but non-duplicative use cases is permitted.

Read that carefully, because it is unusual. X permits automating several accounts, as long as each has a genuinely distinct job. Discord's rule 14 says every account must be associated with a human. X says the opposite, provided you are inside the Developer Policy and the accounts are not clones of each other.

X gives exactly one example of an acceptable distinct purpose, and it is worth quoting because it sets the bar precisely:

For example, you may automate separate accounts to post when the Hubble Space Telescope passes over different cities, such as San Francisco or Hong Kong.

Same script, same data source, same owner, and it is fine, because each account serves a different city. That is the test: not different wording, different subject matter. Two accounts posting the same niche to the same audience in the same language fail it however differently they phrase things.

What gets a whole roster suspended at once?

One behaviour, and it is the same one as on Reddit: accounts you control interacting with each other.

X prohibits posting duplicative or substantially similar content on one account or across several you operate, and it treats engagement between your own accounts as manipulation. Liking, reposting or replying between them to inflate numbers is the clearest version, and enforcement does not stop at the account that did it.

The practical rules that fall out of that:

Never cross-engage. No likes, reposts, replies or quote posts between accounts you own, not even once, not even organically.
Never cross-post the same text. Substantially similar content across accounts is named in both the automation rules and the spam policy.
Give each account a different job, not a different audience for the same job. Two accounts posting the same niche in the same language are duplicative even with different wording.
Do not build a roster to amplify one account. That is the textbook definition of coordinated inauthentic activity.

What does the warm-up look like?

X does not publish ramp guidance, and the shape below is what operators converge on. Numbers stay well under the published ceilings because the ceiling is not the target:

Days	Posts	Replies	Follows	What you are building
1 to 3	0 to 1	2 to 5	5 to 10	profile completeness, some reading
4 to 7	1 to 2	5 to 15	10 to 20	a reply history that looks like a person
8 to 14	2 to 4	15 to 30	20 to 40	topical consistency
15 onward	your real cadence, under 50	under 200	under 400	normal operation

Two X-specific notes. Replies are the cheap currency here, the way comments are on Reddit: they build history faster than posting into an empty timeline does. And following is the fastest way to look automated, because 400 a day is a technical limit while "aggressive following" is separately prohibited behaviour. The technical limit is not permission.

Where do proxies help on X, and where not?

X sits closer to Reddit than to Facebook. There is no payment instrument on a normal account, no identity verification beyond the phone, and the web client is first-class, so the connection and the browser carry more weight than they do on a mobile-first platform.

Where an address does real work:

One identity, one stable exit. A roster whose accounts log in from one address is a roster with a shared signal, and a static address per account is the shape that fixes it.
Not moving mid-session. A logged-in session that changes country is its own flag, which is why a rotating pool is the wrong tool for accounts you operate rather than scrape.
Regional work, where the timeline and the trends you need to see are country-specific.

Where it does nothing at all:

Cross-engagement. The strongest signal on this platform is two of your accounts touching the same post, and that is visible no matter where either one connects from.
Duplicative content. Same text, different address, same violation.
The phone number, which on X is the least of your problems anyway since one covers ten accounts.
Automated following. Aggressive following is a behaviour rule, not a network one.

The honest summary: on X the proxy handles the account-to-account technical link, and the two rules most likely to end a roster are things you do inside the app. Per-account cost of the isolation layer is in what a multi-accounting stack actually costs, and the checks for a new address are in how to test a proxy before you buy it.

What kills X accounts, in order of frequency

Cross-engagement between your own accounts. The single most reliable way to lose all of them together.
Duplicative posting across accounts. Named in two separate policies.
Aggressive following, usually by someone treating 400 a day as a target. Automated posting about trending topics is prohibited by name in the same ruleset, and it is the other half of this mistake.
AI or stolen profile photos, now explicitly listed under fake personas.
Replacing a suspended account, which is ban evasion and converts one loss into several.
Automation outside the Developer Policy. Automation is allowed here, which makes it tempting to run it through unofficial tooling that is not. The fingerprint and the address matter, but the tooling choice matters more.

FAQ

How many X accounts can you have?

X publishes no limit on accounts per person. The commonly quoted ten is the number of accounts a single phone number can be attached to, which X states directly. Its actual page on managing multiple accounts contains no number at all.

How many X accounts can one phone number have?

Up to ten, per X's own help documentation. That makes X the most permissive platform in this series on phone numbers: Discord allows exactly one account per number and rejects VOIP, while Instagram and TikTok publish no figure but treat a shared number as a strong link between accounts.

How many posts can you make per day on X?

Fifty original posts and 200 replies per day on an unverified account, plus 500 direct messages and 400 follows. The older figure of 2,400 updates a day still appears further down X's own limits page, which is why so many guides repeat it.

Does X allow multiple accounts?

Yes. What it prohibits is coordinated inauthentic activity, duplicative or substantially similar accounts and content, and ban evasion. Accounts with genuinely distinct purposes are explicitly acceptable: X's own example is automating separate accounts that post when the Hubble Space Telescope passes over different cities.

Can I automate several X accounts?

Yes, unusually. X's automation rules permit automating multiple accounts for related but non-duplicative use cases, provided you comply with the Developer Policy. What is prohibited is duplicative use cases, bulk unsolicited DMs, aggressive following or unfollowing, and bulk automated reposting.

Will X ban all my accounts if one gets suspended?

It can, when the accounts are linked and the violation involves coordination. Cross-engagement and duplicative content are the behaviours that make a single suspension spread, and creating a replacement after a permanent suspension is itself a violation.

Can two X accounts like each other's posts?

Not if you control both. Engagement between accounts you operate is platform manipulation, and it is the most common cause of a whole roster going down together.

Do I need a separate proxy for each X account?

For accounts that matter, yes, one static address each. But it is not the top risk on this platform: cross-engagement and duplicate content both outrank it, and neither is a network problem.