TL;DR. The fastest way to unroll a Twitter/X thread is still the original one: reply to any post in the thread with
@threadreaderapp unrolland the Thread Reader App bot answers with a link to the whole thread on one readable page, free, and it still works as of this writing. If you'd rather not reply in public, paste the thread's link into the search box at threadreaderapp.com. If the threads you want unrolled are ones you've bookmarked, Tweetsmash ($14/mo) has a built-in thread reader and Dewey (free tier, Pro $10/mo) saves full threads into a searchable library. And if unrolled threads just join a pile you never reopen, the fix is a digest, not another reader; that's the last section.
Last reviewed July . Tool pricing was checked at the time of writing and can change.
Why is a long thread so hard to read on X?
A thread on Twitter/X is a chain of separate posts, and the native app makes you feel every link in that chain. Open a thirty-post thread and you get the first few posts, then a collapsed "Show more" you have to tap, then strangers' replies wedged between the author's own posts, then an ad, then another tap. Lose your place once, scroll past the wrong reply, and you're suddenly reading an argument in the comments instead of the thread you came for. The experience is bad enough that "unroll" became a verb.
Unrolling fixes exactly that. A thread reader stitches the author's posts together, in order, on one continuous page: no taps, no collapsed replies, no ads breaking the flow of the argument. It's a right-now reading fix for the thread in front of you, and for long technical threads or multi-part stories it's the difference between reading and giving up halfway.
It's worth separating this from a nearby problem: keeping a thread for later. A bookmark on X saves only the single tweet you tapped, and the tools for capturing complete threads durably are a slightly different list, which we cover in how to save entire Twitter/X threads. That guide is about keeping; this one is about reading, turning a live thread into one clean page with a thread unroller, right now.
The four ways to unroll a thread at a glance
Four approaches cover essentially everyone. The first is the classic bot that people are usually searching for, the next two are bookmark tools with a thread reader built in, and the fourth isn't an unroller at all, which we'll be upfront about when we get there.
| Method | Best for | Cost | Where you read it |
|---|---|---|---|
| Thread Reader App | One-off unrolls, right now | Free (Premium $3/mo or $30/yr) | A hosted single page |
| Tweetsmash | Threads you've bookmarked | $14/mo | Inside your bookmark library |
| Dewey | A searchable archive of full threads | Free tier, Pro $10/mo | Inside your library |
| Bulkmark | Threads you save and never reopen | $9/mo | Your email inbox, weekly |
Method 1: Unroll it with the Thread Reader App bot
Thread Reader App is what most people mean when they type Twitter thread unroll into a search box, and as of this writing it still works. Reply under any post of a thread, not just the first one, and mention the bot with the word unroll, like this: @threadreaderapp unroll. The bot replies to you with a link, and that link is the entire thread on a single page, the author's posts stitched top to bottom, readable like an article.
If you'd rather not leave a public reply, there's a quieter route: paste the thread's URL into the search box on threadreaderapp.com and unroll it there directly. Either way, the basic service is free, needs no install, and works the same from your phone or a desktop browser.
There's a Premium tier at $3 per month or $30 per year, which adds extras like PDF export. You don't need it for plain unrolling; it's for people who want to keep or share the unrolled copies rather than just read them once. The service is run by indie developers and has quietly outlived a long list of bigger Twitter tools, including plenty that vanished after X restricted third-party tools. That longevity is a real point in its favor, though nothing that depends on X is guaranteed forever, which is why we hedge with "as of this writing."
Weaknesses, honestly. The unroll is a manual, per-thread action: fine for the occasional standout thread, tedious at volume. The reply route is public, so your unroll requests sit visibly on your profile. And the unrolled page lives on Thread Reader's site, so it's a copy you reach through a link rather than a file you own, unless you print it to PDF or pay for Premium's export. For one thread, right now, though, it remains the most direct thread unroller there is, and the free tier is genuinely free.
Method 2: Tweetsmash, the thread reader inside your bookmarks
Tweetsmash approaches unrolling from the other end. Instead of asking a bot in public, you bookmark the thread on X exactly as you already do, and then read it unrolled inside your bookmark library. Its built-in thread reader presents a bookmarked thread as one piece, so the bookmark you saved stops being a single orphaned tweet with the rest of the thread stranded back on X.
The thread reader is part of Tweetsmash's $14 per month plan, which is really a full Twitter/X bookmark tool: email digests of your saves, exports to Notion and Sheets, and chat over your library, with a 7-day trial. That's the right way to think about the price. Nobody should pay $14 a month just to unroll threads; you pay it if you save a lot of tweets and want the whole pipeline, of which the thread reader is one part.
The trade-off is exactly that scope. It's a subscription, an account, and a workflow, not a one-tap unroll of a thread you stumbled into five seconds ago. If you bookmark threads constantly, it's arguably the more natural home for them; if you unroll three threads a month, it's overkill. We put it side by side with the other options in the 2026 bookmark manager comparison.
Method 3: Dewey, save the full thread into a library
Dewey is a Twitter/X bookmark manager with a Save Full Thread feature, which captures the entire thread rather than just the tweet you bookmarked. Where Thread Reader App gives you a hosted page and Tweetsmash gives you a digest pipeline, Dewey's angle is the archive: threads land in a library with tags, folders, and fast full-text search, and the saved copy survives even if the author later deletes the original.
There's a free tier, and Pro runs $10 per month, which unlocks the sync and export options that turn it into a real archive rather than a manual scrapbook. Researchers, journalists, and anyone who quotes threads in their own work later tend to land here, because a citable copy matters more to them than a pleasant five-minute read.
The honest limitation: Dewey is a place you visit. The full thread is captured and searchable, but reading it still means remembering to open Dewey, and the interface serves the archive, not the "I'm in line at a coffee shop and want this thread as one page" moment. Of the three tools above, it's the strongest for keeping threads and the weakest for the impulse unroll.
Which thread unroller should you use?
Match the tool to how the thread reaches you. If you're looking at a thread right now and want it as one page, use the Thread Reader App bot or its website: it's free, instant, and purpose-built, and neither of the paid tools beats it at that specific job. If you'd rather never reply in public and you already bookmark threads anyway, Tweetsmash's built-in thread reader gives you unrolled reading as part of a bigger bookmark workflow at $14 per month. If your goal is a permanent, searchable archive of complete threads, Dewey is the strongest keeper, with a free tier to start and Pro at $10 per month.
And a plain word about the fourth row in the table: Bulkmark, the tool we make, is not a thread unroller. It won't reconstruct a thread word for word on one page, and if that's what you need, Thread Reader App is the more direct choice. What it addresses is the problem that shows up after the unroll, which deserves its own section rather than a euphemism in a comparison table.
The problem unrolling doesn't solve
Unrolling is a reading tool, and it works, when you actually read. But an unrolled thread you don't finish becomes a browser tab, then a saved link, then one more item in the same pile your X bookmarks are already in. The unroll changed the format; it didn't change the odds you'd come back. In our experience, people who search for a thread unroller are often not short on readers, they're short on return visits. If you save threads faster than you read them, a better reader isn't the bottleneck.
That's the case for flipping the model: instead of pulling threads out to read now, let your saves come back to you on a schedule. That's the approach we take with Bulkmark. It's bookmark-first: you bookmark the thread on X, exactly as you already do, and Bulkmark syncs your bookmarks automatically, tags them by theme, and sends a weekly AI-summarized email digest you can also chat with, at $9 per month with a 7-day trial. The digest works at the level of the bookmark you saved, so what lands in your inbox is a summary that gets you back to the thread, not a word-for-word unroll of it. In practice the two combine well: unroll the thread you want to read this minute, bookmark the ones you don't, and let the weekly email return them to you. The full argument for delivery over storage is in what is a Twitter/X bookmark digest.
Bottom line
Unrolling a Twitter/X thread is a solved problem, and it's still mostly solved by the original tool: reply with @threadreaderapp unroll, or paste the link at threadreaderapp.com, and read the thread as one page, free, as of this writing. Pay for Tweetsmash if you want a thread reader inside a full bookmark workflow, or Dewey if you want complete threads in a searchable archive. Just be honest with yourself about which problem you actually have. If threads pile up unread no matter how nicely they're formatted, the reader was never the bottleneck, and a weekly digest that brings your saves back to you is the only approach on this page aimed at that failure. Unroll for the thread in front of you; fix the delivery for all the ones behind you.