What are X (Twitter) daily action limits per account?

X enforces tiered limits: new accounts can send roughly 400 to 500 tweets or follows per day, while verified accounts reach higher thresholds of approximately 2,400 actions daily. Direct messages are capped at roughly 500 per day. Following is limited to around 400 accounts per day, with a hard follow ratio cap of roughly 10:1 followers-to-following. Exceeding these limits triggers temporary action blocks that reset after 24 hours.

What happens when you hit a Twitter rate limit?

When an account exceeds its action limit, X temporarily blocks the specific action type for that account only. Tweet, follow, or like buttons become unresponsive, and API calls return HTTP 429 Too Many Requests responses. The block typically lasts 15 to 60 minutes for first offenses and up to 24 hours for repeated violations. Additional actions during the block period extend the cooldown.

Do rate limits differ between the X app and X API?

Yes, and significantly. The X API operates on a per-endpoint rate-limit system with tiers based on subscription level. Free tier gets roughly 500 tweets posted per month across 3 apps, Basic tier allows 3,000 tweets per month and 10,000 reads, and Pro tier raises to 300,000 tweets per month and 1,000,000 reads. App-level limits are typically more forgiving than API limits, but the API limits are clearly documented while app limits are intentionally opaque.

How to Manage X (Twitter) Rate Limits Across Multiple Distribution Accounts?

X (Twitter) rate limits are per-account caps on the number of actions an account can perform within a given time window: posting tweets, following, liking, retweeting, and sending direct messages. For multi-account distribution, managing rate limits means pacing each account's activity below these thresholds and scheduling actions across accounts to distribute volume without triggering temporary suspensions. Unlike some platforms where rate limits are guidelines, X enforces them programmatically with hard blocks.

X's rate limit system operates at multiple levels: per-account, per-app, per-device, and per-IP. X's official developer documentation details the API-side limits explicitly, but the in-app limits that matter for content distribution are less transparent and enforced more aggressively for unverified accounts.

What Are the Actual Action Limits Per Account?

X does not publish exact action limits for the consumer app, but the community has reverse-engineered consistent thresholds based on account age and verification status. Hootsuite's 2025 Twitter algorithm and limits guide synthesizes community data alongside official statements to map the tiers.

New accounts created within the last 90 days face the strictest limits: approximately 400 follows per day, 400 tweets per day (including retweets and quote tweets), and roughly 500 direct messages per day. The follow-to-follower ratio is also enforced more strictly for new accounts.

Established accounts aged over 6 months with consistent activity history operate under approximately 2 to 2.5 times these thresholds. Verified accounts enjoy significantly higher ceilings at roughly 2,400 tweets per day and 1,000 follows per day.

The following ratio is a hard cap distinct from daily limits. An account cannot follow more than roughly 10 accounts for every 1 follower it has until it crosses approximately 5,000 total follows. At that point, the ratio softens but daily follow limits still apply.

How Should Multi-Account Operators Pace Actions?

For multi-account X distribution, the strategy is not to push each account to its limit but to keep each account well below the danger zone. Running accounts at 60 to 70 percent of their estimated ceiling preserves headroom and prevents accidental blocks from minor volume spikes.

Action distribution across time is as important as total volume. An account that posts 20 tweets in a five-minute burst is flagged differently than an account that posts 20 tweets across 12 hours. The burst pattern looks like automation. The spread pattern looks human.

Multi-account scheduling should stagger accounts so that no single IP, device, or time window shows a coordinated pattern. If ten accounts all post at 9:00 AM, the volume pattern alone raises signals, even if every account stays within individual limits.

How Do API Limits Affect Distribution Tools?

If you use X's API to manage multi-account distribution, the API rate limits are the binding constraint. The free API tier permits only 500 posts per month across all apps associated with a developer account. At the Basic tier, 3,000 posts per month and 10,000 reads. The Pro tier expands to 300,000 posts per month and 1,000,000 reads.

These limits create a structural ceiling on API-based multi-account distribution. Operating 10 accounts at even 2 tweets per day consumes 600 tweets per month, immediately exceeding the free tier. At 5 tweets per day per account, you need 1,500 per month, which requires the Basic tier. The API is not priced for high-volume posting at scale.

For distribution at scale, native app-based posting bypasses API rate limits but introduces different constraints around device management and behavioral authenticity. This is where real-device infrastructure provides an advantage: each account posts natively from its own physical phone, operating under app-level limits that are higher and more forgiving than API limits.

What Causes Temporary Suspensions Beyond Rate Limits?

Rate limits are algorithmic caps. Temporary suspensions are enforcement actions, and they are often triggered by signals beyond raw volume. Content similarity across accounts, IP and device fingerprint sharing, and pattern-recognizable scheduling are all suspension triggers that operate independently of rate limits.

An account well within its daily follow limit can still receive a suspension if its follow requests are accepted at an abnormally low rate. An account under the tweet limit can be flagged if every tweet contains the same external link. Rate limit compliance is necessary but not sufficient for account safety.

How Conbersa Manages X Rate Limits at Scale

We built Conbersa to distribute X content through real-device infrastructure where each account operates from its own physical phone with its own network connection. Our AI agents pace actions below each account's rate limit threshold, stagger scheduling across accounts to avoid coordinated activity patterns, and post natively through the X app rather than through API calls. This means multi-account X distribution operates under the more forgiving app-level limits rather than the tightly constrained API limits, and each account's activity looks human-paced and behaviorally independent.