How to Save Social Media Posts & Forum Threads as PDFs on Mac

Social media posts disappear. Tweets get deleted. Reddit threads get nuked by moderators. Instagram accounts go private. Forum servers shut down. Hacker News threads drift into the archives. One day the post is there, the next it's gone — and no amount of Googling brings it back.

If a post matters to you — a useful discussion, a technical explanation, a thread you want to reference later — the only reliable way to keep it is to save it locally. Not a bookmark. Not a "like." A file on your Mac that works offline and can't be deleted by someone else.

This guide covers saving posts and threads from Twitter/X, Reddit, Instagram, Hacker News, and traditional forums as clean, searchable PDFs. The same technique works across all of them.

TL;DR: Open the post in its own page, capture it with window screenshots, scroll through long threads with Page Down automation, and export as a searchable PDF. Works on any public social media post or forum thread.

Why Save Social Media Posts Locally?

The obvious reason: posts disappear. But there are several specific scenarios worth thinking about:

Content deletion. Authors delete their own posts for all sorts of reasons. A developer shares a brilliant debugging technique in a tweet thread, then deletes their account six months later. Gone.

Moderation and takedowns. Reddit moderators remove threads. Subreddits get banned. Discord servers get deleted. Forum administrators close and archive boards. Content that violates platform rules — or just annoys the wrong moderator — vanishes.

Platform changes. Twitter rebranded to X and restricted its API, breaking many third-party tools. Platforms change URLs, restructure their sites, or shut down entirely. The Wayback Machine catches some of this, but not all.

Access changes. Public accounts go private. Free content moves behind paywalls. Posts that were visible yesterday require a login today.

Saving a local PDF means none of this affects you. The content lives on your Mac, searchable, offline, permanent.

The Core Technique

The approach is the same across every platform:

1. Open the specific post or thread in your browser — not the feed, the individual post
2. Window capture the browser for a clean screenshot
3. Page Down automation for threads that extend below the fold
4. Export as PDF with automatic OCR for searchability

The differences between platforms are mostly about how to get to the right view and how long the content runs.

Twitter / X Threads

Single Tweets

A single tweet is the simplest case. Open the tweet in its own page by clicking on it (or using its direct URL). The tweet, along with any attached images, appears in the center column.

Open Shotomatic, select window capture, choose your browser window, and take one capture. Export as PDF. Done — 30 seconds.

Tweet Threads

Twitter threads can run dozens or hundreds of tweets long. For these:

1. Open the thread by clicking the first tweet — this loads the full thread view
2. Scroll to the top so you start from the beginning
3. In Shotomatic, select window capture and choose your browser window
4. Press Page Down in the key recorder to set it as the automated keypress
5. Set the interval to 1000ms — Twitter loads replies dynamically, so give it time
6. Click Start — Shotomatic captures, scrolls, captures, scrolls
7. Stop when you reach the end of the thread or where replies from others begin

Tip: Twitter/X's thread view includes replies from other users below the original thread. If you only want the author's thread, stop capturing when you see the "More Tweets" divider or replies from other accounts.

Quote Tweets and Embedded Content

Quote tweets and embedded media appear inline in the thread view. They're captured as they appear on screen — images, quote tweet cards, and all. Embedded videos show as thumbnails.

Reddit Threads

Reddit threads are often the most valuable content to archive. Technical Q&A, detailed how-to posts, niche community discussions — Reddit contains genuinely irreplaceable information.

Short Posts

For a post with a handful of comments:

1. Open the post in its own page (click the title or use the permalink)
2. Old Reddit (old.reddit.com/r/...) works better for archiving — it loads all comments on one page without infinite scroll, and the layout is more compact
3. Window capture, single shot or a few Page Down scrolls, export as PDF

Long Threads with Many Comments

Reddit threads with hundreds of comments need scrolling:

1. Open the thread. On old Reddit, click "show all comments" if available. On new Reddit, you may need to click "load more" a few times first
2. In Shotomatic, set Page Down as the keypress and 800ms interval
3. Start capturing and let it scroll through the entire thread
4. Stop at the bottom

Tip: If you only care about the original post and top-level comments, collapse the deep reply chains before capturing. This keeps your PDF focused and shorter.

Saving Entire Subreddit Posts

If you want to archive multiple posts from a subreddit (before it gets banned, for instance), capture each post individually. Open each one, capture it, export. There's no shortcut for bulk Reddit archiving — each thread is its own page.

Instagram Posts

Instagram is trickier because it's designed to keep you in the app, not on the web. But web capture works fine for public posts.

Single Posts

1. Open the post's direct URL in your browser (instagram.com/p/...)
2. The post, caption, and a few comments appear on one page
3. Window capture, single shot, export as PDF

Carousel Posts

Instagram carousels show multiple images in one post. Each image requires clicking the arrow to advance. For these:

1. Open the post in your browser
2. Capture the first image with window capture
3. Click the next arrow manually, capture again
4. Repeat for each image in the carousel

This is a manual process — Instagram carousels don't respond to Page Down. Each slide is a separate capture, but they all export into one PDF.

Instagram Stories and Reels

