Why threads are hard to save
Every post in a thread is a separate page element with its own interactions, timestamps and reply counts. Print the page and you get the interface — like buttons, avatars, navigation, ads — along with the words. What you wanted was the writing.
The other problem is completeness. Long threads lazy-load. Print too early and you capture the first eight posts and quietly lose the rest, which you may not notice until you open the PDF weeks later.
Method 1: the browser print dialog
This is free and needs no tool. It also has predictable limits:
- Scroll the whole thread first. Otherwise the lazy-loaded posts below the fold are missing from the output.
- Use reader mode if available. Firefox and Safari can strip the interface and leave mostly text.
- Expect page breaks mid-sentence. Print CSS for a feed was never designed for reading.
- Images may be dropped or stretched. Especially on narrow phone screens.
Method 2: convert the thread into a document
A converter reads the whole thread, rebuilds it in order, and writes a real document — which means the output is editable, searchable and portable. That is the difference between a screenshot of a page and a document about a topic.
What a good output actually contains
- Posts in the original order — not sorted by likes or by reply threads.
- The author's handle and the post dates, so the file still makes sense in a year.
- Images placed where they appeared in the thread, not dumped at the end.
- Plain text you can select and search, not a stack of screenshots.
- The source link, so a reader can verify it themselves.
Quote posts and long threads
A thread that quotes other posts can look garbled in any converter, because the quoted post is a nested object rather than a line of text. Check the middle of the document where the quotes are, not just the beginning.
For very long threads, some tools stop early or time out. Whatever you use, compare the number of posts in the output with the number in the original before you delete your bookmark.
What about X bookmarks
Bookmarks are a private list of links inside the app. They are still links: if the author deletes the post, the bookmark becomes an empty slot. If the thread matters to you, keeping a copy on your own device is the only version you actually control.
Frequently asked questions
Can I save a thread as a PDF for free?
Yes — the browser print dialog costs nothing. The trade-off is that you get the interface along with the text, and images may not survive. A converter produces a cleaner document with the post order and images preserved.
Why is the last part of my thread missing?
Almost always lazy loading. Scroll to the very bottom of the thread before you save, or use a converter that reads the thread from the source rather than from the rendered page.
Do I need an X account to convert a thread?
For public threads, no. Paste a link and convert. Protected accounts are the exception — if you cannot view a post logged out, no tool can pull it for you.
Which format should I pick — Word, PDF or Markdown?
PDF to send to someone, Word if you want to edit or excerpt it, Markdown if it is going into a notes app or wiki. All three come from the same conversion.
Are the images included?
Public post images are fetched and placed inline, in the position they appeared. Video files are not embedded; the poster and the source link are kept instead.
Turn a thread into something you can keep
Paste an X post or article link and get a clean Word, PDF or Markdown file with the images in place.
Open Postprint