TL;DR. Bookmarking a post on Twitter/X saves only that one tweet, not the whole thread. To keep a complete thread you have three real options: unroll it with Thread Reader (reply with
@threadreaderapp unroll, free), save it into a read-later app like Readwise Reader or Matter that turns the thread into one clean article, or, if your problem is a growing pile of saved threads you never reopen, route your bookmarks into a digest that emails them back to you. Pick the unroller for one-offs, the read-later app for a reading library, and the digest for the backlog.
Last reviewed June . Tool pricing was checked at the time of writing and can change.
Why bookmarking a thread doesn't save the whole thread
When you bookmark a post on Twitter/X, you save exactly one tweet, the one you tapped, and nothing else in the thread. A thread is just a chain of separate replies from the same author, so the platform treats your bookmark as a pointer to a single post. If you bookmark the opening tweet, you've saved the hook and none of the payoff; if you bookmark a tweet in the middle because that's the one that caught your eye, you've saved a fragment with no setup.
This causes two specific problems. The first is friction at read time: to actually read the thread later, you have to reopen the saved tweet, recognize that it's part of a thread, and scroll through the chain on Twitter/X, often past quote-tweets and replies that break the flow. The second is fragility: if the author deletes the thread or their account, your bookmark can break and the content is gone. You bookmarked because you wanted to keep it, but a bookmark doesn't keep it, it just links to it.
The fix in every case is to capture the thread's content somewhere that isn't dependent on a single live tweet. Below are the methods that do that, from the fastest one-off to the most durable system, with the honest trade-offs of each.
The methods at a glance
| Method | Best for | Cost | Keeps a copy? |
|---|---|---|---|
| Thread Reader (unroll) | Quick one-off threads | Free (premium ~$3/mo) | A hosted single-page version |
| Read-later app | Building a reading library | Free to ~$10/mo | Yes, as a clean article |
| Screenshot / print to PDF | Archiving exact wording fast | Free | Yes, as an image or PDF |
| Bookmark digest tool | A backlog you never reopen | ~$9 to $14/mo | Summaries, delivered to you |
Method 1: Unroll it with Thread Reader
Thread Reader is the fastest way to save a single thread, and it's free. Reply to any tweet in the thread (or quote it) and mention the bot with the word unroll: @threadreaderapp unroll. The bot replies with a link to a single-page, readable version of the entire thread, top to bottom, with the replies stitched together. You can also go to threadreaderapp.com and paste the thread's URL or status ID into the search box, then click Unroll Thread.
Strengths: it's instant, it requires no account for the basic flow, and the unrolled page is genuinely pleasant to read compared with scrolling the native thread. It's the right tool when you come across one great thread and want a clean copy right now. There's an optional premium membership (around $3 per month) that adds features like saving threads to your own collection, but you don't need it for one-off unrolling.
Weaknesses: the unrolled version lives on Thread Reader's site, so it's a copy you reach through a link, not a file you own, unless you take the extra step of printing it to PDF. It's also a manual, per-thread action, which is fine for the occasional standout thread and tedious if you're trying to save dozens. For volume, you want one of the next two approaches.
Method 2: Save it into a read-later app
If you want saved threads to live in a proper reading library alongside articles and newsletters, a read-later app is the better home. The standout for threads specifically is Readwise Reader, which explicitly converts hard-to-read threads into clean long-form articles, and pairs that with highlighting, RSS, newsletters, and an AI reading assistant. As of June 2026 it runs $9.99 per month on the full Readwise plan billed annually, with a 30-day trial. Matter is another strong option, with an excellent reading interface, text-to-speech, and a free core tier plus a paid Premium, and it has actively welcomed users migrating from read-later tools that shut down. Instapaper is the long-running minimalist choice, free to save with a Premium tier at $5.99 per month or $59.99 per year for full-text search and a permanent archive.
Strengths: these apps turn a thread into a real, ownable, readable article, store it durably so it survives the original being deleted, and put it in the same queue as everything else you mean to read. If your saving problem is broader than Twitter, this consolidates it.
Weaknesses: threads are usually a secondary feature in these tools, which are built primarily around long-form articles, so the Twitter ingestion is often a forward-or-import step rather than an automatic sync of your X bookmarks. You're adopting a whole reading app to solve a thread problem, which is worth it if you read a lot online and overkill if your saves are almost entirely tweets. If most of what you save is on X specifically, see the dedicated Twitter tools in our 2026 bookmark manager comparison.
Method 3: Screenshot or print to PDF
The lowest-tech method is to capture the thread directly. Unroll it with Thread Reader first so it's on one page, then use your browser's print-to-PDF to save a file, or take stitched screenshots on mobile. This is the right move when you want the exact wording archived fast and you don't care about a tidy reading experience, for example saving a thread as evidence, as a reference you'll quote, or because you suspect it's about to be deleted.
The downside is obvious: a PDF or a stack of screenshots isn't searchable in any useful way, doesn't sit in a reading queue, and turns into its own pile of files you have to organize. It's a capture tactic, not a system. Use it for the handful of threads that genuinely need an exact archived copy, not as your default.
Method 4: Route your bookmarks into a digest
The methods above all assume you'll deal with each thread when you save it. The honest reality, and the reason most people are reading this, is that you don't. You bookmark threads and never reopen them, and a per-thread unroll workflow you have to remember is just another version of the bookmarks tab you already ignore. If the actual problem is a backlog of saved threads you never return to, the fix is to change the delivery, not to add a manual step.
A bookmark digest emails you a summary of what you saved on a schedule, so the threads come to you instead of waiting for you to dig them out. Tweetsmash takes this approach and includes a built-in thread reader, so a saved thread is presented as one piece, with daily or weekly digests starting at $14 per month. Bulkmark, the tool we make, takes a simpler angle at $9 per month: it auto-syncs your X bookmarks, auto-tags them by theme, and sends a weekly AI-summarized digest you can also chat with. We'll be straight that a digest works at the level of the bookmark you saved, so for a guaranteed full, word-for-word unrolled thread, a dedicated unroller like Thread Reader is still the most direct tool. What a digest fixes is the part the unrollers don't: actually getting you back to the threads at all. The two compared head-to-head live in Bulkmark vs Tweetsmash.
Which method should you use?
Match the method to the failure you keep hitting. If you save the occasional brilliant thread and want a clean copy on the spot, use Thread Reader; it's free and instant. If you read widely online and want threads filed in the same library as your articles, use a read-later app like Readwise Reader, Matter, or Instapaper. If you need an exact archived copy of a specific thread before it disappears, screenshot or print it to PDF. And if your real problem is that you save threads constantly and never reopen any of them, no per-thread tool will save you; route the whole pile into a digest so it comes back to you on a schedule. The deeper version of that argument is in why your Twitter bookmarks pile up.
Bottom line
Twitter/X won't save a thread for you; bookmarking keeps one tweet and links to the rest. To keep the whole thing, unroll it with Thread Reader for one-offs, save it into a read-later app for a reading library, or print it to PDF for an exact archive. But if you're saving threads faster than you'll ever read them, the format isn't the problem, the return visit is, and a digest that delivers your saves on a schedule is the only one of these that fixes that. For the full set of approaches to saved Twitter content, start with our complete guide to managing Twitter/X bookmarks.