Stories are ephemeral by design and don't have permanent URLs on the web. If you can see a story in your browser, you can screenshot it, but you'd need to act fast. Reels are video content — a screenshot captures only a single frame.

Hacker News Threads

Hacker News is one of the best platforms to archive from. Threads contain deeply technical discussions, startup insights, and expert opinions that are hard to find elsewhere.

Why HN Threads Are Worth Archiving

HN threads don't get deleted often, but they do become harder to find over time. The search on HN is mediocre, and Google doesn't always surface old threads well. A local archive with OCR lets you search across years of saved discussions.

Capturing HN Threads

1. Open the thread page (news.ycombinator.com/item?id=...)
2. HN loads all comments on one page — no infinite scroll, no "load more" buttons
3. Window capture your browser, set Page Down as the keypress with 600ms interval (HN pages are lightweight and load fast)
4. Capture the full thread, export as PDF

Tip: HN's default view nests comments deeply. If you want a more compact capture, consider using a HN reader extension or the mobile-friendly view.

Traditional Forums (phpBB, Discourse, vBulletin)

Old-school forums are the most at risk of disappearing. Forum software gets outdated, hosting gets expensive, communities move to Discord, and decades of archived knowledge vanish.

Forum Threads

1. Open the thread — most forums show one page of posts at a time
2. Capture the current page with window capture and Page Down
3. If the thread spans multiple pages, navigate to each page and capture separately
4. Each page becomes its own PDF, or you can combine them

Multi-Page Threads

Some forums have a "show all posts" or "print view" option that loads the entire thread on one page. This is ideal — one long scroll capture gets everything.

If not, capture each page separately. Name them sequentially: ThreadTitle_Page1.pdf, ThreadTitle_Page2.pdf, etc.

Organizing Your Archive

Social media and forum content adds up quickly. A naming convention keeps things findable:

Naming Suggestions

Platform_Author_Topic_Date.pdf

Examples:

• Twitter_dhh_RailsPerformance_20260315.pdf
• Reddit_AskHistorians_RomanAqueducts_20260310.pdf
• HN_LLMScaling_20260322.pdf
• Forum_WoodworkingTalk_JointerSetup_20260301.pdf

Folder Structure

Social Archive/
├── Twitter/
├── Reddit/
├── HackerNews/
├── Instagram/
└── Forums/

Searchability

PDF export includes OCR automatically, so all the text in your archived posts is searchable. This is the key advantage — you can search across hundreds of saved threads to find that one comment about a specific technique or tool.

Legal and Ethical Notes

Public posts are public. Saving a public tweet or Reddit post for personal reference is no different from taking a screenshot of it — which millions of people do every day.

Don't redistribute. Saving for personal use is fine. Republishing someone else's content — even as a PDF — without permission is not.

Respect deletions. If someone deletes their post, they had a reason. Your local archive is for your own reference. Don't use it to surface content someone intentionally removed.

Platform terms of service generally prohibit automated scraping, but screenshot capture is a standard OS-level function, not scraping (Twitter/X Terms of Service, Reddit User Agreement). You're capturing what's visible on your screen, the same way the built-in macOS screenshot tool does.

Tips for Better Captures

Use the post's direct URL. Don't capture from the feed view — open the specific post or thread in its own page. This removes feed noise and gives you just the content you want.

Increase the interval for media-heavy posts. If posts contain images or embedded media, set the capture interval to 1000-1500ms to let everything load before the next scroll.

Capture at Retina resolution. On a Retina Mac, window captures are automatically high-DPI. This means text is crisp and images are sharp in the exported PDF.

Clean up before capturing. Use an ad blocker, hide sidebar content, or resize the browser window to focus on the main content column. Less noise means a cleaner PDF.

FAQ

Is it legal to save social media posts as PDFs?

Saving public posts for personal archiving is generally fine. You're making a local copy of content that's already publicly visible. Don't redistribute, republish, or use saved content commercially without the author's permission.

Can I save posts from private accounts or groups?

This guide covers public posts only. You can technically capture anything visible on screen, but saving content from private accounts or closed groups raises ethical and potentially legal concerns. Stick to public content.

Will the PDFs be searchable?

Yes. PDF export includes OCR automatically, so text in your screenshots becomes searchable. You can find specific usernames, keywords, or phrases across your entire archive using Finder or Spotlight.

What about embedded images and videos in posts?

Images are captured in the screenshot as they appear on screen. Videos can't be captured as stills — you'll see the video thumbnail or player. For video content, you'd need a separate download tool.

How do I handle infinitely scrolling pages?

Social media feeds scroll forever, but individual threads don't. Focus on capturing specific threads or posts rather than entire feeds. For long threads, Shotomatic's Page Down automation scrolls through until you stop it.

Keep What Matters

Social media is ephemeral by design. Posts come and go. Threads get buried. Platforms change. The only content you can truly rely on is the content you've saved locally.

A few minutes of capture work gives you a permanent, searchable archive of the discussions and posts that matter to you — immune to deletions, moderation, and platform shutdowns.

Shotomatic has a free trial with limited captures, and paid plans for unlimited use. Everything runs locally on your Mac.

Download Shotomatic