Thread
Also known as: Tweet thread, Connected post, Long-form chain
Quick definition
A thread is a series of connected posts published as a single unit — most commonly on X (Twitter) where each post connects to the next via reply, but the term also covers chained posts on Threads, LinkedIn (carousel of text), and Bluesky. Threads let creators publish long-form ideas that exceed the platform's per-post character limit.
Contents
What is a thread?
A thread is a sequence of social media posts where each post is linked as a reply to the previous one, presented to viewers as a connected narrative. The term originated on Twitter (now X) where the 280-character limit forced long-form ideas to be split across multiple posts; the convention then spread to Bluesky, Threads (Meta's micro-blogging app), and even LinkedIn (where 'threads' usually mean a single long post followed by a chain of comments by the author).
Threads typically open with a strong hook (often a number or contrarian claim — '5 things I learned shipping a SaaS in 2026 / 1.'), followed by 3-15 connected posts each delivering a single point. The final post commonly includes a CTA — link, follow request, or 'reply with your take'.
Why threads outperform single long posts
Three reasons. First, the X algorithm weighs engagement-per-post; a thread of 8 posts effectively gets 8 algorithmic at-bats while a single 4,000-character X Premium long-form gets one. Second, viewers who engage with one post in a thread are more likely to read subsequent posts (the implicit-CTA-per-post effect). Third, threads encourage saves and bookmarks because viewers want to reference the full sequence later — saves are weighted heavily by every modern social algorithm.
Thread structure that works
Five elements show up in nearly every viral thread. (1) Hook tweet — a number, contrarian claim, or curiosity gap. (2) Promise — explicitly state what readers will get if they keep reading. (3) Beats — one idea per post, no padding. (4) Visual variety — embed images, charts, or short videos in 2-3 posts to break up text. (5) CTA close — final post asks for a follow, links to a deeper resource, or invites replies. Threads that skip the hook or close with no CTA underperform consistently.
Common pitfalls
- ×Burying the hook on tweet 3 — viewers decide to keep reading based on tweet 1
- ×Padding with filler posts to hit a target count — quality over length; 5 great posts beat 12 mediocre ones
- ×Forgetting the CTA close — without 'reply', 'follow', or 'link', the thread leaves engagement on the table
- ×Using inconsistent numbering (mixing '1/' and '(1)' and '1.') — clean numbering signals professionalism
Tips
- ✓Open with a number — '5 things', '7 lessons', '3 myths' — sets reading expectation
- ✓One idea per post — avoid running ideas across two posts; each post should stand on its own
- ✓Embed media in 2-3 posts — images, charts, short videos break up text walls and earn extra engagement
- ✓End with a clear CTA — RT the first tweet, follow for more, or link to a deeper resource
Frequently asked questions
Should I use threads or X Premium long-form?+
Both work. Threads earn more total engagement per piece because each post is its own algorithmic at-bat. Long-form is faster to write and easier to read in one screen. Most creators in 2026 use threads for narrative content (lessons, frameworks, hot takes) and long-form for tutorials and detailed how-tos.
How long should a thread be?+
5-10 posts is the sweet spot. Below 4 feels short for the format; above 15 the engagement curve flattens. Most viral threads land around 7-10 posts.
Can I schedule threads via API?+
Yes. Most scheduling APIs support multi-tweet thread publishing in one call — pass an array of post bodies and the API chains them as replies on the platform side. CodivUpload's API uses x_thread_replies as an array of follow-up post bodies.
Do threads work on Threads (the platform)?+
Yes — Threads (Meta's app) supports chained posts the same way X does. The conventions and audience expectations are slightly different (more casual, less how-to oriented) but the mechanics are identical.
Schedule X threads + cross-post to Bluesky and Threads
CodivUpload's API supports multi-post threads on X, Bluesky, and Threads in a single payload. Schedule the whole thread to dispatch at the optimal hour.
Try thread schedulingRelated glossary terms