A campaign wiki that is written by the session, not after it
The reason campaign wikis go stale is not that DMs are lazy. It is that writing one is a second job that happens after a four-hour session, at eleven at night.
Entries come out of what was actually said
Once a session is transcribed, the transcript goes through entity extraction: the model reads it and pulls out the NPCs, locations, items and factions that came up, with a description drawn from what happened rather than from a template.
The extraction is given your existing wiki first. Your current entries, your player characters and your recorded aliases go into the prompt, so when the party calls someone "the innkeeper" in session nine, the mention attaches to the entry you already have instead of creating a second one. That is a deliberate design choice: preventing duplicates at the point of creation is far cheaper than merging them later.
A wiki for your D&D campaign that tracks the lore as it is played
A wiki for a D&D campaign usually has to be typed into existence: a page per NPC, a page per town, a lore page for the history the party keeps tripping over. This one is filled from the sessions. Each transcribed session adds or updates entries for the people, places, items, factions and lore that came up, and each entry the extraction creates carries an Appearances list — which session it surfaced in and the model’s own quote of how it came up — so the wiki doubles as a lore tracker you can read back session by session.
It is the wiki of what has happened, not the wiki of what you have planned. If what you want is to build a setting before play — or to compare the ways a campaign wiki can be built by hand — how to make a D&D campaign wiki walks through the options, this one included.
Nicknames are first-class
Tables do not use canonical names. "Thordak Ironforge" is "Thordak" by session two and "Thor" by session five, and a wiki that treats those as three people is worse than no wiki. Aliases map nicknames to the canonical entry, and the wiki search matches them server-side — searching "Thor" finds "Thordak Ironforge".
The same alias list also feeds back into transcription, so a nickname you record once makes every future transcript more accurate. The two systems are wired together on purpose.
You stay in charge of it
This is AI-assisted, not AI-governed. Any field you edit by hand is locked per-field, and later AI passes will not overwrite it. That is enforced in the data model rather than being a convention — the system records which specific fields a human edited.
Duplicate detection proposes merges rather than performing them. Off-topic detection flags entries that look like table talk or real-world references rather than campaign content — pizza orders, arguments about rules, someone’s cat — and you review before anything is hidden. Deleting, bulk-deleting and merging are restricted to the GM of the campaign.
Sharing it with players
A campaign wiki can be published as a read-only page players open with no account, and your private GM notes are excluded from what gets sent rather than hidden in the interface. How sharing works, and what players can see covers the link, the expiry and the permissions in full.
What this does not do
It does not build a world you have not played yet. Everything here is derived from what happened at the table. If you want to author a continent, a pantheon and four hundred years of history before session one, use a worldbuilding tool — World Anvil, LegendKeeper and Kanka all do that far better than this does, and we would rather say so than waste your evening.
It is not a virtual tabletop. No maps, no tokens, no combat tracker, no dice.
Extraction is a model reading a transcript, so it is wrong sometimes — it will occasionally promote a throwaway joke to an NPC. The review tools exist because that is expected behaviour, not a defect you should have to tolerate silently.
Which plans include it
Included on every plan. Sharing a wiki with players requires Dungeon Master or above. The free plan covers one campaign; paid plans are unlimited.
The rest of what it does
- D&D session transcription that already knows your characters’ names
Upload a session recording and get a timestamped transcript. Your wiki’s character and place names are fed to the model, so fantasy nouns survive.
- A D&D session recording app in your browser: nothing to install, no bot to invite
Record your D&D session in the browser tab you already have open, pause for breaks, then Stop & Save into transcription. What does the microphone hear?
- Session recaps you can read at the table without editing them first
AI session summaries and read-aloud recaps from your D&D audio: key events, NPCs, cliffhangers. Free: 2.5 h/mo plus 3 bonus hours. What do you get back?
- Ask your campaign a question and get an answer with citations
Ask what the party promised the duke, or who gave them the sending stone, and get an answer from your own sessions. Which session said it?
- A relationship map of everyone your party has tangled with
A D&D relationship chart of NPCs, factions and places drawn from your session transcripts, not by hand, and editable. Who owes whom by session twenty?
- Give your players the wiki without giving them your notes
Publish a read-only wiki players open with no account. GM notes are never sent; links expire and can be revoked. What do your players actually see?
- Already have the transcript? Skip straight to the campaign wiki
Bring a transcript from Craig, Whisper or another tool: entities, a wiki and a recap on every plan, zero audio hours, plus the relationship map from $7.99.