How to Build a Campaign Wiki That Actually Gets Used

Why Most Campaign Wikis Die

You built a beautiful wiki. You organized every NPC, sketched every faction, and wrote a three-paragraph description of that tavern the party visited once. Then two months later, nobody's touched it — including you. If this sounds familiar, you're in excellent company. The campaign wiki graveyard is vast, and it's not because DMs are lazy. It's because most wikis are designed to fail.

The problem is structural, not motivational. Campaign wikis collapse for three predictable reasons, and understanding them is the first step toward building one that lasts.

Problem 1: Too much work to maintain

A wiki that requires an hour of upkeep after every session is a wiki with an expiration date. Most DMs already spend time prepping encounters, balancing combat, and herding schedules. Adding "write detailed wiki entries" to that list is a fast track to burnout. Community discussions on EN World and the RPG Pub consistently cite maintenance burden as the number one reason campaign wikis get abandoned — the DM runs out of steam, and nobody else picks up the slack.

Problem 2: Nobody reads it

Research across TTRPG communities suggests a brutal truth: the vast majority of players won't read campaign material you provide. Forum discussions on D&D Beyond and Reddit estimate that fewer than half of players will even open a wiki link, let alone read through entries. One widely shared rule of thumb says you should never give players more than one side of A4 paper worth of text — that's roughly the ceiling of what most people will absorb voluntarily.

This isn't a character flaw. Players show up to play, not to do homework. If your wiki reads like a textbook, it'll get the textbook treatment: ignored until the exam.

Problem 3: No structure, no findability

A wall of unorganized Google Docs is technically a wiki in the same way a pile of index cards is technically a filing system. Without clear categories, search, and linking between entries, information gets buried. Players can't find what they need, so they stop looking. DMs can't find their own notes, so they stop updating. The wiki becomes a write-only database — information goes in, nothing comes out.

What Makes a Wiki That Gets Used

The campaign wikis that survive have four things in common — and none of them involve writing more content. The secret isn't volume. It's design.

Principle 1: Minimal effort to update

The wiki must be easier to update than to not update. That means short entries, templates that pre-fill structure, and a workflow that doesn't feel like a second job. If you can update an NPC entry in under two minutes, you'll do it. If it takes ten minutes of formatting, you won't. The best wiki tools provide templates and forms that reduce entry creation to filling in a few fields.

Principle 2: Player-accessible

If players need a login, a tutorial, and a specific app to access the wiki, they won't. The wiki needs to be wherever your group already hangs out — linked in Discord, bookable in a browser, shareable with a single URL. Gnome Stew's advice on campaign organization emphasizes that the tools players already use will always beat the "better" tool they have to learn.

Principle 3: Searchable and linked

The power of a wiki over a document is hyperlinking. When the party meets an NPC, they should be one click away from that NPC's faction, which is one click away from the faction's home city, which links back to the quest that brought them there. Obsidian Portal's guide to campaign wikis calls this the "web-like network" that makes a wiki useful at the table — and it's what separates a wiki from a stack of notes.

Principle 4: Visual and scannable

Bullet points beat paragraphs. Headers beat walls of text. Images beat descriptions. Players are scanning for specific information — "What was that NPC's name?" or "Where were we supposed to go next?" — not reading for pleasure. Format your wiki entries like reference cards, not short stories. Bold the important stuff. Use tables for stats. Keep prose to a minimum.

The Wiki Structure That Works

After looking at dozens of campaign wikis across World Anvil, Kanka, Notion, and Obsidian, a clear pattern emerges. The wikis that get used and maintained share a similar architecture. Here's a template you can adapt to any tool.

Home Page

Your wiki's front door. Keep it to one screen — no scrolling.

• Campaign name and one-sentence premise (e.g., "A group of mercenaries uncovers a conspiracy in the city of Ashenmere")
• Active quests — a bulleted list of 3-5 current objectives
• Party roster — character names, classes, and a one-line description
• Last session — a link to the most recent session recap
• Quick links — NPCs, Locations, Factions, Loot

NPCs

Each NPC gets a short entry with consistent fields:

Tip: Only create NPC entries for characters the party has actually interacted with. Pre-populating dozens of NPCs "just in case" is how wikis become overwhelming. If you need a system fortracking NPCs and locations across sessions, start with the ones your players already care about.

Locations

Same principle — consistent structure, short entries:

Session Log

Chronological recaps — the backbone of any campaign wiki. Each entry should be scannable in under a minute.

• Session number and date
• Who was present
• 3-5 bullet point summary of major events
• Decisions made — what did the party choose?
• Loose threads — unresolved questions or hooks
• Next session preview — where are we headed?

