“What time should I post on Threads?” is one of the first questions people ask when they start taking the platform seriously.

You can find plenty of answers online: 8 am, noon, 9 pm. But those answers come from other people’s audiences. Where your readers live, when they finish work and when they scroll all change the answer. Rather than borrowing someone else’s schedule, look for it in your own posts.

Why there’s no standard answer

Posting time is only one of the things that affect a post. The topic, the format and whatever else is trending that day can matter just as much. Comparing the timing of two posts on completely different topics won’t tell you much.

There’s also a detail that’s easy to miss: a post’s view count is a running total. A 9 am post that did well may have picked up most of its views in the evening, which doesn’t mean your readers are online at 9 am. Threads Insights explained covers what each number counts.

For the same reason, a post from an hour ago hasn’t finished collecting views, so it isn’t a fair match for one that’s been up for days. When you gather your data, leave out posts from roughly the past week.

Finding candidate hours in three steps

All you need is a few months of posts that reflect what you publish now, with each post’s time, views, format and topic.

The data can only speak for hours you’ve actually posted at. If you have only a couple dozen posts, or almost always post at the same time, there isn’t enough to compare yet. Skip ahead to testing: pick two hours you can keep up with, and the test itself will build the data.

Group by hour and compare medians

Group posts by the hour they went out, then compare the median of each group rather than the average. One viral post can drag the average way up; the median shows what a typical post at that hour does.

Say your posts come out like this:

Posting hourPostsMedian viewsAverage views
8 am121,2001,350
12 pm32,8006,400
9 pm151,9002,100
Demo data for illustration.

Going by averages, noon wins by a mile. But it has only three posts, and its average is more than double its median, which suggests one viral post is doing the heavy lifting. 9 pm has fifteen posts behind it and a median consistently above the morning’s. That’s the candidate worth trusting.

Check the sample size, and don’t trust first place

The example also shows why sample size matters. An hour with two or three posts is a hint, not a pattern. A quick test: remove the single best post and see whether the lead survives. If it disappears, it wasn’t really a lead.

There’s a subtler trap too. Line up 24 hours and one of them will come out on top even if posting time made no difference at all. It’s like having 24 people each roll a die a few times: someone will end up with a high average, but that doesn’t make them better at rolling, and their next round will usually look ordinary. The more slots you compare, the more likely first place is partly luck. That’s why this step gives you candidates, not an answer, and the alternating test at the end is what confirms them.

Then add the weekday

Once you have candidate hours, compare weekdays too. Splitting by both weekday and hour spreads your posts thin, though. Thirty posts across 7 days and 24 hours leaves most slots with one or two, and with 168 slots, some will look great by chance alone. Treat thin groups as ideas to test, not conclusions.

Easy ways to misread the data

Judging by one hit. One viral post doesn’t make an hour good. Look at the median and spread of everything else you posted at that time.

Mixing formats and topics. If your image posts go out at noon and your text posts at night, you can’t tell whether the difference comes from the format or the hour. Compare one format at a time across hours.

Mixing up time zones. Check which time zone your chart uses and stick with it. Also remember that older posts have had longer to collect views, and you had fewer followers back then.

Testing a new posting time

With two candidate hours, put them head to head. A fair test needs two things: posts that can be compared, and the same mix of days for both hours.

Comparable posts means your usual kind of post: the same format (text only, image or video) and the kind of topic you write most. Leave out posts that would stand out anyway, such as giveaways, collaborations or takes on breaking news. If your account posts a bit of everything, don’t force the topics to match. Alternating evenly spreads your mix across both hours; just note the unusual posts and leave them out when you compare.

Alternating is simple: one post at hour A today, one at hour B tomorrow, and keep switching. Because a week has seven days, two weeks of alternating gives each hour every weekday once.

You don’t need to write down numbers 24 hours after each post. Since the two hours take turns, both groups have posts of similar ages. Wait until the last test post has been up for about a week and its views have settled, then compare the median views of the two groups. It’s the same rule as leaving out the past week when you gathered older posts: compare numbers that have mostly finished growing.

Two weeks gives each hour about seven posts. If the medians are close, or the gap vanishes when you remove each group’s best post, call it a tie: keep testing, or pick the hour that’s easier for you to keep up. It also helps to look at each week separately. An hour that wins both weeks is more convincing than one that wins big once.

If one hour clearly wins, make it your main posting time. Audiences shift with seasons, school terms and your own content, so repeat the comparison every two or three months.

Where each step lives in Threads Analytics

Every step above works in a spreadsheet. If you use Threads Analytics, it calculates them from your synced posts, and each one has a chart:

  • Best hours to post, a card on the Overview page showing your top three hours by median views, with post counts and confidence labels. Hours with at least 3 posts are ranked first. Treat it as the shortlist for your test, not the verdict.
  • Best Time to Post, an hourly bar chart in the Performance tab you can filter by weekday. After a test, set the date range to the test period to compare the two hours’ medians directly.
  • Best Day of Week, comparing median views, engagement rate and post count by weekday.
  • Content Type by Time Slot, in the Content tab, showing how each format does at each hour.

Your best time is in your own data

There’s no standard best time to post, but there is a standard way to find yours: group your own posts, check medians and sample sizes to pick candidates, then run a fair, alternating test. The data suggests; the test confirms. An hour found this way fits your audience, not someone else’s.

Frequently asked questions

What is the best time to post on Threads?

There isn’t one hour that works for every account. Start with times you can keep up, compare similar posts in one time zone, and test the hours that look strongest.

Does the day of the week matter on Threads?

It can, depending on your audience and content. Compare weekdays using similar posts, and remember that splitting by both weekday and hour leaves fewer posts in each group.

How many times a day should I post on Threads?

There’s no fixed number. When you change how often you post, watch total views as well as views per post: the typical post may get fewer views while your total goes up. Threads Analytics groups posting frequency by week.

Does scheduling a post hurt reach?

If your scheduled posts seem to do worse, first compare them with manual posts on similar topics, formats and hours. The difference may come from those factors rather than the scheduling itself.

References