How to run a megathread on your subreddit
A megathread is the single most underrated tool in a branded subreddit's programming calendar. It is a pinned post that consolidates a recurring topic so the same questions do not flood the main feed. Done well, a megathread deflects a third to half of repeat questions, keeps the main feed clean, and becomes the permanent reference document for new subscribers who arrive with the same questions everyone else had. Done badly, it goes stale within a week, the OP never gets updated, and the community stops trusting it. The difference is discipline, not cleverness.
What a megathread is, and what it is not
A megathread is one post that absorbs the conversation on a topic that would otherwise generate dozens of near-identical posts. The point is not to suppress discussion. The point is to consolidate it so the main feed stays varied and the specific topic becomes easier to find and easier to answer.
A megathread is not a stickied announcement that gets posted and forgotten. It is an active document that the mod team updates as the conversation evolves, with a clear OP that explains what the thread is for, how to ask questions, and where the canonical answers live. If you post a megathread and never touch it again, you do not have a megathread. You have a dead pinned post that makes the subreddit look neglected.
When to use one
Megathreads are the right tool for a predictable set of situations:
- FAQs. The questions new subscribers ask most often. Put the answers in one place so the community can link to them.
- Product launches. A single thread for everything related to a launch: questions, bug reports, reactions, and links to official docs.
- Event live threads. Conferences, keynotes, earnings calls, or any scheduled event where the community wants to react in real time.
- Customer support consolidation. Billing questions, account questions, or any topic where the same handful of edge cases come up constantly.
- Weekly check-ins. "What are you working on this week?" or "What is frustrating you about the product this week?" Recurring rhythm posts that give regulars a reason to return.
Megathreads are the wrong tool for topics that deserve their own dedicated posts. If every new bug report fits in the weekly support megathread, the megathread is doing its job. If a major outage happens, it needs its own thread with its own sticky. The rule is that a megathread consolidates predictable, recurring, low-individual-weight topics. It does not absorb high-urgency or one-off events.
How to set one up
The mechanical setup is straightforward:
- Write the OP as a real document. Headers, bullet points, links to canonical support pages, and a short statement of what the thread is for. The OP should be useful even if nobody ever comments.
- Sticky it. Reddit allows two stickies per subreddit at any given time. The megathread goes in one of those slots. The other is typically reserved for a welcome post or the most recent announcement.
- Choose the right sort order. For FAQ megathreads, sort by new so the newest questions are visible and the mod team can answer them in order. For discussion megathreads or giveaways, consider contest mode, which hides scores and randomizes comment order to give every reply an equal shot at visibility.
- Assign an owner. One person inside the company is responsible for the megathread. They update the OP, respond to new questions, and refresh the thread on a schedule. Megathreads without owners die.
Reddit's sort modes for threads are hot, new, top, controversial, and contest mode. Each serves a different purpose. For a support FAQ, new is usually right because it surfaces questions that have not been answered yet. For a launch discussion, hot is usually right because it surfaces the conversations that are actually happening. For a giveaway or a "pick one winner" format, contest mode is the right choice because it hides scores and prevents early comments from running away with the thread.
The r/MintMobile gold standard
The canonical example of a megathread done well is r/MintMobile's pinned FAQ. Per Foundation Inc's analysis, the thread is roughly 6,000 words long and contains over 100 links to official Mint Mobile support pages (Foundation Inc). It is not a casual "here are some common questions" post. It is a full reference document. New subscribers read it instead of asking the same questions the previous 4,000 subscribers already asked. The mod team links to specific sections of the FAQ in reply to new questions, which both answers the question and trains the next person to check the megathread first.
The r/MintMobile FAQ is also part of the reason r/MintMobile drives a large share of Mint's social referral traffic. The thread ranks in Google search results for specific Mint Mobile support queries, which means the megathread is doing three jobs at once: serving the community, deflecting repeat questions, and driving organic search traffic back to official Mint resources. Most brands settle for the first job. r/MintMobile does all three because the thread is maintained as a real asset and not treated as a throwaway post.
How to refresh a megathread without losing history
The biggest operational challenge with a megathread is keeping it fresh without losing the conversation history. The working approach is to refresh the OP in place, not to post a new megathread every week. The original thread stays pinned, the OP gets updated with new answers and new links, and the comment history stays intact. Subscribers who return to the thread see the new information without losing track of the older exchanges.
Some topics do need a hard refresh. Weekly check-in threads, monthly recap threads, and event-specific threads should cycle. For those, post the new thread, link back to the previous one in the OP, and unsticky the old thread. The old thread stays accessible for reference but no longer competes for attention.
For evergreen FAQ megathreads, we typically refresh the OP monthly and do a full rewrite quarterly. The monthly refresh keeps the thread current. The quarterly rewrite lets us reorganize sections as the community grows and the common questions shift.
Tracking engagement over time
Megathreads are easy to measure if you watch the right signals. The metrics we track for every client:
- Upvotes on the OP. A proxy for whether subscribers think the thread is useful. Stagnant upvotes mean the thread has gone stale.
- Comment depth. How many comments and how deep the replies go. A thread with 200 top-level comments and no replies is a thread where nobody is having conversations. That is a failure mode worth fixing.
- Repeat questions in the main feed. The megathread's real job is to reduce the volume of repeat questions on the main feed. If repeat questions still show up daily, the megathread is not doing its job and probably needs better positioning or clearer OP content.
- Inbound links from the main feed. Every time a mod replies to a main-feed question with a link to the megathread, that is a measurable data point. Over a month, the count tells you how much load the megathread is absorbing.
Common mistakes that kill megathreads
The predictable failure modes:
- Letting the thread go stale. The OP is the reason people read the megathread. If it is three months out of date, nobody trusts it.
- Not updating the OP. The comment section is a conversation. The OP is a document. Keep them both current.
- Not pinning it. An unpinned megathread disappears within a day. Use the sticky.
- Wrong sort order. A FAQ thread sorted by top hides the newest questions under months of old exchanges. A giveaway thread sorted by new rewards the fastest typers instead of the best entries.
- No owner. A megathread with no assigned maintainer decays within two weeks.
- Trying to make one megathread do too much. A single megathread cannot be both a FAQ, a support queue, a launch thread, and a weekly check-in. Break them apart.
Conclusion
A well-run megathread is a force multiplier for the mod team. It absorbs the questions that would otherwise flood the feed, becomes a permanent reference document that Google and Reddit both surface, and gives new subscribers a way to get oriented without asking anyone to repeat themselves. The only thing it requires is a clear owner, a disciplined refresh cadence, and a willingness to treat the OP as a real document instead of a one-off post.
How Soar saves you time and money
Megathread setup, refresh, and tracking are recurring deliverables in every retainer we run. We rebuild the FAQ megathread monthly, refresh the OP in place, route new questions through it, and measure how many repeat questions it deflects from the main feed. In practice, a well-maintained megathread handles 30 to 50 percent of the repeat support questions the sub would otherwise receive. That is the difference between a mod team that has time to participate in real conversations and a mod team that spends its entire week answering the same five questions.
The alternative is the failure mode we see in most new branded subreddits: the same handful of questions gets asked weekly, the mod team burns out within a quarter, and the community starts to feel like a support ticket queue instead of a conversation. We prevent that by treating the megathread as a real maintained asset from day one, which is usually the single highest-leverage thing you can do in the first 90 days of a subreddit launch.
Soar builds and runs branded subreddits, including the megathread programming that keeps them from turning into support queues. If you want a 30-minute call to scope the engagement, get in touch.