World Anvil Alternatives: Best Picks by Workflow

World Anvil Alternatives: Best Picks by Workflow

August 2, 2026 world anvil alternatives

Explore top world anvil alternatives that enhance your DM workflow. Discover tools for efficient worldbuilding and campaign management.

World Anvil Alternatives: Best Picks by Workflow

Person organizing worldbuilding software notes at desk

For most active DMs, a local-first markdown stack or a typed-entity campaign manager will serve weekly sessions better than an article-first wiki. If you want AI-assisted drafting alongside your worldbuilding, Novel with AI is the integrated option worth considering.

Here’s how the main categories break down:

  • Wiki-shaped SaaS platforms (Campfire, LegendKeeper) — best for creators who want polished, public-facing encyclopedias with cross-referenced articles and built-in maps.
  • Local-first markdown stacks (Obsidian) — best for solo GMs who need offline access, full data ownership, and zero subscription fees.
  • Typed-entity campaign managers (Kanka, Lorekeeper) — best for active DMs who prep weekly sessions and need fast NPC/location lookups and encounter tracking.
  • Database-template stacks (Notion, MythScribe) — best for users who already live in a database platform and want linked records without learning new software.

Data portability is the deciding factor most people overlook until they’re locked in. Prioritize platforms that export to Markdown or JSON before you commit to a paid tier.


Table of Contents

What do the best world anvil alternatives look like side by side?

Dimension Wiki-shaped SaaS Local-first Markdown Typed-entity Managers Database Templates Novel with AI
Best for Public wiki publishing Solo offline GM Session-prep DMs Notion-familiar users Novelist + worldbuilder
Free tier Limited (most) Free (Obsidian core) Free tier (Kanka) Free (Notion personal) Free chapter generation
Data model Article/wiki Local markdown files Typed entity records Relational database Structured story + markdown
Public player view Yes No (manual export) Yes (Kanka) Shareable pages No (export-first)
Collaboration Yes (paid tiers) Plugin-dependent Yes (Kanka) Yes Limited
Offline / portability Low Maximum Moderate Low Markdown export
Maps / timelines Strong Plugin-only Moderate Weak No
AI writing assist No No No No Core feature

Two trade-offs worth flagging before you choose:

  • Speed vs. publishability: Typed-entity tools and markdown stacks get you session-ready in minutes; wiki-shaped platforms take longer to set up but produce shareable, presentation-ready worlds.
  • Portability vs. out-of-the-box features: Local-first stacks give you permanent file ownership but require plugins for almost every advanced feature. Hosted platforms offer more built-in tools at the cost of export flexibility.

How to choose the right alternative for your workflow

Comparison infographic of World Anvil alternatives by category

The fastest path to the right tool is matching it to your mental model, not your feature wishlist.

Ask yourself these questions first:

  1. Do I prep weekly sessions or build a long-term archive? Session-first GMs almost always benefit more from typed-entity tools than from article wikis.
  2. Will I publish a public-facing wiki for players? If yes, wiki-shaped SaaS is the only category that handles this cleanly out of the box.
  3. Do I need offline access? If your game table has no reliable internet, local-first markdown (Obsidian) is the only real answer.
  4. Do I want statblock or encounter automation? Typed-entity managers like Kanka and Lorekeeper handle this; the others don’t.
  5. Am I also writing a novel or long-form fiction from this world? That’s where Novel with AI separates itself from pure campaign tools.

Red flags to watch before committing:

  • Paywalled exports: Some SaaS platforms only unlock Markdown or JSON export on paid tiers. Test the export path on a free account before you build anything substantial.
  • No mobile app or offline mode: A tool you can’t reference at the table is only half useful.
  • Ad-supported free tiers with data caps: These often push you toward a paid plan faster than the feature set justifies.

Pro Tip: If you’re torn between two tools, run a two-tool stack: one fast-access tool for weekly session notes (Obsidian or Kanka) and one archive for finished lore. This pairing reduces burnout and keeps you from forcing a single platform to do every job at once.


Short reviews of each alternative category

Wiki-shaped SaaS platforms (Campfire, LegendKeeper)

These are the closest structural cousins to World Anvil. They’re built around cross-referenced articles, interactive maps, and timelines, and they’re the only category that produces a genuinely polished public-facing wiki without extra work.

