Quick answer: A thread is a sequence of connected tweets. It is the format to use when the product can't be explained in one 280-character post. The first tweet has to stop the scroll; the rest of the thread has to deliver on what it promised.

How long a launch thread is

A good launch thread is 6–10 tweets. Short enough to finish in one read, long enough to tell the story. Anything longer reads like a blog post the author didn't want to host.

The structure

Tweet 1 — the hook. The single tweet that would stand alone. It states the problem or the claim and ends with the promise of the thread.

Tweet 2 — the problem. The specific situation, the friction, the workaround people use.

Tweet 3 — the product. What it is, one sentence.

Tweets 4–7 — the proof. The workflow, the detail, the honest trade-offs. One idea per tweet. One image or screenshot per tweet where it helps.

Tweet 8 — the limitation or the honest note. What's rough, who it's for, who it isn't.

Tweet 9 — the recap and the CTA. The link in the final tweet and one specific reply prompt.

Writing rules

  • One idea per tweet. If a tweet contains two ideas, split it.
  • A number or a label helps. "1/8" style numbering isn't required, but the reader should know where they are.
  • Read the thread as a standalone reader. Each tweet is a chance for the reader to drop off; each one must either deliver value or move the story.
  • The images are consistent. The screenshots and cards use the same size and visual style, so the thread feels like one piece. The 1200 × 675 size is in the X image guide.

The opening tweet

The first tweet is the most important. It has the same structure as the launch tweet and it must be strong enough to stand alone. It doesn't end with "🧵" alone; it ends with a concrete promise of what the thread delivers.

[Hook]

Here's how we built it and what works:

The final tweet

The final tweet is the CTA and the link:

[Product] is live: [link].

Reply with [specific question] if you try it.

The link is fine in the final tweet of the thread. The first tweet stays clean.

What kills read-through

  • A slow second tweet. If the second tweet doesn't add value, readers stop opening.
  • Feature lists. "It does A, B, C" spread across tweets is a list, not a story.
  • Inconsistent images. Different ratios and random screenshots break the rhythm.
  • A thread that's actually a blog. If the material is 20 tweets, write a blog post and link it.
  • No CTA. The reader finishes and doesn't know what to do.

How threads fit the launch week

The thread is usually the day-2 or day-3 post, because it requires more attention than the launch tweet. The launch day itself uses the single-tweet set; the thread carries the technical story or the how-to. It's also the natural cross-source for a Dev.to article.

Frequently asked questions

How many tweets in a launch thread? 6–10. A build story can go to 12; longer than that loses readers.

Should every tweet have an image? No, but the key explanation tweets should. A screenshot or a card per major beat is enough.

Does the link go in the first tweet? In a thread, the first tweet is clean; the link lands in the final tweet and the pinned first reply.

What's the difference between a thread and a blog post? A thread is for the audience already on X; the blog post is the permanent, searchable version. Write the blog post, then thread it.

Can a thread be scheduled? Yes, and it should be prepared before launch; the hour-by-hour timeline shows where it fits.

Write the first tweet as if the thread doesn't exist. If that one tweet can't carry the launch, fix it before writing the rest.