How to Unroll a Twitter/X Thread (and Turn It Into a Document You Can Use)

How to Unroll a Twitter/X Thread (and Turn It Into a Document You Can Use)

Someone shares a 20-tweet thread that's genuinely useful (a breakdown of a technical concept, a founder's lessons from a failed launch, a step-by-step framework) and you want to actually keep it. Not as a link you'll lose in your bookmarks, but as something you can read end-to-end, search later, or hand to an AI tool. The problem is that X renders a thread as a scroll of separate posts, not a document. "Unrolling" is the fix for that: stitching the individual tweets back into one continuous piece of text. PostToSource does the same unrolling, but outputs a clean file instead of just a readable webpage, which matters the moment you want to do more than read it once.

This guide covers what unrolling actually does, the three real ways to do it, and how to go one step further and turn an unrolled thread into a document you can drop into ChatGPT, Claude, or NotebookLM.

What "Unrolling" a Thread Actually Means

A Twitter/X thread is a chain of individual posts connected by "replying to self." Scrolling through one on the timeline means tapping "Show this thread," waiting for replies to load, and reading each 280-character fragment separately, with ads, like counts, and quote-tweets included.

Unrolling collapses that chain into a single page: one block of text, in order, without the surrounding noise. It doesn't change the content, just the format: from "a sequence of posts" to "a document." That distinction is exactly why it matters for anything beyond casual reading: a document can be searched, skimmed, archived, or pasted into another tool. A live thread on X can't.

Three Ways to Unroll a Twitter/X Thread

1. The @threadreaderapp bot. Reply to any tweet in the thread (or quote-tweet it) and mention @threadreaderapp unroll. The bot replies with a link to an unrolled version hosted on its own site. This is the oldest and most widely known method, and it's genuinely useful if you just want a shareable, readable link. See our full comparison in Thread Reader App vs. PostToSource for where it holds up and where it doesn't.

2. Manual copy-paste. Open each tweet, copy the text, paste it into a note or doc, repeat for every tweet in the thread. It works, but it's slow, it's easy to miss a tweet in the middle, and it throws away embedded images, links, and formatting unless you manually re-add them.

3. A dedicated unroll-and-export tool like PostToSource. Paste the thread's URL in, and PostToSource unrolls it and exports it as a clean PDF and Markdown file in one step. The PDF keeps the images; the Markdown keeps the text and links. This is the version worth using if the thread is going somewhere other than "read once and move on."

Step-by-Step: Unroll a Thread with PostToSource

1. Open the thread on X and copy the URL of the first tweet in the chain.
2. Paste the URL into PostToSource.
3. PostToSource walks the reply chain, keeps the author's own posts in order, and leaves out replies from other people and the surrounding UI chrome. (The PDF still shows each post's like, repost and reply counts; the Markdown is text only.)
4. Choose your output: a clean PDF for reading or archiving, or a Markdown file if the thread is headed into an AI tool.
5. Download the file and upload it to NotebookLM, ChatGPT, or Claude as a source.

That last step is the part a bot-reply unroll doesn't cover: it gives you a readable webpage, not a file you can upload anywhere.

Why Unrolling Is Only Half the Job

A readable thread and a reusable thread are different things. Once you've unrolled a thread, you're usually trying to do one of three things with it:

• Archive it before the original author deletes the account or the thread gets buried in your bookmarks. See why X/Twitter bookmarks disappear for how often this actually happens.
• Reference it later across dozens of threads you've saved, which only works if they're searchable files rather than a pile of browser tabs. Our guide on turning Twitter bookmarks into an AI knowledge base covers that workflow end to end.
• Feed it into an AI tool to summarize, question, or build on, which requires a document, not a link, since most AI tools can't log into X to read a thread themselves.

For that third case, Markdown is often the handier export: it's a small plain-text file with every post's text and links, easy to edit or combine before you upload it, and NotebookLM accepts Markdown files as sources. If you're collecting threads on a specific topic rather than just saving one, see our breakdown of turning X/Twitter threads into a personal AI knowledge base for how to structure that at scale. And if the thread in question is actually one of X's longer-form Articles rather than a chain of tweets, the unroll step doesn't apply. See how to convert X Articles to PDF instead.

For a broader starting point on getting any social content into an AI tool, our guide to building an AI knowledge base from social content and the import social posts into NotebookLM guide both walk through the full setup.

Frequently Asked Questions

Does unrolling a thread work on private or protected accounts?

Not with PostToSource. It only reads publicly viewable posts, so threads from protected accounts won't convert, and neither will deleted or age-restricted posts. If you follow a protected account and can see the thread, copying the text by hand is the fallback.

What's the difference between unrolling a thread and converting it to PDF?

Unrolling just reformats the thread into one continuous, readable piece; it's still a webpage. Converting to PDF (or Markdown) takes that unrolled content and saves it as a portable file you can store, share, or upload elsewhere. PostToSource does both in one step; the bot-reply method only does the first.

Can I unroll a thread on mobile?

Yes. The @threadreaderapp bot works the same way from the X mobile app: reply and mention it. PostToSource works from any mobile browser too, since it only needs the thread's URL, not an app install.

Why would I want a Markdown file instead of a PDF?

Markdown keeps the text and links as plain text instead of a fixed visual layout, so it's easy to edit, trim or merge before you upload it, and NotebookLM accepts it as a source just like a PDF. Choose the PDF when you want the images and a layout that's pleasant to read or share.

Unrolling a thread gets you something readable. Turning it into a file gets you something reusable, and that second step is where PostToSource actually earns its keep, whether you're archiving one great thread or building a whole library of them.