Short answer: Dictation usually fails during a video call on Mac because the meeting app changed your input device, pushed a Bluetooth headset into low quality call mode, or claimed your dictation hotkey as a global shortcut. Fix the input device first, then the hotkey, then click into the text field before speaking.
You are in a meeting. Someone says something you need to write down, or you need to fire off a message in the chat panel, and dictation picks that exact moment to stop cooperating. Nothing appears. Or a few words appear and then it drops. Or the transcription comes out garbled in a way it never is when you are not on a call.
This is one of the most annoying failures because it is intermittent by definition. Everything works fine when you test it, then breaks under the one condition you cannot easily reproduce: a live call with other people waiting. The good news is that there are only about five real causes, and every one of them has a specific fix. Here they are in the order you should check them.
First, the myth: "another app is using the microphone"
The most common explanation you will read is that the meeting app has locked the microphone and no other app can get to it. On some operating systems that is genuinely how audio capture works, and an app can claim a device exclusively.
macOS is not usually one of them. Two applications can normally read from the same input device at the same time. You can be recording in one app while another app is capturing your voice for a call. If exclusive locking were the rule, screen recording with audio during a meeting would never work, and it does.
So while "the mic is busy" feels like the obvious answer, it is rarely the actual one. What is actually happening is subtler and more fixable.
Cause 1: The system input device changed under you
This is the single most common culprit and it happens silently.
Meeting apps keep their own audio device selection, separate from the one in System Settings. When you join a call and pick your headset inside Zoom, or when a headset connects mid call and the app auto switches to it, the system default input often follows. Your dictation tool, meanwhile, is listening to whatever the system default is, or to a device you selected once and forgot about. Now one of them is listening to your headset and the other is listening to the built in microphone, or worse, to a device that is currently muted at the hardware level.
A hardware mute switch on a headset is worth calling out separately, because it produces the most confusing version of this failure. The meeting app shows a mute indicator, so you know your mic is off for the call. Your dictation tool has no such indicator, so you speak into a physically muted microphone and see nothing. The system reports success because it captured audio. The audio was silence.
The fix
- Open System Settings, go to Sound, then Input, and note exactly which device is selected.
- Open your meeting app's audio settings and note which microphone it has selected.
- Make them match, or deliberately make them different if you want the call and your dictation to use separate hardware.
- Check the physical mute switch or inline mute button on your headset. Speak a test sentence and watch the input level meter in System Settings move.
That last step matters more than it sounds. The input level meter is the fastest ground truth on a Mac. If it does not move when you talk, no software fix in the world will help, and you have just saved yourself twenty minutes of debugging the wrong layer. We wrote a full walkthrough of that diagnosis path in Mac dictation microphone not working.
Cause 2: Bluetooth headsets drop into call mode
If you are using AirPods or most other wireless headsets, this is probably your problem.
A Bluetooth headset has two modes. In listening mode it is a high quality stereo output device with the microphone switched off. The moment any application starts using the microphone, the headset switches to a two way call profile. Output quality drops audibly, and the microphone side runs at roughly telephone quality rather than the full range signal a wired or built in microphone provides.
Joining a call forces that switch. So during a meeting, your dictation is being fed a much narrower, more compressed version of your voice than it gets the rest of the day. Transcription quality suffers in exactly the way people describe it: not a total failure, just noticeably worse. Words that were never a problem before start coming out wrong.
Add the meeting app's own noise suppression and automatic gain control on top, and you get a signal that has been processed twice for a purpose that has nothing to do with accurate transcription.
The fix
The cleanest answer is to stop using a Bluetooth headset as your dictation microphone during calls. Options, roughly in order of how well they work:
- Wired headset or USB microphone. No profile switching, no compression, and the mic position stays consistent. This is the single highest leverage change you can make.
- Bluetooth for listening, a different mic for speaking. Set your headset as the output device and the built in or USB microphone as the input. You keep the wireless audio and lose the call mode penalty.
- The Mac's built in microphone. Underrated. On recent Macs it is genuinely good in a quiet room, and it never switches profiles.
Our full comparison of what actually helps accuracy is in the best microphone for dictation, and if your Bluetooth setup is failing even outside of calls, Mac dictation not working with Bluetooth covers that specific case.
Cause 3: The meeting app stole your hotkey
This one is invisible until you know to look for it, and it explains the version of the failure where absolutely nothing happens. No error, no indicator, no partial text. You press your dictation key and the Mac acts as though you did not.
Conferencing apps register global keyboard shortcuts so you can mute, unmute, raise a hand, or toggle video without switching windows. Global means system wide. When your dictation hotkey overlaps with one of those, the meeting app receives the keystroke first and your dictation tool never hears about it. The overlap only exists while the meeting app is running, which is exactly why the problem appears during calls and vanishes afterward.
The classic collision is a modifier plus a single letter, but push to talk bindings are a common source too, since they tend to claim keys that people also like to use for dictation.
The fix
- Open the keyboard shortcuts section of your meeting app's settings. Zoom, Teams, and Meet's desktop wrappers all have one.
- Look for anything marked as global or system wide and compare it against your dictation hotkey.
- Change one of them. Turning off the meeting app's global scope while keeping the shortcut active inside the app usually solves it without giving anything up.
- If you would rather not hunt, just move your dictation hotkey to something no other app wants. A modifier key held on its own, or a function key, tends to be safe.
Voice Keyboard Pro lets you rebind its hotkey from Settings, which means you can sidestep the conflict entirely in about fifteen seconds rather than auditing every app's shortcut table.
Cause 4: The text went somewhere else
Sometimes dictation worked perfectly and the words simply did not land where you were looking.
Dictation on a Mac inserts text at the current cursor position in the frontmost app. Calls are unusually good at moving that target around. A screen share starts and focus jumps. A notification steals the front window. You click on the video grid, which is not a text field, so the cursor has nowhere to go. Full screen meeting windows are especially prone to this, because there is often no obvious text field on screen at all.
The result is text that vanishes, or text that shows up in the meeting chat when you meant it for your notes, which is a considerably worse outcome than nothing happening.
The fix
- Click directly into the text field you want before you start speaking, every time. Not the window, the field. You should see a blinking cursor.
- Take notes in a window beside the call rather than in the meeting app, so the target stays put while the meeting window does whatever it wants.
- If you frequently need to dictate into the chat panel, get in the habit of clicking the chat input box first as a deliberate step.
The general version of this problem, along with the fixes that apply outside of calls, is covered in dictation text appears in the wrong place.
Cause 5: Permissions and microphone modes
Two smaller causes worth ruling out once you have handled the big three.
Microphone permission. Every app that captures audio needs its own entry under System Settings, Privacy and Security, Microphone. Both your meeting app and your dictation tool need to be listed and enabled. A macOS update can occasionally reset these, and the symptom is a tool that worked yesterday and does not today. While you are there, check Accessibility permission too, since inserting text at your cursor in another app requires it.
Microphone mode. When an app is using your microphone, macOS shows a Mic Mode control in Control Center with options like Voice Isolation and Wide Spectrum. The setting is per app. Voice Isolation aggressively strips everything that is not identified as speech, which is helpful on a noisy call and occasionally unhelpful for transcription, particularly if you speak quietly or your room is very live. Wide Spectrum does the opposite and lets more of the room through. If your transcription quality changed suddenly and nothing else did, this is worth a look.
The 60-second triage checklist
When it breaks mid meeting and you do not have time to read an article, run this in order:
- Watch the input meter. System Settings, Sound, Input. Talk. Does the bar move? If not, it is hardware, a mute switch, or the wrong device. Stop here and fix that.
- Check the device match. Is the meeting app using the same microphone your dictation tool expects?
- Press the hotkey with the meeting app hidden. If dictation works when the meeting window is not frontmost but not when it is, you have a shortcut conflict.
- Click into a plain text field in a different app, such as a notes window, and try again. If it works there, it is a focus problem, not an audio problem.
- Switch off Bluetooth and use the built in microphone. If accuracy jumps, you found it.
Five steps, in that order, will identify essentially every version of this problem. Most people find it at step one or step three.
App specific notes
Zoom
Zoom keeps its own microphone selection and can automatically switch devices when new hardware appears. It also ships a fairly large set of global shortcuts, which makes it the most common source of hotkey collisions. Its "original sound" setting changes how heavily your outgoing audio is processed, which affects the call rather than your dictation stream, but it is a useful indicator of how much processing is being applied to your voice generally.
Microsoft Teams
Teams applies its own noise suppression with several levels. On a Bluetooth headset the combination of the call profile plus aggressive suppression is the harshest environment your voice will pass through all day. If your Teams calls are the only place dictation degrades, try a wired microphone before changing anything in software. Our guide to dictating in Microsoft Teams covers the chat and channel workflow in more depth.
Google Meet
Meet in a browser adds one more layer, because the browser also holds a microphone permission independently of the operating system. If Meet cannot hear you, check the browser's site permissions in addition to System Settings. Meet running in a dedicated window or a Chrome app shortcut behaves like a separate application for permission purposes.
Should you dictate during a live call at all?
Worth asking, because sometimes the fix is to change the workflow rather than the settings.
Dictating while other people can hear you is socially awkward and practically limited. You have to mute, which means missing the moment you were trying to capture, or you speak over someone. Neither is great. The people who successfully dictate during calls tend to be doing it in short bursts during natural pauses, or while someone else is presenting and their own mic is already off.
The higher value pattern is different. Capture nothing during the call, and dictate everything immediately after. The five minutes after a meeting ends is when your recall is at its absolute peak and your hands are the only bottleneck. Speaking at 130 to 150 words per minute, you can produce a full set of notes, three follow up messages, and two task descriptions in the time it would take to type the notes alone at a typical 40 words per minute. Even a fast typist at 80 to 100 words per minute is giving up most of that margin.
That is the case for treating dictation as a post meeting tool rather than an in meeting one, and it removes every problem described in this article at once, because the meeting app is no longer running.
Where Voice Keyboard Pro fits
Voice Keyboard Pro is a menu bar app for Mac. You hold a hotkey, speak, release, and the text appears at your cursor in whatever app you are using. There is no window to switch to and no separate transcription step, which is what makes the post meeting burst realistic instead of aspirational.
Three things about it are relevant to the failures above:
- The hotkey is rebindable. If a meeting app has claimed the key you want, change it in Settings rather than auditing every conferencing app you have installed.
- Smart Vocabulary handles the names. Colleague names, client names, product names, and internal acronyms are the words that get mangled worst on a degraded call microphone. You can add them once as a personal dictionary with replacement rules so they come out right every time.
- Meeting Mode is built for exactly this problem. On Mac it captures the meeting with speaker detection and produces AI notes, and calendar meeting detection means it knows when a meeting is happening. That is a different job from dictating into a chat box mid call, and it is the one worth automating. We go deeper on it in meeting transcription on Mac.
On the privacy question, which comes up immediately whenever meetings are involved: our server stores only operational pings. No audio and no transcript content.
Frequently asked questions
Can two apps really use the microphone at the same time on a Mac?
Generally yes. macOS does not typically hand one application exclusive control of an input device. When it feels like the meeting app has locked you out, the actual cause is almost always device selection, a Bluetooth profile switch, or a hotkey conflict.
Why does my transcription get worse only during calls?
Most often the Bluetooth call profile. The moment any app opens the microphone on a wireless headset, the headset switches to a narrower two way mode and your voice arrives compressed. Meeting app noise suppression on top of that compounds it. A wired microphone removes both layers.
Will muting myself in the meeting app fix it?
Software mute in the meeting app usually stops your audio from being sent to other participants without releasing the microphone, so the Bluetooth profile stays in call mode. A hardware mute switch on a headset is different and will block your dictation entirely, which is a frequent source of confusion.
Does dictation work in the meeting chat panel?
Yes, as long as you click into the chat input field first so there is a cursor for the text to land at. The most common failure here is speaking while the video grid has focus, which gives the text nowhere to go.
Does any of this apply to the iPhone keyboard?
Less so. The iPhone product is a custom keyboard with a built in mic button, so it works in any app that accepts a keyboard, and there is no global hotkey to collide with. Bluetooth call mode still applies if you are on a call with wireless earbuds.
Does it work offline?
No. Transcription requires an internet connection, and we would rather state that plainly than bury it.
The bottom line
Dictation breaking during video calls looks like a mysterious conflict and is almost always one of five specific, fixable things: the wrong input device, a Bluetooth headset in call mode, a stolen hotkey, focus landing somewhere other than your text field, or a permission that got reset. Run the five step triage in order and you will find it in under a minute.
Then consider whether you need to dictate during the call at all. The five minutes after the call, when everything is still fresh and nobody can hear you, is where the real speed is. Voice Keyboard Pro has a free tier with daily limits, which is enough to try that pattern after your next few meetings and see whether it holds up. Pro is $4.99 a month or $34.99 a year if it does.