The calendar invite says "quick sync — 30 min." It is not quick. Someone in Berlin joins at the end of their day, someone in Denver in the middle of theirs, someone in Bangalore at an hour no one should be working. Half the call is context you already thought through and could have said once; the other half is three people nodding at a screen share they will not remember by Thursday. And when it ends there is no record — just a decision living in four people's slightly different memories until someone reopens the question next week. There is a better shape for most of these meetings, and it is not a meeting at all: a short recording you make once, at whatever hour suits you, that everyone else watches whenever their day allows.
That is what a narrated whiteboard walkthrough is: you draw the thing you would have talked through — the plan, the design, the architecture, the feedback — and narrate it as you go, then hand your team a video they can scrub at their own pace. The full-screen board app now records exactly this, entirely in your browser. You open the board app, allow your microphone, draw and talk, stop, check the playback, and export a video file you drop into Slack or a doc or a ticket. Nothing uploads and nothing installs. This guide covers how to record a walkthrough instead of a meeting, how to be sure it lands before you send it, and where async genuinely beats getting everyone on a call.
The Meeting That Could Have Been a Recording
Most recurring meetings on a distributed team are not really discussions — they are one person delivering context to several people who mostly listen. A design review where you walk the team through your rationale, a sprint kickoff where you explain the plan, an architecture sign-off where you trace how the pieces fit. In each case one voice does most of the talking, and the "meeting" exists only because that voice needs a visual and a way to reach everyone at once — both of which a recording does better. A drawn walkthrough with your narration on top delivers the same context and the same visual, except your teammates absorb it when they are awake and focused, can rewind the part they missed, and can point back to it a month later when the decision is questioned.
The math is stark. A synchronous meeting costs everyone the same slot at once, plus the time-zone tax of pulling someone out of their evening or their sleep; a recorded walkthrough costs you a few minutes to make and each teammate only the runtime, watched whenever suits them. That is the async-team case for replacing meetings with video — not every meeting, but the large share that are really a broadcast wearing a discussion's clothes.
What a Narrated Walkthrough Is (Async, Drawing-Native, No Webcam)
An async walkthrough is a recording your team watches later, on their own schedule, as many times as they need — the opposite of a live call, where everyone must be present the same minute and there is no rewind. It is a Loom-style async video with two differences. First, it is drawing-native: the canvas is an infinite whiteboard with a real vector engine, so a walkthrough is you building a diagram live rather than clicking through slides or waving a cursor at a static doc. Second, it is audio only — no webcam, no talking head, just your voice and the drawing. Your teammates watch the boxes and arrows appear as you reason about them and hear you think aloud, which is exactly where their attention belongs. No one needs to see your face to follow a data flow, and skipping the camera means you can record a good walkthrough looking however you look at 9pm.
It is also not a screen recording of your whole desktop — it captures only the board and your narration, never your other windows or notifications; for internal work that is a feature, keeping the idea and only the idea in frame. The board is the same vector surface as the regular online whiteboard — pen and highlighter, shapes that auto-recognize from a rough sketch, arrows and connectors, sticky notes, text and images — so every mark you make while talking is a real, editable object, and the diagram looks deliberate instead of scrappy.
Recording One: Open the Board, Talk While You Draw
Open the board app and it loads straight onto a blank canvas with the pen ready. Hit record, and the browser asks once for permission to use your microphone — the same prompt any video-call site shows — and you allow it. From that instant your voice is captured alongside every stroke you draw, woven together so that later each mark reappears at the precise moment you talked about it. Then you simply do the walkthrough: sketch the first box while you say what it is, draw the arrow to the next while you explain the dependency, circle the risky part as you flag it. There is no scene to set up and no region to select — you are just explaining, the way you would to a colleague leaning over your desk.
You do not need a script — a rough sense of the three or four points you want to hit is enough. Draw at the pace of your sentences so a viewer sees each piece land as you name it, and zoom out to show the whole shape when a section gets crowded. When the explanation is done, press stop — there is no upload and no render queue, because the whole thing was assembled locally as you spoke.
Scrub the Replay to Check It Lands Before You Send
Before a walkthrough goes to your team, watch it back once — the step that separates a recording people use from one they quietly close. When you stop, the board immediately offers a synced replay: your drawing reappears in step with your audio on a timeline you can scrub. Drag the playhead anywhere and the picture and the sound jump there together, so you can leap to the part you were unsure of and confirm it holds up. As your own first viewer you catch what you cannot notice while talking — a step you raced through, a silence where you were thinking, a label you drew but forgot to say. For a walkthrough meant to stand in for a meeting this matters, because there is no live audience to ask "wait, can you say that again?"
There is no editor — you cannot trim a section, cut a pause, or stitch two attempts together; the replay is for judging the take, not fixing it. If it does not land, you record it again, which steers you toward the right instinct for async work: keep each walkthrough short and single-purpose, and a weak take costs almost nothing to redo. A three-minute walkthrough is quick to re-record; a thirty-minute one is not — another reason to scope each recording to one plan, one design, one decision. When the scrub-through checks out, you are ready to export.
Export the WebM and Drop It Where Your Team Already Is
Exporting turns the synced replay into an ordinary video file. The board writes out a WebM that downloads as whiteboard-recording.webm — a self-contained clip of your drawing and your narration that behaves like any other video. From there it goes wherever your team already works: paste it into a Slack or Teams channel, embed it in the Notion or Confluence doc it explains, attach it to the Jira or Linear ticket it walks through, or share an unlisted link by email. Because it is a standard video file, it plays on any phone, tablet or laptop with nothing to install, and it sits permanently next to the work it describes — a durable artifact your teammates re-scrub weeks later instead of a meeting they reconstruct from memory.
One practical note on browsers. Recording and the synced replay work in every modern browser, but the video export needs Chrome, Edge or Firefox. In Safari the export button is disabled with a tooltip explaining why, though you can still record and replay there — so on a Mac, record in Chrome or Firefox and the download will be waiting. The format is WebM rather than MP4, which every major workplace platform accepts. If you also want a still frame of the finished board as a thumbnail or for the ticket description, our companion guide on exporting a whiteboard to PNG, SVG and PDF covers the static exports.
Why "Nothing Leaves Your Browser" Matters for Internal Work
The whole recording is client-side. Your microphone audio and your drawing are captured and assembled inside your browser on your own machine; nothing is streamed to a server, nothing is stored in an account, and the WebM you download was built locally and handed straight to you — the opposite of a cloud recorder that uploads your voice and screen to someone else's servers under someone else's retention policy.
For a team walkthrough that distinction is not academic, because the material is so often confidential — an unshipped architecture, a design still under NDA, a roadmap the company has not announced, feedback on numbers no one outside the team should see. Because the audio and the board never leave your browser while you record, that draft stays a draft until you decide to share the exported file — you control the single moment it becomes visible, rather than handing that decision to a server the instant you press record. For internal, pre-announcement or client-sensitive work, that is the simplest data protection there is: the recording never travels until you send it.
Four Team Walkthroughs Worth Recording First
The fastest way to feel the shift is to record the kinds of context you would otherwise have called a meeting for:
- A design or UI critique drawn over a rough sketch. Paste the mockup onto the canvas and mark it up as you talk — circle the cramped spacing, draw the alignment you would rather see, arrow from the confusing control to where it should go. Async design feedback video like this lands far more precisely than a thread of comments, because the designer sees exactly what you mean and hears the reasoning behind each note.
- Explaining a sprint plan or roadmap. Lay out the workstreams as columns or a rough timeline, narrate why the order is what it is and where the risks sit, and the team absorbs the plan without a kickoff call — then re-scrubs it mid-sprint when they forget what blocks what.
- An architecture or system walkthrough. Build the diagram live — services as boxes, dependencies as arrows, the data flow traced from request to response — while you explain the trade-offs at each hop. A new engineer can watch it on day one and pause on the confusing part, something no live sign-off ever let them do.
- Narrating feedback on a doc or diagram a colleague sent. Drop their file onto the board and talk through your reaction section by section, so they get your actual voice and thinking instead of terse inline comments — and because nothing uploads, their draft stays on your device until you send the recording.
When Async Beats a Meeting (and When to Just Meet Live)
Async wins whenever the exchange is mostly one-directional and time-shifting it costs nothing: delivering context, explaining a plan, giving feedback, onboarding someone into a system. In all of these the value is in the explanation being clear and re-watchable, not in it happening at a shared instant. If you find yourself writing "let me just walk you through it" in a calendar invite, that meeting is almost certainly a recording.
But async is a tool, not a religion, and some things genuinely need a live room. Anything that depends on real-time back-and-forth — a decision the group has to negotiate, a brainstorm that feeds on people building on each other, a tense conversation where tone and immediacy matter — belongs on a call. When the point is to present to a room and take the discussion live, the synchronous counterpart is worth reading: our guide to presenting with a full-screen whiteboard covers screen-sharing the same board on Zoom or Meet and annotating for a live audience. The healthy pattern is to default to a recording for broadcast-shaped context and reserve live time for the genuinely interactive parts — which, once you stop meeting to deliver context, turn out to be a small fraction of the calls you used to hold.
The Honest Limits
It is worth being straight about what this is not, so it fits your team rather than surprising it. The recording is audio only — your voice and the board, not a webcam, so there is no picture-in-picture of your face; for a walkthrough the drawing carries the meaning anyway. It records the whiteboard, not your screen or any other application, so it is not a general screen recorder for demoing software. The export is WebM, not MP4, and that final export needs Chrome, Edge or Firefox, though recording and replay work in Safari too. There is no built-in editor — no timeline to trim or splice — so you polish by re-recording. And because the file never leaves your device, there is no live co-editing or real-time collaboration; the board is built for one person recording, not a shared multiplayer session, so genuinely two-way work still happens on your call platform. None of these stand between you and a finished walkthrough — they are the trades that keep the tool fast and private. The same record-and-export mechanic also powers a creator-focused whiteboard explainer video with voice and, for educators, narrated whiteboard lessons — same tool, aimed at a different job.
Record the Next Meeting Instead of Scheduling It
The pitch is simple: the next time you are about to book a "quick sync" to walk the team through something, don't. Open the full-screen board app, press record, allow your microphone, and draw the walkthrough you were going to give live. Scrub the replay to be sure it lands, export the WebM, and drop it where your team already is. If you want the full toolkit first, the full-screen whiteboard tool page lays everything out. It runs in your browser, nothing leaves your machine until you send it, and there is nothing to install — which is exactly why the walkthrough gets made instead of the meeting getting scheduled.