Twitter Rate Limits: What X Caps, and What It Never Published

X's help page promises an error message telling you which limit you have hit. In practice the wording varies: on the web it tends to be a blunt notice that you have hit a rate limit and should wait and try again, while the mobile apps can be vaguer, sometimes a generic failure screen. X does not document this copy, so recognise the state by the behaviour: the timeline stops filling and profiles load empty while your connection is fine.

Separate this from the other two ways X can stop you. A suspension or a locked account arrives with a notice and an appeal path. A rate limit arrives with no such notice, because nothing has happened to your account: you asked for more than that window allowed. Outages can look the same, and X says limits may be temporarily reduced during heavy site usage, with an update on its status site, so check that before assuming anything.

Almost every figure circulating for reading limits comes from one weekend. On 1 July 2023 Elon Musk posted that reading was being temporarily capped at 6,000 posts a day for verified accounts, 600 for unverified and 300 for new unverified ones. Within hours he posted 8,000 / 800 / 400, then 10,000 / 1,000 / 500. The stated reason was "extreme levels of data scraping & system manipulation".

Two things about those numbers matter now, in September 2026. They were announced in posts rather than documentation, and they were explicitly temporary. The harshest version lasted only hours, and no equivalent daily reading cap has been announced since with the same clarity. A page telling you today that you can read 600 posts a day is quoting a temporary measure from three years ago.

One surface from that weekend keeps getting quoted alongside the numbers: whether X is readable when you are logged out. Access was walled off on 30 June 2023 and partly restored within days. X's help page says public posts are visible to anyone, with or without an account, but it does not spell out what a logged-out visitor can actually browse, so nobody can state the current position without saying when they checked it. A link that opens a login prompt is that surface, not a limit on your account.

The figure quoted everywhere for posting is 2,400 posts a day, counted in half-hour blocks rather than as one bucket that empties at midnight. For an unverified account that figure is out of date. In May 2026 X cut those accounts to 50 original posts and 200 replies a day, a change Engadget and Social Media Today both traced to a revised help page, and the new allowances are still broken down across 30-minute intervals. The 2,400 line survives elsewhere on the same page, undated as ever and assigned to no tier. Coverage reads it either as the ceiling for verified accounts or as a leftover. X does not say which and states no separate figure for verified accounts, so check the live article before building on either number. Verified here means a checkmark, which X's Premium page includes from the Premium tier up, not in Basic. The half-hour blocks are the part that catches people out. Someone live-posting a football match and replying to everyone in the thread can spend a free account's allowance inside the first half.

Until May 2026 X's page said reposts are counted as posts. That sentence went in the rewrite, and it never mentioned quote posts, so how either counts now is not documented. On unverified accounts replies now have a separate allowance of their own. A twenty-part thread is twenty posts, and X does not say which allowance thread parts draw on. Accounts go quiet for plenty of reasons unrelated to ceilings, and the useful question is rarely how much the system tolerates. It is what a steady cadence does to the people already following you, ground covered in how Facebook followers respond to a weekly posting routine.

Replies are the cheapest thing to produce and the fastest way to burn a posting quota. They are also, on most networks, the part of the work that pays back hardest, as when commenting on Facebook beats posting outright argues.

Following has two brakes. The first is daily: X's help pages list 400 follows a day for every account, still there in September 2026. The second is structural. An account can follow up to 5,000 others regardless of its own follower count, and past that further following is governed by a following-to-follower ratio X has never published precisely. Both figures sit undated on the pages hosting them, so the only date you can attach to either is the day you looked.

Aggressive follow and unfollow cycling is policed twice over. The counter stops you at the daily number, and mass follow churn is separately prohibited under X's authenticity rules. The first is a wait. The second can cost the account.

X's help page lists a daily cap on Direct Messages, 500 a day with no tier named as of September 2026, down from the 1,000 it showed in 2021, so the live help article beats anything a blog reproduces. Who you can message also depends on the other side's settings: X says you can message anyone who follows you, and beyond that the recipient has to have opted in to messages from anyone, or from verified accounts. Treat any specific DM number as dated unless the source says when it was checked.

A failed message is not always a limit. If the recipient accepts messages only from accounts they follow, your message fails for reasons unrelated to volume, and the error may not say which.

X maintains a documented rate limit table for its developer API, listing how many requests per window each endpoint allows. The consumer app gets one undated page of daily ceilings, with no per-interval figures and no revision history, which is how May 2026's cut to posting arrived without an announcement. That page gives its reason as reducing strain and downtime, and the follow limit page adds preventing spam and manipulation. Neither explains why one side gets a table and the other does not.

What can be described honestly is the shape. X's pages set a lower posting allowance for unverified accounts, calculate the follow ratio per account, and warn that limits may be reduced during heavy usage, which is one reason two people doing the same thing on the same evening can get different results. If you were pushing volume because growth had stalled, a ceiling is a reasonable moment to look at the options for building an X account rather than at how much the system will absorb.

The monetisation angle drives a lot of the volume, and the arithmetic is specific to each platform and its payout terms, which is the point of a breakdown like what posting actually pays on Facebook.

Waiting clears it. The window rolls over, the counter resets, and the honest answer to "how do I remove the limit" is that you outlast it. X's help pages give only rough guidance on how long: a few hours after a posting limit, a day after the daily follow limit, an hour or so after following too many accounts too quickly. For reading nothing is published and the app shows no countdown, so you learn it by trying again later.

Several popular fixes are not reported to do anything. X says its posting, following and messaging limits count actions from all devices, so changing device does not help there. For reading it does not publish what the counter is attached to, and logging out and back in is not reported to clear it. Clearing the app cache does not reset a counter held on the server. A VPN or a different IP address is not reported to make any difference either.

Two things genuinely make it worse. Third-party clients and scheduling tools spend quota too: X says its limits include actions from all devices, including the API, and that people using several third-party apps reach the API limit more quickly, so an account that feels idle can arrive at its ceiling untouched. And the account-age tier described in the July 2023 reading-cap posts put new unverified accounts at the bottom of it, so a fresh account bets on undocumented behaviour rather than fixing anything.

Since the published page carries no dates and changes without notice, the only accurate table is the one you build. Write down the date, the time, what you were doing and how long the block lasted. Three entries will tell you more than any figure you can look up.

It lasts until the current window rolls over. For the consumer app X gives only rough guidance: a few hours after a posting limit, a day after the daily follow limit, and nothing for reading. The app shows no countdown, so there is no way to see how much time remains. If a loading error survives an untouched night, a network change and a different device, you are probably looking at an outage or an account restriction rather than a rate limit.

You cannot remove it, and no setting exposes it. It is applied on X's side rather than on your device, so nothing you change locally affects it. Waiting is the whole fix. The lower posting allowance since May 2026 applies to unverified accounts, and a checkmark comes with the Premium tier and up, but X states no posting figure for verified accounts and has not published a current figure for consumer reading limits since the temporary caps announced in July 2023, so treat any promised number as unverified.

Because your account asked for more than the allowance for that action inside the current window, usually by scrolling heavily, replying in fast bursts, following many accounts in one sitting, or running a third-party tool that makes requests in the background. The message is about volume in a time window, not about the content of what you posted. A rate limit on its own comes with no account notice and asks for no appeal, though aggressive following or engagement can separately lead X to limit the account.