Obsidian for Fiction Writers: Setup, Plugins, and Workflow

You downloaded Obsidian because someone on Reddit said it changed their writing life. You opened it. You got a blank screen and a file tree. You created a note called "Characters" and another called "Plot Ideas." Then you stared at the screen for twenty minutes, wondering what all the fuss was about.

Obsidian out of the box is not a writing tool. It's a note-taking engine with no opinion about how you should use it. That blank-slate flexibility is the product's greatest strength and the reason most writers abandon it within a week. They don't need another place to store random thoughts. They need a system that supports the specific work of writing fiction: tracking characters, managing worldbuilding, drafting scenes, and keeping continuity across a 90,000-word manuscript.

This guide builds that system. By the end, you'll have a folder structure, four plugins, a set of templates, and a linking strategy that turns your vault into a living series bible connected to your manuscript.

The Folder Structure

Obsidian vaults can be organized any way you like. That freedom paralyzes people. Start with this structure and modify it once you understand why each folder exists:

MyNovel/
├── Manuscript/
│   ├── Act 1/
│   ├── Act 2/
│   └── Act 3/
├── Characters/
├── Worldbuilding/
│   ├── Locations/
│   ├── Magic/
│   ├── Factions/
│   └── History/
├── Plot/
│   ├── Outline/
│   └── Timeline/
├── Research/
└── Templates/

The Manuscript folder holds your actual draft. Each scene is a separate note. If you're writing a novel with thirty chapters, each chapter subfolder contains the scene files for that chapter. This granularity matters because it lets you rearrange scenes without cutting and pasting inside a massive document.

The Characters folder holds one note per character. Not a single "characters.md" file with everyone crammed in. One note each. This lets every mention of "Elena" anywhere in your vault link back to her character file.

The Worldbuilding folder mirrors whatever categories your world demands. Fantasy novels need locations, magic systems, factions. Thrillers might need organizations, technologies, cover identities. Adjust the subfolders, but keep the parent folder.

The Plot folder holds your outline, beat sheet, and any timeline work. Keep this separate from the manuscript. Your outline will change as you draft, and you want both versions accessible.

Templates holds the note templates you'll create for characters, locations, scenes, and anything else you generate repeatedly. More on this below.

The Four Plugins You Need

Obsidian's community plugin library contains over a thousand options. Most of them solve problems fiction writers don't have. Install these four. Ignore everything else until you've used them for at least a month.

1. Longform

This is the plugin that turns Obsidian from a note-taking app into a manuscript manager. Longform adds a dedicated sidebar that collects your project files, displays them in order, and lets you rearrange scenes by dragging them.

Create a new Longform project by adding a note in your Manuscript folder with the right frontmatter. The plugin picks it up and starts tracking every scene file in that folder. You get a sidebar showing your entire novel's structure, collapsible by act or chapter, with word counts at every level.

The compilation feature is where Longform earns its place. When you're ready to export, the plugin stitches your individual scene files into a single document, in order, with configurable separators between scenes and chapters. You write in fragments. You export a manuscript.

Longform also tracks word count goals. Set a daily target, a project target, or both. The sidebar shows your progress without you opening a separate tracking app.

2. Templater

Obsidian has a built-in template feature. It's basic. Templater replaces it with a system that supports variables, date insertion, cursor placement, and even JavaScript execution.

For fiction writers, Templater means you can create a character template that prompts you to fill in specific fields every time you create a new character note. The template drops your cursor at the first blank field and pre-populates the structure. Same for locations, scenes, magic systems, factions, or any other recurring note type.

A character template might look like this:

---
type: character
role:
age:
first-appearance:
status: alive
---

## Appearance


## Personality


## Wound
What happened to them. What lie did it install.

## Want vs Need
**Want:**
**Need:**

## Relationships
- [[]]

## Arc
Where they start. Where they end. What it costs.

When you trigger this template, Templater creates the note, names it based on your input, and drops your cursor at the first empty section. Thirty seconds, and you have a structured character file ready to link from anywhere in your vault.

3. Dataview

Dataview treats your vault as a queryable database. Every note with YAML frontmatter (those dashed lines at the top of a file) becomes a row in a table you can filter, sort, and display.

Fiction writers use Dataview to answer questions their vault already contains the answers to. If your character notes all have a role field in their frontmatter, you can write a query that lists every antagonist:

