How to Take Notes with Zettelkasten
A practical guide to taking notes with Zettelkasten: preserve sources, rewrite one idea at a time, connect related notes, review lightly, and turn research into useful work.
The Zettelkasten method is a practical way to take notes: capture a useful idea with its source, rewrite it in your own words, give it a clear title, connect it to related ideas, and return to those connections when they can help with real work. Bryan Collins's workflow shows how to adapt that process for articles, videos, books, podcasts, courses, and research without turning note management into a second job.
The method does not depend on one app. It depends on what you do with a note after saving it.
How do you take notes with Zettelkasten?
Use this six-step process:
- Capture an idea and preserve its source.
- Review rough captures later.
- Rewrite one main idea in your own words.
- Give the note a title and add useful connections.
- Review related notes when a question or project calls for them.
- Use the notes to write, decide, research, or make something else.
This guide draws on Bryan Collins's video, "The Zettelkasten Method: How to Use This Research System To Write", and adapts the workflow for different kinds of source material.
What is the Zettelkasten method?
In Collins's video, Zettelkasten is the name for a system that collects, clarifies, and connects ideas so they can support future writing. His process has two main stages: quick captures first, then more deliberate notes after review.
A saved quote shows that something caught your attention. A usable note explains what the idea means, where it came from, and how it relates to a question you may work on later. That distinction is the heart of the method.
Collins describes returning to older notes, updating them when his thinking changes, and searching related material when he begins an article. Those habits matter more than copying his app, tags, or schedule. You can use a notebook, plain-text files, a journaling app, or a knowledge workspace.
This article uses the spelling from Collins's video and focuses on the workflow he demonstrates. It does not depend on a historical account of the method or a translation of the term.
1. Capture the idea and preserve its source
Start with a low-friction place for rough material. When a passage, observation, question, or quote seems useful, record it before the surrounding context disappears.
Your source might be:
- An article or research paper
- A YouTube video
- A podcast episode
- A book or ebook
- A course or lecture
- A conversation or meeting
- Your own observation
Add the link or citation at the same time. For a book, include the author, title, and page when you have them. For a video or podcast, add a timestamp if it will help you find the passage again. For a research paper, keep the full citation.
A rough capture from Collins's video could look like this:
Idea: A note system becomes useful through review and connection, not capture alone.
The inbox note does not need to be polished. If you stop every few seconds to format it perfectly, capture becomes harder to maintain. Save enough information to recover the source and understand why the idea caught your attention. Interpretation can happen during review.
2. Separate rough notes from usable notes
A rough note records what caught your attention. A usable note records what you think about it after reviewing the source. Keeping those stages separate lets you capture quickly without treating every highlight as finished research.
Collins describes reviewing rough notes the next morning, at the end of the week, or whenever fits his schedule. You can use a daily review, a weekly review, or a project-based review. There is no need to copy his timing if another rhythm is easier to keep.
During review, ask:
- What is the actual idea here?
- Can I explain it without looking at the source?
- Is this one idea or several ideas mixed together?
- What did the source say, and what is my response?
- Which question or project could this support?
- Do I need to check the original source before relying on it?
Here is the difference between the two stages:
Rough capture:
Interesting point from the video about review. Look at this later.
Usable note:
Review turns a saved idea into material I can use.
Quick notes preserve possibilities while I am reading or watching. During review, I decide which observations deserve their own notes.
The second note can stand on its own. You do not need to replay the video to understand what you meant, and you have an idea that can connect to notes about research, writing, or information overload.
3. Write one idea per note
Give each note one main claim, observation, or question. A note can contain several sentences when they explain the same idea. Split it when different parts could support different projects or connect to different lines of thought.
Suppose you capture this while watching a video:
The Zettelkasten method uses rough notes, source links, summaries, tags, backlinks, regular reviews, and published writing. It can work for books, podcasts, videos, and articles. Collins uses Day One, but other apps can work too.
That capture contains several possible notes:
A rough note is an inbox item, not a finished research note.
Rewriting a source in your own words turns a saved passage into an explanation you can evaluate.
The note-taking process matters more than selecting a particular app.
The rewrite tests whether you understand the material. It also gives you room to add a qualification, counterpoint, or practical implication.
Keep an exact quotation when the wording matters, but mark it as a quotation and retain the citation. Your paraphrase should not quietly replace the source when you are making an important claim.
4. Make notes easy to recognize and connect
Give each note a title that makes sense in a search result or beside another note. "Podcast notes" and "Interesting idea" are difficult to use later. "Review turns captured material into reusable research" tells you what the note contains.
Connect notes when the relationship is useful. A link might show that one note:
- Supports another idea
- Offers a counterexample
- Defines a term
- Applies a principle
- Extends an earlier observation
- Comes from a different type of source
The link matters more when you explain why it exists. For example:
Related note: Rough notes are an inbox, not a research library. Relationship: This note explains what happens after capture.
Tags can help with broad retrieval. Use one when it answers a question you are likely to ask later, such as "Which notes relate to decision making?" Avoid creating a tag for every possible category. A large taxonomy can become a filing project of its own.
A small, useful note might look like this:
Title: Review turns captured material into reusable research
A saved passage is a reminder. Reviewing it, rewriting it, and connecting it to an existing question turns it into material I can use.
Related notes:
~ Rough notes are an inbox, not a research library.
~ Source context makes notes safer to reuse.
~ Published work tests whether research became useful.
The relationship between notes is often more useful than an elaborate folder hierarchy. You should be able to tell why two ideas belong together.
5. Review the connections, not just the notes
The method becomes useful when you return to ideas and notice how they support, complicate, or contradict one another. You do not need to reread your entire library every week. Start with notes related to a question or project you are working on now.
A lightweight review rhythm could include a short session for processing quick captures, a weekly look at older notes, and a review of connected material before drafting. Those are options, not rules. A project-based review may suit you better than a daily one.
When a new source conflicts with an older note, keep the earlier note and record the disagreement. Add the new source and explain what changed. That gives you a clearer trail when you later write about the subject.
Review and linking create maintenance work, too. In a Hacker News discussion about personal knowledge management, some participants describe tags and folders as difficult to remember or retrieve from. In a Reddit discussion about bookmark organization, one participant describes a related problem: as a collection grows, finding an old item can become harder than saving it.
These are bounded examples, not a survey of note-takers. They point to a useful test: if maintaining a note takes longer than understanding or using the idea, simplify the note. A note system should leave time for reading and thinking.
6. Turn connected notes into published work
The method earns its place when it helps you make something. That might be an article, research memo, product decision, presentation, lesson plan, or experiment.
Begin with a question rather than a broad topic. "What makes a note reusable?" gives you something to investigate. "Zettelkasten" gives you a label, but not a task.
When you start a project:
- Write the question the project needs to answer.
- Search or browse notes that address it.
- Open the original sources behind the strongest notes.
- Group ideas that support the same section or decision.
- Put conflicting and qualifying notes beside them.
- Build a rough outline from those groups.
- Verify important claims against the original sources.
- Draft, then remove material that does not serve the project.
For an article about taking notes, connected notes might produce a working outline like this:
- Capture preserves possibilities, but it does not create understanding.
- Source links make later checking possible.
- One idea per note makes reuse easier.
- Connections matter when they explain a relationship.
- Review creates value and maintenance cost.
- A real writing or decision-making task tests the system.
The same approach works across source types. You might connect a book's explanation, a podcast guest's example, a research paper's qualification, and your own observation. Check whether the sources agree, describe different cases, or place limits on one another.
Before publishing, return to the original article, video, book, or paper for important claims. A note helps you think. It does not replace checking the source.
If your research spans videos, articles, PDFs, discussions, and notes, Reentry is built for active contextual recall. You can save a source while keeping its original material, transcript or extracted content, notes, surrounding context, and relationships connected. Reentry can automatically enrich saved material and resurface the whole item or a relevant fragment through search, the agent, Feed, Tutor, courses, or related context when it becomes useful. That means you can work from the relevant material without immediately replaying or rereading everything. Reentry does not decide which idea belongs in your Zettelkasten or replace source checking.
Which app should you use for a Zettelkasten?
Use the simplest tool that supports the process you will actually follow. At minimum, you need quick capture, readable notes, source links or citations, search, and a way to review related material.
Collins says he uses Day One because it fits his journaling workflow. In the video, he also discusses Roam Research, Readwise, Obsidian, Evernote, Bear, Notion, and book-summary services. These are examples from his workflow, not proof that one of them is right for you or that their current features match his descriptions.
A plain-text folder can work if you can search it and link between files. A notebook can work if you review and reuse the pages. A dedicated knowledge tool can work if its features reduce friction instead of giving you another system to configure.
Before switching tools, ask:
- Can I capture an idea quickly?
- Can I keep the original source beside the note?
- Can I find notes by title or text?
- Can I connect related ideas without a complicated setup?
- Can I export or move the notes later?
- Will I review the system, or will I only keep adding to it?
If you are comparing a flexible local note system with a research workspace, see our comparison of Reentry and Obsidian. The tool comparison is separate from the method itself. No app can supply the understanding and judgment that make a note useful.
Common mistakes that make the method harder
Turning every capture into a permanent note
A saved highlight is not automatically worth processing. Let the inbox hold rough material, then promote the ideas that remain useful after review.
Copying instead of thinking
A long quotation preserves information, but it does not show whether you understand it. Summarize the idea in your own words and keep the quotation when exact wording matters.
Writing notes that are too broad
If a note contains several independent claims, split it. Smaller notes can support more than one project without dragging unrelated material along.
Adding links and tags without a reason
A connection should explain a relationship. A tag should answer a retrieval question. If you cannot explain why you added one, leave it out.
Losing the original source
Keep the article, video, book, paper, or conversation attached to the idea. Source context helps you verify the claim and remember its limits.
Building the system instead of using it
The method becomes a second job when renaming, reorganizing, and decorating notes takes more time than reading, thinking, or writing. Change the system when a recurring problem appears, not because a new template looks appealing.
Our article on digital hoarding and saved content looks at the broader problem of collecting useful material without returning to it. This guide stays narrower: how to turn a source into notes you can use.
Assuming review has to be exhaustive
You do not need to reread everything. Review notes connected to an active question or project. If an old note never becomes relevant, it may not need more maintenance.
FAQ
What is the difference between a rough note and a permanent Zettelkasten note?
A rough note is a quick capture that preserves an idea and its source. A permanent or usable note has been reviewed, rewritten in your own words, given a useful title, and made understandable without immediately replaying or rereading the source. Rough notes can be incomplete. Usable notes should make sense to your future self.
How many ideas should go into one Zettelkasten note?
Usually, one main idea. The test is not word count. If a paragraph contains two claims that could support different projects or connect to different notes, split it. If several sentences explain one claim, keep them together.
How often should you review and connect your notes?
Use a schedule you can maintain, such as a short daily processing session, a weekly review, or a review when you begin a project. The goal is not to process everything. It is to return often enough that useful notes are available when you need them.
Can you use the Zettelkasten method for YouTube videos, podcasts, and articles?
Yes. Capture the title, link, and idea that caught your attention. Add a timestamp for a video or podcast when it helps, then rewrite the idea during review. For an article, preserve the URL and author information. The source type changes the citation details, not the basic workflow.
Do you need Obsidian, Notion, or a dedicated app?
No. You need quick capture, readable notes, source links, search, and a way to review connections. A dedicated app may make linking or searching easier, but the method does not depend on a particular product.
How does a Zettelkasten help turn research notes into an article?
It gives you smaller, reusable ideas instead of one large document full of highlights. When you start with an article question, you can gather related notes, compare supporting and conflicting sources, build an outline, and verify important claims against their originals before drafting.
Private beta