Webex Transcription on Mac: The On-Device, No-Bot Way

Webex is the meeting app a lot of people use because their employer or their customer told them to. Cisco still owns large pockets of healthcare, federal contracting, finance, legal, and any vertical where IT bought a Cisco contract a decade ago and never unwound it. If that’s the world you work in, you live in Webex whether you wanted to or not — and the “can I just get a transcript of this call” question runs into the same wall it does on Zoom or Teams.

Webex does have native transcription. It is also gated behind Webex Assistant, a paid add-on that the host’s Webex plan needs to include, and the host has to turn it on for the meeting. If you are a guest joining a customer’s Webex, or you are on the personal Webex plan, or your employer bought Webex Meetings without the Suite add-on, there is no checkbox you can flip on your end to get a transcript back.

The usual fallback is to invite Otter, Fireflies, or Read.ai’s bot to the call. That works. It also means a third party is logged into your customer’s Webex call and shipping every minute of audio to a cloud transcription pipeline. For some industries Webex is popular in specifically because of data-handling rules, that fallback is the wrong default by construction.

This post is about the third path: capturing a Webex call locally on a Mac running macOS 26 Tahoe, transcribing it on-device, and ending up with a Markdown transcript and an audio-anchored summary that never left the laptop. No Webex Assistant. No bot. No cloud upload.

What Webex gives you natively, and where it stops

Worth being precise about the gap, because Webex’s plan tiers are not intuitive:

Webex Free / Personal. No transcription. 40-minute meeting cap. Recording is local only and saves an MP4.
Webex Meet (around $14.50/user/mo list — check Cisco’s current pricing). Cloud recording, no Webex Assistant transcription unless you separately add the Suite or AI Assistant SKU.
Webex Suite (around $25/user/mo list). Includes Webex AI Assistant, which transcribes meetings, generates summaries, and labels speakers from the calendar context.
Webex Enterprise. Negotiated. Usually includes Suite features plus data-residency controls.

A few practical consequences:

If you are a guest on someone else’s Webex (very common in enterprise sales calls, vendor pitches, and customer onboarding), you have no host permissions. You cannot turn on Webex Assistant. You either get the transcript the host’s plan generated and the host is willing to share, or you get nothing.
If you are the host but on Meet without Suite, you can pay the per-user upcharge for Suite, or you can find another way to get the transcript.
If your IT department disabled Webex AI Assistant for compliance reasons — which is common in healthcare, finance, and federal — the feature is dark even on plans that technically include it.

If you have Webex Suite licensed and IT lets you use it and you are the host on the calls that matter, you do not need any of what follows. The rest of this post is for the case where one of those three conditions doesn’t hold.

The on-device alternative on a Mac

macOS 26 Tahoe ships the two building blocks that make local Webex capture possible:

ScreenCaptureKit audio-only filters. Instead of joining the meeting, the Mac subscribes to the audio a single process is playing — the Webex Mac app, or whichever browser has the Webex web client open. The scope is per-process, so Music, Slack call sounds, and AirPods notification chimes stay out of the recording.
SpeechAnalyzer, the on-device speech recognition framework Apple introduced at WWDC 2025. It runs on-device with no network round trip; MacStories’ independent testing put it roughly 55% faster than Whisper Large V3 Turbo on the same Apple silicon.

Because the capture point is the Mac’s own audio output, the meeting platform is interchangeable — the identical mechanism powers the Zoom no-bot flow and the Teams capture flow. To ScreenCaptureKit, Webex is simply another process making sound.

Dictanta wires those frameworks together with Apple’s Foundation Models on-device LLM for the post-meeting summary. What follows is the Webex-specific walk-through.

The full Webex capture flow

Assume a fresh install on macOS 26.

1. Join the Webex call however you normally do

Webex runs as a native macOS app, a web client, and a Chrome extension. All three send audio to the Mac’s audio output the same way. You can be signed in to a personal Webex account, an enterprise SSO, or joining as a guest with no Webex account at all. The capture path is the same.

You don’t need Webex Assistant licensed. You don’t need to be the host. You don’t need the meeting organizer to enable transcription. None of those gates apply to capturing the system audio your Mac is already producing.

Once the call is live, click Dictanta’s waveform icon in the menu bar and hit Record — the icon turns coral and pulses while the panel streams a live caption and a moving waveform. With Dictanta or its panel frontmost, ⇧⌘R starts a new recording; if you’d rather trigger it while Webex holds focus, switch on the optional “Global record shortcut” toggle (⌃⌥⌘R) in Settings, which is off by default.

