How to Save a Twitter (X) Thread as a PDF or Image

Save the whole thread, then choose the format

A Twitter thread is a sequence of tweets, now called posts on X. To download a Twitter thread for offline use, keep an exported file rather than only a link.

A bookmark keeps a link in your account. A downloaded file gives you an offline copy. Neither guarantees that you have included every post: check the beginning, middle and end before you close the source.

This guide focuses on a sequence of posts by one author. For a single post, an embed or other platforms, use our guide to clean screenshots of social media posts.

1. Open and check the complete thread

Start with a post’s own URL, rather than the Home feed. X describes a thread as connected posts from one person and provides a Show this thread option to expand it. See X’s thread guide.

1. Open the first post. Keep its URL for your notes.
2. Expand the thread. Follow the author’s connected posts, distinguish them from replies by other people, and open any collapsed text you need.
3. Scroll through to the last post. Give images time to appear. If the author numbered the sequence, use those numbers to spot gaps.
4. Record the capture date and source link. Keep the author’s name visible in the exported copy.

If X requires a login, use your own authorized session. A screenshot tool cannot restore a deleted post or grant access to an account you cannot view.

2. Choose PDF, an image or a bookmark

X’s Bookmarks documentation explains how to save a post inside your account. That does not download the thread to your device.

Choose a PDF when you want pages you can read or print. Choose an image when the appearance matters. A PDF made from screenshots will not gain selectable text simply because you changed the file format. Try selecting a sentence in the finished file.

3. Save the thread as a PDF in your browser

Try the thread page first. If the print preview omits posts or includes too much interface, switch to an accessible reader version and preview it again.

1. Open the page you want to keep and check that the required posts and images have loaded.
2. Press Ctrl + P on Windows or Linux, or ⌘ + P on macOS.
3. Choose Save as PDF as the destination. Select a paper size and orientation that keep text readable.
4. Inspect each preview page. Adjust scale or margins if text runs off the page; enable background graphics if needed.
5. Save the file, reopen it and compare its first and last posts with the source. Test text selection and a link if you need them.

The keyboard shortcuts and print settings come from Chrome’s printing documentation. Your operating system may offer a PDF destination with a different name.

Printing uses a page’s print layout. Sidebars, colors and page breaks can differ from the browser view. A good preview matters more than the number of pages. If it contains only the first few posts, stop and change the source page rather than saving an incomplete copy.

Save a Twitter thread on iPhone or Android

Open the thread or a complete reader page in your browser, rather than relying on the X app’s share menu. Load and check the posts first. The options below depend on your browser, operating system and the page you open.

iPhone: save a webpage as a PDF in Safari

1. Open the page in Safari, then open Share. Some Safari layouts put Share inside the More menu.
2. Choose Markup to view and optionally annotate the page as a PDF.
3. Finish with Done and the file-saving option shown by your iOS version; Apple’s current guide labels it Save File To. Choose a location and save.
4. Open the saved file in Files and compare its first and last posts with the source.

These steps follow Apple’s Safari PDF instructions.

For a long screenshot of a supported webpage, take a screenshot and open its preview, then choose Full Page if available. Review the captured area and use the image or PDF save option offered by your iOS version. Apple documents this in its full-page screenshot guide. The Full Page option is not available on every screen.

Android: print a page to PDF in Chrome

1. Open the page in Chrome, then choose More → Share → Print.
2. Open the printer selector and choose Save as PDF.
3. Inspect the preview, save the PDF to your device and reopen it to check the posts.

See Google’s Chrome for Android printing instructions. Menu placement can vary.

For an image on supported Android 12+ screens, press Power + Volume down, then choose Capture more if it appears and select the capture area. Google’s screenshot guide notes that scrolling capture works on supported scrollable screens. If that option is missing or the thread has gaps, use overlapping screenshots or try a complete reader page.

Mobile export has the same completeness limits as desktop capture. A PDF or scrolling screenshot can still miss unloaded posts; check the saved file before sharing it.

4. Unroll a Twitter thread into a reader page

Thread Reader’s help page describes unrolling consecutive posts from the same author. It does not support arbitrary conversations, private accounts or X Articles.

Its documented bot method is to reply to a post in the thread with @threadreaderapp unroll. This publishes a reply from your account; choose it only if you want that public interaction. Open the returned reader link and compare the sequence with the original. Bot responses can fail because of access restrictions or API limits.

