Where D&D DMs Find New Tools and Communities in 2026

The hardest part of finding a new tool for your D&D table is not picking one. It is hearing about the right ones in the first place.

I have been DMing for over twenty years, and the way I find tools has changed more than any other part of the hobby. In 2008 I found things by reading forum signatures. In 2018 it was almost entirely YouTube. In 2026 it is a stack of platforms, each tuned for a different kind of trust signal. None of them are perfect on their own, and the DMs who feel like they always have the right tool are the ones who use a few of these in rotation.

Here is the working map of where DMs actually find new tools in 2026, what each channel is good for, and the questions I ask before I trust anything new at my table.

1. Long form forums: EnWorld and Reddit

Forums feel old. That is the point. A thread that has been running for a decade has been pressure tested by hundreds of veteran DMs, and the bad takes have been replied to until they died.

EnWorld is one of the longest running tabletop forums on the internet. The "Tabletop and RPG Software" subforum is where you will see new tools posted by their creators and torn apart, kindly, by people who have been running games since THAC0 was a thing. The signal is that veterans care enough to write paragraphs. As an example of how a launch thread reads, here is the announcement thread for Saga20 when the session summarizer launched. Scroll the replies. That is what real product feedback looks like.

Reddit is the other half. r/DMAcademy, r/DnD, and r/Pathfinder2e all surface tools constantly, often through "what tool do you use for X" megathreads. The trick is to search rather than browse. A targeted query like "session notes" with the time filter set to the last year will give you a better tool list than any algorithmic feed.

What should I look for in a forum post about a new tool?

Three things. The age of the thread, the ratio of creator replies to user replies, and whether the creator is still answering questions a year later. A founder who keeps showing up two years after launch is a stronger signal than any landing page promise.

2. Worldbuilding showcases

A piece of software is only as good as the artifacts it produces. For worldbuilding tools, the fastest way to evaluate something is to read campaigns that other people have built with it.

There are public wiki communities that host thousands of campaign pages. Browsing them is the closest thing to walking through the showroom of a tool you are considering. You can see how DMs structure their lore, how they link articles, and how they handle reveals across an active campaign.

If you want a sample to anchor on, my own group's worldbuilding lives publicly at Fandelver, and the lighter, more comedic side of our table publishes at Big Top. Looking at two wikis from the same group is useful precisely because the style drift tells you how flexible the underlying tool is. The Fandelver wiki leans into a serious sword and sorcery tone. Big Top is built around a circus themed campaign with a much different sense of pacing. Same group, same tooling, completely different output.

The reason this matters: when you read a tool's marketing site, you see what the founders want you to see. When you browse public campaigns built with that tool, you see what the actual ceiling looks like.

3. Streaming and demos

The hardest thing about evaluating a D&D tool is that screenshots lie. Real software either holds up under a live session or it does not.

Twitch is where you watch the unedited version. Live streams expose every awkward loading state and every menu the streamer fumbles through. If a tool survives a live session, it is probably solid. We run our own Saga20 stream to demonstrate features against a real game, and seeing a tool tested in front of viewers tends to expose more than a polished demo video ever could.

YouTube is the curated version. Channels like Bob World Builder, Deck of DM Things, and Dungeon Dudes regularly review new tools. A walkthrough is the fastest way to skip the marketing copy and see whether the workflow matches your actual DM habits. I usually search the tool name plus "review" and sort by upload date. For example, this short demo shows the auto wiki flow in motion, and a 90 second video like that tells you more than a feature list ever will.

How long should a demo video be?

Three to five minutes is the sweet spot for tabletop tools. Anything shorter is a teaser. Anything longer usually means the workflow is too complicated. If a tool needs a 20 minute setup tutorial to get started, that is a tax on every new player who joins your table.

4. The Discord ecosystem

A surprising number of D&D tools live or die by their Discord integration. The party already chats there, the DM already runs scheduling there, and a tool that does not show up in Discord might as well not exist for some tables.

The two public bot directories worth knowing are Top.gg and Discord Bot List. They both work the same way. Search by category, read user reviews, and check the permissions a bot is asking for before you authorize it. If you are evaluating a campaign tool with a Discord component, our Discord integration page goes into how a publishing flow should work. The principle is universal though. A bot that asks for more permissions than its job requires is a yellow flag.

5. Software discovery platforms

This is where the tabletop world meets the broader software discovery scene. These two platforms exist to help people find software, and DMs have started to show up there in the last two years.

Product Hunt is the launch day platform. You see new tools the day they ship, with hunter notes, founder responses, and an active comment thread. The launch comments are usually the most useful thing on the page. If you want to see what a launch for a tabletop tool looks like, Saga20's product page keeps the comment archive intact. Reading old launch comments is one of the better ways to find feedback that the marketing site quietly stopped surfacing.

SaasHub is the comparison platform. Every product gets an alternatives page that is actually useful. If you find a tool you like, the alternatives view shows you the next four or five tools that share its category. As an example, the Saga20 alternatives page lists adjacent session note tools and worldbuilding apps. The trick with comparison pages is to read them in reverse. Start at the tool with the lowest user count and see why it is rated higher than tools with bigger followings. That is usually where the interesting product decisions are.

