Roundups & Lists
The best second-brain templates for PKM enthusiasts in 2026: PARA, Zettelkasten, MOC, Daily Notes, and more. Steal these proven structures instead of building your own from scratch — with honest notes on what each one actually does well.
A second-brain template is a pre-built structure you can adopt — or adapt — instead of building your knowledge system from scratch. The best templates embed decades of thinking about how knowledge actually works, tested by the people who developed them.
We selected these 10 templates based on:
The honest disclaimer: the best second-brain template is one you'll actually maintain. A brilliant system you abandon after three weeks is worse than a mediocre one you use every day. These templates are starting points, not prescriptions.
What it is: A four-folder top-level structure for all your notes and files: Projects (active, with a deadline), Areas (ongoing responsibilities, no deadline), Resources (interests you might someday use), and Archives (inactive items from any of the above).
Who it's for: Anyone frustrated by topic-based folder systems that grow without limit. PARA works in any app — Notion, Obsidian, Google Drive, a file system, or even email.
Standout strength: The insight is that organizing by actionability (projects vs. areas vs. resources) is more useful than organizing by topic (healthcare, writing, finance). Topics don't have deadlines; projects do. Your active project work should be separated from background reference material because you use them differently.
Weakness: PARA requires honest categorization — many people struggle to distinguish "Areas" from "Resources" consistently. The system can feel too sparse for people who want more nuance in organization.
How to steal it: Create four top-level folders in any tool. Move everything you have into one of the four. When adding new items, ask: is this for a current project? An ongoing responsibility? Future reference? Or archived? That decision determines which folder it goes in.
Origin: Tiago Forte's "Building a Second Brain" (2022, Atria Books).
What it is: A slip-box system (German: "Zettelkasten" = "note box") in which each note contains exactly one idea, is given a unique identifier, and is linked to related notes. Developed by sociologist Niklas Luhmann, who used it to write 58 books and 400+ papers.
Who it's for: Researchers, writers, and serious thinkers who want knowledge to compound — each new note connecting to and enriching prior notes rather than sitting in isolation.
Standout strength: The atomic note principle (one idea per note) and mandatory linking ensure your notes build into an interconnected knowledge network. Luhmann described his Zettelkasten as a "communication partner" — the connections surfaced things he hadn't consciously thought to connect. Research by Ahrens (2017, "How to Take Smart Notes") documented this process and popularized it for academics and writers.
Weakness: High overhead per note. Writing atomic notes with connections for every idea requires more time than traditional note-taking. The system's power emerges over years, not weeks — patience is required.
How to steal it: For each new idea, write one note containing only that idea. Add links to 2-3 existing notes it connects to. Give it a reference number (or a meaningful slug in digital tools). Never dump multiple ideas in one note.
Origin: Niklas Luhmann's physical Zettelkasten (1950s-1998); digitally popularized by Sönke Ahrens' "How to Take Smart Notes" (2017).
What it is: Index notes that serve as navigational hubs for related ideas. An MOC for "writing" links to notes about structure, style, editing, tools, and specific writing projects — providing a map of a topic without enforcing rigid folder hierarchy.
Who it's for: Obsidian users and networked note enthusiasts who want a middle layer between individual notes and the flat global graph.
Standout strength: MOCs solve the "too many notes, no navigational structure" problem that afflicts large Zettelkasten systems. They're flexible — you can have MOCs at multiple levels of specificity. A "writing" MOC can link to a "long-form writing" MOC that links to individual technique notes.
Weakness: Creating and maintaining MOCs adds a meta-organization layer. Some users create MOCs but never update them as notes change. MOCs that fall out of sync with the actual notes become misleading.
How to steal it: When you have 10+ notes on a topic, create an index note for that topic. List the key notes with brief descriptions. Update it when significant new notes are added. The MOC becomes your navigational starting point when you return to that topic.
Origin: Nick Milo's "Linking Your Thinking" (LYT) framework, developed publicly in Obsidian community resources.
What it is: A repeating template for each day's notes — typically containing: date, current projects, thoughts, meeting notes, reading notes, and tasks — with links to project pages and yesterday's note.
Who it's for: Anyone who wants a low-friction daily capture habit. Roam Research popularized this format; Obsidian, Logseq, and Notion all have daily notes plugins or features.
Standout strength: Daily notes solve the "where do I put this?" problem by creating a default destination for everything captured each day. You don't have to decide in the moment — it goes in today's note. Weekly reviews pull the important items forward into permanent notes.
Weakness: Daily notes grow rapidly and require regular processing to prevent accumulation. Raw daily notes without a review habit become an undifferentiated log.
Template structure:
# [Date]
## Today's focus
-
## Notes from reading / meetings
-
## Thoughts / ideas
-
## Processed to permanent notes
- [ ]
What it is: A four-layer highlighting approach to process any piece of content: Layer 1 = save the original; Layer 2 = bold the most valuable passages; Layer 3 = highlight the bolded content further; Layer 4 = write a brief executive summary in your own words.
Who it's for: Knowledge workers who save large amounts of content and want a systematic way to identify and extract what's actually valuable.
Standout strength: The compression approach means you can work at different levels of intensity depending on how important a piece is. You can stop at Layer 2 for most content (quick bold scan) and go to Layer 4 only for the highest-value items. The summary in Layer 4 is in your own words, which makes it retrievable by your vocabulary.
Weakness: Time-intensive when applied thoroughly. Easy to over-bold (Layer 2 loses value if 50% of the text is bolded). The system requires discipline about which level to apply to which content.
How to steal it: The next time you save an article, bold the key sentences (Layer 2). For the top 10% of what you save, add a highlight layer (Layer 3). For the top 1% — things you'll definitely use — write a 2-3 sentence summary in your own words (Layer 4).
Origin: Tiago Forte's progressive summarization methodology, documented in Building a Second Brain (2022).
What it is: A two-note-type system adapted from Zettelkasten: Literature Notes capture what an author says (close paraphrase + citation); Permanent Notes capture what you think about the idea in your own words. Literature notes are discardable; permanent notes are forever.
Who it's for: Researchers, academics, and writers who read heavily and want to convert others' ideas into their own thinking.
Standout strength: The separation between "what the author said" and "what I think" is genuinely important — most people conflate them. Permanent notes in your own words are retrievable by your thinking vocabulary; direct quotes require knowing the author's exact phrasing.
Weakness: Requires disciplined conversion — most people write literature notes but don't complete the conversion to permanent notes. Literature notes without permanent notes accumulate without producing knowledge.
How to steal it: For important ideas you read: write a literature note (3-5 bullet points of what the text said + source). Within 48 hours, convert to a permanent note: write the idea in your own words as if explaining to someone else. Delete or archive the literature note.
What it is: A structured weekly habit for processing the previous week's captures, updating project statuses, identifying next actions, and closing loose ends before the new week.
Who it's for: Everyone with a note-taking or task management system who finds themselves accumulating unprocessed captures and stale to-do items.
Standout strength: The weekly review is where captured raw material becomes processed knowledge. Without it, notes accumulate but don't compound. David Allen's GTD (Getting Things Done, 2001) identified the weekly review as the practice that prevents system breakdown.
Template structure:
# Weekly Review — [Week of Date]
## Clear captures
- Process inbox to zero
- Process daily notes
## Update projects
- [ ] Project A: next action = ?
- [ ] Project B: status?
## This week's wins
-
## Outstanding loose ends
-
## Next week's priorities
1.
2.
3.
What it is: A standard structure for capturing meeting content: attendees, agenda, decisions made, action items with owners and dates, and reference links.
Who it's for: Any knowledge worker in meetings who finds meeting notes either too sparse to be useful or too long to be actionable.
Standout strength: Structured meeting notes solve the problem of notes that sit passively without producing follow-through. By capturing decisions and action items explicitly (with owner + date), the meeting note becomes a reference that drives accountability.
Template structure:
# Meeting: [Name]
Date:
Attendees:
## Agenda
-
## Decisions
-
## Action items
- [ ] [Name] will [action] by [date]
## Notes
## Reference links
Weakness: Maintaining consistency requires a template that loads automatically — most people fill structured templates when they remember to use them, which is inconsistently.
What it is: A standard structure for processing a book or long article: metadata (title, author, date, how you found it), main argument, best ideas (with your reactions), questions raised, and what you'll apply.
Who it's for: Knowledge workers who read to learn and want to extract more from each book than a handful of highlighted quotes.
Standout strength: The "what I'll apply" section forces active response — you commit to at least one behavior change or practical application before filing the note. Notes without application commitments tend to be inert.
Template structure:
# [Book Title] — [Author]
Date finished:
Source:
## Core argument
(The book in 2-3 sentences)
## Ideas worth developing
1. [idea + my reaction]
2.
3.
## Questions this raised
-
## What I'll apply
-
What it is: A single note per project that serves as the entry point for everything related to that project — links to relevant notes, saved research, meeting notes, tasks, and outputs.
Who it's for: Anyone who works on multiple concurrent projects and needs a way to quickly orient themselves when switching between them.
Standout strength: Project hubs solve context-switching friction. Instead of scattered notes across many folders, one hub links to everything relevant for a specific project. When you return to a project after two weeks, you reenter through the hub rather than reconstructing context from a disorganized file structure.
Template structure:
# Project: [Name]
Status: Active / Paused / Complete
Deadline:
## What I'm trying to accomplish
(1-2 sentences)
## Key resources
- [[Research notes]]
- [External references](link)
- [WebSnips library for this project](link)
## Meeting notes
- [[Meeting — date]]
## Decisions made
-
## Next action
-
## Output files
| Template | Best for | Maintenance overhead | Works in any tool? | Origin |
|---|---|---|---|---|
| PARA | File/folder organization | Low (4 buckets) | Yes | Tiago Forte |
| Zettelkasten | Research/writing | High (per-note linking) | Yes | Niklas Luhmann |
| MOC | Navigation in large vaults | Medium | Best in linking tools | Nick Milo |
| Daily Notes | Daily capture | Low | Yes | Roam Research |
| Progressive Summarization | Content processing | Medium | Yes | Tiago Forte |
| Literature + Permanent Notes | Academic reading | High | Yes | Ahrens/Luhmann |
| Weekly Review | System maintenance | Medium | Yes | David Allen (GTD) |
| Meeting Notes | Meeting capture | Low | Yes | Universal |
| Reading Notes | Book processing | Medium | Yes | Universal |
| Project Hub | Project context | Low (per project) | Yes | Universal |
Best single template to start with: Daily Notes template — lowest overhead, highest capture rate, works in any tool.
Best for building a writing system: Zettelkasten + Literature/Permanent Notes combo — every book and article feeds into a growing knowledge network.
Best for project-heavy knowledge workers: PARA + Project Hubs — PARA organizes your file structure; Project Hubs organize your context.
Best for readers: Progressive Summarization + Reading Notes template — compress what you read to what's actually valuable.
Best for maintaining the system: Weekly Review template — without it, every other template decays.
WebSnips adds a specific layer that none of these templates covers directly: the capture and organization of web-based reference content. The Project Hub template works best when every project's key research links point somewhere organized — WebSnips provides that layer for web sources. Instead of pasting URLs into a Project Hub (where they'll rot into dead links), you save sources to WebSnips with context notes, then link your WebSnips topic collection into the project hub.
The PARA method handles files and notes; WebSnips handles the web-reference layer that PARA doesn't address cleanly.
The best second-brain templates are ones you'll adapt and actually use — not the most elegant or elaborate on paper. Start with Daily Notes (captures everything), add a Weekly Review (processes everything), and adopt PARA (organizes everything) as your foundational three. Add Zettelkasten principles as your note volume grows and your need for connected thinking increases. Templates are scaffolding; the building is what you write.
More WebSnips articles that pair well with this topic.
10 daily habits for a useful second brain in 2026 — from morning capture to weekly review. A practical, research-backed guide for PKM enthusiasts who build second brains in Obsidian, Notion, or Roam but want them to actually compound over time.
10 ways to fight link rot in 2026 — from the Wayback Machine and Perma.cc to Zotero snapshots, DOIs, and archive.today. A practical guide for academic researchers who need web sources to remain accessible when they write up their research.
12 browser tips for power researchers in 2026 — from Google operators to tab groups, custom search engines, and save-before-close habits. A practical guide for knowledge workers who want to extract more from every research session.