According to its membership page, unrolling by pasting a URL on the website and the built-in PDF archive are Premium features. Its help page also documents free PDF archives for authors of their own threads. Check the current account options before choosing a plan.

If you can view a complete reader page, preview it with your browser’s print dialog or capture it as an image. Later additions to a thread can leave an older reader copy incomplete. A reader link is also not permanent storage; keep the exported file you need.

5. Save a long screenshot as PNG or JPG

Use the original thread if it captures correctly, or a complete reader page when you need a simpler layout.

1. Choose a browser width where post text wraps comfortably and the images are readable. Keep the same width throughout the capture.
2. Expand the content and load the images you need before starting.
3. Run a full-page capture tool. GoFullPage offers PNG, JPG and PDF downloads. Chrome also exposes screenshot commands through DevTools; our Chrome screenshot guide covers the steps.
4. Open the downloaded image at full size. Check for blank regions, repeated headers and missing posts.
5. If the file is too tall to read or share, capture shorter sections with one complete post overlapping between consecutive images. Number them in reading order.

PNG is a useful starting point for text-heavy captures. JPG can reduce file size but may blur small letters. Avoid shrinking a tall screenshot to a tiny width just to fit it into a message.

A screenshot captures a still frame of a video or animation. Keep the original post link alongside the image when a reader needs to view that media.

6. Fix missing posts, blank areas and broken captures

Loading more content and keeping that content on the page are different behaviors. In a virtualized list, the application can remove offscreen items as you scroll. Google’s explanation of list virtualization shows how this works. This explains a possible failure mode; it does not establish which rendering technique X uses in every view.

Waiting longer cannot reconstruct a missing post. Compare the output with the source after changing tools or settings. Our full-page capture guide explains the difference between document height, scrolling and loaded content.

Automate an accessible page with SnapshotFlow

If you maintain an authorized public page containing the thread, SnapshotFlow can render that page to PNG or PDF. It does not unroll an X thread, reconstruct missing posts or inherit the login from your desktop browser.

1. Create a SnapshotFlow account or sign in to your dashboard.
2. Open API tokens to get your API key. Keep the key in your server environment or local shell.
3. Try your public page URL in the SnapshotFlow playground, select PDF or PNG, and inspect the result. Use the API example below when you are ready to automate it.

The following request uses a public page URL that you supply. Set THREAD_PAGE_URL to a page you own or have permission to process, and SNAPSHOTFLOW_API_KEY to your key. Check one result before adding it to an automated workflow.

: "${THREAD_PAGE_URL:?Set an authorized public page URL}"
: "${SNAPSHOTFLOW_API_KEY:?Set your SnapshotFlow API key}"

curl --get --fail-with-body 'https://api.snapshotflow.com/screenshot' \
  -H "X-Api-Key: ${SNAPSHOTFLOW_API_KEY}" \
  --data-urlencode "url=${THREAD_PAGE_URL}" \
  --data-urlencode 'format=pdf' \
  --data-urlencode 'media_type=print' \
  --output thread.pdf

For a long PNG, change format=pdf to format=png, use media_type=screen, add full_page=true and save to thread.png. PDF uses a print layout; full_page controls image capture, not PDF pagination. See the API documentation and webpage-to-PDF guide.

Direct X URLs may show a login screen, a block or an incomplete sequence to a hosted browser. A successful API response alone does not prove that you captured the thread.

Check the file before sharing it

• Compare the first, middle and last posts with the source. Check any numbering for gaps.
• Keep the author, original URL and capture date with the copy.
• Inspect images and text at the size your recipient will use.
• Separate the author’s thread from other people’s replies.
• Remove unrelated personal information from the copy you plan to share.

A downloaded copy does not itself grant permission to republish the author’s content. For attribution, embeds and reuse, continue with our social media screenshot guide.

Frequently asked questions

Sources and further reading

Provider documentation checked October 20, 2026. Membership rules and interfaces can change.

• X: creating and viewing a thread
• X: Bookmarks
• Chrome: printing a page
• Thread Reader: unrolling, limitations and author accounts
• Thread Reader: membership features
• GoFullPage: full-page capture and exports
• web.dev: how virtualized lists render content