1. Start Google Docs voice typing on a Mac
Open a document in Google Docs using the latest version of Chrome, Edge or Safari. Choose Tools → Voice typing, select the language above the microphone if needed, then click the microphone and speak at a normal pace.
Click the microphone again when you are finished. Google Slides exposes a related Tools → Dictate speaker notes command, but its voice-command support differs from Docs.
- Open a Google Docs document in a supported browser.
- Choose Tools → Voice typing.
- Allow microphone access when the browser or macOS asks.
- Click the microphone to start and stop.
2. Know where speech processing happens
Google’s current help page says the web browser controls the speech-to-text service: the browser determines how speech is processed, then sends the text to Google Docs or Google Slides.
That is a different boundary from on-device dictation. Review the browser’s current privacy terms and your Google Workspace policy before using Voice typing for sensitive material. An organization administrator can also disable the feature.
3. Use punctuation and editing commands
Google documents spoken punctuation such as “period,” “comma,” “question mark,” “new line” and “new paragraph.” Punctuation availability varies by language.
Voice commands for editing and formatting are available only in English, with both the account and document language set to English. Docs supports commands such as “select paragraph,” “bold,” “insert comment,” “go to the end of the line” and “stop listening.” Those commands are not available in Slides speaker notes.
4. Fix a missing menu or silent microphone
First confirm you are editing a document—not only viewing it—and that the browser is a current Chrome, Edge or Safari release. A managed Google Workspace administrator may have disabled Voice typing.
If the microphone appears but cannot hear you, check System Settings → Privacy & Security → Microphone and allow the active browser. Also inspect the browser’s site permission for docs.google.com, confirm the correct input device in Sound settings, close another app that may be using the microphone, and reload the document.
- Test the Mac microphone in another app.
- Check the browser in Privacy & Security → Microphone.
- Check the docs.google.com site-level microphone permission.
- Try a new document to separate document permissions from browser permissions.
5. Distinguish Google Voice typing from Apple Dictation
Google Voice typing is a Docs-owned feature with its own microphone panel and document-editing commands. Apple Dictation is a macOS input feature that can enter text in supported fields across apps. They can therefore fail for different reasons.
If Google’s microphone is unavailable but Apple Dictation works in TextEdit, inspect the browser, site permission and Workspace policy. If neither path hears the microphone, start with the Mac input and permission settings.
6. Choose a local cross-app workflow only when you need it
Google Voice typing is the right free first choice when the destination is already a Google document and its browser-controlled processing boundary is acceptable.
IraVoice 0.7.1 is a separate option for macOS 26+ Apple-silicon Macs when speech recognition should run on the Mac or one held-key workflow should be available across supported editable fields. Browser editors can expose custom fields differently, so IraVoice retains a clipboard fallback instead of claiming perfect insertion everywhere.