Short answer: Google Meet has no dictation setting, so the fault is in macOS Dictation, your browser, or focus. Test in TextEdit first. If that works, click into the chat box again, check Dictation's microphone source matches your headset, and mute yourself in Meet before dictating so the call cannot hear you.
You are in a Google Meet call, someone asks for a link or a quick summary in the chat, and you reach for dictation because typing while listening is hard. Then it goes wrong. The microphone icon appears but no words show up. The words land in the wrong place. Dictation works fine in Notes but refuses to cooperate the moment a call is running. Or, worst of all, it works perfectly and everyone on the call hears you reciting your chat message out loud.
Google Meet makes dictation trickier than almost any other web app because two things want your microphone at the same time: the call and the dictation tool. Add a browser in the middle, a chat panel that loses focus easily, and headphones that switch audio modes when a microphone opens, and there are plenty of places for things to break.
The good news is that the failures fall into a handful of categories. The thirty-second test below tells you which category you are in, and the nine fixes are ordered so the most common causes come first.
Start here: the thirty-second split test
Google Meet does not have a dictation feature of its own. Its live captions are a separate thing that only displays what people say in the call; they never type into a text field for you. That means a dictation failure inside Meet always belongs to one of three layers:
- macOS Dictation (or whichever dictation tool you use). It listens to a microphone, turns your speech into text, and inserts that text into whichever field currently has keyboard focus.
- Your browser. Meet runs inside Chrome, Safari, Edge, Firefox, or a Chrome-installed Meet app window. The browser decides which part of the page receives inserted text.
- The call itself. Meet holds a microphone open while you are in a call, and that can change how your audio hardware behaves for everything else.
Run this test before changing any settings:
- Open TextEdit, click into a blank document, and start dictation. Speak one sentence.
- If nothing appears in TextEdit either, the problem is macOS Dictation or your microphone. Start at Fix 1 and Fix 2.
- If TextEdit works, leave it open, join a test call in Meet (or open a new meeting on your own), and dictate into TextEdit again while the call is running.
- If dictation now fails in TextEdit too, the call is interfering with your audio. Go to Fix 3 and Fix 4.
- If TextEdit still works during the call but the Meet chat box does not, the problem is focus or the browser. Go to Fix 5 through Fix 7.
That split saves a lot of time, because the fix for "the call grabbed my headset" is completely different from the fix for "the chat box lost focus."
Fix 1: Confirm Dictation is on and the shortcut actually fires
Open System Settings, go to Keyboard, and find the Dictation section. Make sure Dictation is switched on and note which shortcut is assigned. On many Macs the default is pressing the microphone key or pressing a modifier key twice, but it may have been changed.
Watch for the small microphone indicator when you press the shortcut. If it never appears, the shortcut is not reaching macOS. Common reasons include a keyboard utility that remaps keys, an external keyboard without the dedicated microphone key, or a browser extension that captures the same key combination. Try switching the shortcut to a different option in Dictation settings and test again.
If you are on a work Mac enrolled in device management, your organisation may have disabled Dictation through a configuration profile. In that case the toggle may be greyed out or missing, and only your IT team can change it.
Fix 2: Check the microphone source and language
In the same Dictation section, there is a microphone source setting. It can be set to automatic or to a specific device. This matters in Meet more than anywhere else, because Meet has its own separate microphone choice in its audio settings. It is entirely possible for Meet to be using your headset while Dictation listens to the built-in microphone on a closed MacBook lid or a webcam sitting across the room.
Pick the microphone you actually speak into and set it explicitly in Dictation settings rather than leaving it to guess. Then check the Dictation language. If it is set to a different language or regional variant from the one you are speaking, results will be poor or empty.
Fix 3: Stop the call from breaking your Bluetooth headset
This is the most Meet-specific cause, and it confuses people because it looks random. Many Bluetooth headphones, including popular earbuds, switch into a lower-quality audio mode when any app opens their microphone. Joining a Meet call triggers that switch. Audio sounds thinner, and dictation accuracy can drop sharply because the microphone signal it receives is lower quality too.
Worse, some headsets briefly disconnect or reconnect during the switch. If dictation starts listening at that moment, it can lose the microphone entirely and return nothing.
Things to try, in order:
- Join the call first, wait a few seconds for the headset to settle, and only then start dictating.
- In Meet's audio settings, choose the same microphone that Dictation uses, so both apps share one device instead of fighting over two.
- If your headset keeps misbehaving, use a wired headset or a USB microphone for calls where you expect to dictate.
- As a test, disconnect the Bluetooth headset and try the built-in microphone. If dictation suddenly works, the headset profile switch was the cause.
Fix 4: Mute yourself in Meet before you dictate
This one is less a fix than a rule, but it solves two problems at once. When you dictate into the Meet chat while unmuted, everyone on the call hears every word you say to your dictation tool. That is the single most common Meet dictation mistake, and it is embarrassing when the message was meant to be quiet.
Muting also helps accuracy. If your speakers are playing other participants' voices, an open microphone can pick them up, and dictation may transcribe a colleague's sentence into your message. Use headphones so call audio does not leak into the microphone, and mute yourself in Meet first. On a Mac, Command+D toggles your Meet microphone, and you should see the microphone icon turn red before you start speaking to dictation.
Be aware that some Meet versions offer a hold-to-talk behaviour where holding the spacebar temporarily unmutes you. If the spacebar is being captured by Meet while focus is not in a text field, you can unmute yourself by accident. Make sure your cursor is inside the chat box before you press anything.
For more on keeping in-call dictation private and useful, see our guide on how to dictate in Google Meet on Mac.
Fix 5: Make sure the cursor is really in the chat box
Dictation types into whatever has keyboard focus, and in Meet, focus moves around more than you might expect. Clicking on the video grid, the participant list, a reaction button, or the screen someone is presenting all pull focus out of the chat box, even if the chat panel is still visible.
Signs that focus has moved: nothing appears, or the text lands in a different field such as the Meet search box or your browser's address bar. The fix is simple but easy to forget. Click directly inside the chat message field, confirm the text cursor is blinking there, and only then start dictating.
If the chat panel closes when you click elsewhere, reopen it with the chat button, click into the field again, and try once more. Avoid clicking anything else between placing the cursor and releasing your dictation shortcut.
Fix 6: Rule out the browser
If dictation works in TextEdit and in other websites but not in Meet, try the same call in a different browser. If Meet works in Safari but not Chrome, the problem is specific to that browser setup.
Common browser-level causes include:
- Extensions. Grammar checkers, meeting-note extensions, and keyboard shortcut extensions can intercept text input or add their own overlay to Meet. Open a private window, where most extensions are disabled by default, and test again.
- The Meet app window. If you installed Meet as an app from Chrome, it runs in its own window. Some people find focus behaves differently there than in a normal tab. Try the regular tab.
- Out-of-date browser. Update the browser and relaunch it fully, not just the tab.
- Managed browser policy. Work-managed browsers can restrict extensions, permissions, or input behaviour. If your browser shows that it is managed by your organisation, check with IT.
Browser microphone permissions are worth a quick look too. Meet itself needs microphone access in the browser and in macOS Privacy & Security settings for the call to hear you. System Dictation uses its own access, so a blocked Meet permission usually breaks the call, not dictation. If you use a dictation tool that runs as its own app, that app needs its own microphone permission in macOS. Our Chrome dictation troubleshooting guide walks through the browser side in more detail.
Fix 7: Stop screen sharing from getting in the way
When you present in Meet, two things change. First, if you share your entire screen, everyone can see the dictation indicator and every word as it appears in the chat box. Second, sharing a tab or window can move focus to the shared content, so your next dictation goes nowhere.
If you need to dictate while presenting, share a specific window or tab rather than the whole screen, then click back into the Meet chat field before dictating. If you are dictating notes in another app during a presentation, keep that app off the shared window entirely.
Fix 8: Shorten what you dictate into chat
The Meet chat box is built for short messages. Long, multi-paragraph dictation into it tends to go badly: line breaks may send the message early, formatting disappears, and a mid-sentence focus change can split your message into fragments.
For anything longer than two or three sentences, dictate into a notes app or document, read it over, then paste it into chat. This also gives you a chance to fix names and numbers before your colleagues see them.
Fix 9: Restart in the right order
If none of the above solved it, a clean restart often clears a stuck audio or dictation process. Do it in this order:
- Leave the Meet call.
- Quit the browser completely (Command+Q, not just closing the window).
- In System Settings, turn Dictation off, wait a few seconds, and turn it back on.
- Disconnect and reconnect your headset, or switch it off and on.
- If it still fails, restart your Mac.
- Test in TextEdit first, then rejoin the call and test in the chat box.
Testing in TextEdit before rejoining tells you whether the restart fixed dictation itself or whether the problem only appears once a call is running again.
Google Meet behaviours that are not actually bugs
A few things feel broken but are working as designed:
- Captions do not type anything. Meet's captions show speech on screen for the call. They are not a dictation tool and cannot fill in chat or documents.
- Meet's noise cancellation does not help dictation. Any noise filtering Meet applies affects what other participants hear. Your dictation tool receives the microphone signal separately.
- Dictation pauses when you stop talking. Built-in dictation can stop listening after a period of silence. In a meeting, where you pause to listen, it may time out before you finish your thought.
- Spoken punctuation is literal. Saying "comma" or "question mark" produces punctuation in some tools and the actual word in others. If you see the word, check our guide on dictation typing the word "period".
When the words come out wrong, not missing
Sometimes dictation works but the text is wrong: colleague names spelled differently, project codenames turned into ordinary words, product names mangled. Meetings are full of this vocabulary, which is exactly the kind of language general dictation handles least well.
Built-in macOS Dictation does not offer much control here. Voice Keyboard Pro has Smart Vocabulary, a personal dictionary with replacement rules, so you can add the names and terms that keep coming out wrong and have them replaced automatically. It works the same way everywhere on your Mac: hold a hotkey, speak, release, and the text appears at your cursor, whether that is the Meet chat box, a doc, or an email.
A calmer way to handle meeting text
Most people reach for dictation in Meet for one of two reasons: answering chat without breaking their train of thought, or capturing notes. These are different jobs and deserve different tools.
For chat, the fixes above are usually enough. Mute, click into the field, dictate a short message, and check it before sending.
For notes, dictating into chat or a document while also listening and talking is hard to do well. Voice Keyboard Pro's Meeting Mode on Mac is built for that job instead, with speaker detection and AI notes, and it can detect meetings on your calendar so you are not scrambling to start it when the call begins. If you record a meeting, make sure everyone knows and that it fits your organisation's policies. For more on that workflow, see our guide to meeting transcription on Mac.
On privacy, Voice Keyboard Pro's servers store only operational pings. No audio and no transcript content is stored.
Frequently asked questions
Does Google Meet have its own voice typing?
No. Meet has live captions that display speech during a call, but it has no built-in feature that types into the chat box or any other field. Voice typing in Meet relies on macOS Dictation or a separate dictation app.
Why does dictation work in Zoom chat but not Google Meet?
Zoom is a native Mac app, while Meet runs inside a browser, so browser focus, extensions, and page behaviour all come into play. Run the TextEdit split test above, then work through the focus and browser fixes. Our Zoom dictation fix guide covers the Zoom side.
Can people in the call hear me dictating?
Yes, if you are unmuted. Your dictation tool and Meet can both hear your microphone at the same time. Mute yourself in Meet before you dictate anything you do not want the call to hear.
Why did my dictation accuracy drop as soon as I joined the call?
Usually because a Bluetooth headset switched into a lower-quality mode when Meet opened its microphone. Try a wired headset, or make sure Dictation and Meet are both using the same microphone.
Does this work on iPhone?
The Meet app on iPhone uses the iOS keyboard for chat, so dictation there depends on the keyboard's mic button. The Voice Keyboard Pro iPhone keyboard has a built-in mic button for dictation in any iOS app, including Meet chat. The same rule applies: mute yourself first.
Quick reference
- Nothing works anywhere: Fix 1 and Fix 2 (Dictation settings, microphone source, language).
- Breaks only once a call starts: Fix 3 and Fix 4 (headset mode, mute, speaker echo).
- Works in TextEdit, not Meet chat: Fix 5 and Fix 6 (focus, browser, extensions).
- Breaks while presenting: Fix 7 (share a window, click back into chat).
- Long messages go wrong: Fix 8 (dictate elsewhere, then paste).
- Still stuck: Fix 9 (restart in order, test in TextEdit first).
Most Google Meet dictation problems come down to three things: a headset that changed modes when the call started, a cursor that left the chat box, or dictation listening to a different microphone than the one you are speaking into. Check those three first, and remember to mute before you speak.
The words land at your cursor in whatever app you are already in — Mail, Slack, Word, a browser form. No dictation window, nothing to copy across.
Free forever for casual use · Apple Silicon & Intel