On the very first system-audio recording, macOS asks for screen recording permission — ScreenCaptureKit gates its audio path behind the same TCC entitlement as video capture, even when no video frames are requested. One grant, and the prompt never comes back.

3. Dictanta scopes the capture to the Webex process

Because audio capture is per-process, Dictanta captures the Webex Mac app (or the browser running the Webex web client) rather than “anything making noise on this Mac.” Dictanta recognizes both Webex Meetings and the Webex App among the meeting apps it watches for, so its source picker’s This meeting option already points at the running call. The picker has exactly three options: My voice (just your mic), This meeting (the detected meeting app’s audio plus your mic), and Another app (the frontmost app’s audio plus your mic). If you have Spotify playing in another app, none of that ends up in the transcript.

On the two system-audio options your microphone is mixed in automatically: SpeechAnalyzer transcribes the combined stream, so the transcript covers Webex’s audio (everyone else) plus you. For solo recordings — a voice memo, a dictated draft — choose My voice.

4. Live captions during the call

While the recording runs, the menu-bar panel carries a live caption line and a moving waveform: one glance confirms the capture is healthy, and the caption earns its place the moment a counterpart reads out a contract clause or an account number you want to confirm on the spot. Neither appears in a screen share unless you open the panel on the shared display. The full transcript view comes after the call — double-click the recording in the library, or right-click it and choose Open in New Window.

Captions stream in near real time. Keep in mind the system-audio path exists only on macOS — iOS and iPadOS never let one app subscribe to another’s audio — so Dictanta on iPhone and iPad handles mic recordings and Voice Memo imports rather than Webex capture.

5. Stop the recording, get a finished summary

End the call — or hit stop in the menu-bar panel, or press the global shortcut again if you enabled it — and the post-processing runs entirely on the Mac:

A timestamped final transcript. Segments are tap-to-seek: click any line and the audio player jumps to that instant.
A structured recap from Apple’s Foundation Models. TL;DR, action items with best-effort owners and due dates, decisions, and open questions — generated on-device, same as the transcription, never uploaded.
Audio-anchored bullets. Each recap bullet points at the audio span behind it; clicking scrubs the recording there and highlights the matching transcript line. When the recap claims “the customer agreed to a Q3 renewal,” one click settles whether anyone actually agreed on this call.

6. Export, or just leave it

Exports cover Markdown, PDF, Word (.docx), SRT subtitles, and JSON: Markdown for Notion, Obsidian, Bear, Apple Notes, Logseq, and Craft; PDF or Word for anyone who just needs a readable document; SRT for video workflows; JSON for Shortcuts flows and your own automation.

By default your transcripts and summaries follow you to your other Apple devices via CloudKit. The audio never does — it stays on this Mac, full stop, and deleting a recording deletes its audio.

Webex-specific things worth flagging

A few quirks of Webex shape the flow slightly differently than Zoom or Meet.

Webex Personal and the 40-minute cap. Webex’s free plan limits meetings to 40 minutes. The cap is on the meeting itself, not on your ability to record it — Dictanta keeps recording continuously. When the meeting reconnects after the host restarts it, you can either keep the same recording running (one continuous file with a brief silent gap) or stop and start a new one. The former is usually what you want for action-item continuity.

Cisco AI Assistant transcripts vs. local transcripts. Webex AI Assistant produces transcripts in Cisco’s cloud, stored under the host’s Webex account, governed by Cisco’s data residency settings. Dictanta produces transcripts locally on your Mac, governed by nothing other than your own filesystem permissions. The two can coexist — nothing about local capture interferes with Webex’s own transcript if the host has it enabled.

Guest joins are the most common Webex case for this. Enterprise sales calls are disproportionately on Webex because the customer’s IT mandated it. As a vendor joining as a guest, you have no host permissions, no Webex Assistant access on your end, no path to the host’s transcript unless they email it to you. Local capture is the only route that lets a guest walk away with a transcript of the call they were just on.

End-to-end encrypted Webex meetings. Webex offers E2EE meeting modes for regulated verticals. The audio is still decrypted at your Mac in order to play through your speakers — that decrypted audio is what ScreenCaptureKit reads, and ScreenCaptureKit sees no plaintext anywhere other than where the OS already does. The capture path is the same as for a non-E2EE meeting; the E2EE only governs the wire, not what your Mac is playing.

Where the on-device path has limits

The tradeoffs deserve stating plainly — they’re the same ones covered from the Meet angle in the Meet write-up:

