X (Twitter) Audience Engagement Forecast Calculator

1. Pick a recent sample of your own posts, such as the last 28 days. Add up the engagements on them and enter the total with the number of posts.
2. Enter the plan: posts per day and the number of days.
3. Add the optional sample figures for the engagement rate, the split by type and the posting-rate check. Then read the projection and the verdict.

What each result tells you:

An X audience engagement forecast is an estimate of the total engagements a set of future posts will receive. This page builds it from one measured number: your own average engagements per post.

The X developer documentation lists engagements as a post metric in its own right, next to likes, reposts, replies, quotes, bookmarks and impressions. It marks engagements, link clicks and profile clicks as non-public, which means only the account owner sees them. Use the engagements total from your own analytics, and do not rebuild it from likes alone.

The forecast is a projection in the plain sense: past average times future volume. X publishes no engagement rates by account size, format or topic, so the page contains none. It suits content planners, social media managers and creators who must put an expected number in a plan and want to show where it came from.

The calculator finds your mean engagements per post and multiplies it by the size of the plan.

1. It divides the engagements in your sample by the posts in your sample.
2. It multiplies posts per day by days to count the planned posts.
3. It multiplies the two. That is the projection.
4. It shares the projection between likes, reposts and replies in the proportions your sample shows.
5. It compares planned posts per day with past posts per day and flags a change above 25%.

The 25% flag is our own caution rule. An average measured at one posting rate is weaker evidence at a very different rate.

Example values only, not benchmarks. Over 28 days an account published 84 posts. They earned 5,460 engagements from 210,000 impressions, including 3,822 likes, 546 reposts and 437 replies. The plan is 4 posts a day for 30 days.

Meaning: the plan projects to 7,800 engagements. The plan also raises the posting rate by a third, so the verdict flags it. Had the average slipped from 65 to 52 per post, the same 120 posts would bring 6,240.

The projection moves in direct proportion to its two inputs. These factors decide how far to trust them.

The Size of the Sample

A handful of posts gives a shaky average. The tool marks a sample under 10 posts as provisional. That threshold is our caution rule.

One Outlier Post

A single widely shared post lifts the mean for the whole sample. Run the numbers with and without it to see the range.

A Change in Posting Rate

The example average of 65 was measured at 3 posts a day. At 4 a day it may differ. Your own before-and-after numbers answer that question better than any rule.

The Mix of Post Types

Replies, quote posts and original posts earn different engagement. Build the sample from the kinds of post the plan contains.

The Age of the Sample

The X developer documentation says non-public metrics are only available through the API for posts from the last 30 days. A recent sample is also the closest match to your current audience.

Both projections use the same method on different metrics, and they answer different planning questions.

For the visibility side, use the X impressions forecast calculator. To study how the two metrics relate on past posts, see the impression-to-engagement ratio calculator.

Writing a Content Plan

A plan that states "120 posts, about 7,800 engagements at our current average of 65" shows its working. A reader can check it.

Setting a Campaign Expectation

Project the campaign posts at your usual average. After the campaign, compare the actual total with the projection. The percentage calculator gives the difference.

Testing a Lower Posting Rate

At 3 posts a day the example plan gives 90 posts and 5,850 engagements. The gap to 7,800 is the price of posting less, if the average holds.

1. Applying an Engagement Rate to Followers

Engagement rate is measured against impressions. The old version of this page multiplied it by followers and a made-up "timeline reach ratio" of 22% to 42%.

2. Trusting Format Multipliers

The old tool raised results by 1.25 for images, 1.45 for video and 1.65 for threads. X publishes no such multipliers. We removed them.

3. Reading a Fake Range as Uncertainty

The old "P25 to P75 range" was the total times 0.72 and 1.31. It was not based on any data.

4. Projecting from Your Best Posts

A sample of hand-picked hits overstates the average. Use every post in the window.

5. Forgetting the Post Limit

X Help lists a limit of 50 original posts and 200 replies a day for unverified accounts, as read on 2026-10-03. A plan above that cannot run.

6. Buying Engagement to Hit the Number

The X authenticity policy prohibits exchanging engagement and paying others to inflate likes, replies, reposts or views.

The multiplication is exact. The assumption that your average holds is the uncertain part, and the tool cannot test it.

Multiply your average engagements per post by the number of posts you plan. An average of 65 across 120 planned posts projects to 7,800 engagements.

X reports engagements as its own metric in post analytics. The developer documentation lists it separately from likes, reposts, replies, quotes and bookmarks, and marks it as visible only to the account owner.

No official benchmark exists. X publishes no average engagement rate, so compare your rate with your own earlier periods. The rate shown here is your sample engagements divided by your sample impressions.

More posts give a steadier average. The tool marks a sample under 10 posts as provisional, and a full 28 days of posts is a sensible base.

Only your own data can say. This page holds the average per post flat, which is an assumption. Compare two periods with different posting rates on the posting frequency impact page.

A range needs a measured spread, and totals alone do not give one. The old page printed a range made from two fixed multipliers, which we removed.

Only roughly. Likes, reposts and replies are public, but the engagements total is not. Summing the public counts understates the full figure.

No. It projects organic posts at your organic average. The X developer documentation reports organic and promoted metrics separately, so keep promoted posts out of the sample.

This page projects engagements and splits them into likes, reposts and replies. The impressions forecast projects how often posts appear on screen and works back from an impressions target.

No. The maths runs in your browser and nothing is sent to us. Save keeps a result only in this browser.

• X API metrics: impressions, engagements and the 30-day limit (X developer documentation, read 2026-10-03).
• About X limits: daily post and follow limits (X Help Center, read 2026-10-03; opens in a browser, blocks automated checks).
• Authenticity policy: engagement spam and follower inflation (X Help Center, read 2026-10-03; opens in a browser, blocks automated checks).
• Measures of location: definition of the mean (NIST/SEMATECH e-Handbook of Statistical Methods).