Recording a meeting with Notetaker
Last updated: November 11, 2026
Available on: Mac (macOS 13 or later), Windows and iOS
Notetaker records a meeting, shows a live transcript, and produces a summary afterward. Follow the conversation in the notepad and type your own notes.
Before you record
Ask participants for consent before transcribing, and complete Flow onboarding before starting a recording. Microphone access captures you on both platforms; Mac also requires system-audio access to capture other participants, while Windows has no separate system-audio permission step.
“Complete setup to start Notetaker” means recording has not started. If “Notetaker isn't recording yet” appears, choose Finish Setup to continue or Close Notetaker to leave without recording.
Click Turn on for each permission requested in setup.
Allow access in the permission dialog or the system settings opened by the action.
Restart using Restart Wispr Flow only when setup requests it.
On Macs that show “Restart Wispr Flow to apply changes,” a new system-audio grant requires that restart before recording works; Open Settings remains available to adjust access. Without a restart instruction, new access takes effect immediately. If Turn on becomes available again, retry. “All set!” confirms setup is complete.
An unsupported Mac instead shows “System audio not available” or “Notetaker blocked,” with no permission action that enables recording. On Macs supporting an automatic system-audio prompt, it can appear when setup opens for an eligible meeting only if access has not been allowed or denied; it does not open System Settings.
Revoking microphone or system-audio access can reopen setup while the meeting is idle, not during recording or on a read-only shared note. See Getting started with Notetaker for setup help.
If your account or organization blocks recording
Organization privacy settings and attendee rules can block recording. Cloud Sync restrictions can also block recording when it is unavailable or off, including restrictions associated with a signed HIPAA BAA or organization policy. Recording is blocked until Flow has loaded the account settings it needs.
Policy blocks show their own message instead of setup. Follow its Request access, Open Settings or Open Admin Portal action, or contact your administrator. Dismissing the message does not enable recording or Resume. An attendee-rule block brings the notepad forward and prevents that meeting from recording.
Start a recording
Note: Only one meeting records at a time. Starting another can wait for the previous recording to finish saving; summary processing continues separately.
Open the Notetaker hub.
Choose New note or Start Notetaker for an in-person or unscheduled meeting; the start action's label varies between installs.
Recording starts once setup and access requirements are satisfied.
For a scheduled meeting, choose Join + Start on its upcoming-list row. If you are already in the call, the event has no conference link, or it clashes with another meeting, start recording without joining: use Start Notetaker in the caret menu, or the record-only button on a row without a joinable link.
⌘N on Mac or Ctrl+N on Windows starts a new recording in the Notetaker list, except while typing in a text field. The separate, rebindable start/join shortcut is Opt+M on Mac or Win+Alt+M on Windows. To customize it, stop recording first, then open Settings → Notetaker → Keyboard shortcut → Change shortcut (the action is Join meeting / start Notetaker).
Note: When your organization posts a recording-consent notice in the meeting chat, Flow looks for the call for up to 60 seconds after recording starts before asking you to post the notice yourself. For in-person meetings or apps Flow can't detect, recording can run for up to a minute before any notice or prompt appears.
In eligible Business or enterprise organizations with the consent-chat policy enabled, each recording computer can post a consent notice. Where your organization suppresses duplicates for the same calendar event, a notice from you or a colleague can prevent or delay another, and resuming or joining through Wispr Join can skip the repeated notice and manual prompt. The notice is posted as usual if Flow was restarted since, the calendar event has already ended, or your organization can't be reached to check.
Start automatically (optional)
Auto-start is off by default and applies separately to each computer.
Open Settings → Notetaker → Meeting detection.
Enable Automatically detect any call.
Enable Start Notetaker automatically, directly below it.
With detection off, auto-start is disabled and reads “Turn on “Automatically detect any call” to use this”; your choice is retained.
An eligible “Meeting detected” card starts recording after a countdown: 10 seconds by default, bounded to 5–60 seconds. Only the front eligible card can start one; scheduled reminders and Join + Start cards have none.
Start now: click Start Notetaker to bypass the countdown.
Pause: hover, hide or drag the card. An unfocused, collapsed or parked card also pauses; it resumes with the remaining time and cancels after 60 seconds without being presented.
Cancel: open the caret menu or choose Snooze for 2 min; that card then requires a manual start.
Decline this call: click X, press Esc, or join without Notetaker. The card stays suppressed for that call; rejoining later shows it again.
Auto-start can be refused before or after the countdown if you are actively working in the notepad, another recording is in progress, setup, permissions, consent, account access or an organization policy prevents recording, or Flow cannot confirm an eligible ongoing call. A notepad left open behind your meeting window does not block it.
Sleep, screen lock, switching Mac users, quitting Flow, losing the meeting signal, a system-clock change, a delayed start, or changed settings or access cancels the countdown, so check that recording actually starts.
If the notepad is open but you are not typing in it, Flow saves your unsaved edits and switches it to the new meeting's note; the earlier note reopens from the hub.
While recording
Closing the notepad does not stop recording. Click the Flow Bar's recording pill, or reopen the active meeting from the hub, to return to the same transcript and notes; when the notepad is in front, use its in-window recording control.
Follow Transcript or write in My thoughts. Your typed notes are separate from the AI Summary, are not rewritten by summary generation, and are excluded when you share the note.
If a source stops sending audio
Flow attempts to restart a microphone that stops delivering audio, or system audio on Mac. Recording continues once audio returns. If recovery fails after about half a minute, “Notetaker isn't getting any audio” appears beside the Flow Bar.
Click Restart Flow.
Start recording again after Flow reopens.
The card clears when audio returns or the meeting ends; Dismiss only clears it. A device another app is holding exclusively can't be captured, so check your microphone selection if the card keeps returning.
On Windows, Flow separately attempts to recover other participants' audio. If recovery fails, it can show “System audio capture stopped” or, for a start failure, “Could not capture system audio.”
Stop recording and review
Warning: Signing out or force-restarting during recording can lose the final words. Use the normal Stop action first; audio captured so far is kept on the device.
Click Stop Notetaker in the recording pill or meeting window; capture ends immediately, even mid-sentence.
Wait for audio saving to finish.
Open the meeting's Summary and Transcript tabs from Past notes.
Start and Resume can be unavailable while audio saves, for up to 15 seconds, and Stop is unavailable during wrap-up. Flow saves the words captured up to your Stop click above the pause divider, even if you quit immediately afterward.
Without an existing summary, meetings with five minutes or less of total recorded audio — including earlier segments — or meetings stopped by switching Mac users wait for Generate summary or automatic processing after 24 hours. Other meetings process after stopping when connectivity and account access permit.
Warning: An existing summary, including your edits, stays until you choose Update Summary. Updating replaces your edits without a confirmation dialog; the button changes to “Updating summary…”. Little or no new audio does not remove an existing summary.
A very short or silent recording can show “The meeting was too short to summarize.” or “No transcript or audio available for a summary.” If “We hit a snag processing your meeting” appears, use Retry when offered. “We couldn't process your meeting” means no further attempt will run; “The full recording is no longer available to retry” means the saved audio cannot support another attempt.
Your audio stays on the device until the stop has been saved. If Flow quits, crashes or fails to save while a recording is stopping, the recording is picked up and finished the next time you open Flow, including audio captured after a resume. With Notetaker cloud sync turned off, meetings stay on your device and are picked up for processing once you turn sync on.
Started by mistake?
A new recording with no audio, transcript or typed notes is discarded; resumed meetings are protected. If live transcription started and the current segment captured fewer than 20 words, a retained meeting can show “Started by mistake?” with Keep or Discard. This does not apply to demos or recordings stopped for setup. With nothing recorded, the message instead reads “Stopped meeting” / “No audio was recorded.”
Warning: On the short-meeting card, Discard deletes a new meeting — and its audio — unless protected by typed notes. For a resumed meeting, it only dismisses the card; the prior transcript, summary and newly appended words remain.
Couldn't start recording
A failed start is discarded only for a new meeting with no typed notes and less than 10 seconds of audio. A kept failed start waits for manual processing rather than starting it automatically.
Read whether the card says “We couldn't capture any audio, so nothing was saved.” or “We couldn't start live transcription. Your audio was saved on this device.” If the card says audio was saved on this device, reconnect and allow processing to resume. Try again starts a fresh recording.
Warning: On the failed-start card, explicitly choosing Discard deletes a newly created meeting and its audio. For a resumed meeting — or when nothing was saved — it only dismisses the card and closes the notepad. Ignoring or timing out the card does not delete a saved meeting.
Automatic stops and recording limits
Settings → Notetaker → Stop Notetaker when a call ends controls end-of-call stopping. Recordings finish shortly after you leave, once Flow has seen a few seconds of silence; other participants' speech can add a wait of up to 30 seconds. Live calls, browser lobbies before joining, reconnecting, dictation and app startup can suppress or delay stopping, but not the recording-length limit.
Prompts appear next to the Flow Bar, with Stop available while you decide:
Prompt | If ignored |
Notetaker stopping | Recording stops and saves when the countdown ends. |
Meeting still going? | Recording stops after the 30-second silence warning. |
Still taking notes | Recording continues unless you choose Stop. |
Stop taking notes? | Recording continues. |
The silence warning follows ten continuous minutes without transcribed speech after earlier speech was captured, while capture and live transcription are working. When enabled, “Still taking notes” appears once 10 minutes past the calendar end and once after an hour of recording. Keep going or Keep recording answers only that prompt; later automatic stops remain active. Hovering “Notetaker stopping” pauses its countdown, but does not cancel the stop or postpone it indefinitely.
After an automatic — not manual — stop, “Notetaker stopped” can offer Resume, and anything said during the short stop is still captured. Resume continues the same meeting.
Browser meetings on Mac
Call-end detection differs by browser: picture-in-picture meeting-window detection works in Chrome only, while detecting a browser Leave click is supported for Google Meet in Chromium browsers on Mac. Check whether Flow is still recording when the call ends and stop it manually if needed.
A quiet Google Meet call can stop without a clear “meeting ended” signal. If the call picks the microphone back up, the pending stop is cancelled; changing audio devices can delay it. If you are presenting to silent or muted participants and the browser briefly releases the microphone, the recording can stop on its own — click Resume to carry on in the same meeting.
Browser meetings on Windows
Closing the tracked meeting tab can trigger an automatic stop. After a browser releases the microphone, stopping takes about 20–25 seconds unless Flow confirms the call ended sooner. Conference-page detection covers Chrome and Edge only; with other browsers, stop recording yourself when the call ends.
Flow keeps recording with a fullscreen or background meeting tab, with vertical tabs in Edge or Chrome, and with Teams or Zoom app windows opened from the browser — stop it yourself when the call ends.
Silence warnings, calendar and one-hour check-ins, and the length limit also apply on Windows; Mac sleep and user-switch stopping do not.
Maximum recording length
Settings → Notetaker → Maximum recording length offers 30 minutes, 1 hour, 2 hours or 3 hours; the default is 2 hours. The longest option stops at approximately 2 hours 58 minutes. All recorded segments count, so stopping and resuming does not reset the limit.
A warning appears two minutes before the 30-minute limit or five minutes before longer limits. To extend when offered:
Choose Yes.
Select a longer duration.
Click Save before the deadline.
Alternatively, choose End recording. At the longest setting, “Transcription will end soon” offers no extension. Dismissing or ignoring the warning does not prevent stopping, even with end-of-call stopping off.
Connection, sleep and storage interruptions
Connection lost or offline
Flow can keep recording locally while reconnecting, and missing live-transcript words can be recovered afterward from saved audio. An explicit account or policy refusal ends the attempt rather than retrying. “Connection lost” says “We lost the connection. Your audio was saved.” and has no Retry or Discard action.
Starting manually while offline records immediately: this includes the hub, notepad, Flow Bar, hotkey, tray, calendar Join and “Meeting detected” card. When Flow detects that the device is offline at start and no notepad is open, “Recording offline” confirms recording; this card is not shown when you explicitly chose offline recording.
Audio stays on the device for transcription after connectivity returns; if the audio can't be saved to disk, “Couldn't start recording” appears instead. For calendar auto-start, auto-join or automatic recovery while offline, Flow first asks you to confirm with Record offline. See Offline meeting recording.
Mac sleep or switching users
Capture ends when the Mac sleeps — not merely when its screen locks. On wake, Flow finalizes the recording, dated to when the Mac slept, and “Notetaker stopped when your Mac went to sleep” offers Resume into the same meeting. Rejoining the call after sleep also continues that same note.
Sleep does not postpone the length limit: a recording already past it on wake ends shortly afterward, dated to the moment the Mac slept. Switching Mac users stops recording immediately without a countdown and delays summary processing; if sleep occurred first, that earlier end time applies.
Storage full
An offline recording stops and keeps audio captured so far on the device — free up space and restart Flow, and it processes automatically.
Warning: A live-transcribed meeting can continue after a storage-write failure, but its partial local audio is discarded and later audio-based processing is unavailable. Transcript saving can also fail.
If the upload doesn't finish
Your recording is saved, and the meeting card and Summary tab explain upload delays.
Message | Action |
Waiting for a connection | Reconnect to let the meeting upload automatically. |
Can't reach our servers to upload this meeting. | Turn off the VPN or switch networks, then click Retry. |
Your connection is too slow to upload this meeting. | Flow keeps trying; switch to a faster network and click Retry. |
Your computer is out of storage. | Free up space on your computer, then retry. |
A finished meeting that cannot be sent shows Waiting for a connection in the recorder window and the Notetaker hub and stays listed until it uploads. A meeting you stopped while offline completes on its own once your connection returns or your computer wakes — no relaunch needed. If it remains stuck, use the retry control labelled Retry processing; this waiting state does not show the text button used for the other upload warnings.
Resume or recover a meeting
Warning: Processing after Resume can replace the final transcript. Resume appends to the live transcript and does not overwrite your own notes.
Open the saved meeting from the Notetaker hub.
Click Resume to append another recorded segment.
Resume waits for the meeting's unfinished save; if saving takes too long, it can refuse until saving finishes. When another meeting is recording, continuing a different saved meeting can require confirmation to switch; otherwise Resume is refused and the active recording continues. Choose Record as new meeting when recovery is unavailable and that action is offered.
Automatic stopping remains active after Resume, although Flow temporarily limits repeated early stops, and automatic recovery attempts are not unlimited.
Why Resume can be unavailable
A deleted transcript blocks Resume. Flow also refuses when both the recording limit and previously recorded duration are known and the duration has reached the limit. If either cannot be checked, this check alone does not block Resume, so an available button does not prove time remains.
If Flow can continue the paused recording still held open in the app, it need not reload saved audio; deletion and duration checks still apply. Otherwise, Resume requires nonempty, readable original audio within the resume window, which defaults to 7 days. Missing, empty, expired or unreadable audio hides Resume and prevents continuation, even if a button appeared earlier. Flow checks again before resuming; it does not silently start a replacement segment.
A deleted or unloadable meeting can also be refused. Setup, account access, recording locks, Notetaker availability and organization attendee rules still apply.
Missing or empty audio: “The original audio is no longer available”.
Expired or unreadable audio: “This recording can no longer be resumed” or “The original audio can no longer be read”.
Deleted transcript or exhausted time: “This meeting transcript is no longer available” or “This meeting has used its full recording length”.
Unavailable meeting: “This meeting could not be loaded” or “This meeting was deleted”.
Note: Local-audio retention defaults to 7 days for fully processed meetings and 30 days for incompletely processed meetings. These periods can vary, but the unprocessed period is never shorter. They do not guarantee audio is still present, and extended retention does not extend the resume window. Missing or deleted meetings, or meetings with a deleted transcript, use the normal retention period rather than the extended one. A deleted transcript blocks Resume but does not prove local audio has already been deleted.
Still stuck?
For permission errors, missing audio, failed starts, or unavailable Resume, see Troubleshooting Notetaker recording and audio. When contacting support, include your platform, meeting app, exact message and what you tried.