Choose a free Kanban board tool by what must happen after a card moves. Trello, Notion, Jira, ClickUp, GitHub Projects and Asana can track work records; CodePic provides a visual canvas for explaining or manually sketching a process.
Check free collaborator, storage and automation limits separately. This comparison includes a blocked-card exercise so you can test a working policy rather than choose from screenshots alone.
What to Look For in a Kanban Tool
Card customization. Labels, custom fields, color coding, attachments, checklists — these determine whether a board can reflect your actual workflow or just a simplified version of it.
Automation and workflow rules. Moving a card to "Done" and having it auto-assign the next person, or flagging cards that have been idle for a week. Automation separates a kanban board from sticky notes on a wall.
WIP limits. Work-in-progress limits are a core kanban concept — they cap how many cards can sit in a column at once. Without them, your "In Progress" column becomes a dumping ground. Surprisingly few free tools support this natively.
Integrations. Slack notifications, GitHub links, Google Drive attachments, calendar sync. A kanban board that lives in isolation requires constant manual updating.
Collaboration. Real-time editing, comments, mentions, activity logs. A solo kanban board works fine for personal task management, but team use requires proper collaboration features.
Trello
Trello is a board-oriented task system. Its current Free plan lists up to ten collaborators and ten boards per Workspace, unlimited cards and 250 Workspace command runs per month. Custom Fields are a Standard feature; third-party Power-Ups can have their own subscriptions.
For a simple board, test an assigned card, a due date and a blocked item. Keep the team policy visible even if a column does not enforce a WIP limit. Confirm which automation consumes command runs before building a high-frequency rule, and keep a manual recovery path if the allowance is exhausted.
Choose it when cards and a lightweight board are the main work record. A file attached to a card, an external integration and a native task field have different maintenance behavior.
Notion
Notion displays a database as a board grouped by a status or select property. It is useful when tasks need to live near notes and other structured information. Free individual access and a multi-member workspace have different content limits, so do not describe every team workspace as unlimited.
Test the properties, permissions and saved views the workflow needs. Database automations and integrations have their own plan requirements. A manual WIP policy can still be used, but check the actual warning or enforcement behavior instead of assuming the board is a dedicated Kanban engine.
Choose it when the database is the maintained source and the board is one view of that source.
Jira
Free tier: Up to 10 users, unlimited projects
Collaboration: Real-time
Card customization: Custom fields, labels, story points, sprints
Automation: Limited (100 rule executions/month on free)
Jira's free tier is more generous than most people expect — 10 users, unlimited projects, kanban and scrum boards, backlog management, and basic automation. For a small development team, it's a serious option at zero cost.
The kanban board in Jira is one of the most full-featured available. WIP limits are natively supported and configurable per column. The board can pull from a backlog, and cards support custom fields, labels, story points, epics, and sprint tracking. If you're practicing kanban as a methodology (not just using a board as a task list), Jira supports the workflow properly.
The tradeoff is complexity. Jira is built for software teams running agile processes, and the interface reflects that. Setting up a board for a non-technical team or a simple personal workflow feels like driving a truck to the grocery store. The learning curve is real, and casual users often find the configuration overwhelming.
Best for: Software development teams of 10 or fewer who want a proper agile kanban workflow with WIP limits, sprints, and backlog management.
ClickUp
Free tier: Unlimited tasks and boards
Collaboration: Real-time
Card customization: Custom fields, tags, statuses, priorities
Automation: Limited (100 actions/month on free)
ClickUp Free includes Kanban boards, unlimited tasks and basic custom-field access. Gantt and Timeline allowances differ from the board view; do not treat all views as unlimited on free access. Check current storage and automation allowances before moving a working team.
The board view is functional and customizable — you can group by status, assignee, priority, or any custom field. Automation exists on the free tier but is capped at 100 actions per month, which runs out fast if you're automating anything meaningful.
ClickUp does not have native WIP limits on the board view. You can create workarounds with automations or custom statuses, but it's not a first-class feature.
The platform's main drawback is density. ClickUp packs a huge number of features into every screen, and the learning curve reflects that. Users who just want a clean kanban board may find the interface noisy.
Best for: Teams that want kanban as part of a broader project management platform and don't mind a steeper learning curve in exchange for more features.
GitHub Projects
Free tier: Unlimited (included with GitHub)
Collaboration: Real-time (for repo collaborators)
Card customization: Custom fields, labels, milestones
Automation: Built-in workflows (auto-move on issue close, PR merge, etc.)
GitHub Projects turns Issues and Pull Requests into kanban cards on a board. For development teams already using GitHub, this is the most natural kanban integration available — cards link directly to code, PRs, and CI status.
The built-in workflows are developer-centric: auto-move a card when an issue is closed, when a PR is merged, or when a review is requested. Custom fields let you add priority, sprint, or any other metadata.
WIP limits aren't supported natively. The board view is clean but basic compared to dedicated kanban tools. Non-developers won't find much use here — the entire experience is built around GitHub's issue and PR workflow.
No cost, no user limits, no board limits — but only useful if your workflow is already on GitHub.
Best for: Development teams using GitHub who want kanban boards tightly integrated with their code and issue workflow.
CodePic
Free tier: Unlimited
Collaboration: Read-only link sharing
Card customization: Visual only (freeform text, colors, shapes)
Automation: Not applicable
CodePic is a diagramming tool, not a task management platform. It has a kanban board template, but the board is visual — you arrange cards, columns, and labels as drawing elements. There's no underlying task database, no automation, no WIP limits, no due dates.
This is a fundamentally different use case from the other tools on this list. CodePic's kanban template is for situations where you need to show a kanban board, not run one: project proposals, team presentations, process documentation, onboarding materials, blog illustrations, or strategy decks.
The hand-drawn style makes boards feel approachable — more like a whiteboard sketch than a rigid project management screenshot. You can customize every visual detail: card colors, column widths, annotations, arrows between cards.
If you need to explain a workflow to stakeholders who don't have access to your project management tool, a CodePic kanban board communicates the concept faster than a screenshot of Jira ever will.
Best for: Anyone who needs a kanban board visual for communication — presentations, proposals, documentation, or process diagrams — rather than day-to-day task tracking.
Try a communication sketch in the board below: replace one sample task with your own, move it from To Do to In Progress, and add a note explaining what blocks it. Keep any WIP policy as a visible annotation; the canvas does not enforce limits or track task history.
Asana
Asana's current Personal plan is for two users and includes list, board and calendar views with unlimited tasks and projects. The old ten-user claim should not guide a new rollout. Timeline and Gantt are paid Starter features.
For a simple two-person board, test assignment, due dates and review. Check custom fields, rules and any additional role requirements on the actual plan. This article does not assume that every type of automation or WIP enforcement is available on free access.
Choose it when the current team size and the task workflow fit. Re-evaluate cost before inviting a larger group.
Quick Comparison
| Tool | Access boundary to check | Work record |
|---|---|---|
| Trello | 10 collaborators, 10 boards/Workspace; 250 monthly command runs | Task cards |
| Notion | Individual versus multi-member workspace limits | Database items |
| Jira | Current user allowance and automation plan | Issues |
| ClickUp | Storage, fields, automation and view-specific limits | Tasks |
| GitHub Projects | Project and repository access are separate | Issues, pull requests and draft items |
| CodePic | Read-only public sharing; no task automation | Drawing objects |
| Asana | Personal: two users; advanced views paid | Tasks |
A visible WIP count, an automation rule and a hard movement restriction are different features. Use the exercise below to verify which one you actually need.
How to Choose
If you want the simplest kanban experience: Trello. It does one thing well and the free tier covers most personal and small-team use.
If your team already lives in Notion: Use Notion's board view. No new tool to learn, no context switching.
If you need proper WIP limits and agile kanban methodology: Jira is the only free tool on this list with native WIP limit support. The complexity is the price you pay.
If you want kanban inside a full PM platform: ClickUp gives you the most features for free, though the interface takes time to learn.
If you're a dev team on GitHub: GitHub Projects. Zero friction, direct integration with your code workflow.
If you need a kanban board for a presentation, proposal, or document: CodePic. It's not a project management tool, but for communicating workflows visually, it's faster and more flexible than screenshotting any of the above.
The reality is that most free kanban tools are good enough for basic board usage. The differences show up when you need automation, WIP limits, or deep integrations — and those features are often where the paywall kicks in.
Related Reading
- What Is a Kanban Board? — A complete guide to how Kanban works.
- Kanban vs Gantt Chart — When to use each approach.
- Kanban Board Template — Create a visual Kanban board in CodePic.
A blocked-card exercise with an explicit WIP policy
Create a fictional board with Ready, Doing, Review and Done. Agree that Doing has a working limit of two items and Review has a limit of one. These are example team policies, not universal Kanban numbers.
Start two tasks in Doing and one in Review. Mark one Doing item blocked because it needs an answer from another person. Does the team count that blocked item toward the limit? For this exercise, yes: it still represents unfinished work. Record an owner and the next follow-up instead of moving it out of sight to make capacity look free.
| Event | Expected team decision | Tool behavior to check |
|---|---|---|
| A third item is ready to start | Help finish or unblock existing work first | Visible count or warning; enforcement may be manual |
| Review finishes | Move the accepted item to Done | History and any configured automation are correct |
| A card is reopened | Put it back in the agreed active stage | Owner and prior context remain available |
| An outside reviewer joins | Give only the access needed | Participant limit and permissions remain suitable |
A tool can warn about WIP without preventing a move. A team can also honor a visible limit manually. Distinguish display, automation and hard enforcement before deciding that a product either “supports Kanban” or does not.
For a live work system, reopen the board and inspect the card history. For a communication drawing, save the editable source and label the snapshot date. CodePic's template does not create an underlying task database or calculate cycle-time reports. See Kanban vs Gantt when the real need is coordinating dependencies and dates.
