The best time to post on Threads
There is no universal best time, and the accounts that grow are not the ones who found it. What matters is the hour after you post, and whether you are in it.
The short version
- There is no universal best time. Every chart is an average of accounts unlike yours.
- The first hour is the real variable. Post when you can reply for the hour after, not when a graphic says to.
- Three windows are worth testing first: early morning, lunch, and mid-evening in your audience's time zone.
- Two weeks, one variable. Same post types, three fixed slots, then read the median, not the best day.
- Timing multiplies a good post. It does not rescue a bad one.
What is the best time to post on Threads?
For most English-language accounts, three windows outperform the rest: early morning (7–9am), the middle of the day (12–1pm) and the evening (7–10pm), in the time zone where most of your followers actually are. Those are hypotheses to test, not an answer. The account-specific answer comes from two weeks of your own data, and it usually turns out to be the hour you can reliably be online for.
That last clause is the whole article, so it is worth saying plainly before the detail: the best time to post on Threads is a time you can spend the next hour on Threads. An account that posts at 8am and replies until 9 will beat the same account posting at the theoretically optimal 7:42pm and going to bed.
You are not choosing a time to post. You are choosing an hour to be present.
Why does the first hour matter so much?
Because Threads decides how far to push a post based on what happens to it immediately, and it weights replies far above likes. A post that collects a conversation in its first hour gets shown to people who do not follow you; one that collects silence stops at your own followers. The clock time only matters insofar as it changes who is awake to start that conversation.
The mechanism is covered properly in how the Threads algorithm works, but the practical consequence is narrow enough to state here. Your post is being tested on a small sample. The test is short. Replies are the strongest signal in it, and replies require someone to be there, including you, because a reply from the author restarts the conversation and pulls the thread back up other people's feeds.
The hour is not passive. Answering every reply in the first hour is worth more than any posting-time optimisation you will ever make. It is also the one lever that does not depend on the algorithm behaving the way it did last month.
Why do the published charts disagree with each other?
Because each one averages a different pile of accounts. A chart built from B2B software accounts peaks on Tuesday morning; one built from lifestyle accounts peaks on Sunday evening. Both are accurate about their sample and useless for you, because your audience is neither.
| What the chart says | What it is actually measuring | Why it may not be you |
|---|---|---|
| "Post at 9am Tuesday" | An average across thousands of accounts | Averages hide every niche, including yours |
| A single global peak | Whichever time zone dominated the sample | Usually US Eastern, whoever you are |
| "Engagement is highest at X" | Total engagement, not per-post reach | The busiest hour is also the most competitive |
| Data from last year | A platform that has changed since | Threads has moved fast, and continues to |
There is a second, subtler problem. The hour with the most people online is also the hour with the most posts competing for them. A slightly quieter window where your specific audience is awake often beats the global peak, and no aggregate chart can tell you where that is.
How do you find your own window?
Fix three slots, post the same kinds of post into them for two weeks, and compare the medians. One variable at a time: same post types, same effort, same reply behaviour after each one. Two weeks is roughly the minimum that survives the enormous variance of individual posts.
| Week | Slot A | Slot B | Slot C |
|---|---|---|---|
| Days 1–7 | 07:30 | 12:30 | 20:00 |
| Days 8–14 | 08:30 | 13:00 | 21:00 |
| Record | Replies in the first hour · replies total · profile visits · follows |
- Compare medians, not best days. One post going unusually well tells you about the post, not the hour.
- Count replies in the first hour as the primary number. It is the closest thing to the signal the platform is reading.
- Ignore likes. They move with reach and tell you nothing you did not already learn from replies.
- Keep the post types constant. Testing a question post against a story post at different hours measures two things at once and settles neither.
Then check where your audience is. If a meaningful share of your followers is in another continent, the winning slot may be one that is inconvenient for you, which is the point at which you decide whether to serve that audience or narrow to the one in your own time zone. Both are legitimate; drifting between them is not.
What do you do in that hour?
Reply to every reply, and go and reply on other people's posts. The window after publishing is the only time your own post benefits from your replies elsewhere: each one puts your name in front of an audience that can click straight into a post that is currently live.
This is the loop described in the Threads reply strategy, and posting time is really just the question of when to run it. Twenty minutes of replies before you post warms the feed; forty minutes after keeps the conversation alive long enough for the platform to notice. The post is the smaller half of the work.
Does posting more often help?
Up to a point. Two to four original posts a day, spread across the day, gives you several independent chances at a good first hour without the posts competing with each other. Beyond that they cannibalise: two posts an hour apart split the same audience in half.
- Space them at least three hours apart. Closer than that and the second post lands on people who have just seen the first.
- One good post beats three rushed ones. Volume is only useful when each post could have carried the day on its own.
- Replies are unlimited. There is no equivalent ceiling on how much you should be replying, and no day where more replying was the wrong choice.
- Consistency over frequency. Four posts a day for a week and nothing for ten days is worse than one a day forever.
Sustaining that requires having something to post, which is a supply problem rather than a scheduling one: how to build a Threads post bank is how the two-to-four figure stops depending on inspiration.
What matters more than timing?
The first line, the reply behaviour, and posting at all. Timing is a multiplier somewhere in the range of a few tens of percent; a first line that stops the scroll is a multiplier of several times, and being absent from the platform is a multiplier of zero.
The order of operations, if you are deciding where to spend an afternoon: get the first line right, be present in the first hour, post consistently, and only then optimise the clock. Accounts that grow have all four. Accounts that argue about the fourth usually have none of the first three.
Pick the hour you can defend. The best slot in your data is worthless if it lands during a meeting three days a week. Choose the best hour you can actually be online for, and then never move it. A fixed hour compounds in a way an optimal one does not.
Frequently asked questions
What is the best time to post on Threads?
For most English-language accounts the reliable windows are roughly 7–9am, 12–1pm and 7–10pm in the time zone where most of your audience lives. Those are starting points to test against, not an answer: your own two weeks of data beats any published chart.
How many times a day should I post on Threads?
Two to four original posts, spread out, plus replies throughout the day. One post a day is enough to grow if the replies are there; six posts a day with no replies is not.
Does posting at the wrong time kill a post?
It caps it rather than kills it. Threads keeps surfacing a post that earns replies for far longer than an hour, so a good post at a bad time underperforms and a bad post at a good time still dies. Timing is a multiplier on quality, not a substitute.
Should I use a scheduler for Threads?
Only if you are present when the post lands. Scheduling solves the writing, not the first hour, and the first hour is the part that decides how far the post travels. Schedule the post, diary the twenty minutes after it.
Does the day of the week matter?
Less than the hour. Weekday mornings are more competitive and weekend evenings are quieter with a smaller audience awake, which roughly cancels out. Test hours first; test days only once the hour is settled.
The system behind this, written down
Everything above is the map. The Income Loop is the work inside it: modules 0–6 from the problem you solve to the offer that pays for it, plus ten traffic paths: the deeper post banks, the content sales systems and the full software build sequence, in one place.
Get The Income LoopNot ready to pay for anything? The Basic Income Loop is free and includes a complete seven-day starter for Threads, Instagram or software, enough to find out which one suits you before spending anything.