```dataview
TABLE role, age, first-appearance
FROM "Characters"
WHERE role = "antagonist"
SORT first-appearance ASC
```

That query generates a live table. Add a new antagonist character note, and the table updates automatically. No manual list maintenance.

Other queries fiction writers run constantly: all scenes tagged with a specific POV character. All locations mentioned in Act 2. Every character marked as "dead" whose death hasn't been revealed to the protagonist yet. Every scene without a defined conflict. If you put the data in your frontmatter, Dataview retrieves it.

4. Calendar

The Calendar plugin adds a visual calendar to your sidebar. Click a date, and it creates or opens that day's daily note. For fiction writers, daily notes become writing logs: what you wrote, what you figured out, what's stuck.

This sounds minor. It isn't. A month of daily notes creates a searchable record of your creative process. When you can't remember why you changed the antagonist's motivation in chapter twelve, the answer is in your daily note from three weeks ago. That note links to the character file, which links to the scene where you made the change.

Linking Strategy: The Real Power

Plugins are useful. Links are the reason Obsidian works for fiction. Every time you mention a character, location, or concept in any note, wrap it in double brackets: [[Elena]], [[Varenhold]], [[the Binding Oath]]. This creates a bidirectional link.

When you open Elena's character file, the backlinks panel shows every note that mentions her. Every scene she appears in. Every worldbuilding note that references her family. Every plot note where her arc intersects with the main conflict. You didn't build this index manually. It built itself as you wrote.

This is where Obsidian outperforms Scrivener, Word, and even Notion for fiction writers. In Scrivener, your character sketch and your manuscript are separate systems. You update one and forget to update the other. In Obsidian, they're the same system. Mention Elena in a new scene, and her character file knows about it instantly.

Linking Rules That Keep Your Vault Clean

One note per entity. One character, one note. One location, one note. One magic system concept, one note. If you're tempted to put three characters in a single file, split them. Links break when entities share files.

Link on first mention per note. If Elena appears ten times in a scene, link her name the first time. Don't turn every mention into a link. It clutters the text and inflates your backlink counts with noise.

Use aliases for name variants. Obsidian supports aliases in frontmatter. If your character's full name is "Elena Vareth" but you usually write "Elena," add both forms as aliases. Links will resolve regardless of which name you use.

Link from manuscript scenes to worldbuilding notes, not the reverse. Your scene mentions the Binding Oath? Link it. But don't go into the Binding Oath note and manually add links to every scene that references it. Backlinks handle this automatically. Manual bidirectional linking creates maintenance work that defeats the purpose of the system.

Building Your Series Bible

A series bible is a reference document that tracks continuity across a long project. In traditional writing software, it's a separate document (or a binder of documents) you maintain alongside your manuscript. In Obsidian, the series bible builds itself from your existing notes.

Create a note called "Series Bible" and fill it with Dataview queries:

## Characters
```dataview
TABLE role, status, first-appearance
FROM "Characters"
SORT role ASC
```

## Locations
```dataview
TABLE type, region
FROM "Worldbuilding/Locations"
SORT region ASC
```

## Timeline
```dataview
TABLE event, date, characters
FROM "Plot/Timeline"
SORT date ASC
```

This note becomes a dashboard. It pulls live data from your vault. Add a character, and they appear in the bible. Kill a character (set status: dead), and the table reflects it. You never manually update the series bible. Your writing updates it for you.

For multi-book series, add a book field to your frontmatter and filter queries by book number. Your series bible can show all characters from Book 1 who haven't appeared in Book 2 yet. Try doing that with a Word document.

Scene Notes: Where Drafting Meets Planning

Each scene in your Manuscript folder should have frontmatter that tracks more than just the text. A scene template with metadata lets Dataview query your manuscript the same way it queries your worldbuilding:

---
type: scene
pov: "[[Elena]]"
chapter: 7
act: 2
status: draft
conflict: Elena discovers the Binding Oath has a loophole
wordcount:
---

Now you can query for scenes. All scenes in Act 2 that haven't been revised. All scenes from Elena's POV. All scenes without a defined conflict (which tells you where your outline has gaps). The frontmatter takes fifteen seconds to fill in. The queries save hours of scrolling through your manuscript wondering what you've written and what you've skipped.

