· 6 min read
Best time to post on Threads: find yours from your own stats
A four-step method to find when your followers respond on Threads, with a test plan, a results table and the mistakes that spoil a timing test.
Govir Team · How we write
The best time to post on Threads is the time when your followers read and answer you, and the only way to find it is to measure it. A universal table of "best hours" can't know where your audience lives or when they scroll. A small test with your own posts can: pick two or three time slots, publish comparable posts in each for a few weeks, and keep the slot that earns more replies.
This guide gives the method in four steps, a notes template, and the mistakes that make a timing test useless.
Why a one-size table doesn't work
Any list of "best times" averages accounts that have nothing in common with yours: different countries, different topics, different habits. A morning slot that suits a news account can be quiet for someone writing to night-shift nurses or developers on another continent.
Two things matter more than any average:
- Where your followers are. A time that is lunchtime for most of them is more useful than a time that is generally popular.
- What you post. A quick question and a long thread are read at different moments. Compare like with like.
Meta doesn't publish a "best time" for the feed, and it hasn't said that posting at a given hour is rewarded, so treat timing as an experiment about your audience, not as a ranking trick. For the overall rhythm, see how often to post on Threads; this article is only about when in the day.
Step 1: Look at where and when your audience is
Open Threads' own insights first: on mobile, tap the icon at the top left of your profile; on the web, open the menu at the bottom left or go to threads.com/insights (Threads, post by @threads). Look at where your followers are, if your account shows it, and think about their working day: when do they have a break, a commute or an evening on the sofa?
From that, write down two or three candidate slots, for example:
- a morning slot before work,
- a lunch slot,
- an evening slot.
Use your followers' time, not yours. If most of them live a few time zones away, convert before you schedule.
Step 2: Set up a fair test
A timing test only works if the only thing that changes is the time.
- Keep the format steady. Compare text posts with text posts, or threads with threads. Don't let one slot get all the photos.
- Rotate the slots. Don't post mornings in week one and evenings in week two; a holiday or a news event would pollute one side. Mix the slots across the same weeks.
- Change nothing else. Same account, same kind of topic, same length of first line.
- Run it long enough. Give each slot at least a handful of posts before you decide. One great post in one slot proves nothing.
- Let posts age equally. Measure each post after about the same time live, such as the next morning, so a post isn't judged early.
Illustrative example (a test plan written for this article, not real data):
Slots: 08:00, 12:30, 19:00 (followers' time) Format: single text posts, one question or tip each Rotation: Mon 08:00, Tue 12:30, Wed 19:00, Thu 08:00, Fri 12:30, and so on Measure: replies and views, the morning after each post
If you plan the rotation in a calendar, scheduling it ahead keeps the experiment honest, because the times are fixed before you see any results. In Govir, you can lay the test out on the Calendar and set your weekly slots once in the Queue, so each post goes out at the slot you chose (Scheduling & Calendar, Queue).
Step 3: Read the results
Choose one measure before you start and stay with it. Views show reach; replies show conversation. If you want a rate that compares posts fairly, use the same formula every time; the engagement rate calculator explains the two usual ones.
Then compare slots, not single posts:
| Slot | Posts | Average views | Average replies | Notes |
|---|---|---|---|---|
| Morning | [count] | [your numbers, with the date you measured them] | [your numbers] | |
| Lunch | [count] | [your numbers, with the date you measured them] | [your numbers] | |
| Evening | [count] | [your numbers, with the date you measured them] | [your numbers] |
Fill this in with your own figures. Treat a slot as a clear winner only if it comes out ahead more than once and not because of a single outlier. If two slots are close, the answer is that timing isn't your lever right now; spend the effort on the first line or the topic instead.
In Govir, Analytics → Timing shows the average engagement of posts published at each hour of each day in your timezone, and the best time to post appears on your Dashboard. Both come with Pro; on other plans, the same comparison works with the table above (Analytics in Govir). Either way, the numbers describe your past posts, so they are a hint to test, not a promise.
Step 4: Keep the winner, then test again
Move most of your posts to the winning slot, but keep one experimental slot going. Audiences change: a new topic or a growing follower base in another country shifts when people read you. Repeat the test when something big changes, and otherwise review it a few times a year.
For the weekly check of your numbers, the quarter-hour weekly review fits this test: add a line to your notes saying which slot each post used.
Mistakes that ruin a timing test
- Judging by one post. A post can travel because of its topic, not its time.
- Changing slot and format together. Then you can't tell which one made the difference.
- Ignoring time zones. Scheduling at your own morning when your followers are asleep.
- Posting only at the winner forever. Leave room to find out whether it still wins.
- Chasing the hour instead of the post. A weak post at the best time is still a weak post.
Questions
What is the best time to post on Threads? There is no single answer. The best time is when your own followers read and reply, and you find it by rotating a few slots and comparing replies or views.
Does Meta say when to post on Threads? Meta doesn't publish a recommended posting hour. Use your own insights and treat any universal table with caution.
How long should a timing test run? Long enough that each slot has several comparable posts, usually a few weeks. A single week is too easy to distort.
Do weekends work differently? They can, because routines change. Test weekdays and weekends as separate groups instead of mixing them.
Should you schedule posts to hit the best time? Scheduling makes the test cleaner, because the times are decided in advance and you don't have to be online at the slot.
Sources
- Threads, post by @threads, "To access Threads insights, tap the icon at the top left of your profile on mobile. On web, click the menu at the bottom left or visit www.threads.com/insights." https://www.threads.com/@threads/post/DMavCS_AMq8 (accessed 2026-10-12).
