You can manage tasks in Obsidian with almost no plugins, and for a lot of people that is the right call, because the native checkbox plus a little discipline handles more than the plugin-heavy tutorials admit. Obsidian recognises a Markdown checkbox out of the box, so you can write, tick, and search tasks across your whole vault without installing anything. The limits are real, no due-date logic, no recurrence, no automatic today view, but if your task life is modest, a plain-text system you fully understand beats an elaborate one you stop maintaining. This shows how far native tasks go, the one lightweight plugin worth adding, and the point where a deciding layer earns its place.
The appeal of a minimal setup is not laziness. Every plugin is a thing that can break, need configuration, or quietly change how your tasks behave. Starting from the native experience and adding only what you feel the lack of is how you end up with a system you actually keep.
What native Obsidian tasks can do
Out of the box, a task is a checkbox: type - [ ] call the dentist and Obsidian renders it as a tickable box in reading view. You can nest them, mark them done, and use Obsidian’s built-in search to find every open checkbox in the vault. The newer Bases feature lets you build simple table views from note properties, which covers light project tracking. For a person with a handful of active tasks a day, this is genuinely enough: write tasks where the work is, and scan your daily note to see them.
What native tasks give you is the two things that matter most, capture and context. The task sits in the note about the thing it concerns, so you never lose the connection between the to-do and the material. No plugin is required for that, and it is the single biggest advantage of managing tasks in a vault at all.
What native tasks cannot do
The gaps are specific, and knowing them tells you exactly when to add something. Native checkboxes have no concept of a due date, so Obsidian cannot show you what is due today. They have no priority, no recurrence, and no way to gather tasks from across the vault into a single sorted list beyond a raw text search. And there is no notification; nothing reminds you.
| Capability | Native Obsidian | Needs a plugin |
|---|---|---|
| Write and tick a task | yes | no |
| Search open tasks across the vault | yes, basic | no |
| Due dates and a today view | no | yes (Tasks plugin) |
| Recurrence and priority | no | yes (Tasks plugin) |
| Decide which task matters most | no | a ranking layer |
Read that table by your own needs. If you never assign due dates and rarely have more tasks than you can see at a glance, the native experience covers you and any plugin is overhead. The moment you find yourself wanting “show me what is due today”, you have hit the first real limit.
The one plugin worth adding
If you outgrow native tasks, the single most valuable addition is the Tasks plugin, and for most people it is the only task plugin they will ever need. It adds due, scheduled and start dates, recurrence, six priority levels, and a query language that gathers matching tasks into a live list. One query, tasks due today or overdue, gives you the today view native Obsidian lacks. That is the whole upgrade, and it is enough for a long time.
Resist adding more than that. The failure pattern is installing five task plugins and a tag taxonomy before you have enough tasks to justify any of it. A single plugin plus one query is a system you maintain; a wall of plugins is a system you abandon. The full landscape, if you do want to compare options, is in Obsidian task management, and if you are coming from a standalone app, replacing your external task manager with Obsidian walks through the switch.
A minimal system that works
Here is a complete setup that uses at most one plugin. Keep a daily note, and capture tasks in it as plain checkboxes as they arise, or write them in the relevant project note when they belong to a project. Once a week, glance over your project notes and pull anything urgent into focus. If you never touch due dates, that is the whole system, native and plugin-free. If you want a today view, add the Tasks plugin and one due-today query in your daily note, and stop there.
The discipline that makes a minimal system work is a regular, light review rather than elaborate tooling. A two-minute daily glance to see what is open, plus a slightly longer weekly pass to clear what is done, keeps a plain-text task list from silently rotting. That habit, not a plugin, is what most people are actually missing, and it is worth building before adding any machinery.
Here is the progression, so you add each piece only when you feel its absence rather than up front.
| Add this | When you feel | Effort |
|---|---|---|
| Native checkboxes plus a weekly review | you just need to track a modest list | none |
| The Tasks plugin and one today query | you want to see what is due today | low, one plugin |
| A ranking layer | your today list is too long to rank by eye | low, reads what you have |
| Anything else | a specific, named gap the above do not fill | only then |
The rule the table encodes is simple: never add a layer speculatively. Each row solves one felt problem, and most people stop at the first or second.
Why less tooling often works better
There is a counterintuitive reason a minimal setup frequently outperforms an elaborate one, and it is worth stating because it changes how you shop for plugins. Every plugin and every query is a small ongoing tax: something to keep configured, to understand when it misbehaves, and to migrate when it breaks or is abandoned. A system made of one plugin and one query has almost no tax; a system made of a dozen has a large one, and the tax is paid in exactly the moments you are busiest, which is when you quietly stop maintaining it and the whole thing rots. The elaborate setups that look impressive in a screenshot are often the ones their owners abandoned a month later, precisely because the upkeep outran the benefit.
Minimalism also keeps your data legible. A task that is just a checkbox in a note is readable by any editor, portable forever, and understandable at a glance; a task buried in five plugins’ worth of metadata and custom fields is tied to that exact configuration. For a plain-text tool whose whole appeal is ownership and longevity, the fewer moving parts between you and your tasks, the more of that appeal you actually keep.
When even the minimal setup is not enough
There is a clear point where native tasks and a single query stop being sufficient, and it is worth naming so you do not blame yourself for it. As your vault grows, your today list starts returning more tasks than you can rank by eye, and the morning shifts from reading a short list to re-deciding a long one. Native tasks and even a Tasks query only present the list; neither decides which of the surfaced tasks matters most given everything around it. That deciding step is a separate job, and it is where a ranking layer like ZPXE fits: it reads the tasks you already wrote and ranks today’s priorities on-device, with a visible reason for each, so a large plain-text task list becomes a short ordered one. The argument for making that step explicit rather than doing it by eye is in why your task app should explain itself, and the attention cost of not doing it is real; task switching can consume up to 40% of productive time.
Key takeaways: managing tasks without complex plugins
Start with native Obsidian checkboxes, because for a modest task load a plain-text system you fully understand beats an elaborate one you abandon, and it keeps every task next to the note that gives it meaning. Add exactly one plugin, Tasks, only when you want due dates and a today view, and add one query rather than a wall of them. Lean on a light daily and weekly review, which is what most minimal setups are actually missing, not more tooling. And recognise the ceiling: when your today list outgrows what you can rank by eye, add a deciding layer to turn the long list into a short one. Keep it simple, and add each piece only when you feel its absence.
Quick answers
Can you manage tasks in Obsidian without a plugin?
Yes. Obsidian recognises Markdown checkboxes natively, so you can write, tick and search tasks across your whole vault with nothing installed, and its Bases feature adds simple table views. For a modest task load this is genuinely enough, and it keeps each task beside the note it concerns. The limits are no due dates, no recurrence and no today view; when you want those, one plugin covers them, but many people never need to go further than native checkboxes and a weekly review.
What is the simplest task setup in Obsidian?
Capture tasks as plain checkboxes in your daily note or the relevant project note, and do a short weekly review to clear what is done and surface what is urgent. That is a complete, plugin-free system for a modest load. If you want a today view, add only the Tasks plugin and a single due-today query, and stop there. The discipline of a light regular review, not extra tooling, is what actually keeps a minimal task list working over time.
When do you actually need a task plugin?
The moment you want to answer “what is due today” automatically, because native checkboxes have no date logic. That is the first real limit, and the Tasks plugin closes it with due dates, recurrence, priority and a query language. You need more than that only when your today list grows too long to rank by eye, at which point a deciding layer helps. Until you feel one of those specific gaps, native tasks plus a weekly review are enough, and adding plugins early is overhead.
Is the Tasks plugin complex to set up?
Not really, and it is the least complex way to add real task features. You install it, optionally set a global filter so only tagged lines count as tasks, and write one query that shows tasks due today. Its create-or-edit command writes the date and priority syntax for you, so you never memorise it. The complexity people fear comes from stacking many plugins and elaborate queries, not from Tasks itself; used minimally, it is a gentle addition to a native setup.
When is a minimal Obsidian task setup not enough?
When your vault grows to the point that even a today query returns more tasks than you can meaningfully rank by eye. At that scale the list is complete but undifferentiated, and choosing a starting point becomes the daily friction. Native tasks and a plugin both present tasks without deciding among them, so the gap is ranking, not features. That is when a deciding layer that weighs context and shows its reasons earns its place on top of the simple setup you already have.