This is also where the Lazy DM's guide to documentation becomes relevant — you don't need polished prose, you need useful reference material.

Factions

Loot and Items

A running inventory of notable items — magic weapons, quest objects, keys, letters, maps. Skip mundane gear. Include:

• Item name
• Who has it
• Where it was found (link to session)
• What it does (if known)
• Relevance — is it tied to a quest?

Tool Comparison: Finding Your Wiki Platform

There's no single best D&D campaign wiki tool — but there is a best tool for your group. The right choice depends on how much time you want to spend building, how much control you want, and whether you'd rather design a wiki from scratch or have one generated for you. Here's an honest breakdown of every major option.

World Anvil — The Feature-Rich Worldbuilder

World Anvil is the maximalist's dream — a sprawling platform with over 25 worldbuilding templates, interactive maps, timelines, and a hierarchical wiki system. It's the most comprehensive tool in this space, and if you want to build a deeply detailed world with interlocking lore, it's hard to beat.

• Pricing: Free tier (limited storage, ads, public content). Paid tiers — Master (~$6.50/mo), Grandmaster (~$8.25/mo on annual), and Sage (higher) — with discounts for quarterly, semi-annual, and annual billing.
• Best for: DMs running homebrew campaigns with extensive worldbuilding, writers who want to develop their setting beyond the game table.
• Strengths: Massive feature set. Timeline tools. Interactive maps. Active community. Supports 45+ RPG systems. Content can be made public for community sharing.
• Weaknesses: Steep learning curve. The interface can feel overwhelming for new users. Many features locked behind higher-tier subscriptions. More tool than most campaigns need.

LegendKeeper — The Clean, Modern Option

LegendKeeper focuses on speed and polish — a streamlined editor, fast load times, and a visual-first approach to worldbuilding. It outperforms most competitors on workflow speed and offers real-time multiplayer editing, making it collaborative out of the box.

• Pricing: 14-day free trial. Then $9/mo or $90/year. All features included — no tiered feature gates. Collaborators join free.
• Best for: DMs who want a polished, shareable wiki without the complexity of World Anvil. Groups that want to edit together in real-time.
• Strengths: Beautiful editor. Fast performance. Interactive maps and whiteboards. Automatic interlinking. All features at one price. Export to HTML or JSON.
• Weaknesses: No free tier (only a trial). Smaller community than World Anvil. Some planned features (timelines, calendars, relationship graphs) still in development.

Kanka — The Open, Flexible Option

Kanka is trusted by over 375,000 worldbuilders and takes a flexible, entity-based approach where everything — characters, locations, items, quests — is treated as the same type of object. This makes it incredibly adaptable to any campaign structure.

• Pricing: Free Kobold plan includes unlimited campaigns, uploads, and access to all core features. Owlbear plan ($5/mo) adds campaign boosters, custom images, 8MB upload limit, and a private Discord channel.
• Best for: DMs who want a capable wiki without paying anything. Groups that value flexibility and a clean interface.
• Strengths: Generous free tier. Intuitive interface. Calendars, interactive maps, timelines, and a visual relation explorer. Active development with regular updates. Campaign boosters can be moved between campaigns.
• Weaknesses: Premium features require boosting individual campaigns. Fewer worldbuilding-specific templates than World Anvil. Less visual polish than LegendKeeper.

Notion — The DIY Powerhouse

Notion isn't built for TTRPGs, but it's one of the most popular campaign wiki tools anyway — because it's free, flexible, and most players already have it. With databases, templates, linked entries, and gallery views, you can build a fully functional campaign wiki from scratch or grab one of many community templates.

• Pricing: Free for personal use. Paid plans ($8-10/mo) add collaboration features, but the free tier handles most campaign wiki needs.
• Best for: DMs who like building custom systems. Groups already using Notion for other things. Anyone who wants full control without learning a TTRPG-specific tool.
• Strengths: Free. Extremely flexible databases. Great sharing and collaboration. Dozens of community-made D&D templates on the Notion Marketplace. Works on every device.
• Weaknesses: Entirely manual — every entry is written by hand. No TTRPG-specific features (no maps, no stat blocks, no system integration). Requires setup time to build a useful structure. Can become unwieldy without discipline.

Obsidian — The Local-First Markdown Option

Obsidian stores everything as plain markdown files on your own computer — no cloud, no subscription, no dependency on a service staying alive. Its bi-directional linking creates a genuine wiki experience, and a thriving plugin ecosystem includes several TTRPG-specific tools.

