Draw with someone else over a direct browser connection

Some disagreements are impossible to resolve in writing. Two people describing a layout, a process, or a system architecture in prose will produce two different pictures in their heads and not discover the difference for another week. Drawing it takes ninety seconds.

Where a sketch beats an explanation

The recurring cases are spatial or relational:

• System and data flow. Which component calls which, and where the boundary sits.
• Page and screen layout. Where things go, relative to each other.
• Process and approval flow. What happens after what, and who decides.
• Physical arrangement. Room layouts, seating, equipment placement, site plans.
• Anything with a shape. If your explanation includes the phrase "sort of like a box with...", stop writing and draw it.

The shared whiteboard connects two browsers directly so both people draw on the same surface and see each other's strokes as they happen. That immediacy is the point: the conversation and the drawing happen together, which is what makes the disagreement surface early.

No board is stored anywhere

Because the connection is direct between the two browsers, the drawing is not held on a service. There is no board sitting in an account, no workspace accumulating everything your team ever sketched, and no retention policy to consider.

That has an obvious upside for anything confidential — architecture diagrams, customer data flows, org charts, commercial structures — and one very practical consequence you must plan for:

If you do not export it, it is gone.

There is no autosave, because there is nowhere to save to. Export the board before either party closes the tab. The tool produces a full-resolution PNG, which is worth taking even when the sketch felt throwaway. Whiteboard sketches have a habit of being the clearest artefact of a decision, and reconstructing one from memory a fortnight later never works.

Practical session habits

• Agree who is drawing what. Two people sketching simultaneously on the same region produces a mess. Take turns, or divide the canvas.
• Talk while you draw. A whiteboard on its own is ambiguous; a whiteboard plus a conversation is not.
• Label everything. A box with no label is meaningless in the exported image, even to the person who drew it.
• Date the board. Write the date and topic in a corner before exporting, so the image is identifiable later.
• Keep it rough. The value is in the shared understanding, not in the artwork. Tidy diagrams belong in a proper diagramming tool afterwards.
• Export at the end of each topic, not only at the end of the call. Boards get erased and redrawn.

Both people have to be there

The same trade-off applies as to any direct connection, described in the direct transfer guide: there is no store-and-forward. Both parties must be online at the same time, and a restrictive corporate network can interfere with establishing the connection.

That makes this a tool for live conversation rather than asynchronous review. For "have a look at this and comment when you can", export an image and send it instead — or annotate an existing document, which is a different job entirely.

What to do with the export

The PNG is a normal image, so it goes wherever images go:

• Paste it into meeting notes while the discussion is fresh.
• Attach it to the ticket or document that records the decision.
• Combine several boards from one session into a single document with the image to PDF tool, as covered in the image assembly guide.
• Send it to whoever was not on the call.

That last use is the most valuable and the most often skipped. The people who were not present get the decision without the reasoning, and a sketch carries far more of the reasoning than a paragraph summarising the outcome.

If the exported board contains anything sensitive — internal architecture, client names, commercial terms — remember it is now an ordinary image on your disk, and it should be handled with the same care as any other document containing that information. The session left nothing behind; the export is entirely your responsibility.