Guide · By PostBoost team · · Markdown
Short answer: yes, Threads can schedule a post on its own. In the composer, tap the three-dot menu, then Schedule, choose a date and time and tap Schedule again; the post waits in your drafts folder until it goes live. At launch, the built-in scheduler couldn't schedule replies (reported by launch coverage), so a post with a chain of replies below it still needed you at the keyboard. A scheduler such as PostBoost publishes the post and every reply at the time you set. Before you schedule, paste the text into the free social media character counter: its Threads row counts emoji the way Meta does.
What the Threads scheduler can and can't do
| Threads app | PostBoost | |
|---|---|---|
| Schedule a single post | Yes, three-dot menu → Schedule, up to 75 days ahead (reported) | Yes |
| Schedule replies or a reply chain | No (reported) | Yes, Add Post for each reply |
| Edit before it goes out | Yes, in the drafts folder | Yes, in the calendar |
| Post the same update to other networks | No | Yes, one post to all your accounts |
| Schedule from code or an AI assistant | No | Yes, REST API and MCP |
Threads announced the feature on January 23, 2025 with a post that was itself scheduled: "We scheduled this post, and now you can do the same." The 75-day range and the missing reply scheduling come from launch coverage (MacRumors); Meta's own post gives the steps but no limits, so check your app if you plan right at the edge.
For one post a week, the built-in scheduler is enough. A scheduler earns its place when you post replies under your own posts, publish the same update on several networks, or want posts to come from a script, a spreadsheet or an AI agent.
Why PostBoost posts don't appear in your Threads drafts
The Threads API has no publish-later field. An app creates a post container, then publishes it, and both happen when the app calls. So every scheduler holds the post on its side and publishes it at the set time; nothing sits in your Threads drafts in the meantime. In PostBoost the post lives in the calendar until then, and you edit or reschedule it there.
Schedule a Threads post in PostBoost
1. Connect your Threads account
- In the sidebar, open Accounts (under Configuration; you need to be a workspace admin).
- Click Connect account and choose Threads.
- Threads' sign-in page opens. Log in with the profile you want to post from and approve the connection. You land back in PostBoost with the account connected.
Threads access tokens expire after 60 days. PostBoost refreshes the token a week before that and warns you if the refresh fails, so you don't have to reconnect on a timer (connection health).
2. Write the post
Open a new post and select the Threads account. The post editor checks Threads' rules as you type:
- 500 characters per post. Over that, the account shows "Maximum of 500 characters allowed." and the post can't be scheduled until it is shorter. Threads counts each emoji as its UTF-8 bytes (most cost 4), which the Threads character limit guide explains, including how PostBoost warns about emoji-heavy text.
- Up to 20 images or videos, mixed if you like, published as a carousel; videos up to 5 minutes. The editor reminds you when an image has no alt text.
- One hashtag. A second one brings up the suggestion "Threads works best with no more than 1 hashtag", since Threads turns a tag into a single topic. It is a suggestion: you can still schedule.
3. Pick the time and schedule
- Click Schedule and choose a date and time. The time zone is shown next to the time; to change it, click the icon beside it, which opens your profile settings.
- Click Done, then Schedule.
The post appears in the calendar and goes out at that time. Add to Queue puts it into the account's next free slot of your posting schedule instead. The Schedule panel also shows Best times to post once the account has at least 10 published posts with imported statistics, based on how your own Threads posts performed. Posting to several networks at once? Set a time per account gives each account its own time.
Schedule a Threads reply chain
At launch, the Threads app couldn't schedule replies (reported); PostBoost schedules the whole chain. Click Add Post in the composer for each reply. Every part gets its own 500 characters and its own images, and an error names the part that breaks a rule (such as "Post #2 - Maximum of 500 characters allowed."). At the scheduled time, PostBoost publishes the first post, then each reply under the one before it, in order.
To split a long draft, paste it into the free thread maker and pick Threads as the network. It breaks at paragraphs, then sentences, never inside a word or link, keeps each part under 500 the way Threads counts emoji, and can add "1/4"-style numbers. Paste the parts into the composer.
If the same post also goes to Facebook or Instagram (or a LinkedIn account that offers first comments), the button reads Add first comment instead of Add Post. Create a version for the Threads account and add the replies there.
If one reply fails to publish, the parts already live stay up, and the post's Delivery tab shows how many parts were published. Its retry button (Continue publishing) picks up from the failed part instead of posting the whole chain again. Why scheduled posts fail to publish covers the usual causes.
Schedule Threads posts with the API
Find the Threads account's id with GET /{workspaceUuid}/accounts, then create the post. This one is a post with one reply, scheduled for 10:00 Berlin time:
curl -s -X POST "https://postboost.co/app/api/$WORKSPACE_UUID/posts" \
-H "Authorization: Bearer $POSTBOOST_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"accounts": [21],
"schedule": true,
"date": "2026-11-18",
"time": "10:00",
"timezone": "Europe/Berlin",
"versions": [{
"account_id": 0,
"is_original": true,
"content": [
{ "body": "We moved our weekly report from slides to one page. Three things we cut, and one we brought back:" },
{ "body": "1. The vanity chart. Follower growth went to a single number at the top." }
]
}]
}'
Item 0 of content is the post; every later item is the next reply in the chain. A part over 500 characters is refused with 422 and nothing is created. If a part fits at 2 per emoji but not at Threads' byte count, the post is saved and the response carries a threads_too_long warning naming it. To check without creating anything, send the same body to validatePost; createPost lists every field.
Two limits matter when a script schedules for you. Meta allows 250 API-published posts and 1,000 replies per Threads profile in 24 hours (Threads API overview). PostBoost's API accepts up to 50 Threads posts per account per UTC day (half on the free plan), and refuses a post that repeats one created for the same account in the last 24 hours unless you set allow_duplicate (guardrails).
Schedule Threads posts from Claude or ChatGPT
With the PostBoost connector added to your AI assistant, you can schedule in plain language:
Write a Threads post with two replies about our new one-page report template, keep each part under 500 characters, and schedule it for Wednesday at 10:00 Berlin time.
The assistant finds the account with list-accounts, then calls create-post with the three parts, schedule set to scheduled, a scheduled_at such as 2026-11-18 10:00 and the timezone Europe/Berlin. Ask it to run validate-post first if you want the rules checked before anything is saved. Schedule social media posts with Claude walks through the setup.
Before you hit Schedule
- Count it: the social media character counter shows the Threads count, emoji at their byte cost, next to X, Bluesky and the rest.
- Check it: the social media post checker flags a post that is too long, has too many images or breaks another network rule.
- Moving from X? The same reply-chain approach works there; how to schedule a thread on X covers its limits.
- Try it on your own profile: create a free PostBoost account, connect Threads and schedule your first reply chain. Plans are on the pricing page.
Do this in PostBoost
Free tools for this guide
Free tool
Social media character counter
Free character counter for X, Threads, Bluesky, Instagram, LinkedIn, TikTok and more. Counts as each network does, live in your browser.
Free tool
X thread maker: split long text into numbered posts
Split long text into numbered posts for X, Threads, Bluesky or Mastodon. Never cuts a word or a link. Free, no signup, runs in your browser.
Free tool
Social media post checker: check your post before you publish
Check a post before posting: character limits, hashtags, media count, video length and see-more cut-offs for X, Instagram, LinkedIn, TikTok and more.
FAQ
Can you schedule posts on Threads?
Yes. Since January 2025 the Threads composer has a Schedule option in its three-dot menu: pick a date and time and tap Schedule again. Scheduled posts wait in your drafts folder, where you can edit or delete them before they go live.
How far ahead can you schedule a Threads post?
Up to 75 days in the Threads app, according to launch coverage of the feature. Meta's own announcement post does not state a limit. A scheduler such as PostBoost holds the post itself and publishes it through the Threads API at the time you chose.
Can you schedule a reply or a thread chain on Threads?
Not in the Threads app: launch coverage reports that replies can't be scheduled. In PostBoost, click Add Post in the composer to add each reply; PostBoost publishes the post and then each reply under the one before, in order, at the scheduled time.
Why don't my PostBoost posts show up in the Threads drafts folder?
Because they are not stored on Threads until they go out. The Threads API has no publish-later field, so PostBoost keeps the scheduled post and publishes it at the set time. You see and edit it in the PostBoost calendar instead.
How many Threads posts can I schedule per day?
Meta allows 250 API-published posts and 1,000 replies per profile in 24 hours. PostBoost's API accepts up to 50 scheduled Threads posts per account per UTC day, half that on the free plan.
Do I have to reconnect Threads every 60 days?
No. Threads access tokens last 60 days, and PostBoost refreshes them a week before they expire. If a refresh fails, PostBoost warns you so you can reconnect.
Sources
- Threads (@threads): scheduling launch post, January 23, 2025
- Adam Mosseri on Threads: "You can now schedule posts on Threads" (January 23, 2025)
- TechCrunch: Threads rolls out a post scheduler, markup feature and more (January 23, 2025)
- MacRumors: Threads Now Lets You Schedule Posts Up to 75 Days in Advance (January 24, 2025)
- Meta for Developers: Threads API publishing reference (container and threads_publish parameters)
- Meta for Developers: Threads API overview (250 API posts and 1,000 replies per 24 hours)
- PostBoost docs: guardrails and daily caps per network
- PostBoost docs: connection health (Threads token refresh)