Auto-posting to Threads: 250 a day, no built-in scheduler

Two facts define publishing on Threads in 2026. The app still has no built-in scheduling, and the API opened in June 2024 with a generous ceiling. Together they mean cadence here is entirely a tooling decision, and cadence is the variable that pays.

The API, in numbers

• 250 posts per 24 hours, counted per user rather than per app, so ten managed accounts get ten separate budgets.
• Video up to five minutes; video containers can take thirty seconds or more to finish processing.
• Text capped at 500 characters, with up to ten images per post.
• No native scheduler, so a third-party tool with API access is the only route to a queue.

Growth context

Threads reached 275 million monthly users by late 2024 and around 400 million by August 2025, with roughly 115 million daily actives and a median engagement rate above six percent. The feed is still hungry, which is why volume behaves differently here than on a mature platform.

Making video work here

1. Render the usual vertical master: 1080×1920, captions, clean audio.
2. Keep it under a minute in practice even though five are allowed.
3. Pair it with one strong line of text: posts with a hook outperform bare video.
4. Publish through a tool with API access, allowing for container processing time.
5. Trim copy to 500 characters before the API does it for you.

How Monty fits

Monty turns one take into a finished vertical clip - cuts, captions synced to speech, ducked music, b-roll, cleaned audio, per-platform versions - and publishes to YouTube Shorts, Instagram Reels, TikTok and Telegram. Threads is not on that list yet, so the file goes to your own scheduler. Given that eight to ten posts a day is the winning cadence, the pipeline is the part that makes it possible at all.