6. Open source: GitHub

Even if you do not write code, GitHub is one of the best sources of truth about a project's health. The repository tells you whether a project is alive, how it handles bug reports, and how often the team ships.

I check three things on any project page:

• Last commit date. If the most recent commit was over a year ago, the project is probably hibernating.
• Open issues vs closed issues. A high closed to open ratio means the team is actually responding.
• The roadmap or projects tab. This tells you what is coming next, which matters more than what is currently shipped.

For tools that publish part of their stack in public, the Saga20 GitHub repo is an example of how an open component looks alongside a closed one. You do not need to clone anything. Just read the issues tab and you will know how the team behaves under pressure.

7. Background checks: Crunchbase

Tabletop software has a notorious shutdown problem. Tools come and go, and migration costs are real when you have years of session notes locked in a format that nobody is exporting cleanly.

Crunchbase is the cheap, fast sanity check before you commit. The company page tells you who runs the project, whether they have any funding, and what the public business model looks like. Even a sparse profile is informative. As an example, Saga20's Crunchbase entry shows the basics that a DM should expect to find on any tool they are about to migrate years of notes into. Find a tool with no entry at all? That is not necessarily a problem, but it is a question worth asking before you build your campaign on top of it.

The DMs I know who got burned by tool shutdowns almost always skipped this step. They fell in love with a beautiful interface and never asked who was paying the hosting bill.

8. Performance and security checks

A tool's marketing site does not tell you whether the actual app is fast or whether it leaks data. Free scan tools do, and most of them take less than a minute.

I run any tool I am about to migrate notes into through three quick checks. None of them require an account.

• Performance. Run the homepage through PageSpeed Insights or GTmetrix. Anything below a B grade on a marketing site is a red flag, because if the marketing site is slow, the app is usually slower. The linked PageSpeed analysis for Saga20 is what a properly tuned site looks like, including LCP, CLS, and INP for the new Core Web Vitals model.
• Security. Paste the domain into Security Headers and SSL Labs. A tool that handles your campaign notes should at minimum score an A on header configuration. The linked report shows the headers a properly configured site puts in place by default.
• Tech stack and host. Run the domain through BuiltWith and check the audience profile on Similarweb. You learn quickly whether a tool is hosted on a serious platform and whether the audience is real or rented. Empty BuiltWith profiles and zero-traffic Similarweb pages are a yellow flag.

Why bother with archives?

Free archives are the cheapest insurance you can buy on a campaign tool. Two snapshots of every important page take five minutes:

• The Internet Archive snapshot of Saga20 is what a Wayback save looks like the moment after capture. Run "Save Page Now" on every page that holds your wiki structure.
• The archive.ph mirror is the redundancy. Different infra, different uptime characteristics. If one disappears, the other survives.

If the company you trust with three years of session notes shuts down on a Tuesday, the archive snapshot is how you reconstruct your wiki for the next tool. This is not paranoia. Tabletop software has been dying on a quarterly cadence since 2018.

One more cheap check: domain and traffic profile

You can confirm a tool is hosted on real infra in about 30 seconds. The DNS Checker propagation view tells you if the A records are stable globally. The auto-generated StatShow profile gives a third-party traffic estimate that is independent of whatever the marketing site claims. Neither is gospel. Both are sanity checks.

How I sequence these channels

I do not check all eight for every tool. That would be ridiculous. The actual workflow looks more like this:

1. Hear about a tool in a Reddit megathread, a forum reply, or a YouTube review.
2. Watch a stream or demo video to see if it survives real use.
3. Skim the GitHub if it is open source, or the Crunchbase entry if it is a closed company.
4. Run the scan-tool battery if I am seriously considering migrating notes. Five minutes, eight tabs.
5. Search SaasHub for two or three alternatives so I am not anchoring on the first thing I found.
6. Take it for a spin on a one shot or a side game before introducing it to my main campaign.

The rule that has saved me the most pain. Never adopt a tool mid campaign. If you are six months into Curse of Strahd, do not suddenly migrate your session notes from Google Docs to a brand new wiki tool. Wait for a campaign break. Tool transitions are a tax on your prep time, and that tax compounds.

What this looks like at the table

The point of all this is not to spend more time researching tools. It is to spend less time regretting the ones you adopted.

If you want a single starting point, pick one tool from each category at most. A forum to lurk, one streamer to watch, one wiki tool, and one notes tool. That is enough. The DMs who chase every new release tend to have the worst session notes, because their entire prep window gets eaten by setup. The DMs whose tables run smoothly almost always picked their stack two years ago and have been refining it since.

If session notes are your specific pain point, Saga20 handles the recording to recap loop and feeds an auto updating campaign wiki so your worldbuilding does not slowly drift out of sync with what actually happened at the table. If you want a wider menu of options, the best D&D tools for players and DMs post covers the more general toolkit.

The best tool is the one you stop noticing, because your campaign just runs.

Further reading

• Best D&D Tools for Players and DMs
• How to Keep Track of Your D&D Campaign
• Stop Taking Notes: The Lazy DM Guide