Claude Whiteboards is a collaborative board built into Claude. You put ideas down by voice, keyboard or pen, and Claude organises them into diagrams, flows and groups. Anthropic launched it in beta in November 2026, on every paid plan, on the web, the desktop app and mobile.
I built three boards to test it in November 2026, a migration plan dictated out loud, a team retrospective and the supplier invoice process of a small company. Here is what Claude actually organises, what it spots that nobody had seen, and the four limits to know before telling your teams you are switching tools.
What exactly is Claude Whiteboards?
Claude Whiteboards is a shared canvas where a team and Claude work together in real time. You dictate a plan, you drop sticky notes, you draw an arrow. Claude reads the whole board, then organises it. It groups by theme, builds a timeline with owners and dates, and adds its own suggestions straight onto the canvas. Boards are saved in Claude's Artifacts tab.
Three mechanics set it apart from a classic whiteboard. Claude writes on the canvas instead of commenting beside it. You drag across a region to ask a question about that region alone, and Claude answers only on it. And voice dictation covers more than thirty languages, which changes how a meeting turns into a plan.
The board then converts into a doc or a deck on request. It exports as PNG, and it ships out to Lucid, Miro or Vani by Zoho. It is the same movement as Claude Design, where the conversation produces the deliverable directly instead of text to paste elsewhere.
Which Claude plans include Whiteboards
Claude Whiteboards is available on every paid plan, from Pro to Enterprise, and it counts towards the plan's usage limits like the rest of your work with Claude. Entry is through the Pro plan, around 20 euros a month on monthly billing as recorded in November 2026. If you are weighing the tiers, I covered when Max pays off elsewhere. The feature is not open on Claude for Teachers yet.
The default setting changes by plan, and that is the point that blocks teams most often.
| Plan | Default state | Where to enable it |
|---|---|---|
| Pro, Max, Ultra | On | Nothing to do |
| Team | On by default | Organization settings, Artifacts section |
| Enterprise | Off by default | An admin enables it under Artifacts |
Two compliance restrictions are worth reading before you run a pilot. Claude Whiteboards is not available to organisations with HIPAA-ready configurations, and it falls outside zero data retention. It is also absent from Claude Code. The full conditions sit in the official documentation.
What Claude actually organises, tested on three boards
The most telling test was a team retrospective. I dropped sixteen sticky notes written by five people, in no order. Claude grouped them into four themes, then drafted five actions, one per person, each with a deadline.
Second test, a sales software migration plan dictated out loud, in a mess. Claude produced seven dated steps and four owners. It resolved the implicit dates on its own, "Friday" became 13 November, "before the holidays" became 18 December. Above all, it isolated the oversight. Nobody owned the quotes already in progress, and Claude raised the question in a separate block, with a suggestion clearly marked as one.
That separation between what was said and what Claude proposes is the reflex many tools lack. It stops a generated assumption from being read as a team decision.
The gaps Claude spots between two steps
The third test is the one I keep for scoping workshops. I described out loud the supplier invoice process of a small company, from the PDF landing in the accounting inbox to the monthly handover to the accountant. Claude turned it into six steps, each with a named owner.
Then it added three gaps between the steps. The same invoice arrives by email and through the buyer, so nothing prevents entering it twice. No approval threshold is written down anywhere. And supplier disputes have no owner, so the invoice goes quiet.
The line Claude put at the top of the board sums the exercise up. Every step has an owner, the handovers between steps do not. That is exactly what a process mapping looks for, and it came out of a two-minute dictation.
What Claude Whiteboards cannot do yet
Four limits show up within the first hour of use, and two of them come from Anthropic's own documentation.
- No access to connected apps. Claude works only from what sits on the board. Your sales software and your inbox stay outside.
- No board import. You can add pictures and videos, but you cannot load an existing board from a file. Migrating from another tool is manual work.
- A rigid layout. Past six steps, a process wraps to a second row starting back at the left. An arrow cannot point at another arrow, it has to target a block or a free point.
- Compliance restrictions. HIPAA-ready configurations exclude the feature, and zero data retention does not cover it. Two things to check before a rollout in healthcare or finance.
On the Hacker News thread about the launch, the most repeated criticism in November 2026 is simplification. Several developers find these tools too basic for serious design work, and some refuse to put their sales figures in. The criticism lands on finish. It misses on actual use, because Claude Whiteboards serves the workshop and the scoping, while a design tool serves the mockup.
Whiteboards, Sheets and Data, Claude's office suite
Whiteboards arrived alongside two other pieces, in the same announcement. Claude Sheets is a spreadsheet Claude builds and edits with you, tabs, formulas and drop-downs included. Claude Data, formerly Dashboards, moves to general availability and queries data in a connected warehouse or sales tool.
The same month, Anthropic also launched Claude Meetings in beta, on Team and Enterprise plans, on Google Meet first. Claude joins the call as a visible participant, announces itself, and builds the board during the meeting. It leaves automatically if an external guest joins, unless an admin allows it.
For a small or mid-sized company, the reading is simple. Claude stops being an assistant sitting next to the tools, and becomes the place where the deliverable is made. The board turns into a doc, then a deck, without ever switching apps. I described that shift back in June 2026 in my newsletter on slides, and the same movement continues with Cowork.
Should you replace Miro with Claude Whiteboards?
Not yet, and certainly not in one move. Claude Whiteboards wins on one thing whiteboard tools do not cover. The board fills itself from a dictation, then reviews itself to find what is missing. No template library does that.
Established tools keep the lead on finish, on the number of templates, on the integrations already wired in and on team habits. The current version is still a beta, with the bugs that implies, and Anthropic has in fact planned export to those tools rather than their replacement.
The sensible move fits in one sentence. Keep your current tool for boards that live for months, and take Claude Whiteboards for workshops that must produce a plan the same day. On that specific slot, the gain is measured in half-days, from the very first workshop.
