TabbitBlog

Claude Whiteboards: How to Create and Share a Board

Learn how to start a Claude Whiteboard, prompt and revise it with a team, share or export the result, and check beta access and data limits.

In this article
  1. Key takeaways
  2. Claude Whiteboards at a glance
  3. What Claude Whiteboards is—and what it is not
  4. How to start and shape a board
  5. 1. Open a Whiteboard
  6. 2. Give Claude enough structure
  7. 3. Revise the board with Claude and your team
  8. 4. Share, export, or continue the work
  9. Choose a workflow that matches the work
  10. Example: turn a messy retrospective into a usable plan
  11. When Tabbit can help around a Whiteboard
  12. Access, privacy, and beta limits

A Claude Whiteboard is a shared visual workspace for turning early ideas into a diagram, flow, grouped themes, or rough plan. Open one from a Claude chat or from the Artifacts tab, describe the outcome you need, then revise the board with Claude and your collaborators. It is a useful place to work before a plan is settled; it is not a replacement for every dedicated whiteboard or diagramming app.

One commenter on the launch thread put the core question plainly: “The whiteboard might be cool if Claude can actually decently write to it.” That is a fair test. Treat Claude’s first layout as a draft, check the logic with your team, and choose a dedicated tool if you need its established diagramming controls or self-hosting. Anthropic’s Help Center documents the current workflow and limits.

Three teammates shape a shared project plan on a whiteboard during a video call
A shared board works best while the team is still shaping the plan.

Key takeaways

  • Start a board from chat or the Artifacts tab; both routes lead to a Whiteboard workspace.

  • Give Claude a clear question, audience, constraints, and desired board sections. Ask for a draft you can correct, not a finished answer you should accept without review.

  • Collaborators with access can rearrange the board in real time. Use region selection when you want Claude to focus on one part.

  • Share with invited people, export a PNG, or send the board to Lucid, Miro, or Zoho Vani. Official docs do not describe an unrestricted public link or importing an existing board file.

  • Check plan availability and organization settings first. Whiteboards is a beta, counts toward plan usage, and has data-control exclusions.

Claude Whiteboards at a glance

Use Claude Whiteboards when…Keep another tool when…
The team is still exploring options, causes, or a rough sequence.You need a mature diagram editor, strict templates, or self-hosting.
You want Claude to turn a prompt or rough discussion into a visual starting point.The diagram must follow exact notation or a regulated production process.
Several people need to rearrange ideas live and agree on the structure.Your team already has a board system with required permissions and history controls.
You expect to convert the agreed structure into a document or deck.The task is primarily numeric modeling; use a spreadsheet workflow instead.

A skeptical commenter in the same launch discussion said, “I don't see the value proposition with whiteboards or sheets,” then compared the feature with existing options such as draw.io. That is a useful reminder: a new workspace is worth adopting only if Claude’s drafting and collaboration shorten a real step in your process. Keep your existing tool if its controls or deployment model matter more.

What Claude Whiteboards is—and what it is not

Anthropic describes Whiteboards, Sheets, and Claude Data as distinct work surfaces in its launch overview.

Whiteboards is a shared board where you can talk, type, or sketch an idea and ask Claude to organize it. Anthropic describes diagrams, flows, and grouped ideas as examples. A teammate can rearrange items, and you can follow a collaborator to see the area they are working on. You can also select a region of the board and ask a question about that part.

Anthropic’s launch overview of Whiteboards, Sheets, and Claude Data treats them as separate work surfaces. It is different from the other recently introduced Claude work surfaces:

FeatureMain jobChoose it for
Claude WhiteboardsShared visual thinking with ClaudeBrainstorms, process maps, retrospectives, early project plans
Claude SheetsSpreadsheet creation and collaborative formula workStructured rows, calculations, and working with data in a sheet
Claude DataDashboards and data stories connected to data sourcesExploring and presenting business data
Claude MeetingsA Google Meet workflow that can create meeting outputs, including a whiteboardCapturing a live meeting and continuing from its notes or artifacts

The standalone Whiteboard is not a meeting bot. Claude Meetings is the separate feature that joins a supported Google Meet when enabled; one possible output from a meeting is a whiteboard. For setup and participation details, use the separate Claude Meetings guide when it is published, and consult the official Meetings documentation.

How to start and shape a board

1. Open a Whiteboard

In a chat, ask Claude to start a whiteboard for a specific task. For example:

Start a whiteboard for our onboarding workshop. Map the first 30 days for a new customer success hire. Include stages, owners, open questions, and handoffs. Mark assumptions separately from confirmed steps.

Or open Claude’s Artifacts tab, select the Whiteboard tile, and describe the board you want. You can dictate through the microphone; the recognized text stays in the prompt box so you can review it before sending.

2. Give Claude enough structure

A useful prompt says what the team is deciding, who will use the board, what is already known, and which parts are still uncertain. Name the output shape too: a timeline, a process flow, options with trade-offs, or groups of retrospective themes. Ask Claude to label assumptions and unresolved questions. That makes it easier for collaborators to tell a proposal from a decision.

Avoid asking for “a complete launch plan” without context. Instead, provide the launch date, teams involved, known dependencies, and the decision the board should help the group make. If the result is too broad, ask for a smaller board with fewer sections.

3. Revise the board with Claude and your team

Once the first structure appears, scan it for missing steps, duplicated ideas, and claims that need an owner or source. Ask Claude to regroup notes by theme, make a timeline, or identify gaps between steps. Select a specific area when you want a focused question; this keeps the request anchored to the part under discussion.