• Pricing: Free for personal use. Sync ($4/mo) and Publish ($8/mo) are optional add-ons.
• Best for: DMs who want total ownership of their data. Tech-comfortable users who enjoy customizing workflows. Anyone paranoid about a service shutting down and losing their world.
• Strengths: Free. Local-first — your files, your filesystem. Powerful bi-directional linking and graph view. Extensive community plugins for D&D (initiative trackers, stat block renderers, etc.). Works offline.
• Weaknesses: Not inherently collaborative — sharing requires Sync or Publish. Steeper learning curve than Notion. Players need the app to view content (unless you use Publish). No maps or visual tools built in.

Google Docs / Sheets — The Zero-Friction Option

Sometimes the best tool is the one everybody already has. A shared Google Doc with headers, a table of contents, and internal links can function as a perfectly serviceable campaign wiki. Google Sheets works well for NPC trackers, loot tables, and faction relationship matrices.

• Pricing: Free.
• Best for: Groups that don't want to learn anything new. Short campaigns. Backup wikis alongside another tool.
• Strengths: Everyone has a Google account. Real-time collaboration. Commenting and suggesting features. Zero setup.
• Weaknesses: No linking between documents (without manual effort). Gets messy fast as campaigns grow. No search across documents. Not really a wiki — more like organized notes. No templates or structure enforcement.

Auto-Generated Wikis — The Zero-Effort Option

What if the wiki just... wrote itself? A newer category of tools builds campaign wikis automatically from session recordings. You play your game, and the wiki populates with NPCs, locations, events, and plot threads extracted from what actually happened at the table.

Kazkar records your sessions through Discord, transcribes them, and generates wiki entries for NPCs, locations, factions, and events — turning your actual gameplay into a living lore wiki. It's a fundamentally different approach: instead of writing the wiki yourself, you get one fromturning recordings into a wiki automatically. The trade-off is customization — because entries are auto-generated from transcripts, they reflect what was said at the table rather than polished worldbuilding prose. For groups who would never maintain a manual wiki, that's a feature, not a bug.

SessionKeeper takes a similar approach with a mobile-first design. It records sessions (via app, web, or Discord), transcribes with speaker identification, and builds a self-updating wiki for NPCs, locations, quests, items, and factions. Plans range from free (join campaigns) to $24.99/mo for the full feature set including custom recaps and character portraits.

Archivist focuses on session transcription with entity extraction, generating timelines, quest logs, and a campaign wiki from recordings. It integrates with Discord, Foundry VTT, and Obsidian, with pricing starting around $10/mo for one campaign.

Best for: Groups that want campaign documentation but won't maintain it manually. DMs who are already recording sessions. Tables that value "what actually happened" over curated worldbuilding.

Comparison Table

How to Get Players to Actually Read the Wiki

You built the wiki. You filled it with content. Now comes the hard part: getting anyone else to look at it. This is the challenge that sinks more campaign wikis than any technical limitation. Here are the strategies that actually work, drawn from years of community wisdom.

Keep entries short enough to read on a phone

If a wiki entry doesn't fit on a phone screen, it's too long. Most players will check the wiki between sessions on their phone — in bed, on the bus, during a boring work call. Format entries for mobile: short paragraphs, bullet points, bold key information. An NPC entry should be five to eight lines, not five paragraphs.

Make the wiki part of the session

The wiki shouldn't be homework — it should be a tool you use at the table. When a player asks "Wait, who was that NPC again?", pull up the wiki and show them. When the party needs to remember where they're going, check the quest log together. The more the wiki gets referenced during play, the more players see it as useful rather than optional.

Let players contribute

The wikis that last are the ones where the DM isn't the only person writing. Assign rotating session recap duty. Let players write their own character entries. Create a "Loose Ends" section where anyone can add unresolved questions. Obsidian Portal's wiki guide specifically recommends inviting players to contribute — it transforms the wiki from the DM's project into the group's shared resource.

Post recaps in your group chat

Don't make players go to the wiki — bring the wiki to them. After each session, drop the recap summary in Discord or your group chat with a link to the full wiki entry. Most people won't navigate to a separate site, but they'll read a message that's already in front of them. Use it as a teaser: "Session 7 recap is up — turns out Mirabel wasn't who she said she was. [Full entry here]."

Reward engagement

Many DMs offer Inspiration to the player who does the session recap — and it works. A small mechanical incentive goes a long way. Some groups give bonus XP, downtime days, or narrative advantages to players who reference wiki content during play. You're not bribing your players; you're recognizing that engagement with the campaign's story deserves the same reward as engagement with its mechanics.

Use the "one page max" rule

Keep the total amount of required reading to one page per session. That means one page of recap, not one page per NPC. If players need background on an NPC or location, link to it — don't dump it into the recap. Let the wiki be deep for those who want to explore, but keep the surface layer thin enough that anyone can stay current in under five minutes.

