How to save Twitter threads

X shows a thread as a stack, and stores it as separate posts. Each one has its own URL, its own chance of being deleted, and its own bookmark. The first post is the one people share. The argument, the data and the images are often five posts down. Saving the top post feels like saving the thread. It isn’t.

There is also no official “download this thread” button. Anything that looks like one is a third-party reader, a print dialog, or a save of whatever post is in the address bar.

An unroller fetches the public posts in a chain and lays them out as one page, so you can read without tapping “show more”. Thread Reader is the best known. Others do the same job. They are good for reading a long public thread once, and for making a PDF of that single page.

They are a bad archive. They can only read posts that are still public. A protected account, a deleted post in the middle, or a suspended author leaves a hole. You do not control their copy, and you should not assume they keep one after X removes the post. If the thread matters, the unrolled page is a convenient view to save from — not the save itself.

The reliable manual method: unroll, or open the thread expanded in a desktop browser, then Ctrl+P or Cmd+P and choose Save as PDF. Check the page count before you save. Browsers often capture the first screen and clip the rest unless you scroll the thread open first. A PDF of the top post only is a very short thread.

You now have a private file. It will not pick up posts the author adds later, which is usually what you want. Finding it again means finding that file. See how to save tweets for how PDF compares with a bookmark and a screenshot.

A full-text archive stores words you can search. For a thread, that means saving the posts that hold the content. WHT.day’s extension saves the post open in front of you — its text, author and images — and files that post on today’s page in your archive. It does not walk the reply chain and pull every post the author wrote underneath. Claiming otherwise would be false.

In practice you save the opener if it says something, then the posts with the numbers, the images and the conclusion. Three saves is a normal thread. Fifty replies from other people are usually not the thing you meant to keep. If a post is deleted later, the saves you made still have their text. The ones you skipped do not. That is the same rule as archiving tweets generally.

You will not remember that the sentence lived in post seven. Search has to run across the posts you saved, not inside one image. A single PDF is searchable if your reader supports it, and only inside that file. Separate text saves are searchable together, which is how you find “the thread about the grid” when you remember a phrase and not the author.

Dating the saves helps more than a folder called Threads. Threads are about a moment. Opening the day you saved them puts the posts next to the articles from the same story. That is what the archive is for, and it is why a thread of pointers on X is still fragile even after you have organised the bookmarks.