Pros: Strong map and timeline tools; built-in player-view pages; good cross-referencing between articles. Cons: Steeper setup time; most advanced features sit behind paid tiers; export options vary by platform. Pricing: Campfire offers a free tier with paid plans starting around $5–$10/month. LegendKeeper is subscription-based with a free trial. Platform: Web-based; limited mobile. Export: Markdown and HTML on most paid tiers. Who should pick this: Worldbuilders who want a finished, shareable setting and don’t mind the setup investment.

Local-first markdown stacks (Obsidian)

Obsidian stores everything as plain .md files on your own device. No subscription, no server, no vendor dependency. The plugin ecosystem (Dataview, Leaflet for maps, Templater) extends it significantly, but every feature beyond the core requires manual configuration.

Hands typing on laptop with markdown notes overhead

Pros: Free core app; full offline access; permanent file ownership; Dataview plugin enables queryable databases. Cons: No public player view; plugins require setup time; collaboration is awkward without a sync service. Pricing: Free core; Obsidian Sync costs $4/month if you want cross-device sync. Platform: Desktop (Windows, Mac, Linux); mobile app available. Export: Native markdown files — maximum portability. Who should pick this: Solo GMs who want zero lock-in and are comfortable with a light technical setup.

Typed-entity campaign managers (Kanka, Lorekeeper)

Kanka organizes your world around typed records: NPCs, locations, quests, items, journals. Every entity is queryable, linkable, and filterable. That structure solves the blank-page problem that kills session prep in open-ended wikis. Lorekeeper takes a similar approach with a focus on homebrew tracking.

Pros: Fast entity lookup; built-in campaign journals and session trackers; public sharing options; Kanka has a solid free tier. Cons: Less suited to long-form prose lore; visual/map tools are more limited than wiki-shaped platforms. Pricing: Kanka is free for core use; premium plans unlock more features. Lorekeeper is free and open-source. Platform: Web-based; Kanka has a mobile-friendly interface. Export: JSON export available on Kanka. Who should pick this: Active DMs running weekly sessions who need quick lookups more than publication polish.

Two people collaborating on campaign manager tablet in library

Database-template stacks (Notion, MythScribe)

Notion’s relational databases and linked views make it surprisingly capable for campaign management when you use a purpose-built template. MythScribe is a lighter, worldbuilding-specific tool built on similar database logic.

Pros: Low setup time if you already use Notion; linked records work well for NPC/location relationships; flexible dashboards. Cons: No native map or timeline tools; export to Markdown is possible but not always clean; Notion’s free tier limits collaboration. Pricing: Notion is free for personal use; paid plans start at $10/month. MythScribe pricing is not publicly listed. Platform: Web and desktop; good mobile apps. Export: Markdown and CSV from Notion. Who should pick this: Users who already live in Notion and want a worldbuilding layer without switching apps.

Migration note: Moving from an article-first wiki to any of these categories requires some manual work. Export your World Anvil content as Markdown or HTML first, then map article types to entity types in your new tool. The practical migration approach most practitioners use: export to Markdown, build a minimal CSV schema for core entity types (NPC, Location, Item), import those IDs first, and enrich the records progressively during weekly sessions rather than trying to migrate everything at once.


Which mental model fits your world?

The three dominant data models for worldbuilding software are wiki-shaped, local-markdown (file-first), and canvas/visual. Choosing the wrong one costs you more than features — it costs you a data migration later.

Data model Best for Strengths Weaknesses
Wiki-shaped Published settings, player wikis Cross-referencing, presentation polish, maps Setup time, export lock-in risk
Local-markdown Solo GMs, privacy-first writers Full portability, offline, free No public view, plugin-dependent features
Canvas/visual Story structure, beat mapping Spatial relationships visible at a glance Struggles past a few hundred entries
Typed-entity Active campaign management Queryability, session speed, structured schemas Less suited to long prose lore
Database templates Notion-familiar users Low friction, relational views Weak visual tools, export messiness

Most experienced creators end up using two tools: one for fast session access and one as a long-term archive. That’s not a workaround — it’s a deliberate workflow choice that keeps prep fast and lore permanent without forcing one platform to do both jobs.

