On this page12
- What's the actual difference between a thread and a single post?
- The thread test: five questions before you hit "add post"
- Which crypto content works as a thread, and which as a single post?
- How should you structure a single post?
- How should you structure a crypto thread?
- Do threads or single posts get more reach on X?
- When does a thread hurt you?
- FAQ
- How long should a crypto thread be?
- Should I number the posts in my thread?
- Can I turn an old single post into a thread later?
- Is it better to post a thread all at once or one post at a time?
Use a single post when you have one idea that stands on its own: a reaction, an opinion, a sharp observation. Use a thread when the reader needs a sequence to follow, such as an explainer, a timeline, a step-by-step breakdown or a teardown, and when every post in it earns the next one. Most crypto content is better as a single post. Threads win for a narrower set of jobs, and they win big when they're doing those jobs.
I've written both for years. The two posts I still list in my portfolio are both threads from 2022: one on the battle of L1s and L2s, one on the FTX, Genesis and Gemini saga. Most of my day-to-day posting is single posts. Below is how I decide which one a given idea should be.
What's the actual difference between a thread and a single post?
A single post is one idea, delivered whole. The reader gets it, reacts or doesn't, and moves on. It's built for reach and reaction.
A thread is a reading experience. The first post has to win a click, and every post after it has to keep the reader going. It's built for depth and saves, and it asks more of the reader in exchange for giving more.
That trade is the whole decision. If your idea doesn't need the extra space, a thread just makes the reader do more work to get the same thing. If it does need the space, cramming it into one post either loses the nuance or turns into an unreadable block.
If you have access to longer posts on X, a single long post can sometimes replace a thread. The same test applies: does the reader need a sequence, or one point.
The thread test: five questions before you hit "add post"
I run any idea that's tempting me toward a thread through five questions. If I can't say yes to at least three, it becomes a single post.
- Does it have a natural order? Steps, a timeline, a cause-and-effect chain, or a comparison point by point. If you could shuffle the posts without losing anything, it's a list, and lists usually work better as one post.
- Would a reader save it to come back to? Explainers, frameworks and resource lists get saved. Opinions mostly don't.
- Can every post stand as a useful sentence on its own? Each one should hold a fact or a step, not filler like "but wait" or "here's where it gets interesting".
- Is there enough evidence to fill it? A thread padded to seven posts with two real points in it costs you trust.
- Is the first post strong enough to stand alone? Most people only ever see the first post. If that post isn't worth reading by itself, the thread fails before it starts.
Which crypto content works as a thread, and which as a single post?
Here's the split I work from, by type of content.
| Content type | Better as | Why |
|---|---|---|
| Reaction to breaking news | Single post | Speed matters and reporters lift single posts more easily |
| Hot take or opinion | Single post | One claim lands harder without padding |
| Protocol or concept explainer | Thread | Readers need a sequence to build understanding |
| Timeline of an event (exploit, collapse, governance fight) | Thread | Chronology is the structure |
| Marketing or launch teardown | Thread, or single post with image | Depends on how many distinct points you have |
| Resource list (tools, podcasts, newsletters) | Thread, or single post if short | Each item can carry a line of context |
| Lesson from your work | Single post | One lesson, told well, travels further |
| Comparison of two projects | Either | A thread for many dimensions, a single post with a visual for a few |
The explainer and timeline rows are where threads earn their keep. When I wrote about L1s and L2s in September 2022, the topic genuinely needed steps.
1/ 🤺The smart contract wars are on fire, here's a deep understanding of L1's v/s L2's: A Thread [🧵] Shilika Jain on X, 5 Sep 2022
The next day I followed it with a second thread on why L2s exist at all, built around the blockchain trilemma.
Why have L2's when you have so many L1's: Understanding how The Blockchain Trilemma: A THREAD (🧵) Shilika Jain on X, 6 Sep 2022
Two threads on consecutive days worked because each answered a different question. Merging them into one long thread would have lost readers halfway.
How should you structure a single post?
A good single post in crypto has three parts, and it can do all three in under 280 characters:
- The claim. What you think, said plainly in the first line.
- The proof. One specific detail: a number you can stand behind, an example, a pattern you've seen.
- The edge. What it means, or who should care.
A worked example, using a lesson from my own client work. A weak single post: "Launches need a strong narrative! Think carefully about your messaging." A strong one: "Your mainnet launch doesn't need ten features in the pitch. It needs one angle. Rari Chain led with NFT creator royalties protected at the chain level and landed in CoinDesk, The Block and Cointelegraph the same week."
The strong version has a claim, proof the reader can check, and an instruction. It doesn't need a second post.
Single posts also work for comparisons when you can show rather than tell. In 2022, when a couple of threads were already comparing Aptos and Sui on the tech, I posted the marketing side as one post with an image instead.
I've seen a couple of threads differentiating between @AptosLabs & @Mysten_Labs on a technical standpoints:) But here's the specs from the marketing side👇 Shilika Jain on X, 21 Sep 2022
The image carried the comparison. A thread would have split something that worked better seen at once.
How should you structure a crypto thread?
A thread has more moving parts, so it needs more structure. The shape I use:
- Post 1, the hook. States the topic and the payoff, and stands alone. Number it "1/" or mark it with 🧵 so readers know there's more.
- Post 2, the context. Why this matters now. One post, not three.
- Posts 3 to 7 or so, the body. One idea per post, in order. Each should make sense if someone lands on it from a repost.
- A visual somewhere in the body. A diagram, a table screenshot or a chart breaks the wall of text and gets saved.
- The closing post. A one-line takeaway and, if it fits, a pointer to something longer you've written.
Keep most threads between five and ten posts. Past that, I'd ask whether it should be an article instead, and that's often the right call: a strong thread is frequently the first draft of a blog post. I go through that process in turning X posts into blog and LinkedIn content.
Things that kill a thread: a hook that's all suspense and no substance, posts that exist only to build tension, and an ending that asks for a follow without having earned one.
Do threads or single posts get more reach on X?
It depends on the post, not the format, and anyone who gives you a fixed answer is guessing about an algorithm that keeps changing. What I can say from practice is that each format earns a different kind of attention.
Single posts are better at quick reactions, replies and reposts, because they're easy to engage with in a scroll. Threads are better at saves, profile visits and follows from people who want more of your thinking, because they show depth. A balanced account needs both. Mostly single posts to stay present, with a thread when you have something that needs the room.
For founders, I'd frame the mix around what each format does for your profile. Single posts keep you in the conversation and make you quotable to reporters, which I cover in how journalists find sources on X. Threads build the record that convinces an investor or a hire you understand your market. My 12-month X operating system for Web3 founders shows how the two fit into a weekly plan.
When does a thread hurt you?
When it's a single idea wearing a costume. Readers can tell when a thread exists for format reasons, and it costs you trust that a plain post wouldn't.
Threads also hurt during fast-moving news. If an exploit is unfolding, a seven-post thread written in a rush will contain mistakes, and the first post will be screenshotted with them. One careful post, followed later by a thread once the facts are clear, is safer.
And they take time. A good thread takes me far longer to write than a single post, because each post has to be edited to stand alone. If you're posting while running a company, spend that time on one thread a week at most, and let single posts carry the rest. If you'd rather have help shaping long-form threads and the articles they turn into, that's part of my content writing work.
FAQ
How long should a crypto thread be?
Long enough to cover the sequence and no longer. Most of mine land between five and ten posts. If you find yourself going past twelve, the topic probably wants to be an article, with a short thread that points to it.
Should I number the posts in my thread?
Numbering ("1/", "2/") helps readers know where they are and signals a thread in the first post. Some people prefer only a 🧵 on the first post to keep the rest clean. Either works, as long as the first post makes clear more is coming.
Can I turn an old single post into a thread later?
Yes, and it's a good way to develop ideas. If a single post got strong replies or questions, that's a sign people want more. Quote your original post and expand it into a thread that answers what readers asked.
Is it better to post a thread all at once or one post at a time?
Post it all at once. Drip-feeding a thread over hours means early readers see an unfinished piece and many won't come back. Write it in a draft or a scheduling tool first, check that each post stands alone, then publish the whole thing.
Have an idea that's either a great thread or a great article and can't decide which? Book a 30-min teardown with me and we'll shape it together.


