Platforms — Threads
Schedule Threads posts
Connect a Threads account, compose posts and chained threads, and schedule them next to everything else you publish.
The text network Meta actually built for threads
Threads is the one Meta surface with a native self-reply, which means a thread composed in postfast publishes as a real chained thread rather than as a series of unrelated posts.
It also takes 500 characters instead of X’s 280, so a body that overflows on X frequently fits here untouched. Publish Guard counts against the tightest limit among the networks you actually selected, so it tells you which ones are the problem rather than making you guess.
What Threads accepts in one post
Read from the same capability table the composer warns from and the publisher builds payloads from. postfast's own bound of 5,000 characters and 4 media items applies on top, whichever is tighter.
- Characters
- 500 per post.
- Media items
- 20 per post on Threads's side; postfast accepts 4.
- Media required
- No. A text-only post publishes fine.
- Threads
- Native. Threads sets no limit of its own; postfast accepts up to 25 replies in one composed thread.
- Cost per post
- Nothing. The platform charges no API fee for publishing.
- Scheduling
- postfast holds the post and hands it over at the moment it is due, so a post can be scheduled a minute out or a year out.
How connecting works
- OAuth 2.0, redeemed server to server. You approve postfast on Meta’s consent screen; the authorisation code is exchanged for a token by our server, never in the browser.
- Tokens are sealed at rest. Encrypted under the application secret, opened in memory only to sign a call, and returned by no endpoint.
- Meta’s deletion callback reaches it. Threads is covered by the Meta data-deletion endpoint postfast operates: when Meta says to forget somebody, every connected Threads account belonging to that person is erased across every workspace it appears in, and a confirmation code is issued.
What you get
Chained threads
Self-replies chain the way Threads models them, published in order and resumed rather than restarted after a failure.
One composer, several networks
Aim the same post at Threads, Instagram and X together; each carries its own status and its own error.
Free per post
Threads charges no API fee, so nothing about publishing here is metered.
A real deletion path
Not a promise in a policy — an endpoint Meta calls, an erase that crosses workspaces, and a status page you can check with the confirmation code.
Common questions
- Can postfast publish threads to Threads?
- Yes. Threads supports a self-reply, so a composed thread publishes as a genuine chain rather than as separate posts.
- What happens to my Threads data if I remove the app?
- Meta calls postfast’s data-deletion endpoint. Every connected Threads account belonging to that Meta user is erased, in every workspace it was connected to, and you get a confirmation code and a status page. Posts you composed stay, because they are your workspace’s content rather than Meta’s.
- Does a Threads post need an image?
- No. Threads publishes a text-only post fine. Instagram is the network in postfast that refuses one.
Scheduling to Threads, and six other networks
postfast is pre-launch. Join the waitlist and you will hear from us when early access opens.