Pro Tip: When evaluating any new platform, test the export path on day one. Download a sample export and confirm it opens cleanly in a plain text editor. If the platform can’t produce readable Markdown or JSON, treat that as a long-term lock-in risk regardless of how good the features look today.


Per-tool mini-reviews: core features, pros, cons, and pricing

Campfire is the most writer-friendly wiki-shaped tool on this list. It handles character relationships, timelines, and world maps with a cleaner interface than most competitors. The free tier is functional but limited; the paid tiers unlock collaboration and advanced templates. Best for fiction writers who also run campaigns and want one place for both.

Kanka is the standout typed-entity option. Its entity system covers NPCs, locations, organizations, quests, calendars, and more, all linkable and filterable. The free tier is genuinely usable, not just a demo. The community is active on Discord, and the API opens integration possibilities for technical users. One limitation: the map tools are less polished than dedicated wiki platforms.

Obsidian is the privacy-first choice. Everything lives on your hard drive. The Dataview plugin turns flat notes into queryable databases; the Leaflet plugin adds basic map support. Setup takes a few hours to get right, but once it’s configured, it’s the most resilient long-term option on this list. No server can shut it down.

Notion works best as a campaign manager when you start from a solid template. On its own, the blank-canvas approach can slow you down. With a good worldbuilding template, linked databases for NPCs and locations become genuinely fast to query. The weakness is visual tools — there are none natively, and the Markdown export can be inconsistent with complex page structures.

Lorekeeper is free, open-source, and focused on homebrew tracking for D&D 5e specifically. It handles races, classes, spells, and items well. The trade-off is narrow scope: it’s a homebrew manager, not a general worldbuilding tool.

MythScribe sits between Notion and a dedicated worldbuilding app. It’s lighter than Kanka and more structured than a blank Notion page. Pricing is not publicly listed, which makes it harder to evaluate against the others.

Novel with AI occupies a different lane entirely. It’s not a campaign manager or a wiki. It’s an AI-assisted writing platform with a Pointer System that tracks narrative consistency across chapters, structured story arc generation, and markdown export. For a GM who is also writing a novel set in their campaign world, or a writer who runs campaigns as research, it’s the only tool on this list that handles both jobs with AI support built in.


How does community and support compare across these tools?

Community strength varies sharply across this category. Kanka has an active Discord and a public roadmap; users regularly contribute templates and report bugs directly to the development team. Obsidian’s plugin ecosystem is one of the largest in any note-taking tool, with dedicated subreddits and community vaults shared freely. Campfire has a smaller but engaged community, mostly on its own forums and Discord.

Notion’s community is enormous but not worldbuilding-specific. Finding a good campaign template requires searching Reddit (r/worldbuilding, r/DnD) or the Notion template gallery, and quality varies. Lorekeeper’s community is smaller and more niche, centered on D&D 5e homebrew.

VTT integrations and SRD libraries matter for GMs running published campaigns. Kanka has community-built integrations with Foundry VTT and Roll20 through its API. Obsidian has community plugins that connect to Foundry. Most other tools on this list don’t offer direct VTT integration out of the box.


What integrates with the tools you already use?

Most worldbuilding tools sit alongside, not inside, your VTT. The practical integration question is: can your notes tool talk to Foundry VTT, Roll20, or D&D Beyond?

Kanka’s API is the most open on this list. Technical users have built Foundry VTT modules that pull entity data directly from Kanka into their game sessions. Obsidian connects to Foundry through community plugins like TTRPG System. Neither integration is plug-and-play, but both are documented and actively maintained.

Notion connects to external tools through Zapier and its own API, which means you can push session notes to a Notion database from other apps. It doesn’t connect natively to any VTT, but the flexibility is there for users willing to build it.

Campfire and MythScribe don’t publish VTT integrations. Novel with AI is designed for writing workflows rather than live game management, so VTT integration isn’t part of its feature set. Its markdown export means you can move content into any tool that accepts plain text.

For users who rely on D&D Beyond for character sheets and rules lookups, none of these tools integrate directly. The practical solution most GMs use is a browser-tab workflow: worldbuilding tool open in one tab, VTT or D&D Beyond in another.


Mobile and offline access: what you can actually use at the table

Offline access splits this list cleanly. Obsidian is the only tool that works fully offline by default, since your files live on your device. Every other tool on this list requires an internet connection for full functionality, with varying degrees of cached access.

