X (Twitter) Impressions Forecast Calculator

1. Pick a recent sample of your own posts, such as the last 28 days. Add up their impressions and enter the total with the number of posts.
2. Enter the plan: posts per day and the number of days.
3. Add a target, the sample days and your follower count if you want the last four results. Then read the projection and the verdict.

What each result tells you:

An X impressions forecast is an estimate of how many times a set of future posts will appear on screens. This page builds it from your own average impressions per post.

The X developer documentation defines impressions as the count of times a post appeared on a user's screen. It adds that the count is not unique: the same user viewing twice counts as two impressions. The X Help Center describes the public view count in the same terms and notes that your own views of your post count as well.

Impressions are therefore not people. A projection of 300,000 impressions does not mean 300,000 different accounts. X publishes no figure for the share of followers who see a post, so this page uses none.

The tool suits anyone who must state an expected visibility number in a plan: social media managers, creators pitching a partner and small teams setting monthly goals.

The calculator finds your mean impressions per post and multiplies it by the size of the plan. It then runs the same sum backwards for a target.

1. It divides the impressions 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 divides the target by the average to find the posts needed, and by the days for the daily rate.
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 with 5,220 followers published 84 posts that earned 210,000 impressions. The plan is 4 posts a day for 30 days, and the goal is 500,000 impressions.

Meaning: the plan projects to 300,000 impressions, 200,000 short of the goal. Closing the gap takes 80 more posts at the same average, or a higher average. Had the average slipped to 2,000 per post, the plan would bring 240,000 and the target would need 250 posts.

The projection moves in direct proportion to the average and the post count. These factors decide how far to trust the average.

One Outlier Post

A single widely seen post lifts the mean. In the example, one post with 46,000 impressions would leave the other 83 at 1,976 each. The 120 planned posts would then project to about 237,000.

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.

A Change in Posting Rate

The example average of 2,500 was measured at 3 posts a day. At 4 or 7 a day it may differ, and only your own before-and-after data can show how.

Recommendations Beyond Your Followers

X Help says the For you timeline shows posts from followed accounts plus recommended posts, chosen with a variety of signals. Impressions can therefore come from people who do not follow you, and that share is not stable.

The Mix of Post Types

Replies and original posts earn very different impressions. Build the sample from the kinds of post the plan contains.

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

For the interaction side, use the X audience engagement forecast calculator. The two results divide into a projected engagement rate, which the impression-to-engagement ratio calculator explains.

Setting a Monthly Visibility Goal

Enter last month as the sample and next month as the plan. The projection is a baseline, and a goal above it needs a reason.

Sizing a Campaign

Enter the campaign goal as the target. The tool returns the posts needed at your current average, which shows early whether the goal is realistic.

Reporting Against the Plan

After the period, compare actual impressions with the projection. The percentage increase calculator gives the difference.

Testing a Lower Posting Rate

At 3 posts a day the example plan gives 90 posts and 225,000 impressions, if the average holds.

1. Starting from Followers

The old version of this page multiplied followers by a "reach rate" of 12% to 35%. X publishes no such rate. Start from impressions you have measured.

2. Adding Account-Type Multipliers

The old tool multiplied results by 1.8 for one subscription tier and 2.6 for another. No published source supports those numbers, so we removed them.

3. Counting Impressions as People

Impressions are not unique. One person scrolling past a post twice counts twice.

4. Reading a Fake Range as Uncertainty

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

5. Planning Past 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. The tool flags any plan or target that needs more.

6. Mixing Promoted and Organic Posts

The X developer documentation reports organic and promoted metrics separately. Keep promoted posts out of an organic sample.

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

Multiply your average impressions per post by the number of posts you plan. An average of 2,500 across 120 planned posts projects to 300,000 impressions.

The X developer documentation defines it as the count of times a post appeared on a user's screen. The count is not unique, so one user viewing twice adds two impressions.

X shows a view count on each post and its help page describes it as the total number of times a post has been viewed. Use the figure your analytics reports, and use the same one for every post in the sample.

No official ratio exists. X publishes no share of followers who see a post. The per 100 followers figure here is your own measured ratio, useful only against your own earlier periods.

Divide 1,000,000 by your average impressions per post and round up. At 2,500 per post that is 400 posts, if the average holds.

Total impressions rise only if the average per post does not fall by more than the post count grows. Compare two of your own periods on the posting frequency impact page to see what happened for you.

Yes for the view count. X Help says that if you are the author, looking at your own post also counts as a view.

No. X Help states that embedded posts will not add to view counts.

This page projects visibility and works back from an impressions target. The engagement forecast projects actions on your posts and splits them into likes, reposts and replies.

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).
• View counts: who counts as a viewer and how views are counted (X Help Center, read 2026-10-03; opens in a browser, blocks automated checks).
• About your For you timeline: followed accounts and recommendations (X Help Center, read 2026-10-03; opens in a browser, blocks automated checks).
• About X limits: daily post and follow limits (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).