Twitter Rate Limits: Every Cap X Enforces and What Trips Them

Most people meet X's rate limits by accident, in the middle of doing something ordinary, with an error message that does not say which limit they hit or how long it lasts. The limits are real, several are unpublished, and the one that catches people is almost never the one they were watching.

Here is the full picture.

The caps X publishes

These appear on X's own limits page and are the ceilings, not the thresholds where trouble starts:

Premium and Premium+ carry higher ceilings on most of these. X does not publish the exact numbers for every tier, and they have changed more than once.

The caps X does not publish

This is where accounts actually get caught:

Hourly throttles under every daily cap. Almost every action has a rolling hourly limit as well as a daily one. You can be well under 500 DMs for the day and still be blocked because you sent too many in the last sixty minutes.

Read limits. X has enforced caps on how many posts an account can view per day, most visibly during 2023. They come and go, and unverified and brand-new accounts get the lowest ceilings.

Behavioural throttling. The most important one and the least visible. A spam classifier watches patterns rather than counts, and it will throttle an account far below every published number if the behaviour looks automated. Nothing tells you this has happened. Your actions just start failing or quietly stop reaching people.

Rolling windows, not calendar days

Almost every limit runs on a rolling window. If you use your daily DM allowance by 4pm on Tuesday, you do not get a fresh allowance at midnight. Capacity returns gradually from about 4pm on Wednesday as your earliest messages age out.

This single detail explains most "I waited and it still will not let me" complaints. It also explains why steady pacing beats batching: an account that trickles always has headroom, while an account that empties its allowance in an hour locks itself out for most of a day.

Speed trips limits before volume does

If you take one thing from this: how fast you act matters more than how much you do.

Forty follows across a day is unremarkable. Forty in ten minutes is a machine. The same is true of replies, likes and DMs. Most restricted accounts were not doing anything against the rules, they were doing an ordinary amount of it in an unnatural shape.

The signals that get weighted hardest:

• Bursts. Many actions in a short window.
• Uniformity. Identical text, or perfectly even intervals between actions. Real people are irregular.
• One-directional activity. Lots of outbound contact with strangers and few replies coming back.
• Account age. New accounts get a fraction of the tolerance. This is the most common aggravating factor by far.

What the safe rate actually looks like

For DMs specifically, the gap between published and sustainable is dramatic. X publishes 500 a day. From what we measure across accounts sending outreach, the rate an account holds without tripping a restriction is roughly 30 a day verified and 7 a day unverified.

That is not a typo. The published cap is where X stops you; the safe rate is where X stops noticing you. Verification is worth roughly four times the throughput, which is the strongest argument for it if you send at any volume.

Our DM limit calculator turns that into a starting number and a seven-day ramp for a specific account.

If you have already hit one

1. Stop entirely for a few hours. Not slow down. Continuing to hit a limit is what escalates a throttle into a suspension.
2. Work out which limit it was. Follows, DMs, posts and reads have different windows, and guessing wastes a day.
3. Restart at roughly half. Whatever rate triggered it, half it for a few days before creeping back.
4. Check nothing worse happened. Repeated limit-hitting sometimes comes with a visibility restriction you cannot see from your own account. Our shadowban test checks whether your account and posts still appear in X's search index.

Scaling without fighting the ceiling

The per-account ceiling barely moves. You can improve it with verification, account age and a healthy reply rate, but you cannot multiply it, and every hour spent trying is an hour spent risking the account.

What does scale is running more accounts at a sustainable rate each. Ten accounts sending comfortably beats one account sending recklessly, and it fails gracefully: one restricted account is an inconvenience rather than an outage.

Short version

X publishes a handful of daily caps and enforces many more it does not publish, including hourly throttles and behavioural throttling that ignores the published numbers entirely. Windows roll rather than reset at midnight. Speed and uniformity trip limits before totals do, and new accounts get the least room. For DMs, plan around roughly 30 a day verified and 7 unverified rather than the advertised 500.