Notion is great. It's also wrong for worldbuilding, and the reasons aren't obvious until you've spent six months building a beautiful template and discovered that you can't actually write your novel in it.
This isn't a hit piece. Notion is a genuinely good tool for what it is. But "what it is" is a flexible database with documents on top, and worldbuilding asks for something fundamentally different. Here's where the cracks show up, why they show up, and what to actually use instead.
The honeymoon: why Notion seems perfect at first
You discover Notion. You watch a YouTube video where someone has a stunning worldbuilding setup with character galleries, location databases, magic system pages, and timelines. You spend a weekend recreating it. It looks gorgeous. Your characters have property fields for hair colour and faction allegiance. Your locations have a map embed. Your timeline is a database sorted by date.
For about three weeks, this feels like the answer. You add entries. You tweak the template. You feel productive.
Then you start actually writing, and something starts to feel off.
Where it starts to break: the linking problem
The first crack is linking. In Notion, when you mention a character in a location's description, you can manually create a link to that character's page. You have to remember to do it. Every time. For every mention.
Miss one, and the connection doesn't exist. Your character page won't show that they're associated with that location. Your location page won't show them in any backlinks unless the link was made. The "connectedness" of your world is entirely dependent on you remembering to type @ and pick the right entry, every single time you write a name.
For a project with 20 entries, fine. For a worldbuilding project that grows to 200, 500, 2000 entries — and they do, fast — you're now maintaining a manual graph of connections. The graph is full of holes. You don't know which holes, because the missing links are invisible.
Some people use Notion's relation properties to fix this. Now every character has a "locations" relation, every location has a "characters" relation, every event has both. You're now doing manual database administration on your fantasy novel. The question stops being "what's the lore of this place" and becomes "did I update the relations correctly when I added Captain Vex."
The timeline problem
Notion's timeline view is a database sorted by date. It is not actually a timeline.
Real worldbuilding timelines need to handle things Notion doesn't: events that span ranges (the Ash War lasted four years), uncertain dates (the founding of the kingdom is "around year 200"), nested timescales (centuries of history alongside day-by-day events in your draft), and — crucially — the ability to overlay your draft's outline on top of canon to see when planned events would contradict established history.
You can fake some of this with creative database properties. None of it works smoothly. And the moment you want to ask "what was happening politically when my protagonist was born," you're back to manually scrolling through entries.
The character voice problem
This is the one nobody warns you about. Notion is a static reference. Your character pages are documents. They sit there. They don't do anything.
When you're drafting a scene and you're not sure how a character would react — would Mara actually trust this stranger, given what she knows? what she's been through? — Notion can't help you. You can read her page. You can re-read her backstory. But you can't ask her. You can't have a conversation with the character grounded in everything you've established about them.
For a static reference document, this is fine. For a creative tool meant to help you write fiction, it's a significant gap. The character is supposed to feel alive. The tool treats them like a row in a table.
The scaling collapse
Around 50 to 100 pages of worldbuilding content — this varies by project, but the threshold is real — Notion starts to feel like wading through treacle. Specific symptoms:
Search becomes unreliable. You remember writing about a smuggling route, but you can't find it. It's filed under "trade" or "criminal organizations" or "the northern coast" — you don't remember which. Notion's search finds exact matches but isn't great at the associative recall worldbuilders actually need.
Pages get long. A character page that started as a half-screen of notes is now four screens of backstory, relationships, secrets, motivations, scars, accent notes, and stuff you keep forgetting. Loading is slower. Editing is slower. Finding the specific bit you need within the page is slower.
The template starts fighting you. That gorgeous template you set up assumed every character would have the same fields. Now you've got minor characters who only need a name and a function, and major characters who need pages of detail, and the database is forcing them into the same schema. You either over-fill minor entries or your major entries don't fit the template.
Cross-references rot. You renamed a place. The 30 mentions of the old name in other entries are still there, unlinked, slowly becoming invisible. Six months later you find one of them and have no idea whether it's a typo or a different place.
The drafting problem
Eventually you want to actually write your novel. Notion has a document editor, so technically you can draft in it. People have. It's not great. The editor isn't built for long-form prose — chapter management is awkward, there's no real focus mode, formatting for export to standard manuscript format is painful, and word count tracking is rudimentary at best.
So most worldbuilders end up with a split: world in Notion, draft in Scrivener or Word or Google Docs. Now your reference and your prose live in different applications, and every continuity check is a context switch. The connection between world and story — the whole point of having a worldbuilding setup in the first place — is broken by tab-switching.
What you actually need
The worldbuilding-to-novel pipeline asks for things general-purpose tools weren't designed for:
Automatic connections. Mention a character in another entry, and the connection should exist without you doing anything. The graph of your world should build itself.
A real timeline. Canon events and your outline on the same line, with the ability to spot contradictions before they reach the prose.
Living characters. Not pages, but voices — characters you can actually talk to, grounded in what you've established about them.
Drafting in the same place. Not a clunky document editor bolted onto a database, but a real long-form writing environment with your world right there when you need it.
Contradiction surfacing. The tool should tell you when you've contradicted yourself. You should not have to find errors by re-reading 200,000 words.
This is what Inkwarden was built to do. Lore, characters, places, and timelines stay connected automatically. Canon and outline share one timeline so you catch problems early. You can talk to your cast in their own voice, from what they actually know — and draft your manuscript in a focused editor with your world's encyclopedia a click away. The whole pipeline lives in one workspace, and the tool catches the slips before a reader ever could.
Join the Inkwarden waitlist if you've felt your Notion setup start to creak.
The honest case for sticking with Notion
If your worldbuilding fits on a single page, Notion is fine. If you're building a tabletop one-shot or a short story setting, Notion is fine. If you genuinely enjoy database administration as a hobby and the tinkering is part of the appeal, Notion is more than fine — it's flexible enough to do almost anything if you put the work in.
But if you're building something at the scale of a novel — let alone a series — and you've started to feel that creeping sense that the tool is in your way rather than helping, that's not a sign you need a better template. It's a sign you need a tool built for the job.
Worldbuilding isn't a database problem. It's a connected-knowledge problem with a story attached. Treat it like one.