Picking a personal knowledge management app is not really a feature decision. It is a decision about where five years of notes, links and files will sit, and how painful it will be to move them the day the app raises its price, changes its editor, or stops being maintained. Almost every roundup answers the first question; this one answers the second, so the criteria below are weighted for the long game: what it costs today, what you can get back out, and what silently fails to survive the trip.
The four things that actually matter
Can you take everything out, in a format something else reads? Notes are the easy part. Attachments, tags, links between notes and creation dates are where exports get thin.
Is capture fast enough to use while standing up? A store you only feed at a desk fills with the wrong half of your life. Share sheets, hotkeys and a capture bar are the difference.
Does search cover everything, or only text? Most people search for the container — the project, the trip, the client — and expect the PDF back alongside the note. Apps that index only note bodies quietly fail that.
Does the material live next to the work? A note about the plumber is nearly useless in a general archive and very useful inside the flat-renovation project. Roundups skip this one because it crosses the line between notes apps and task apps.
Feature counts are off that list on purpose. Every serious app here can nest, tag and sync. They differ on exit, on capture speed, and on how far they sit from the work.
What each one costs, and what you can take back out
Prices checked at the time of writing, from each vendor's own page, with the billing basis named against each one — yearly and monthly are about a fifth apart at both Obsidian and Notion, which is enough to change a shortlist.
| app | what it costs | how the material gets out | the catch |
|---|---|---|---|
| Obsidian | free for personal use, no sign-up; Sync is $4 per user a month billed annually, $5 billed monthly | nothing to export — your notes are already Markdown files in a folder you chose | plugin-specific syntax reads as plain text elsewhere; sync and publish are the paid parts |
| Logseq | free, and open source | Markdown files on disk, same as Obsidian | it is outline-first, so block references flatten into ordinary text in a normal editor |
| Notion | free personal tier; Plus is $12 per member a month billed monthly, or $120 a year — $10 a month — billed yearly | Markdown and CSV, HTML, or PDF | a database exports as one view only, form views cannot be exported, and the free tier caps uploads at 5 MB per file |
| Evernote | free tier, then paid plans whose prices are not shown until checkout | ENEX, HTML or PDF; ENEX is the one that carries tags and attachments with it | the free tier is capped at 50 notes, 1 notebook and 1 syncing device, so it stops being a store long before it stops being an app |
Two of those rows deserve reading twice. Obsidian's pricing page is unusually blunt — "Free without limits. No sign-up required." — because the app is a reader over local files, which makes the export question moot. No amount of export tooling elsewhere matches that.
And Evernote's plan comparison lists the free tier at 50 notes, one notebook, 20 tags and a single synced device. If the plan was to trial it properly before paying, the trial ends at note fifty-one.
Where each one genuinely wins
Obsidian wins on ownership. Local Markdown files mean no vendor can strand your material, and the plugin ecosystem covers workflows nothing else touches. If you would rather own files than rent an account, stop reading roundups and use it.
Logseq wins for outline thinkers. If you write in nested bullets and think in daily notes, its structure fits how you already work, and it is open source on top of that.
Notion wins on flexibility. Databases, views and templates let you build a small internal tool rather than a note pile, and the interface explains itself.
Evernote wins on capture breadth. Web clipping and document handling have had a long time to mature, and ENEX is a genuinely complete archive format — attachments and tags included — which is more than most exports manage.
None of the four is a task app, and that is the gap in this category. They organise what you know. They do not hold what you owe, so dates, next actions and deadlines end up somewhere else.
The switching cost nobody prices
Say you leave Notion after three years. The export hands you Markdown files and CSVs. What arrives is not what you had: databases become spreadsheets, relations between them become text, and the views you built your day around do not exist in the destination. Nothing was lost, exactly. It just stopped working.
That is the shape of most migrations. The material survives and the structure does not, and structure was what you were paying for. Budget a weekend rather than an afternoon, and expect to rebuild.
One thing has genuinely changed. An export that used to be an unusable pile of files is now something you can hand to an AI assistant along with a description of the structure you want back. That does not make lock-in free, but it moves it from a wall to a cost.
When init.Tasks is the wrong answer
Be clear about this, because a roundup that never says it is not worth trusting.
If you write long-form and want a note graph with backlinks, use Obsidian. If you need public-facing pages or a database with several views, use Notion. If your material is thousands of clipped web pages, Evernote's clipper still has no equal. And if a documented export is your first criterion today, init.Tasks is in private beta — so wait and ask again at release rather than trust a promise.
init.Tasks is the right answer when your knowledge is mostly attached to things you are doing — buying a flat, changing jobs, running a course, selling a car — rather than to subjects you study.
Where init.Tasks fits
In init.Tasks what you know and what you owe sit in the same tree, on iOS, macOS and web, behind a terminal-styled interface — so there is no second product to keep in step. A pasted link fetches its own title on the way in, so the inbox reads as sentences rather than as addresses.
Measured against the criteria at the top: one search runs over the whole store at once, and material is filed into the project it serves rather than into a general archive. Start date and deadline are separate fields, which sounds like a scheduling detail until reference material starts wearing fake due dates to stay visible — start date vs deadline covers how that happens. Exit is the criterion it cannot answer yet, and the section above says so plainly.
The AI connection is coming in september. Access starts read-only, and a connection can be pulled without you touching your password. The beta waitlist is open, and everything is free while in beta.
For the wider question of what belongs in a store like this, what is a second brain is the primer, second brain apps is the shortlist by capability rather than by exit cost, and the app for GTD piece handles the task-method half.
FAQ
What is a personal knowledge management app?
A personal knowledge management app is a single store for the notes, links, files and ideas you want to be able to find again — organised so that retrieval works months later, not just filing today. The category covers note graphs like Obsidian, workspace tools like Notion, and archives like Evernote. What separates them in practice is capture speed, search coverage, and how hard it is to leave.
Which personal knowledge management app is best for one person?
For a single person, Obsidian is the safest default: the files stay on your own disk and cost nothing for personal use. Choose Notion instead if you want databases and views, or Evernote if your material is mostly clipped web pages. If what you save is attached to active projects rather than to subjects, a task app that stores material fits better than any of the three.
Can I move my notes between these apps later?
Partly. Notes and text move well. Attachments, tags, internal links and the structure you built are what degrade — Notion databases arrive as CSVs, Evernote's ENEX only reads back into apps that speak it, and Markdown tools drop each other's syntax. Plan for a rebuild, and check the export format before you commit.
Do I need both a task app and a knowledge app?
Many people run both and pay a reconciliation cost every week. One app covering both is simpler when your material is tied to projects. Two apps is better when your knowledge base is genuinely a library — research, writing, study — with a life independent of any task list.