The status field is particularly useful during revision. Tag scenes as draft, revised, or final. A Dataview query showing all draft scenes gives you a live revision checklist that empties as you work through your manuscript.

Daily Writing Workflow

Here's what a writing session looks like once the system is in place:

Open Obsidian. The Longform sidebar shows your manuscript. The Calendar plugin shows today's date. Click it to create your daily note.

Check your Dataview dashboard. Your series bible shows where things stand. Your scene query shows which scenes are still in draft. Pick the next scene to write or revise.

Open the scene file. The backlinks panel shows every note connected to this scene: the characters who appear, the location, the plot thread it advances. You have your reference material one click away without leaving the writing environment.

Write. As you mention characters and locations, link them. If you invent something new (a place name, a spell, an NPC), create the note now while it's fresh. Templater fills in the structure. You add the details you know. The rest can wait.

Log your session. In today's daily note, jot down what you wrote, what you figured out, what's bothering you. Tomorrow, your past self will have left you a trail.

Common Mistakes and How to Avoid Them

Over-organizing before you write anything. Writers spend three weeks building an elaborate vault structure and never write a scene. Start with the basic folder structure above. Add complexity only when the simple version fails you. If you haven't written 10,000 words of manuscript, you don't need a custom CSS theme or fifteen Dataview dashboards.

Installing too many plugins. Every plugin you install adds cognitive overhead and potential conflicts. The four plugins listed here handle 95% of fiction writing needs. The Kanban plugin, the Mind Map plugin, the Excalidraw plugin. They're all interesting. They're also distractions until your core workflow is solid. Give yourself a month with only these four before adding anything else.

Linking everything to everything. New Obsidian users link aggressively because the graph view looks impressive with lots of connections. Meaningful links connect entities that have narrative relationships. Your protagonist and her mentor should be linked. Your protagonist and the tavern she visited once in chapter three probably shouldn't be. Link entities that recur, that develop, that matter to your story's logic.

Treating the vault as a second manuscript. Your character notes should contain reference information, not prose you plan to use in the novel. The vault is your workshop. The manuscript is the finished product. If you're writing beautiful paragraphs in a character note, you're writing in the wrong place.

Forgetting to back up. Obsidian stores files locally. Local files can be lost to hardware failure, accidental deletion, or a bad sync conflict. Use Git, a cloud backup service, or at minimum a weekly manual copy to an external drive. Your vault is your entire creative infrastructure. Protect it the way you'd protect any other irreplaceable document.

Syncing Across Devices

Obsidian's files live on your computer. If you write on multiple machines or want mobile access, you need a sync solution.

Obsidian Sync ($8/month) is the official option. It's encrypted, handles conflict resolution, and works reliably. If you're earning money from your writing, the cost is trivial compared to the pain of a sync conflict destroying a day's work.

iCloud works well on Apple devices. Point your vault to an iCloud Drive folder, and it syncs between Mac and iOS. Occasional sync delays happen, but for most writers the experience is seamless.

Dropbox or Google Drive can sync your vault folder, but Obsidian's many small files sometimes trigger sync conflicts with these services. If you use this approach, avoid editing the same note on two devices without syncing between sessions.

Git gives you version history and backup in one system. If you're comfortable with Git, it's the most robust option. Every commit is a snapshot you can return to. But Git has a steep learning curve, and resolving merge conflicts in a 3,000-word scene file is not how most writers want to spend their morning.

Pick one sync method and commit to it. The worst outcome is no backup at all.

When Obsidian Is the Wrong Choice

Obsidian rewards investment. If you're willing to spend a weekend setting up your vault, learning the plugins, and building your templates, it becomes a writing environment that no commercial tool can match for flexibility and ownership. But that investment is real, and it's not for everyone.

If you want something that works the moment you open it, use Scrivener. If you want visual databases and effortless collaboration, Notion is the better fit. If you're writing a single standalone novel and don't plan to build a series bible, a word processor is fine.

Obsidian pays its biggest dividends on complex projects: multi-book series, sprawling secondary worlds, stories with large casts and intricate continuity. The more information you need to track, the more the linking and querying system justifies the setup cost. A writer tracking three characters in a contemporary romance doesn't need Dataview queries. A writer managing forty characters across a five-book epic fantasy does.

Match the tool to the project. Your writing process matters more than your software. But when the project demands it, Obsidian delivers infrastructure no other free tool can replicate.