Every reply you send comes out of a fixed daily allowance, and most people find out where the ceiling is by running into it. X publishes the numbers — but it publishes them on a page that also carries an older figure, which is why the limit you read about online rarely matches the limit you hit. Here is what X documents, what counts against it, and how to pace a reply routine that never gets close to the wall.
X's limits page states that unverified accounts get 50 original posts and 200 replies per day, broken down further into smaller limits at semi-hourly intervals. The same page's older paragraph still cites 2,400 updates per day. If you hit the limit, you get an error message naming the limit you hit, and the allowance returns after the time window elapses. Plan against the lower number and the semi-hourly pacing, not the legacy one.
The limits X documents today
These are the current technical limits listed on X's own About X limits page. They apply per account, not per device — X states that the limits "include actions from all devices, including web, mobile, phone, API, etc."
| Action | Documented limit | Who it applies to |
|---|---|---|
| Replies | 200 per day | Unverified accounts (the only tier the page names) |
| Original posts | 50 per day | Unverified accounts |
| Direct messages | 500 per day | All accounts |
| Following | 400 per day, then account-specific ratios after you follow 5,000 accounts | All accounts |
| Account email changes | 4 per hour | All accounts |
Two things about that table matter more than the numbers. First, the reply allowance is the largest single action budget on the list — four times the post allowance — which tells you where X expects conversation to happen. Second, the word "unverified" is doing real work: the page documents limits for unverified accounts and does not publish a separate figure for Premium subscribers, so do not treat any specific premium reply number you read elsewhere as official.
Why you will see a different number quoted
The same page closes its limits section with a legacy sentence: "The post limit of 2,400 updates per day is further broken down into semi-hourly intervals." Read the page end to end and you have two conflicting post limits — 50 in the current list, 2,400 in the older paragraph — plus an explanation of what happens when you hit one.
This is not a trap so much as a documentation artifact: the page has been revised over the years and the historical paragraph stayed. Practically, the honest reading is:
- Treat 200 replies / 50 posts as the working limit. It sits at the top of the page under "Current X limits," and it is stated in the present tense.
- Treat 2,400 as history. It describes the pre-rate-limit-reform ceiling and does not match the current list above it.
- Do not build a tool that assumes the larger number. Any scheduler or drafting workflow that plans 2,400 posts a day is planning for a limit that a fresh account will hit in its first hour.
If you want the same discipline for policy questions, the 2026 automation rules breakdown follows the same rule: quote the current page, flag the ambiguous line, and never round up in your own favor.
What counts against the reply allowance
The limit is on actions, not on how you made them. A reply sent from the web app, a reply sent from the mobile app, and a reply sent through a third-party client all draw from the same 200. X is explicit that API requests from third-party applications are tracked against limits too, which is why a scheduling tool plus manual replying can exhaust a budget faster than either alone would.
| Action | Counts toward | Notes |
|---|---|---|
| Reply to someone's post | Reply allowance (200/day) | The main line item for anyone whose strategy is conversation-led |
| Reply that also mentions other accounts | Reply allowance | A mention inside a reply does not create a second action |
| New post, quote post, thread entry | Post allowance (50/day) | A ten-post thread spends ten of the fifty |
| Repost | Post allowance | Cheap engagement, but not free — it is an update action |
| Draft you never posted | Nothing | Drafts are local until you press post, which is why draft-then-review tools spend none of the budget |
| Reading, searching, liking | Separate limits | Not part of the post or reply allowance |
That table is also the argument for review-first drafting. A tool that proposes fifteen replies and posts none of them until you approve the ones worth sending consumes the allowance exactly where a human would have spent it — see how to automate replies without spamming for the workflow side of that split.
The semi-hourly breakdown is the part people forget
X states that the daily allowance is "further broken down into smaller limits for semi-hourly intervals," but does not publish the per-interval numbers. That single sentence explains the most common confusing experience on the platform: you have replies left according to your own count, you send one, and you get an error — because you spent the day's allowance in a burst rather than across the day.
The practical translation, reading only what X documents:
- A daily budget is not a burst budget. Any allowance divided into thirty-minute windows rewards a steady habit and punishes a forty-reply session.
- Clearing the error is passive. X says time-based limits reset after the period elapses — "try again in a few hours after the limit period has elapsed." There is no button, no appeal, and no reason to keep retrying.
- Heavy site-wide usage can reduce limits temporarily. X says limits may be temporarily reduced during periods of heavy usage and will post updates on its status site. If your number suddenly looks different with no change in your behavior, check there before assuming an enforcement action.
What happens when you actually hit it
Three documented behaviors, in order of how often they are misread as a penalty:
- You get an error message naming the limit. X states that it tells you which limit you hit. Read it literally: "over the daily limit" is a clock problem, not a moderation problem.
- The allowance returns with time. For time-based limits — direct messages, posts, replies, email changes — X's stated remedy is to wait for the window to elapse.
- Nothing about your account changes. Hitting a documented technical limit is not the same as a rules violation. Rules pages are about behavior: search filtering, spam folds, and suspension live on the automation rules and authenticity policies, not on the limits page.
If what you are seeing is not an error message but silence — a reply that posted and then seems invisible — you are looking at a different mechanism entirely: ranking, spam folds, or search filtering. That case is diagnosed step by step in why your replies aren't showing on X, and it is worth reading before you change anything about your reply volume.
Pacing a routine that never gets near the ceiling
For almost every account, the reply limit is not the binding constraint — attention and quality are. The number still matters, because the semi-hourly breakdown turns a badly timed burst into a hard stop mid-conversation. These bands are a planning convention built on the documented 200/day allowance, not an X-published schedule, and they assume a human is reviewing each reply:
| Session length | Replies per session | Sessions a day | Daily total |
|---|---|---|---|
| 10 minutes | 3-5 | 2 | 6-10 |
| 15 minutes | 5-8 | 2-3 | 10-24 |
| 30 minutes | 10-15 | 2 | 20-30 |
| 60 minutes | 20-30 | 1-2 | 20-60 |
Even the heaviest band lands at under a third of the documented allowance — which is the point. The limit is a safety rail, and a routine that treats it as a target has already optimized for the wrong variable. Two tools on this site make the pacing concrete rather than theoretical: the reply cadence planner turns your available minutes into a session plan and a four-week ramp, and the reply quality checklist grades a draft before it spends one of your 200. When the session itself needs ideas rather than editing, the reply idea generator produces starter angles for six common post types. If your goal is the broader system rather than the arithmetic, the engagement strategy guide covers which conversations deserve the budget in the first place.
Where the limit meets the automation rules
The limits page and the automation rules answer different questions, and confusing them is how accounts get into trouble. The limits page says how many actions you get. The automation rules say which automated actions are allowed at all — and for replies the bar is behavioral, not numeric. Among the conditions the rules set: automated replies or mentions require that the recipient has opted in or clearly indicated intent, one automated reply per user interaction, and a clear way to opt out. Sending automated replies based on keyword searches alone is named as not permitted. Scripting the X website instead of using the API is named as a suspension risk.
So a reply tool can be perfectly inside your 200/day allowance and still be a bad idea. The safe pattern is the one X's rules imply: automation drafts, a human reads and posts, one reply per interaction, no keyword-triggered outreach. That is the split we build to, and it is documented further in what developers can build under the X API rules.
Five checks before you blame the limit
- Read the error text. It names the limit. A daily post limit, a semi-hourly interval limit, and a rate-limit message from a third-party tool are three different problems.
- Count your bursts, not just your day. If your replies cluster into one or two sessions, you are hitting the interval ceiling long before the daily one.
- Include tools in the count. Anything posting on your behalf draws from the same allowance, and X tracks third-party API requests against it.
- Check the status site when the number changes without you. Limits can be temporarily reduced during heavy usage.
- Separate visibility from volume. An error means a limit; silence usually means ranking, a spam fold, or search filtering — and adding volume makes the second case worse, not better.
None of this requires a spreadsheet. It requires knowing there are two ceilings — one for the day, one for the half hour — and that the allowance is meant to be spent in a habit, not a burst. The cadence planner will do the arithmetic if you would rather spend your time on the replies themselves.