The short answer

Start an Obsidian worldbuilding notebook with a home note, a few connected character and location notes, and a list of open questions. Separate established facts from possibilities, give each fact one main home, and keep a separate backup. Add structure only when retrieving information becomes difficult.

You remember that the ferryman owes someone a favor. You do not remember whether it was the innkeeper, the customs officer, or a character you removed last week. The useful notebook is the one that resolves that uncertainty quickly enough for you to keep writing.

This guide proposes a small workflow, not a hands-on product review. Obsidian’s documentation describes Markdown notes stored in local folders and internal links between notes. Those documented capabilities are enough for the core approach below, which requires no plugins; later sections mention a few optional core plugins built into Obsidian. The folder names and templates are editorial suggestions.

Make a home note with three questions#

Create a vault using Obsidian’s new-vault flow, then create a note called World home. Put three headings in it: what is established, what is undecided, and what the next scene needs. Under the first heading, link only to notes you use repeatedly.

The home note should be a small working index. Do not make it a list of everything you could someday invent. If the story currently involves one river town, its harbor, and three people, those can be your entire initial collection.

Give a fact one main home#

Create Mara the ferryman and North landing. In Mara’s note, write the current fact about her debt. In the location note, link to Mara rather than copying the debt’s wording. A link written as [[Mara the ferryman]] uses Obsidian’s documented wikilink syntax.

This convention reduces the number of places you must remember to update. It does not prevent contradictions automatically. When a fact changes, inspect the notes and scenes that depend on it.

A compact character note might read:

# Mara the ferryman

## Established
Owes the customs officer one favor after the winter crossing.
Works at [[North landing]].

## Open questions
Would she risk the ferry to repay that favor?

## Story use
The debt complicates the escape in chapter four.

Distinguish a possibility from a decision#

Use explicit headings or labels. “The officer might be Mara’s cousin” belongs under open questions until you decide. Without that separation, a discarded possibility can quietly return as a supposed fact.

When you revise a decision, leave a brief reason if it affects several scenes: “Changed the creditor from innkeeper to officer to connect the debt to the border dispute.” You do not need to preserve every brainstorm forever. Keep the history that explains a consequential choice.

Follow one change through the notebook#

Say you settle the question from the opening: Mara owes the customs officer, not the innkeeper. Carry that decision through:

  1. Rewrite the fact in its main home, Mara the ferryman, and add the one-line reason from the previous section.
  2. Check what depends on her. The Backlinks core plugin lists two kinds of mention: linked mentions, from notes that link to the active note, and unlinked mentions, where its name appears as plain text. North landing probably still holds; read it anyway.
  3. Search for the old answer. A line such as “the favor owed to the innkeeper” may never name Mara, so backlinks miss it. Search the vault for innkeeper; wrap a phrase in quotes to match it exactly.
  4. Reread her story use. Does the chapter four escape still work now that her creditor is a customs officer? If you are unsure, record an open question instead of patching the chapter from memory.

If Mara later gains a surname and you rename her note, Obsidian can update internal links across the vault automatically. It changes links, not prose. Sentences that call her “the ferryman” are still yours to check.

Use a short retrieval exercise#

Before adding more folders, try to answer three questions without reorganizing anything: who wants the ferry closed, where the disputed register is, and which scene depends on it. If one answer is hard to find, improve that link or heading first.

For chronology, keep a small working timeline with links to the relevant people. Avoid repeating the entire timeline in every character note. The same principle applies to a map of story locations.

Add a template when a note type repeats#

Write three or four location notes by hand first. By then you know which headings you actually fill. Templates is a core plugin included with Obsidian, though some core plugins start disabled; check Settings → Core plugins. Choose a template folder in its settings, then insert a template at the cursor in the active note. The {{title}} variable becomes that note’s title (Templates).

# {{title}}

## Established

## Open questions

## People here
Link whoever lives, works or hides here.

## Story use

Keep the template as short as your real notes. Twenty empty fields invite you to fill them, and filling them becomes the second project this notebook was meant to avoid.

Fix common notebook mistakes#

Each of these makes the notebook look busier without making it easier to use.

MistakeFix
Building folders before writing notesLink from the home note; add a folder once three notes clearly belong together
Copying a fact into every related noteKeep it in one note and link there
Letting open questions pile upWhen a scene settles one, move the answer under established facts; delete questions the story no longer needs
Writing lore no scene usesIf a note’s story use stays empty, ask whether the book needs it yet
Reading a busy Graph view as progressJudge the notebook by the retrieval exercise instead

Keep a recoverable copy#

Local storage is not itself a backup strategy. Keep a separate copy of your notes and any attachments, and periodically check that you can open that copy. Decide how frequently to back up according to how much work you can afford to lose.

If you later need a reader-facing reference world, compare the organizational approach with World Anvil. Take the small example project with you; moving your entire archive should follow a successful evaluation, not be the evaluation itself.

Update, 10 October 2026: Added a worked example that follows one changed fact through the notebook, a short note template, and a table of common mistakes.

Sources