Why repurpose instead of starting from scratch
The hard part of writing is having something to say. If you've written a blog post, recorded a podcast or given a talk, that part is done. Repurposing is translation: same ideas, new format, new readers.
It works because most of your followers never saw the original. A newsletter reaches subscribers, a podcast reaches listeners. On X, the same idea reaches people who didn't know you had either.
One piece, many posts
Each kind of source has natural pieces to pull out, and each piece has a format it fits on X:
| Source | What to pull out | X formats |
|---|---|---|
| Blog post or guide | The main argument, each subheading, any list | Thread, quick tips, an opinion tweet |
| Newsletter | The lead story, a surprising number, the links | Single tweets, a weekly roundup thread |
| Podcast or interview | Quotable lines, disagreements, stories | Quote posts, a story thread, a question |
| Talk or webinar | The framework, the slide people photographed | Framework thread, image post |
| Case study | Before and after, the process, the result | Case study thread, milestone tweet |
| Changelog or docs | What changed and why it matters | Feature update tweet, how-to thread |
A five-step repurposing process
- Pick one strong source. Something that did well where it was published, or that you'd still stand behind today.
- Pull out the atoms. Every standalone claim, number, story, list and quote. A 1,500-word article often holds a dozen or more.
- Match each atom to a format. A list becomes a thread, a sharp claim becomes a single tweet, a story becomes a short thread.
- Rewrite for the feed. Shorter sentences, a hook in the first line, one idea per tweet. Drop the original intro.
- Spread them out. Schedule the posts across one to two weeks instead of dumping them on one day.
Step four is where most repurposing fails. Paragraphs written for a page read as walls of text in the feed. Cut transitions (“In this section...”), cut the throat-clearing, and lead with the most interesting sentence even if it was buried in the original. How to write hooks helps with that first line.
Worked example: one blog post, three posts
Say a fitness coach wrote a blog post called “Why your step count matters more than your workout”. Here's part of what it can become.
- Y
Your name@you
Your 45-minute workout is not the main thing moving the needle. It's the 23 hours around it. The clients who make the most progress with me train three times a week and walk every day. The ones who train six times and sit the rest of the day tend to stall.
- Y
Your name@you
Quick tip: take every phone call standing up and walking. It's the easiest way I know to add steps without finding time for a separate walk.
- Y
Your name@you1/2
I've tracked steps with every client for five years. Here's why step count beats almost anything else you can measure:
- Y
Your name@you2/2
1. It's the easiest habit to keep. No gym, no plan, no change of clothes. You just need a reason to stand up.
Each post stands on its own. None of them needs the blog post to make sense, and that's the test.
Tips by source format
Blog posts into threads
Use the headings as the skeleton: one tweet per heading, the post's main claim as the hook. The thread splitter breaks pasted text at 280 characters, but rewrite each tweet afterwards so it reads as a tweet, not a fragment. See how to write a thread.
Video and podcasts into quotes
Pull lines from the transcript that work without context: short, specific, a little surprising. Add one sentence of your own around each.
Newsletters into a series
If your newsletter has a recurring structure, mirror it on X with a recurring post, like a weekly “three things I learned” thread. The listicle thread and newsletter promo tweet templates fit here.
Long pieces into long posts
For pieces too long for a thread, X offers long-form posts and articles to some accounts, depending on subscription. Keep the structure, tighten the intro, and post a short tweet that sells the read.
Turn one source into a two-week plan
Here's how a single strong article can spread across two weeks without anyone feeling they've read it twice:
| Day | Post from the source |
|---|---|
| Day 1 | A thread with the main argument |
| Day 2 | A single tweet with the most surprising claim |
| Day 4 | A quick tip pulled from one subsection |
| Day 6 | A question to your audience about the topic |
| Day 8 | A story or example from the piece, told as a short thread |
| Day 10 | An opinion tweet that takes the argument one step further |
| Day 13 | The link post, pointing to the full version |
Fill the days between with posts on other topics. Put the link post last: by then people have seen the idea several times, and the ones who want more will click.
- Y
Your name@you
For two weeks I've been posting pieces of one idea: why most budgeting apps fail people with irregular income. The full version, with the spreadsheet I actually use, is in this week's newsletter. Link in the reply.
Mistakes to avoid
- Posting everything from one source on the same day.
- Keeping the original intro. Start with the payoff.
- Copy-pasting without rewriting. A paragraph is not a tweet.
- Repurposing weak material. If it didn't work as a blog post, it won't work as a thread.
- Linking every post back to the source. One link post per piece is plenty.
Extudio's thread maker helps with the rewrite step: paste a long draft, split it into a thread at 280 characters, then rewrite any single tweet in your brand's voice or generate a linking tweet where the jump between two is too big. The article writer goes the other way, drafting long-form from a topic.