Obsidian does not have built-in task management in the way a dedicated app does. Out of the box it recognises a Markdown checkbox, - [ ] buy milk, and can toggle it done, and that is close to the whole of it. There is no native concept of a due date, a priority, a recurring task, or a “today” view. Everything past a flat, manually maintained list comes from community plugins. That sounds like a gap, and for some people it is, but it is a deliberate design choice with real consequences worth understanding before you decide whether Obsidian is the right home for your tasks.
The short version: Obsidian gives you the raw material for tasks and expects you to assemble the system. Whether that is freedom or friction depends entirely on how much task machinery you want and how willing you are to install and wire it yourself.
What Obsidian can do with tasks natively
The core app treats a task as what it literally is: a line of Markdown with a checkbox. You can type - [ ] anywhere, click to toggle it between open and done, and it renders as a checkbox in reading view. Obsidian’s search can find open checkboxes across the vault, and the newer Bases feature can build table views from note properties. That is genuinely useful for light needs, and for a small vault it may be all you ever want.
What it cannot do natively is anything that depends on understanding a task as more than text. It does not parse a due date, so it cannot show you what is due today. It has no priority field, no recurrence, no notion of a task being blocked or scheduled or waiting. It will not roll an unfinished task forward to tomorrow. None of that is a bug; the core simply stops at “a checkbox is a checkbox.” Everything richer is left to plugins on purpose, which is the same philosophy that governs the rest of Obsidian.
To make the boundary concrete, here is what belongs to the core, what a query plugin adds, and what still is not solved even with plugins installed.
| Capability | Native Obsidian | With Tasks / Dataview | Still unsolved |
|---|---|---|---|
| Toggle a checkbox done | Yes | Yes | |
| Search open tasks across the vault | Yes, basic | Yes, filtered and grouped | |
| Due dates, scheduled, recurrence | No | Yes (Tasks) | |
| Priority levels | No | Yes, six levels you set | |
| A live “today” list | No | Yes, via a query | |
| Decide which surfaced task matters most | No | No | ranking, a separate job |
The last row is the one people miss when they ask whether Obsidian does tasks: even a fully plugged-in setup presents tasks without deciding among them.
Why Obsidian leaves task management to plugins
This is a design decision, not an oversight, and it follows from what Obsidian is trying to be. Obsidian’s core is a fast, local, plain-Markdown editor over files you own, and its extensibility comes from a large community plugin ecosystem rather than a big bundled feature set. Keeping tasks out of the core keeps the core small and keeps your files portable: a task is just text, readable in any editor, with no proprietary task format locking you in.
The trade-off is that you become the integrator. Two people can both say “I manage tasks in Obsidian” and mean completely different systems, one running the Tasks plugin with dated queries, another using Dataview dashboards, a third keeping bare checkboxes in daily notes. That flexibility is the whole appeal for tinkerers and a real source of friction for people who just want a task manager that works on install. Knowing which camp you are in is most of the decision.
The plugins that add real task management
Three or four plugins do the work the core leaves undone, and they solve different parts of the problem. The full landscape is laid out in the Obsidian task management guide; here is the short map.
The Tasks plugin is what most people mean when they say Obsidian handles tasks. It adds due, scheduled and start dates, recurrence, six priority levels, and a query language, so you can write a block that shows every task due today across the vault. Dataview goes wider, querying any structured data in your notes to build custom dashboards, though the Tasks documentation is clear that it does not understand recurring tasks. TaskNotes takes the opposite approach of making each task its own note. Between them, these cover capture, dating and presentation thoroughly, and the Obsidian forum is full of people combining them.
What none of them do is decide. Even a perfectly configured Tasks query gives you an ordered list, not a judgement about which of the listed tasks actually matters most right now, since a sort by priority orders by one field and cannot weigh context. That deciding step is a genuinely separate job, and it is the one people are often surprised to still be doing by hand after installing three task plugins. It matters because that manual decision is where attention leaks: the American Psychological Association notes that the mental cost of switching between tasks can reach 40% of productive time, and re-reading an undifferentiated list every morning to choose a starting point is exactly that switching, paid before work begins. If that is the part you care about, the best Obsidian task management plugin works through which tool owns which job, including the ranking layer that fills that last gap.
So should you manage tasks in Obsidian at all?
The honest answer depends on where your tasks belong. If your tasks are entangled with your notes, project work, research, anything where the task and its context live together, then keeping them in the vault is a real advantage, because the task sits next to the material that gives it meaning, and no context-switch to a separate app is needed. Obsidian, plus the Tasks plugin, plus a deciding layer when the vault gets large, is a strong system for exactly that reader.
If your tasks are mostly standalone, quick captures, errands, shared lists, phone-first reminders, then a dedicated task manager built for that will beat any Obsidian setup, and trying to force the vault into that role is effort spent fighting the tool. Obsidian’s task story is best when tasks and notes are the same body of work. It is weakest as a general-purpose to-do app with a polished mobile inbox, and being clear-eyed about which you need saves a lot of wasted configuration.
| If your tasks are | Obsidian fit | Better served by |
|---|---|---|
| Tied to notes, projects, research | strong | Obsidian plus the Tasks plugin |
| A large self-directed backlog | strong with a deciding layer | Obsidian plus Tasks plus ZPXE |
| Quick standalone errands | weak | a dedicated task app |
| Shared lists, phone-first capture | weak | a mobile-first task manager |
The mobile reality, since it decides a lot of this
One factor settles the “is Obsidian good for tasks” question for more people than any feature comparison: how you capture and check tasks on your phone. Obsidian mobile runs the same plugins as the desktop, so a Tasks query works there too, but it is the same document-first interface, not a quick-capture task inbox. There is no home-screen widget that adds a task in two taps, no share-sheet flow tuned for firing off a reminder, no shared list a partner can edit. For someone whose task life is mostly captured on the go, that friction is the deciding factor, and no plugin removes it, because it is a consequence of Obsidian being a notes app first.
If, on the other hand, you mostly work at a desk, review tasks alongside the notes they belong to, and treat your phone as a read-only glance, then the mobile limitation barely registers and the vault’s advantages dominate. This is why two people can reach opposite conclusions about the same setup: they are describing different task lives, not different plugins. Be honest about yours before you invest a weekend in configuration.
How to start without over-building
If you do want tasks in Obsidian, resist the urge to install everything at once. Start with bare checkboxes in your daily notes for a week and see whether the native experience is already enough; for many people with light needs, it is. When you outgrow that, add the Tasks plugin and a single “due today or overdue” query, and stop there until you feel a specific need it does not meet. Add Dataview only for dashboards, and keep completion inside Tasks so recurrence survives. Reach for a ranking layer only when the problem has clearly shifted from writing tasks to deciding among them. Building the system one felt need at a time is how you end up with a setup you maintain, rather than an elaborate one you abandon.
Key takeaways: does Obsidian do task management?
Obsidian does not manage tasks natively beyond toggling a Markdown checkbox; it has no dates, priorities, recurrence or today view, and leaves all of that to community plugins on purpose. That makes it endlessly flexible and a real project for anyone who wants a working system out of the box. Add the Tasks plugin for dates and queries, Dataview for dashboards, and a deciding layer when a large vault makes “what do I start” the real question. And be honest about fit: Obsidian is excellent for tasks that live beside your notes and a poor choice for standalone, phone-first to-dos. The core gives you the pieces. Whether that is a feature or a chore is the actual decision.
Quick answers
Does Obsidian have built-in task management?
No. Natively, Obsidian only recognises a Markdown checkbox and lets you toggle it done. It has no concept of due dates, priorities, recurrence or a today view. All real task management comes from community plugins such as Tasks, Dataview and TaskNotes. This is a deliberate design choice: the core stays small and your files stay portable plain text, at the cost of you assembling the task system yourself from plugins.
What plugin do I need for tasks in Obsidian?
The Tasks plugin is the standard choice and the right first install. It adds due, scheduled and start dates, recurrence, six priority levels and a query language, so you can show every task due today across the vault. Add Dataview if you want custom dashboards, though it does not handle recurring tasks well, and a ranking layer if your problem is deciding among tasks rather than writing them. Start with Tasks alone and add more only when you feel a real gap.
Is Obsidian good for task management?
It is good when your tasks live beside your notes, project work, research, anything where task and context belong together, because keeping them in the vault avoids a context switch to a separate app. It is a poor fit for standalone, phone-first to-do lists with shared items and a polished mobile inbox, where a dedicated task manager wins easily. The right question is not whether Obsidian is good at tasks in general, but whether your tasks belong next to your notes.
Can Obsidian replace my to-do app?
Sometimes, but not always, and it depends on the tasks. If your to-dos are tied to notes and projects you already keep in Obsidian, then the Tasks plugin can genuinely replace a separate app and keep everything in one place. If your to-dos are quick standalone captures and shared lists you manage mostly on your phone, a dedicated app will serve you better, and running both, notes in Obsidian, errands in a task app, is a perfectly reasonable setup rather than a failure.
Does Obsidian have a today view for tasks?
Not natively, but you can build one with the Tasks plugin by writing a query that shows tasks due on or before today, grouped and sorted however you like. That gives you a live today list. What a query cannot do is rank the surfaced tasks by which actually matters most, since it sorts by a single field; for that you need a deciding layer on top, which weighs due dates, priority, recent activity and link context into one ordered list.