Then let collaborators edit the structure directly. The board is meant for shared work: people can rearrange it, add ideas, and follow another member’s view. Before leaving a workshop, turn loose notes into a small set of decisions, owners, dates, and open questions. Have a person confirm every assignment and date.

4. Share, export, or continue the work

Open the board and choose Share to invite collaborators. People outside your organization can be invited by email only when the organization allows external email invitations under Organization settings > Artifacts. Do not assume a copied link is public or that an outside guest can access the board without an invitation.

For a static copy, use Share > Export to save a PNG. Anthropic also documents a Send to option for Lucid, Miro, and Zoho Vani. If the structure is settled, ask Claude to turn the board into a document or deck. The Help Center says you can add images and videos, but cannot import an existing board from a file. If you need to preserve a working board in another tool, confirm the handoff format before relying on it.

Choose a workflow that matches the work

Work in progressA practical starting pointCheck before you share
Product launchAsk for phases, dates, owners, dependencies, and unresolved decisions.Separate confirmed commitments from proposed dates.
RetrospectiveAdd one note per observation, then ask Claude to group themes and draft actions.Have participants verify that a theme reflects their notes.
Process mappingAsk for each step, handoff, exception, and decision point.Validate the flow with the people who perform the process.
Decision workshopPut options side by side with benefits, risks, and evidence gaps.Keep facts, estimates, and preferences visibly distinct.
Research synthesisUse a board to arrange questions and themes, then make a source-backed document.Keep source links attached to claims; a visual grouping is not evidence by itself.

Example: turn a messy retrospective into a usable plan

Suppose a team leaves a retrospective with a page of comments about a delayed release. The raw notes mix causes, symptoms, and proposed fixes. Start by asking Claude to organize the notes without treating each comment as a confirmed fact:

Group these retrospective notes by theme. Keep each note traceable to its original wording. Separate observed facts, interpretations, and proposed fixes. Flag themes that have only one supporting note.

Review the groups with the people who wrote the notes. Move comments that Claude placed incorrectly and rename any theme that overstates the evidence. Then ask for an action draft with blanks where the team still needs to decide:

For each agreed theme, draft one next step and describe the evidence it should change. Leave the owner and due date blank. Keep unresolved causes in a separate section; do not present them as decisions.

The blank fields are deliberate. Claude can organize the discussion, but the team should assign an owner, agree on timing, and decide whether an action is feasible. If the board becomes crowded, ask Claude to focus on one selected region or split the work into decisions the team can finish separately. Once owners confirm the list, ask Claude to turn the agreed structure into a document. Keep the board as the discussion surface and the document as the handoff the team will act on.

Before sharing the result, check three things: can each theme be traced to notes, are proposals visibly different from decisions, and does every action have a person who accepted it? This review is more useful than polishing the board’s appearance.

When Tabbit can help around a Whiteboard

Tabbit Browser is not a Whiteboard client and the materials reviewed do not document an integration that sends browser research into Claude Whiteboards. Its adjacent use is source gathering: keep reference pages together, compare them, and summarize what each source says before asking the team to map a decision. The researcher browser guide and deep-research workflows cover that browser-side work. The board still needs its own source links and human review.

If your input is scattered across many tabs, these guides cover ways to organize it: browser productivity, profiles and workspaces, and Tabbit Browser practices. For source-based synthesis, see research with browser agents and Claude Cowork browser workflows. If you are choosing a browser for the surrounding research process, read the AI browser comparison.

Access, privacy, and beta limits

The plan, sharing, usage, and data-control details in this section follow the Claude Whiteboards Help Center.

Claude Whiteboards is currently a beta on Pro, Max, Ultra, Team, and Enterprise plans, across the web, Claude Desktop, and Claude Mobile. It is not available in Claude for Teachers yet. Team organizations have Whiteboards enabled by default; Enterprise organizations start with it off, and an admin can enable it under Organization settings > Artifacts. If the tile is missing, check your plan and ask the organization admin about the setting.

Whiteboards uses plan usage limits. The current Help Center also says connected apps do not supply extra context to the board: Claude works from the material on the board. Organizations with HIPAA-ready configurations cannot use Whiteboards. For organizations with ZDR for Claude Code, Whiteboards is available in chat and Cowork, but is not covered by ZDR and is not available in Claude Code. If your organization relies on a particular data-control setting, confirm that limitation with an admin before adding sensitive content.

The practical choice is simple: try Claude Whiteboards when the team needs a quick shared structure and is prepared to review it. Keep a dedicated tool for strict diagram standards, deeper access controls, or a hosting requirement. Start with one small decision, ask Claude for a clearly labeled draft, and make the team—not the first generated layout—the final authority.

FAQ

What is Claude Whiteboards?

Claude Whiteboards is a shared visual workspace in Claude for brainstorming, planning, and organizing ideas with Claude and teammates. It is currently in beta.

How do I open Claude Whiteboards?

Ask Claude in a chat to start a whiteboard, or open the Artifacts tab and select the Whiteboard tile. Describe the task, audience, and structure you want.

Can my team edit a Claude Whiteboard together?

Yes. People with access can work on the board together in real time, rearrange it, and follow another teammate’s view. Sharing with people outside the organization depends on the organization’s email-invitation setting.

Can Claude Whiteboards export to PDF or Miro?

The Help Center documents PNG export and Send to options for Lucid, Miro, and Zoho Vani. It does not document PDF export or importing a board file.

Which Claude plans include Whiteboards?

The beta is available on Pro, Max, Ultra, Team, and Enterprise on web, desktop, and mobile. Team has it on by default; Enterprise admins must enable it. It is not available in Claude for Teachers yet.

Take the next step

Let Tabbit work alongside you.

Research across tabs, automate repetitive browser work, and keep every piece of context within reach.