How to Turn Session Recordings Into a Campaign Wiki (Automatically)

The Dream: A Wiki That Builds Itself

Imagine finishing a four-hour session, closing Discord, and checking your phone the next morning to find a fully written chronicle of everything that happened — plus updated wiki entries for every NPC, location, and faction your party encountered. No notes. No homework. No "wait, who was that guy?" at the start of the next session.

That's the dream, and for most of D&D's history, it's been exactly that — a dream. Campaign wikis have always been the gold standard for tracking lore across long-running campaigns. World Anvil hosts over 2 million worldbuilding articles created by GMs and writers. Notion templates for D&D campaign management are among the platform's most popular community creations. The tools for building a wiki have been available for years.

The problem was never the wiki. It was feeding the wiki. Someone had to sit down after every session and manually write up what happened, who appeared, what was said, and where the story went. For a hobby that's supposed to be fun, that's a lot of unpaid homework. Community discussions on D&D Beyond and EN World consistently surface the same complaint: DMs spend 2-6 hours on session prep, and adding post-session documentation on top of that leads straight to burnout.

In the last two years, the pipeline from raw session audio to finished campaign wiki has gone from "theoretically possible if you're a programmer" to "type one command and wait." This guide walks through all three approaches — manual, semi-automated, and fully automated — so you can pick the workflow that fits your table.

The Manual Way: Recording to Wiki in Four Steps

Before automated tools existed, resourceful DMs built their own pipelines — and some still prefer the control that comes with doing it yourself. The manual workflow has four distinct steps, each with its own tools and time cost. Understanding this pipeline matters even if you plan to automate, because it's exactly what the automated tools are doing under the hood.

Step 1: Record Your Session

Every pipeline starts with audio. If your group plays on Discord, recording your sessions is straightforward with a bot like Craig. Type /join, play your session, type /stop, and Craig delivers multi-track audio files — one per speaker — within minutes. Craig has recorded over 270 years of audio across 2.8 million recordings, so the tool is battle-tested.

For in-person groups, a phone in the center of the table or a USB microphone works, though you'll get a single mixed audio track instead of per-speaker files, which makes the next step harder.

Time cost: ~2 minutes (invite bot, start recording, stop recording).

Step 2: Transcribe the Audio

This is where most manual pipelines either succeed or stall. You need to turn hours of audio into searchable text, ideally with speaker labels so you know who said what.

The go-to open-source option is OpenAI's Whisper, which you can run locally for free. Whisper handles general speech well, but TTRPG sessions are a special challenge — fantasy proper nouns, overlapping chatter, in-character voices, and table crosstalk all trip up generic transcription models.

For a more streamlined approach, TASMAS is an open-source tool built specifically for file-per-speaker recordings from Craig Bot. It transcribes each speaker's audio file down to word-level timestamps and merges them into a unified, time-ordered transcript. If you're comfortable running a desktop app, it's the best free option for Craig recordings.