Kanka has a mobile-friendly web interface that works reasonably well on a phone or tablet, but it’s not a native app and requires connectivity. Notion has polished iOS and Android apps with offline caching for recently viewed pages — useful for reference during a session, less reliable for editing.

Campfire’s mobile experience is limited. LegendKeeper is primarily web-based. Obsidian’s mobile app (iOS and Android) syncs via Obsidian Sync or iCloud and works fully offline once synced.

Novel with AI is a web platform. It’s not designed for at-the-table reference during a session; it’s a writing and planning environment you use between sessions.


How extensible are these tools through plugins and templates?

Obsidian’s plugin library is the deepest on this list. The Dataview plugin alone transforms it from a note-taking app into a queryable campaign database. Templater handles structured note creation. Leaflet adds map rendering. The trade-off is that every plugin requires manual installation and occasional maintenance when updates break compatibility.

Notion’s extensibility comes through templates rather than plugins. The community has produced hundreds of worldbuilding and campaign templates, ranging from simple NPC trackers to full campaign management systems. The ceiling is lower than Obsidian’s plugin ecosystem, but the floor is much higher — a good template gets you functional in an afternoon.

Kanka’s API is its extensibility layer. It’s not a plugin system, but it allows developers to build integrations and automations. The community has used it to create Foundry VTT connectors and bulk import tools.

Campfire uses a modular feature system where you activate the modules you need (characters, maps, timelines, etc.) rather than installing plugins. It’s less flexible than Obsidian but more predictable.

Novel with AI’s extensibility is focused on writing configuration: adjustable tone, style, and narrative structure settings rather than a plugin ecosystem. Its markdown export means the output is portable into any tool that accepts plain text, which is its own form of extensibility.


Key Takeaways

For most session-focused DMs, a typed-entity campaign manager or local-first markdown stack will outperform an article-first wiki on every practical measure that matters week to week.

Point Details
Session-first DMs Typed-entity tools like Kanka give faster lookups and session prep than wiki-shaped platforms.
Privacy and portability Obsidian stores files locally with no subscription and maximum long-term ownership.
Publication and player wikis Wiki-shaped SaaS platforms are the only category that handles public-facing worlds cleanly out of the box.
Two-tool workflow Pair a fast-access prep tool with a separate archive to avoid forcing one platform to do everything.
Novelwithai for writers Novel with AI suits GMs who are also writing long-form fiction and want AI-assisted drafting with markdown export.

The tool category most DMs skip, and why that’s a mistake

The conventional wisdom in worldbuilding communities is to find one tool that does everything. That framing is what leads people to World Anvil in the first place, and it’s also what makes them frustrated with it six months later when the weekly session prep feels like maintaining a wiki instead of running a game.

The more honest framing: your worldbuilding needs split into two distinct jobs. One is fast, messy, and session-specific. The other is slow, structured, and archival. These jobs have different requirements, and no single tool optimizes for both. The GMs who seem to have the smoothest workflows aren’t using a better all-in-one tool. They’re using two lighter tools deliberately, each doing one job well.

What gets underestimated is the cost of the wrong data model. Switching from an article-first wiki to a typed-entity system isn’t just a data migration. It’s a conceptual remap. Your prose-heavy world articles don’t translate cleanly into structured entity fields. You lose context, you lose nuance, and you spend a weekend doing it. That’s the real switching cost, and it’s worth thinking about before you build anything substantial in a new tool.


Novel with AI brings AI-assisted writing into your worldbuilding workflow

The tools above cover campaign management and lore organization well. What none of them do is help you write. Novel with AI is the option for worldbuilders who are also writing long-form fiction from their settings, or GMs who want AI-assisted story structure alongside their campaign prep.

Novelwithai

The Pointer System tracks narrative consistency across chapters, so character details and plot threads stay coherent as your world grows. Structured story arc generation and chapter outlines give you a starting framework rather than a blank page. Everything exports to Markdown, so your content stays portable and readable in any tool. For writers who want AI support built into the process rather than bolted on after, it’s worth a look. Start with a free chapter to see how it fits your workflow.


Useful sources to check before you switch

Before committing to a new platform, these resources cover portability, community comparisons, and migration paths in practical detail: