“Free Kanban Board Template for Obsidian (Download + Guide)”

` lines as cards, opened in board view by the community Kanban plugin.|The template is four lanes — Backlog, Next, In progress, Done — with WIP limits written into the lane titles, for example `## In progress (3)`.|Turn off Restricted Mode, install the Kanban plugin, then create a board from the command palette or by right-clicking a folder.|Cards support dates (`@` trigger), tags, checklists, and links to full notes created from the card.|The board is single-user by design. Real-time collaboration, permissions, and notifications are the point where a dedicated project tool wins.”]

What is a kanban board template for Obsidian?

A kanban board template for Obsidian is a reusable markdown note whose structure the Kanban plugin renders as columns and draggable cards. The file contains a small YAML frontmatter block, one H2 heading per lane, and task lines using standard markdown checkboxes. Because it is just text, it syncs through any file sync service, diffs cleanly in Git, and remains readable in ten years.

That definition matters more than it sounds. Most kanban tools store your work in a proprietary database; the board is a view of data you cannot open. In Obsidian the board *is* the data. Move a card and you are editing a line of text. Delete the plugin and the file still makes sense.

The trade-off is that nothing is automatic. There is no server enforcing permissions, no assignment notification, and no audit log. You get ownership of your planning data in exchange for maintaining it yourself.

How do you install and enable the plugin?

Install the community Kanban plugin and enable it, then create your first board in under three minutes. Obsidian blocks community plugins by default, so the first step is the one people miss.

1. Open Settings → Community plugins and turn off Restricted Mode (older versions call it Safe Mode). Without this, the plugin browser stays hidden.
2. Click Browse, search for Kanban, and install the plugin by mgmeyers.
3. Click Enable after installation.
4. Create a board with any of three routes: right-click a folder and choose New Kanban board, run Kanban: Create new board from the command palette, or run Kanban: Convert empty note to Kanban to turn an empty file into a board.

One caveat worth knowing before you commit: the plugin is now hosted under the `community-archive` organisation on GitHub and its maintainers have been looking for someone to take it over. It still works and still carries roughly 4,600 GitHub stars, but treat it as mature-but-quietly-maintained rather than actively developed. If long-term maintenance is a hard requirement, keep the raw markdown compatible so a future migration is a copy-paste job rather than a rebuild.

What does the template file look like?

Save this as `Templates/Kanban board.md` in your vault, then duplicate it per project. The file opens with a YAML block containing the single line `kanban-plugin: board` between the usual two fence lines — that line is what makes Obsidian render the note as a board instead of a document. Everything after it is the board itself, and lane titles carry the WIP limit in parentheses, which the plugin reads and displays as a counter.

## Backlog

- [ ] Collect three supplier quotes
- [ ] Draft Q1 content calendar
- [ ] Review analytics for October

## Next (3)

- [ ] Rewrite onboarding email #marketing
- [ ] Book workshop venue @{2026-01-20}

## In progress (2)

- [ ] Landing page copy
- [ ] Pricing page outline

## Done

- [x] Audit existing blog posts

Four details do most of the work:

• `kanban-plugin: board` in the frontmatter tells Obsidian to open the file in board view rather than reading view.
• `## Lane name` creates a lane. Renaming the heading renames the column; order in the file is order on screen.
• `- [ ]` is a card. Checking it marks it complete, and the card stays visible until you archive it.
• `@` opens the date picker when typed inside a card. The plugin converts it to a date in your chosen format, and with the right setting that date links to the matching daily note.

You can also add tags (`#marketing`), bold text, links to other notes, and nested checklists inside a single card. Keep cards to one line where possible; the plugin is a board, not an outliner.

How should you configure the board settings?

The defaults are reasonable, but five settings decide whether the board survives week two. Open Settings → Kanban and set them once. Most apply globally; local settings can override them per board if you prefer different behaviour for a personal and a work vault.

The archive deserves special mention because it confuses new users. Archived cards are not deleted; they are appended to the bottom of the same markdown file inside a collapsible block. You can only see that block in markdown mode: run Kanban: Toggle between Kanban and markdown mode from the command palette. If your board feels heavy after a few months, that block is usually why.

Worked example: a 14-card board with WIP limits

Here is a real setup for a freelance designer rebuilding a portfolio site, planned over three weeks with roughly six hours of work per week.

Lanes: Backlog (no limit), Next (3), In progress (2), Review (1), Done (no limit). Fourteen cards in total. Backlog holds eight, Next holds three, In progress holds two, Review holds one.

Week one: two cards move from Next to In progress, both finish, and one moves on to Review. Throughput for the week is three cards. Week two repeats the pattern. Week three clears the backlog of four small items.

Now apply Little’s Law, which says average cycle time equals average work in progress divided by throughput. Average WIP across the three weeks is 3.2 cards. Throughput is 4.7 cards per week. Expected cycle time is 3.2 ÷ 4.7 = 0.68 weeks, or about 3.4 working days from “In progress” to “Done”.

