After three years of helping researchers set up their Obsidian vaults, I’ve noticed a pattern: most fail in the same way, and most succeed for the same reasons.
The failing vaults share one trait — they were built for a blog-post workflow, not a research workflow. Too many plugins, no clear structure, and a daily note template designed for a productivity YouTuber rather than someone managing 400 papers and three parallel projects.
This guide fixes that.
What You’ll Build
By the end of this guide you’ll have:
- A vault structure that scales to thousands of notes without becoming unnavigable
- A paper reading and annotation system connected directly to your Zotero library
- A daily note template designed for research lab notebooks
- The 5 plugins that actually matter (and why the other 200 probably don’t)
- An export workflow that produces clean LaTeX, Word, or PDF output
Video companion
Why Obsidian Specifically?
Three properties make Obsidian uniquely suited to research compared to alternatives:
Local-first, plain text. Your notes are Markdown files on your hard drive. They work offline, transfer between computers trivially, and won’t disappear when a startup pivots. After five years in academia, I’ve watched researchers lose work to sunsetting cloud services twice.
Bidirectional links. The ability to link from any note to any other and navigate that graph backwards is genuinely transformative for connecting literature across a large reading pile.
Plugin ecosystem depth. The Dataview plugin alone — which lets you query your notes like a database — is worth the learning curve for researchers with complex projects.
The weakest point is the learning curve. This guide is designed to flatten it.
Part 1: Installation and First-Run Settings
Installing Obsidian
Download Obsidian from obsidian.md. It’s free, runs on Windows, Mac, and Linux, and the core application has no subscription.
The installer is straightforward. After first launch, you’ll be asked to create a vault — this is just a folder on your computer.
Critical First-Run Settings
Before you add a single note, configure these settings:
Editor:
- Turn off “Auto-pair brackets” if you write a lot of LaTeX inline math
- Enable “Use tabs” and set tab size to 2 for clean indentation in templates
Files and Links:
- Set “New link format” to “Shortest path when possible”
- Enable “Automatically update internal links” — this is crucial when you reorganise files later
Appearance:
- Choose a theme. For researchers who read for hours, I recommend Minimal (install via Community Plugins) for its clean typography
Part 2: Vault Architecture
The 4-Folder System
Most failed Obsidian setups have one or two problems: either no structure at all (one giant flat folder) or over-engineered structure that collapses under complexity.
The system below is opinionated but proven at scale:
📁 00-Inbox/
📁 10-Projects/
📁 20-Literature/
📁 30-Concepts/
📁 40-Resources/
📁 50-Archive/
00-Inbox — Everything goes here first. Newly captured ideas, downloaded papers waiting to be processed, rough notes from meetings. The rule: everything starts here, nothing stays here.
10-Projects — One subfolder per active project (thesis chapters, papers, grants). Contains daily notes, meeting notes, and project-specific to-dos.
20-Literature — One note per paper you’ve read. Named AuthorYear_ShortTitle. Connected to your Zotero library.
30-Concepts — Your Zettelkasten-style concept notes. Not summaries of papers — your own synthesis of ideas. “The three main critiques of X methodology” goes here, not in Literature.
40-Resources — Templates, reference materials, checklists, and plugin configs.
50-Archive — Finished projects, old notes you want to keep but not see daily.
The critical rule
Part 3: The 5 Essential Plugins
Install these via Settings → Community Plugins → Browse:
1. Dataview
The most powerful plugin in the ecosystem. It turns your notes into a queryable database.
Use case for researchers: create a reading list that auto-populates from all notes in 20-Literature/ that are tagged #status/unread.
TABLE title, year, journal FROM "20-Literature"
WHERE contains(tags, "status/unread")
SORT year DESC
2. Templater
Automate note creation with intelligent templates. Unlike the built-in templates plugin, Templater can run JavaScript, fetch dates, prompt for input, and move files automatically.
3. Citations (Better BibTeX compatible)
Connects your reference manager to Obsidian. With Zotero + Better BibTeX installed, you can:
- Select a paper in Zotero
- Press a hotkey in Obsidian
- Get a new literature note with title, authors, abstract, and citation key pre-filled
Setup time: approximately 20 minutes. Time saved: incalculable.
4. Pandoc + Pandoc Plugin
Obsidian’s Pandoc plugin lets you export any note to Word, LaTeX, HTML, or PDF with a single command — preserving citations in any format your supervisor or journal requires.
5. Excalidraw
Draw conceptual diagrams directly in Obsidian notes, embed them inline, and have them update when you edit the drawing. Essential for visually mapping theoretical frameworks.
Part 4: The Literature Note Template
Your template for 20-Literature/ notes should capture:
---
title: "{{title}}"
authors: [{{authors}}]
year: {{year}}
journal: "{{journal}}"
doi: "{{doi}}"
citekey: "{{citekey}}"
tags: [literature, status/unread, {{pillar}}]
dateAdded: {{date}}
---
## Summary
*(1–3 sentences: what they did and what they found)*
## Key Argument
*(The central claim of the paper)*
## Methods
*(Relevant methodological details)*
## Key Findings
*(Bullet points — only what's new or relevant to your work)*
## My Notes
*(Your reaction, questions, connections to your own work)*
## Connections
- [[RelatedConcept1]]
- [[RelatedPaper1]]
## Citation
{{citekey}} — {{fullcitation}}
Part 5: The Daily Research Note
The daily note in Obsidian is often set up like a life organiser. For researchers, it should function more like a lab notebook.
---
date: {{date}}
project: "[[{{active_project}}]]"
type: daily-note
---
## Today's Focus
*(One sentence: what will make today successful)*
## Working Log
*(Running notes as you work — rough, unpolished)*
- 09:15 — Reading [[AuthorYear_Title]]; note on methodology at [[Concept note]]
- 11:00 — Stuck on section 3.2; [question to address tomorrow]
## Papers Added to Reading List
-
## Ideas to Develop
-
## Tomorrow
-
Common Problems and Fixes
Problem: Graph view is a useless spaghetti mess.
Fix: This usually means you’re linking dates and common words. Use the graph view filters to exclude 00-Inbox/ and filter to a single project folder.
Problem: The vault is slow to load. Fix: Usually caused by Dataview reindexing too frequently or community plugins with background processes. Disable unused plugins — you need 5, not 30.
Problem: Citations plugin can’t find my Zotero library.
Fix: Ensure Better BibTeX is installed in Zotero and has exported your library to a .bib file. In the Citations plugin settings, point to that file path.
The One-Week Setup Plan
| Day | Task |
|---|---|
| Day 1 | Install Obsidian, create vault, configure settings |
| Day 2 | Create folder structure, add 5 existing notes to test it |
| Day 3 | Install and configure Dataview + Templater |
| Day 4 | Set up Citations + Zotero integration |
| Day 5 | Import 10 papers as Literature notes |
| Day 6 | Create your first Concept note from your reading |
| Day 7 | Review what felt awkward — adjust one thing |
Don’t try to import your entire reference library on day one. Build the habit with 10 papers, then expand.
Next Steps
Once your vault is running, the companion articles in this series cover:
- The Zettelkasten Method Adapted for Academic Research
- Dataview Queries for Researchers: 15 Practical Examples
- Exporting from Obsidian to LaTeX: The Complete Workflow