No speaker tagging. Webex Assistant knows which account is talking because Webex routes named audio streams; a local capture hears one mixed feed, and diarizing that mix on short clips is planned for a later release. If per-speaker labels are non-negotiable today, Webex Assistant (when you have it) or Otter’s calendar bot serves that need better.
Your presence is required. A bot can attend a meeting you skipped; a local recorder cannot. The Mac has to be in the call, awake, playing the audio.
No automatic Webex space push. Webex Assistant transcripts can post to a Webex space after the call. Dictanta exports Markdown, PDF, Word, SRT, or JSON on your Mac. If you need the transcript automatically posted into a Webex team space, the native flow with Suite licensed is structurally easier.
The call has to run on the Mac. If you join the Webex call on your phone instead of the Mac, there’s no Mac audio to capture. Capture works whenever the call itself runs on the Mac, whatever headphones you use — ScreenCaptureKit taps the Webex app’s audio stream directly, so the output device doesn’t matter.

If those gaps don’t matter to your meetings, the on-device path is the cleaner default.

When Webex Assistant is the right call

Three cases where Cisco’s built-in transcription is genuinely the better answer:

Your organization standardizes on the Webex Suite for compliance reasons. If customer contracts require transcripts to live in Cisco’s certified data center under your enterprise’s Webex tenant, swimming against that current with a local recording costs more than you gain.
You need speaker labels today, on every call, with no setup. Webex’s transcription labels speakers automatically because of the account-level signal. Local recording can’t see that signal.
You’re recording every enterprise meeting at scale with retention policies. A company-wide policy of “all customer calls transcribed and retained for 7 years” is better served by the native flow with your enterprise’s retention controls applied. Local recording on each person’s Mac is a worse fit for org-wide compliance.

If you’re not in any of those buckets — and most contractors, vendors joining as guests, or individual contributors on Webex Meet without Suite aren’t — the local path is better.

What this unlocks that Webex’s native flow doesn’t

No Webex Suite upgrade required. Webex Suite carries a real per-user upcharge over Meet alone (check Cisco’s current pricing). For a one-person shop on Webex Personal, or a small team on Meet without Suite, that adds up. The on-device path runs on the macOS 26 you already paid for.
Recording calls that aren’t yours. Joining a customer’s or vendor’s Webex as a guest gives you no transcription rights on their end. The local capture path is the only one that lets a guest walk away with a transcript at all.
No third-party cloud processor on the data path. Cisco’s own cloud is one thing. Adding Otter or Fireflies as a bot adds a second cloud processor on top. The local path adds zero new processors.
Sovereignty for federal and regulated work. A lot of Webex’s user base is in industries where adding any additional cloud vendor to the data path is a procurement hurdle. Local transcription removes the question.

Trying it on your next Webex call

Practical first-time flow:

Grab Dictanta from the Mac App Store — a small download; macOS fetches the SpeechAnalyzer language model once if it isn’t already on the Mac, and transcription then runs fully offline.
Launch it once and approve the microphone and screen recording prompts. Flip on the “Global record shortcut” toggle (⌃⌥⌘R) in Settings if you want to start recordings without leaving Webex.
When your next Webex call starts, hit Record in the menu bar (or press the global shortcut) — then ignore it for the rest of the meeting.
Afterward, the recording sits in the meetings list — named after the meeting topic once the summary lands, with the date, duration, and source type on the row. Open it for the transcript and summary.
Export Markdown if the destination is Notion or Obsidian, or leave everything in Dictanta and lean on its on-device full-text search.

Three full recordings are free, with no length cap — enough to put the local transcript side by side with whatever Webex Assistant recap the host may (or may not) have shared. After that it’s $9.99/mo, $79.99/yr, or $149.99 lifetime, and nothing is metered per minute: a three-hour quarterly business review transcribes the same way a ten-minute customer check-in does.

Bottom line

Webex’s native transcription is fine when you are the host, you have Webex Suite licensed, and your IT department lets you use it. For an enterprise user with the right plan, that path is the simpler answer.

For everyone else on Webex — guests on customer calls, Personal-plan users, Meet-plan users without the Suite SKU, anyone in a vertical where IT disabled Webex AI Assistant for compliance reasons — the local path is the missing option. Capture Webex’s system audio with ScreenCaptureKit, transcribe with SpeechAnalyzer, summarize with Apple Foundation Models, all on the Mac, no bot, no upload.

That is what Dictanta ships, the same way it ships the Zoom no-bot flow, the Teams no-bot flow, and the Meet on-device flow. If you are on Webex Suite and it’s working, keep it. If you’re not, the on-device path costs nothing to install and try on the next call.