Most personal knowledge management posts spend 400 words defining PKM and then recommend one app. If you are reading this, you already know what PKM is. You want to know which tools do which job, and where the seams between them are.
Short version before the walkthrough. A working PKM setup is two layers, not one. A capture layer that catches things from everywhere you actually find them, and a notes layer where your own thinking lives. Most people try to run both on one tool and it falls apart around month six.
I have rebuilt this system three times. The splits below are what stuck.
Why one app never does both jobs well
Capture is a firehose problem. X posts, articles, YouTube videos, newsletters, a screenshot from your phone, a paragraph from a PDF. It needs to be fast, ambient, and work on every device you use without thinking.
Notes are the opposite. Slow, considered, linked, written in your own words. The thing you sit down to.
The tools that are great at one are usually bad at the other. Obsidian is a beautiful notes tool with an awful capture story on mobile. Readwise Reader has great capture for articles and highlights but you would not write a book outline in it. Notion can do both in theory and neither well in practice, because a fast capture inbox sits uneasily next to the rest of Notion's database machinery.
So the durable shape is: pick one tool for capture, pick one tool for notes, let them do their jobs, and accept that two tools is the floor.
Split the stack into capture and notes
Here is what that stack looks like in practice.
- Capture layer. Every save from anywhere lands here. Articles, X bookmarks, newsletters, YouTube, PDFs, quick thoughts. Full text stored where possible so a deleted source does not cost you the save. Search across everything.
- Notes layer. Your writing. Permanent notes, project outlines, meeting notes, book notes, the stuff you actually make. Linked however your chosen tool likes to link.
- The bridge. You pull from capture into notes when you are actually using something. Not on capture. Not on a schedule. At the moment you sit down to write, plan, or think about a topic.
The bridge is the bit that most PKM advice skips. People describe how they save and how they write but leave a three-step gap in the middle where nothing explains how the saved thing becomes part of the note. I will come back to that.
How the main tools actually stack up
There are maybe six serious choices for the notes layer and four for the capture layer. Here is honest placement, by where the tool is genuinely strongest.
Notes layer
Obsidian. The strongest notes tool in the category for people who want their knowledge to compound. Local markdown files, backlinks, graph view, a plugin ecosystem that is closer to an IDE than a note app. The cost is learning curve and vault discipline. Without a clear structure your vault sprawls faster than anything else on this list. If you want your future self to find a thread you pulled in 2024, Obsidian is the best pick.
Notion. The most structured of the notes tools. Databases, relations, views, and templates. Best when your notes overlap heavily with work you are coordinating with other people. The trade-off is speed (it is the slowest on this list) and portability (getting your content out cleanly is still a pain). Good for team knowledge bases, less good for pure personal PKM.
Logseq. Outliner-first. Blocks instead of pages, daily notes as the main surface, local-first markdown. The right pick if you think in bullets and like the daily-journal workflow. Smaller ecosystem than Obsidian, faster to get started with.
Apple Notes. Underrated. Fastest capture on any Apple device, sync that just works, search that is fine. No backlinks, no graph, no programmatic access worth talking about. The right pick for people whose PKM ambition is "find the thing I wrote down" and nothing more. Do not force yourself to run Obsidian if this is actually all you need.
If you already own the notes problem with one of these, do not switch. The cost of migration is larger than the benefit for almost everyone.
Capture layer
Readwise Reader. The strongest capture-plus-read tool if highlights are your format. You read the full article inside Reader, highlight as you go, and the highlights sync to Readwise and into any notes tool via the daily review. Currently $9.99/month billed annually or $12.99/month billed monthly on Readwise's pricing page. If your PKM is built on "here is the quote that got me", start here.
Keep. Where I save. Keep indexes every word of every article, X post, newsletter, and YouTube transcript you save, and the whole library exports to Markdown, CSV, or JSON. No graph, no daily-review UI, no in-article highlighting (you save the whole source and pull passages back later by search or an LLM query against the full text). Keep is the capture layer in this stack, not the notes layer. It does not replace Obsidian and it is not trying to. It sits alongside whatever notes tool you already like and feeds it. Readwise wins if your format is passage-level highlights. Obsidian and Notion are notes tools, not capture tools. Keep wins if you save a lot from many places and want the whole library searchable and portable.
Raindrop. Bookmark-first. Great for link libraries with tags and collections. Light on content storage (it is the URL and a preview, not the full article by default), which is fine if your workflow is mostly "find the link again later".
Apple Notes / your browser's default. Viable for very small volumes. Stops scaling somewhere around the hundredth save.
A quick note on category confusion. Search results for "best knowledge management tools" fold enterprise KM platforms (ServiceNow, Confluence, SharePoint) into the same list as personal tools like Obsidian and Readwise. Those are different products for different problems. Enterprise KM is about organizing shared knowledge for a company. Personal knowledge management is about you, your reading, and your own thinking. This post is about the second one. If you landed here looking for the first, the search engine has failed you.
Which stack actually fits which person
This is not a ranked list. It is four shapes that work, depending on who you are.
- The writer who reads a lot. Readwise Reader for capture plus highlights, Obsidian for permanent notes. Highlights sync from Reader into Obsidian via the Readwise plugin. Simple, mature, expensive (the Readwise subscription is real money).
- The builder who saves from everywhere. Keep for capture across X, articles, newsletters, and YouTube, Obsidian for notes. Keep's export is markdown, which drops into an Obsidian vault in one step when you want to promote something. This is my stack.
- The team operator. Notion for both layers, reluctantly. It is not the best at either job, but if your team already runs in Notion, the cost of a second tool is higher than the cost of a slower capture flow.
- The minimalist on Apple hardware. Apple Notes for everything, one folder per durable topic, search as the primary navigation. No graph, no highlights, no backlinks. Not glamorous. Works for people whose PKM ambition is modest and honest.
If you are not any of those, do not invent a fifth stack. Pick the closest and adapt.
Process: the loops that keep the stack alive
A PKM stack without running loops is a graveyard. Three loops matter, and they are not complicated.
Weekly review. Fifteen minutes. Open your capture tool, filter to the last seven days, skim. Anything that survived the first skim and is actually worth reading: tag it or move it to a read-next shortlist. Everything else can stay in the capture pile indefinitely because full-text search will find it when you need it.
Just-in-time promotion. When you sit down to write, plan, or prep for a meeting, search your capture library for the topic. Pull the three or four sources that are actually relevant into your notes tool as you work. Do not try to promote things ahead of time. You will guess wrong about what future-you needs.
Monthly topic pass. Once a month, pick one durable topic you care about, open everything tagged or matching that topic in your capture library, and reread. Move anything that earned a second read into a permanent note. This is where the compound interest actually lives. If you only do one of these three loops, do this one.
I have tried longer processes (the weekly PARA audit, the daily zettel goal, the Friday review that turns into three hours). They all collapsed within two months. These three survived because they cost almost nothing on any given day.
Benefits that hold up, and ones that do not
PKM evangelists oversell this part of the pitch badly. Here is what I have actually seen from running a system like this for years.
Hold up. You stop losing sources. You can find a passage from something you read eighteen months ago in under a minute. Your writing improves because you are reading the same topics more than once. You think more clearly about things you have revisited three times.
Do not hold up. "Second brain" framing. Your PKM does not think for you and it is not a backup of your mind. It is a library with search. Calling it a brain is a marketing line that has been worn smooth and now obscures what the thing actually does. It is a shelf. You still do the reading and the thinking.
If you want a longer piece on the reading-and-thinking habit that sits inside a PKM setup, the digital commonplace book guide is the companion read.
Where LLMs actually fit in a PKM setup
Every third PKM post right now is "ask AI to take notes for you". Most of that is magical thinking.
What does work, and what I use every week, is querying your capture library with a local LLM tool. Because Keep stores every save as clean markdown and exposes a CLI, MCP server, and HTTP API, Claude Code, Cursor, or any MCP-compatible client can read your library directly. That makes prompts like these work against your actual saves:
- "Pull three passages I have saved about attention that would fit in a draft about deep work."
- "Summarize everything I have tagged with writing from the last six months."
- "Find that quote I saved from a Paul Graham essay about makers and managers."
Your capture library becomes a dataset, not an archive. That is the point where PKM stops being admin and starts being useful.
Obsidian and Notion can do versions of this with effort, plugins, or custom exports. The difference with Keep is that markdown is the native format, so there is nothing to export or convert before an LLM can read it.
How tags and structure fail (and what to do instead)
Every PKM system eventually hits the same wall. You end up with 400 tags, 90% of which you used exactly once, and a folder tree four levels deep that only today-you can navigate.
What survives past a couple of thousand entries is close to this.
- Eight to twelve durable topics you keep returning to. Not forty. If you cannot name them from memory, there are too many.
- One tag per entry. Two at the most. Tags are for filtering, not for describing the entry.
- Search as the default navigation, tags as a shortcut for the queries you run constantly.
- A flat structure at the top level. Your capture pile does not need folders. Your notes pile needs at most one folder per durable topic plus a daily-notes folder.
People push back on flat structures because a hierarchy feels like organization. In practice a hierarchy you built in 2024 fights you in 2026. Search does not. Let the hierarchy live in your head and your tools do the retrieval.
For a longer take on the curation half of this, the content curation workflow post walks through the save-to-publish pipeline.
Examples of what this looks like day to day
Three days picked off my actual calendar in the last fortnight.
- Tuesday. Saved eleven X posts (a thread about CSS cascade layers, a product-market-fit framework, a Claude prompt that worked for somebody). Sat down Thursday to write about onboarding, searched Keep for "onboarding", found two saved articles I had forgotten and one thread. Pulled quotes into an Obsidian note. Published Friday.
- Saturday. Read three long-form pieces on attention and habit. Highlighted passages I liked (mentally, because Keep does not highlight yet; I pasted the passages into the note). Six weeks later, writing about focus, I searched my notes for "attention" and the three sources were sitting there with my paragraph next to each.
- A Wednesday last month. Cursor plus Keep's MCP, asked "find everything I have saved this year about pricing strategy and list the claims". Got back a list of twelve, with source links. Time from question to useful answer: forty-five seconds.
None of that is a "second brain". All of it is a library with search, and a habit of saving with intent.
Start with two tools, not five
If you do not have a system today, the shortest path is this.
- Pick a notes tool. Obsidian if you want power, Apple Notes if you want speed, Notion if your team already lives there.
- Pick a capture tool. Readwise Reader for highlights, Keep for everything else.
- Connect them loosely, not tightly. When you need something from capture inside your notes, search and paste. Do not build sync pipelines before you have a working habit.
- Run the three loops. Start with the monthly topic pass if you can only do one.
Five or six apps is not a PKM system, it is a yak-shave. Two is enough, and two is what survives.
Keep is where I save everything from X, RSS, newsletters, and articles, and where my PKM capture layer lives. If you want to see what it looks like to have one searchable library under your notes tool, start saving from every source you read. Your X bookmarks and RSS sources sync in under a minute once the account is connected.