That number is useful because it turns a vague feeling into a forecast. If the client asks when the next card will finish, the honest answer is “about three and a half working days, assuming WIP stays at two”. If WIP creeps to five, cycle time rises to roughly 5.3 days at the same throughput — the same team, 56% slower delivery, purely from starting too much.

How do you turn cards into full notes?

Right-click any card and choose New note from card. The plugin creates a note in your configured note folder, using your note template, with the card text as the title, then links the card to that note. The board keeps the one-line summary; the note holds the brief, decisions, and links.

This is the pattern that makes Obsidian boards scale beyond simple task lists. A card called “Rewrite onboarding email” is enough for a board, but the actual work needs research, drafts, and approval. Splitting summary from detail keeps lanes readable while preserving depth one click away.

A practical rule: create a note from a card when the task needs more than three sentences of context, or when it will be revisited after a week. Below that threshold, the card itself is the right container.

How do you sync, back up, and review a board?

Sync is the weak point of every local-first board, so choose a method before you have a board worth losing. Three options cover most cases.

Obsidian Sync is the paid first-party service. It handles version history and conflict copies, and it works on mobile without extra setup. A file sync service such as a cloud drive folder is cheaper but can duplicate a file when two devices edit offline. Git gives you a full history and a diff for every card move, which is excellent for technical users and confusing for everyone else.

Whichever you pick, add a second layer of protection: a weekly export of the vault to a dated archive. A board file is small — a 14-card board is typically under 6 KB — so keeping 12 monthly copies costs nothing and survives a sync disaster.

Then run a ten-minute weekly review on the board itself. Three questions, in order: which cards in “In progress” have not moved in five days; which cards in “Review” are waiting on someone else; and what should move from Backlog to Next given next week’s available hours. Answer them by moving cards, not by writing a report. A 14-card board usually takes six minutes; a 40-card board takes twenty and is a sign the project needs splitting.

How do you use templates without the plugin?

You can get a usable board with only core plugins, though you lose drag-and-drop. Two approaches work.

Core Templates plugin plus a manual board. Store the markdown template above in a templates folder, insert it into a new note, and work in reading view. Cards are checkboxes; lanes are headings. It is slower but dependency-free.

Templater or QuickAdd. Both can insert the template with variables such as a project name and a start date, then file it in the right folder. This is the better option if you create boards weekly, because it removes the duplicate-rename-file routine that quietly accumulates `Untitled 3` notes.

Neither approach gives WIP counters, dragging, or the date picker. If those matter, use the plugin and keep the template plain enough to survive its absence.

What are the real limits of an Obsidian kanban board?

The limits are collaboration and enforcement, not features. Obsidian is a local-first notes app, and the Kanban plugin is a view over one file.

• No real-time co-editing. Two people editing the same board through a sync service will eventually create a conflict copy. Git-based sync produces merge conflicts inside the markdown that a non-technical teammate cannot resolve.
• No permissions or audit trail. Anyone with vault access can edit anything, and there is no record of who moved a card.
• No notifications, assignments, or due-date alerts. A date in a card is text, not a reminder. Nothing will tell you it is late.
• Mobile is read-mostly. Board view works on mobile but dragging between lanes is fiddly, and long boards need constant zooming.
• The archive is hidden. Managing completed work requires switching to markdown mode.
• Licensing. Obsidian is free for personal use; work use requires a commercial licence, roughly $50 per user per year at the time of writing.

None of these are bugs. They are the cost of owning plain text. The question is whether your team’s work needs enforcement or just visibility.

Obsidian kanban vs Trello, Notion, and a project platform

The pattern is clear: Obsidian is unbeatable for a single person who wants their planning next to their notes forever, and weakest the moment a second person needs to be held accountable.

What mistakes should you avoid?

• Too many lanes. Seven columns means nothing finishes. Four is a good default; five is the ceiling before cards start circulating.
• Using cards as projects. A card should be completable in a day or two. Anything larger becomes a note with its own checklist.
• Text dates instead of the date trigger. `20 Jan` sorts badly and cannot link to daily notes. Use `@`.
• No WIP limit. Without a number in the lane title, “In progress” becomes a graveyard of good intentions.
• Archiving everything. Archive completed cards monthly, not daily; the file stays navigable and the history stays useful.
• Storing the board in a synced folder with no conflict plan. Decide now whether sync is Git, a file sync service, or Obsidian Sync, and tell collaborators what to do when a conflict appears.

Conclusion

A kanban board template for Obsidian is worth building when you want your planning to live beside your notes, in files you control, without a subscription. The setup is genuinely short: enable community plugins, install Kanban, paste the template, set five options, and add WIP limits.

Be honest about the ceiling. The moment a board needs owners, deadlines that notify, permissions, or a second editor in real time, you are managing people rather than notes, and a platform with workload views, dependencies, and reporting will cost less in friction than the free file costs in confusion. Use Obsidian for thinking, and a shared system for coordinating.

If this post on kanban board template for Obsidian was helpful, you might also enjoy Outputs vs Outcomes in Project Management: What’s the Difference? and How to Track Work Without Micromanaging.