Posting time still matters on X, but less than it did and for a different reason than the advice usually gives. On the old chronological timeline the logic was brutal: a post went out, it sat at the top of the feed for a few minutes, and everyone asleep missed it forever. That feed is gone. What replaced it is a test with a short fuse. X shows a new post to a slice of your followers, watches what they do with it, and decides from that how much wider to push it. So the hour you pick no longer decides who sees the post. It decides how many people are awake for the test that decides who sees the post.
Which makes timing a tiebreaker rather than a lever: worth getting roughly right, never worth a spreadsheet. The difference between 9am and 10am is noise. The difference between 9am and 3am is not.
What the ranked feed changed about the question
The honest version of "does posting time matter" has two halves and most articles print one. The half that says timing is dead is right that a bad hour is no longer fatal: your post can surface in somebody's For You tab a day later, and nothing about the modern feed erases a midnight post the way a chronological one did.
The half that says timing is everything is right that the first window does real work. Ranking is decided on early signal, and early signal needs people present to produce it. Replies weigh heaviest, then reposts, then likes, with profile visits and long dwell counting as well. Post into an empty room and the system reads that thin response as the post not landing, because from the outside those two things look identical.
What a posting time actually buys you
One thing: a denser first half hour. X does not publish how long that early window runs, and anyone quoting an exact number is guessing, but the shape is not in dispute. The reaction a post gets in its first stretch of life decides whether it is shown to more people, so the value of a good hour is entirely front-loaded. After that push, when you posted stops mattering and what you posted takes over.
The size of the effect reads most honestly as a relative index. In the composite benchmark our heatmap is built from, where 100 is the busiest hour of the week, Wednesday at 10am is that 100 and 3am the same night sits at 2. None of that gap is the algorithm punishing you. It is how many people are awake.
Why a published benchmark is a start, not your answer
Every benchmark you will find, ours included, is an average built from millions of posts across tens of thousands of accounts. That is what makes it a reasonable place to stand on day one and exactly what makes it wrong for you on day thirty. An average built from everybody describes nobody: it blends a recruiter posting to people at desks with a football account posting to people on a sofa, and returns a compromise neither of them should take.
The shape those studies agree on is worth knowing anyway. Weekday mid-mornings lead, a softer second band holds in the early afternoon, Tuesday through Thursday run ahead of Monday and Friday, weekends are flatter and later, and overnight is close to dead. Then your own audience bends all of it. A B2B readership makes Saturday close to a write-off. A creator audience that follows a person rather than a company routinely makes the 7pm to 10pm band beat the morning. An audience spread across timezones flattens the grid, and the flatter it is, the less the exact hour is worth optimising.
Use it as a hypothesis, not a verdict: post into the top slots for a fortnight, then check them against your own numbers.
How to find your own best time to post
Fifteen minutes, a free account, and it beats every benchmark on the internet because it is measured on your own readers.
- Open your post analytics. Tap the small bar-chart icon underneath any of your own posts, then follow the Account overview link at the top of that panel through to the full view. Post-level analytics are free.
- Set the range to 28 days. Seven days is not enough posts to see anything and ninety reaches back past whatever you last changed. Twenty-eight days holds enough posts and one recognisable version of your account.
- Sort by impressions and take the top ten. Note the day of the week and the hour each of the top ten posts went out. Then do the same for the bottom ten, because the hours that never work are as informative as the hours that do.
- Throw out your single biggest post. Impressions are driven far more by what a post said than by when it went out, so one post that travelled will dominate the whole sample. Remove it before you look for a pattern.
- Look for a cluster, not a winner. If eight of your top ten went out between 8am and 11am on a weekday and six of your bottom ten went out after 7pm, you have an answer. If the hours are scattered evenly, timing is not what is moving your numbers and you should stop optimising it.
- Check whether the data is just your own schedule. If every post you have ever published went out at 9am, your analytics will say 9am is best and that is not evidence. Deliberately move a third of your posts to other hours for two weeks, then re-read the pattern.
- Convert the window to your audience timezone. Your analytics report in your own clock and your readers may not share it. Work out where the bulk of your followers are, then shift the winning window onto their local time.
The same screen feeds the other number people ask about: what counts as a healthy result is in the engagement rate guide.
Timezone matters more than hour of day
If your readers are not where you are, the timezone is the bigger of the two variables and it is not close. Published benchmarks are reported in US Eastern time, so a 10am peak arrives at 3pm in London and at 7:30pm in India, and Wednesday at 10am in New York is already Thursday in Sydney. Taking a headline hour at face value from another zone is how people end up posting into the middle of their audience's night while following the advice exactly.
Half-hour zones deserve their own warning, because most tools round them away. India is UTC+5:30, Nepal is UTC+5:45, parts of Australia are UTC+9:30, and rounding any of those to the nearest whole hour puts the peak thirty minutes off every time. The fix is tedious rather than clever: work out where your followers are, convert the window into their clock, and schedule against that.
When timing genuinely does not matter
Some posts are not timing-sensitive at all, and optimising them is wasted effort. An evergreen post that answers a question people search for keeps surfacing long after its first window closed. A thread is written to be read later as much as live, every part of it gets its own chance to be shown, and threads accumulate bookmarks for days, which is why the thread format rewards the writing far more than the scheduling.
Timing also stops mattering when your audience is spread across the world, because there is no shared working day to aim at and someone is always awake. And it matters far less than your subject does when your account is small: at low volume, one post that travelled swamps any timing pattern in your data, so what you post carries the week. That decision, rather than the clock, is the one covered in what to post on X.
The answer, in proportion
Posting time is worth about one afternoon of attention, once. Pick a benchmark window, convert it to your readers' clock, hold it for a fortnight, then spend fifteen minutes in your own analytics and replace it with what you find. After that the return on more timing work is close to nothing, and what is left is the writing. The rest of the section is at the X guides hub.
Frequently asked questions
Does it matter what time you post on X?
Yes, but less than it did on the chronological timeline and for a different reason. X shows a new post to a slice of your followers and decides how much wider to push it from how they react, so the hour sets how many people are awake for that early test rather than deciding who sees the post. Treat it as a tiebreaker: 9am against 10am is noise, 9am against 3am is not.
How do I find the best time to post for my own account?
Open post analytics on any of your own posts, follow Account overview through to the full view, and set the range to the last 28 days. Sort by impressions and note the day and hour of your top ten and bottom ten posts, looking for a cluster rather than a winner. Discard your single biggest post first, because one post that travelled will swamp the pattern, and scatter a third of your posts across other hours for a fortnight so the data is not just your own schedule reflected back.
Does the X algorithm care when you post?
Not directly, and there is no bonus for a particular hour. What ranking reacts to is early engagement: replies weigh heaviest, then reposts, then likes, with profile visits and long dwell counting too. Posting when your readers are around produces those signals faster, which is how the hour matters without the clock being a ranking factor.
Is it better to post at the same time every day?
A steady rhythm is worth more than a perfect hour, with one caveat. Posting at the same time daily makes your own analytics useless for finding a better slot, because every post you have shares one timestamp. Hold a consistent core slot, then deliberately move a third of your posts around for two weeks whenever you want to retest the assumption.
What if my followers are in a different timezone from me?
Then the timezone matters more than the hour. Published benchmarks are reported in US Eastern time, so a 10am peak is 3pm in London and 7:30pm in India, and Wednesday at 10am in New York is already Thursday in Sydney. Convert the window to where your readers are, and watch the half-hour zones: India is UTC+5:30 and parts of Australia UTC+9:30, so rounding to the nearest hour moves the peak by thirty minutes.
Does posting time matter for a thread?
Less than for a single post. A thread is written to be read later as much as live, every part gets its own chance to be shown, and threads accumulate bookmarks for days. Evergreen posts behave the same way. Timing pays off most on time-sensitive posts that need their audience present at publication.