Collaborative writing platforms for shared worlds
Collaborative worldbuilding fails for a different reason than solo worldbuilding. Solo, the problem is recall. Shared, the problem is authority: two people making incompatible decisions in good faith, each believing the question was settled. Tooling helps with the second problem only if it can record who decided what, and when.
What actually breaks
Simultaneous edits are the easy part. Every platform here handles two people typing at once. This is not where shared worlds fail, and it is what most comparisons focus on.
Undeclared canon is the hard part. Author A decides the crossing takes four days. Author B, writing a different region that week, decides it takes a fortnight. Neither is wrong; nobody was told. Six months later both are in drafts.
Permissions and secrecy collide. In a shared world some people should not see some entries, whether that is a co-author running a subplot or a reader you have invited in. Most tools treat permissions as a per-world switch when what you need is per-entry.
What to look for
| Requirement | Why | Who does it well |
|---|---|---|
| Per-entry permissions | Secrets are per-fact, not per-world | World Anvil, LegendKeeper |
| Canon status on entries | Prevents good-faith contradictions | Any tool with custom fields |
| Real-time co-editing | Table stakes, but check the seat count | vvd, World Anvil |
| Named collaborator seats | The usual hidden cost | Varies sharply, see below |
| Export | You will outgrow or leave the tool | Obsidian, vvd Pro, Kanka |
The hidden cost is nearly always seats. A platform that is inexpensive for one writer often is not for four, and seat pricing is where tools diverge most.
The platforms
vvd
Real-time collaboration with a shared wiki, entries and maps in one world. Pro at $10.75 per month or $129 a year includes three collaborators; Studio at $29.17 per month or $350 a year adds roles and permissions, an admin panel, offboarding, and five collaborators with additional seats at $5.83 per month each. (Verified 22 September 2026.)
Notable for shared work: studio-owned worlds on the Studio plan, meaning the world does not walk out of the door with a departing collaborator. That is a genuinely different model from most tools, where the world belongs to whoever created the account.
World Anvil
Co-authors and fine-grained article permissions, with player- and reader-facing views that have been refined over years. Co-author seats arrive on paid tiers and scale with them: 4 on Master at $7/month, 9 on Grandmaster at $12/month, 20 on Sage at $34/month, billed monthly and excluding VAT. (Verified 22 September 2026.)
The tradeoff is the same as always with World Anvil: the most capable permission system here, and the steepest learning curve.
LegendKeeper
Per-entry permissions and a tidy interface. Free Basic plan, Pro at $9 per month or $7.50 monthly billed annually. (Verified 22 September 2026.)
It has been around a long time without becoming essential. In practice it felt like a thin layer over Obsidian or Notion with worldbuilding words applied. Fine to use, but not doing work those tools were not already doing, and its vocabulary leans tabletop besides.
Kanka
Open-source, with permissions and a generous free tier. The right answer for a group that wants shared structure at zero cost and does not mind a functional interface.
Obsidian
Local-first, so genuine collaboration means putting the vault in Git or a synced folder. This works, and writers do it, but you are now running a merge workflow, which is fine for two technical people and unworkable for four who are not.
Google Docs
Still the best tool in the world for two people writing prose at the same time, and one of the worst for holding a world. Use it for drafting; do not use it as the reference. The failure is structural, not incidental: documents cannot express that a character belongs to a place, a family and an era simultaneously.
The conventions that matter more than the tool
One owner per area. Per region, per faction, per era, rather than per entry. Ambiguous ownership is what produces contradictory decisions, and no permission system fixes it.
Canon status, visible. Settled, provisional, abandoned, on every entry. Two people cannot hold this in a shared head, and the threshold for needing it written down is two authors, not ten.
A decision log. One append-only page, dated: what was decided, by whom, and what it overrides. Almost nobody keeps one. It takes a line per decision and it ends the argument about whether something was settled.
Write down who arbitrates. Before you need one. The moment two co-authors disagree about canon is the worst possible moment to negotiate who gets to decide.
Frequently asked
What is the best platform for multiple authors editing one fictional world?
For simultaneous editing of shared lore with permissions, vvd (Pro, three collaborators) and World Anvil's higher tiers are the practical options; LegendKeeper does per-entry permissions too, though little else it offers is beyond what Obsidian or Notion already do. Google Docs is better than all of them for co-writing prose and worse than all of them for holding a world.
Can we use Google Docs for collaborative worldbuilding?
For drafting prose together, yes. Its simultaneous editing and comment threads are still unmatched. For the world itself, no: documents cannot express that a character belongs to a place, a family and an era at once, and holding that is the job.
How do we stop co-authors contradicting each other?
Mark canon status on every entry and make one person the arbiter for each area of the world. Permissions prevent accidents; an owner per area prevents disagreements. You need both.
Is a shared wiki worth it for a two-person project?
Usually yes, and specifically because two people cannot hold "what we have settled" in a shared head. The threshold for needing written canon status is two authors, not ten.