Commercial transcription services like Deepgram or AssemblyAI offer speaker diarization (automatically labeling who's talking) and handle audio quality issues more gracefully, but they cost money per hour of audio.

Time cost: 15-45 minutes (downloading files, running transcription, fixing errors).

Step 3: Summarize the Transcript

A raw transcript of a four-hour session can run 30,000-50,000 words. Nobody's reading that. You need to condense it into a session summary that captures the key events, NPC interactions, decisions, and plot developments.

This is where ChatGPT and Claude have become the default tool. The typical workflow, documented extensively by Brandon Harris on Medium, looks like this:

1. Upload your transcript to ChatGPT (or paste it in chunks if it exceeds the context window)
2. Prompt it with something like: "Summarize this D&D session transcript. List key events, NPC interactions, locations visited, items found, and unresolved plot threads."
3. Review and edit the output for accuracy
4. Optionally, run a second pass to extract specific entities: NPCs, locations, factions, items

Some DMs build custom GPTs with their campaign context pre-loaded — character names, setting details, recurring NPCs — so the AI produces more accurate and consistent summaries. Others use Claude Projects to maintain ongoing campaign context across sessions.

Time cost: 20-60 minutes (uploading, prompting, reviewing, editing).

Step 4: Add Everything to Your Wiki

Now you have a summary and a list of entities. The last step is putting it all somewhere useful. Popular options include:

• World Anvil — the most feature-rich worldbuilding wiki, with templates for NPCs, locations, organizations, and more. Supports cross-linking between entries and has built-in campaign management tools.
• Notion — flexible and free, with community templates specifically designed for D&D campaign wikis. Great for groups already using Notion.
• Obsidian — local-first markdown notes with wiki-style linking. Clicking an NPC name takes you to their page. Popular with privacy-conscious DMs.
• LegendKeeper — a wiki platform built specifically for worldbuilding and TTRPG campaigns.

You'll need to create or update entries for each NPC, location, and faction that appeared in the session, add the session summary as a chronicle entry, and cross-reference everything. In a well-maintained wiki, the entry for "Lord Vanthor" links to the faction he leads, the city he governs, and every session where he appeared.

Time cost: 30-90 minutes (creating entries, formatting, cross-linking).

Total Time: 1.5 to 4 Hours Per Session

Add it all up, and the manual pipeline costs 1.5 to 4 hours of post-session work for each session you play. For a group that plays weekly, that's an extra part-time job. For a monthly group, it's more manageable — but you're still spending a significant chunk of your free time on documentation instead of prep, worldbuilding, or, you know, having a life.

Here's a summary of the full manual pipeline:

The manual way works, and some DMs genuinely enjoy the process. But for every DM who treats post-session documentation as a beloved ritual, there are ten who start strong and abandon it by session five. The Lazy DM's guide to documentation exists for a reason.

The Semi-Automated Way: Tools That Handle Some Steps

A growing category of tools automates the recording-to-summary pipeline but stops short of building a persistent, cross-referenced wiki. These are useful if you want to save time on transcription and summarization but are happy maintaining your own wiki (or don't need one).

GM Assistant

GM Assistant lets you upload audio from your TTRPG session and get detailed notes back within minutes. It extracts NPCs, locations, and key events, and supports multiple languages. The focus is on session notes, not an ongoing wiki — each session produces a standalone summary, and it's up to you to organize those summaries across your campaign. Currently free while in development, with GDPR compliance for European groups.

Best for: Groups who want transcription and summarization handled but prefer to manage their own campaign wiki in Notion, Obsidian, or World Anvil.

CharGen

CharGen bundles session recording on Discord with dice rolling, initiative tracking, character generators, and AI summaries. Use /start to record, /stop to end, and /summarise to generate a summary with NPC, location, and loot extraction. It also builds "AI dossiers" with NPC relationships and generator-ready entities. The RPG tools are free; voice recording and summaries require a subscription.

Best for: Groups who want an all-in-one Discord RPG toolkit with recording as one of many features.

Saga20

Saga20 focuses on session summarization with voice-matching technology that automatically identifies which player is speaking and matches voices to characters across sessions. Upload audio or connect via Discord, and get summaries with speaker attribution. Designed to track your party across multiple sessions.

Best for: Groups who prioritize accurate speaker identification and character-level tracking in their session summaries.

What Semi-Auto Misses

The gap in semi-automated tools is persistence. Each session produces a summary, but those summaries don't automatically connect to each other. If an NPC appears in sessions 3, 7, and 12, you'll have three separate mentions across three separate summaries — but no unified NPC page that collects everything about that character in one place. That cross-referenced, wiki-style organization is what separates session notes from a campaign wiki.

The Fully Automated Way: Record, Play, Wiki

The newest generation of tools closes the entire loop — from the moment you start recording to a fully updated, cross-referenced campaign wiki — without any manual steps in between. You play your session, stop recording, and the rest happens automatically.

Kazkar

Kazkar is a Discord bot purpose-built for this exact workflow. Add it to your server, create a campaign on the dashboard, and invite your players. When you're ready to play, type /summon to bring the bot into your voice channel. Run your session, then type /banish when you're done. Behind the scenes, Kazkar records per-speaker audio, mixes it, runs it through Deepgram transcription with speaker diarization, generates a narrative session chronicle using AI, and then extracts lore entities — NPCs, locations, factions, items — into a wiki that updates after every session.

What you get:

• Session Chronicles — a narrative summary of what happened, organized by campaign, readable as a story
• Lore Wiki — auto-generated entries for every NPC, location, faction, and item, cross-referenced and updated as new sessions mention them
• Campaign Dashboard — a web interface at kazkar.ai where your whole group can browse chronicles, search the wiki, and manage campaigns
• Speaker Identification — players create characters linked to campaigns, so the transcript labels dialogue by character name, not Discord username

Here's what the pipeline actually produces. Imagine your party spent a session infiltrating a thieves' guild in a port city:

Pricing: Free tier includes 10 hours of recording with full feature access. That's enough for roughly 2-3 full sessions to see if it fits your group.

Honest limitations: Kazkar is a young product. It works best for groups that play on Discord. The wiki gets smarter over time as more sessions feed it context, so the first session's output won't be as refined as the tenth.

SessionKeeper

SessionKeeper takes a broader approach — it works via mobile app (iOS/Android), web recorder, or Discord bot, making it the most flexible option for groups that alternate between online and in-person play. It records, transcribes with speaker identification, builds a campaign wiki, and adds unique touches like AI-generated character portraits and recap "podcasts" you can listen to between sessions.

Unique features: Character portraits, achievement system based on in-game events, DM insights, and a mobile app for in-person recording.

Pricing: Free tier for joining campaigns. Adventurer ($3.99/mo) for 1 campaign with summaries. Hero ($9.99/mo) adds wiki, Discord bot, and DM tools. Legendary ($24.99/mo) shares premium with your party.

What Makes a Good Campaign Wiki

Not all wikis are created equal. Whether you're building one manually or letting a tool generate it, a campaign wiki that actually gets used by your players needs three things.

Cross-References

The single most valuable feature of a wiki over linear session notes is linking. When you look up an NPC, you should see every session they appeared in, every location they're connected to, and every faction they belong to. When you look up a location, you should see who you met there and what happened. These connections are what transform a collection of session summaries into something that feels like a living campaign encyclopedia.

Manual wikis in World Anvil and Obsidian excel at this — if someone puts in the time to create the links. Automated tools vary in how well they handle cross-referencing. Look for tools that don't just list entities but connect them.

Searchability

Your wiki is only useful if players can find things in it. That sounds obvious, but it disqualifies a lot of formats. A Google Doc with 30 sessions of notes isn't searchable in a practical sense — try finding every mention of a specific NPC across 50,000 words. A proper wiki with individual entity pages and a search function solves this. If you're building a campaign wiki that gets used, searchability is non-negotiable.

Session-Over-Session Growth

A good campaign wiki gets better with each session, not just bigger. Early sessions might introduce an NPC with a single line of description. Ten sessions later, that NPC's page should reflect everything the party has learned — their motivations, alliances, betrayals, and current status. The wiki should accumulate knowledge the same way your players do.

This is where automated tools have an inherent advantage: they process every session against the existing wiki, updating and enriching entries as new information surfaces. Manual wikis can achieve the same result, but it requires disciplined upkeep.

FAQ

How long does it take to go from session recording to a finished wiki entry?

With a fully automated tool, the entire pipeline — recording, transcription, summarization, entity extraction, and wiki update — completes within 10-15 minutes of ending your session. Kazkar processes a typical 3-4 hour session and delivers chronicles plus updated wiki entries before most groups finish their post-game chat.

Do automated wikis work for homebrew campaigns with custom lore?

Yes — and they often get better over time. Automated tools learn your campaign's vocabulary as more sessions feed the system. The first session might tag a made-up faction name as a generic entity, but by session five, the tool has enough context to correctly categorize and cross-reference your homebrew content. Providing character names and basic campaign context during setup helps the AI start with better accuracy.

Can I edit the auto-generated wiki entries?

This varies by tool. Most automated tools let you view and browse generated content on their dashboards. The level of manual editing support differs — some let you correct entity names and details, others focus on read-only browsable output. If heavy customization of wiki entries is important to you, a semi-automated approach (auto-generate notes, manually curate the wiki) might be the best middle ground.

What if my group plays in person, not on Discord?

SessionKeeper is the strongest option for in-person groups, with iOS and Android apps that record via your phone's microphone. Audio quality from a phone on the table won't match per-speaker Discord recordings, but the transcription and wiki pipeline still works. You can also record in-person audio with any recorder, then upload to tools like GM Assistant or Saga20 for summarization — though you'll need to handle the wiki step manually.

How accurate are AI-generated session summaries?

Modern transcription and summarization handle most sessions well, but accuracy depends heavily on audio quality. Clear audio with minimal crosstalk and background noise produces significantly better results. Speaker identification works best when each person's audio is captured separately (which Discord bots do naturally). The summaries occasionally miss nuance or misattribute dialogue, so a quick review is always worthwhile — but even imperfect auto-generated notes are far more useful than no notes at all.

Your Campaign Deserves a Chronicle

Every D&D campaign is a story your table creates together. The tragedy is how many of those stories are lost — not because they weren't worth remembering, but because nobody had time to write them down.

The tools to solve this are here now. If you've been maintaining a campaign wiki manually and want to reclaim those hours, or if you've never had a wiki because the effort was too daunting, the automated pipeline from recording to wiki is real and getting better with each generation of tools.

If your group plays on Discord, the simplest way to start is to try Kazkar for free — /summon, play your session, /banish, and see what the wiki looks like the next morning. Ten hours of recording on the free tier is enough to run a few sessions and decide if an automatic campaign journal fits your table.

However you build your wiki, your future selves will appreciate having somewhere to look when someone asks, "Wait, who was that NPC in the tavern three months ago?" The answer should be one search away.