Maintaining the Wiki Without Burning Out

The DM who maintains a wiki for a two-year campaign isn't working harder — they're working smarter. Here are the habits that make wiki maintenance sustainable rather than soul-crushing.

Update during session, not after

The best time to update the wiki is while things are happening. Keep a tab open during the session and jot quick notes — NPC names as they're introduced, location details as you describe them, decisions as the party makes them. A sentence written in the moment beats a paragraph reconstructed from memory three days later.

Use templates religiously

Every entry type should have a template with pre-filled fields. When you introduce a new NPC, you shouldn't be staring at a blank page — you should be filling in Name, Role, Faction, Location. Templates enforce consistency and reduce the mental load of "how do I format this?" to zero. Every major wiki tool supports templates, and even in Google Docs you can keep a template section to copy-paste from.

Batch your updates

If real-time updating doesn't work for you, set a specific time each week for wiki maintenance — and keep it under 30 minutes. Sunday afternoon, Tuesday morning, whenever. The key is making it a routine rather than a task that gets perpetually deferred. During this time, clean up session notes, add new entries, and update existing ones. Thirty minutes of focused editing per week keeps even a complex wiki current.

Accept imperfection

A wiki with typos and incomplete entries is infinitely more useful than a perfect wiki that doesn't exist. The enemy of wiki maintenance is perfectionism. Not every NPC needs a backstory. Not every location needs a description. If all you have is a name and a one-line note, that's still more than nothing — and it's something you can flesh out later if it becomes important.

Know when to delegate — or automate

If maintaining a manual wiki isn't sustainable for your group, that's okay. Some tables thrive with Notion databases and detailed entries. Others need a tool that handles documentation automatically. If you're already recording your sessions, tools like Kazkar can turn those recordings into wiki entries without anyone writing a word. There's no shame in letting the robot do the filing — the point is that the information exists and is findable when you need it. Whether your campaign eventually becomes source material for turning your campaign into a novel or just a reference you check before each session, the wiki's job is the same: keep the story accessible.

Frequently Asked Questions

What's the best free D&D campaign wiki tool?

Kanka offers the most complete free tier for a dedicated TTRPG wiki tool, with unlimited campaigns, unlimited uploads, and access to all core features including calendars, maps, and timelines — no payment required. For a more general-purpose option, Notion's free plan gives you powerful databases and templates, and Obsidian is entirely free for local use. Google Docs costs nothing and requires zero setup. The "best" free option depends on how much structure you want out of the box versus how much you're willing to build yourself.

How do I get my players to actually use the campaign wiki?

Keep entries short, make the wiki part of gameplay, and bring content to your players instead of expecting them to seek it out. Post session recaps directly in your Discord or group chat with links to the full wiki. Use the wiki at the table — pull it up when someone asks "who was that NPC?" Assign rotating recap duty so players have ownership. And consider offering Inspiration or small rewards for wiki engagement. The number one rule: if the wiki is useful during the session, players will check it between sessions.

Should I use a dedicated worldbuilding tool or a general-purpose app like Notion?

Use a dedicated tool if you want built-in TTRPG features like interactive maps, timelines, and system-specific templates. World Anvil, LegendKeeper, and Kanka are purpose-built for this. Use Notion or Obsidian if you prefer total flexibility, already use these tools for other things, or want to avoid a TTRPG-specific subscription. There's no wrong answer — the tool you'll actually maintain beats the "better" tool you'll abandon in a month.

How much time should I spend maintaining a campaign wiki?

Aim for 15-30 minutes per week, maximum. That's enough to write a short session recap, add any new NPC or location entries, and update quest status. If it's taking more than that, your entries are probably too detailed — remember, bullet points and one-liners are fine. If even 15 minutes feels like too much, consider auto-generated options that build wiki entries from your session recordings, or rotate maintenance duties among your players.

Can I convert an existing campaign wiki to a different tool?

Most dedicated tools support import and export in some form, but migration is rarely seamless. Kanka supports JSON import/export. LegendKeeper exports to HTML and JSON. World Anvil has export tools for paid tiers. Notion can export to markdown, and Obsidian is already markdown-native, making migration between those two relatively straightforward. If you're moving from Google Docs, expect manual copy-pasting. Before choosing a tool, consider whether export/portability matters to you — your campaign might outlast the platform you build it on.

Your campaign's story is worth remembering. Whether you build a wiki by hand, set up a database in Notion, or let a recording bot handle the documentation, the point is the same: make the lore findable, keep it current, and don't let the perfect be the enemy of the good. The best campaign wiki is the one your table actually uses.