Threads posting schedule: best times

Each row is one published analysis, read from its own page on 2026-09-23. They measure different samples over different periods, so they are listed side by side rather than merged into one number.

With one large study there is nothing to cross-check it against, so weigh it accordingly. Its pattern — midweek mornings strong, weekends and evenings weak — resembles Buffer’s findings for Instagram and Facebook, which is unsurprising but not independent confirmation.

Both large studies express times as the audience’s local time: Sprout Social records every time in local time (a 9 a.m. window is 9 a.m. in Los Angeles, London and Sydney alike), and Buffer says to “consider all the recommendations local time”. If your audience is spread across time zones, schedule for the zone where most of your followers are.

Every figure here is an aggregate across many accounts and industries. It tells you where to start testing, not when your audience is online.

We did not find a large published frequency benchmark for Threads: neither Buffer’s roundup nor HeyOrca’s survey includes one. Threads is a text-first, conversational feed, so a workable starting point is a cadence you can sustain while replying to comments — but that is our judgement, not a measured finding.

Threads has built-in scheduling: when Meta launched it in January 2025 it allowed posts up to 75 days ahead, several a day, but not replies. Posts are scheduled one at a time from the composer.

Threads posts through SkedCast follow the same rules as the composer: up to 500 characters, with text-only posts allowed.

SkedCast holds a scheduled post and publishes it at the time you set, from one calendar shared with every other connected account, with the same per-platform limits checked when you schedule rather than at publish time. Scheduling never changes when your audience is online; it only makes sure the post goes out in the window you chose.

A study average is a starting hypothesis. Your account’s own results are the evidence. A simple test:

SkedCast’s best-times feature does the “find your own window” step for you where the data exists: a daily job reads each connected account’s own publish history and the engagement analytics SkedCast has ingested for it, and recommends the day-and-hour slots where that account’s posts did best, in the account’s own time zone. It never invents a slot — an account with no analytics data yet simply has none — and how much it can derive depends on what each platform exposes to third-party apps. The same slots are available through the API (GET /v1/best-times, scope besttimes.read) and the MCP get_best_times tool. Best times is included from the Solo plan.