How to transcribe audio in Google Docs (what Docs does and doesn’t do)
You recorded the meeting, opened Google Docs, and looked for the transcribe button. There isn’t one. The menu has voice typing, there are third-party add-ons, but nowhere to drop the .m4a file sitting on your phone and get the text back.
This is not a temporary gap. Docs works with live voice input from a microphone, not with files. Knowing exactly where that line is saves you the next half hour of clicking through menus.
The short answer
Google Docs transcribes what you speak into the microphone, in real time. It does not transcribe an audio file you upload.
The official help page describes a single path: open a document in a supported browser and use Tools → Voice typing. A microphone box appears, you click it and talk, and the browser itself handles the speech-to-text conversion, not Docs (Google Help, Type and edit with your voice).
It works in recent versions of Chrome, Edge and Safari, with your computer’s microphone enabled, and Brazilian Portuguese is on the supported language list. It is genuinely useful — for something else.
What Voice Typing is actually for
It was built for writing by dictating, not for transcribing recordings.
It works well when:
- You need to draft a report, a long email or a first pass at something, and you type slower than you speak.
- Your hands are busy and you want to capture an idea before it disappears.
- You want to dictate a short passage and fix it in place: you can move the cursor and correct without turning the microphone off, and right-click the words underlined in gray to see alternative suggestions.
It works badly when:
- The audio already exists. The only way through is to play the recording on a speaker and let the microphone pick it up. The sound gets compressed twice, room noise comes along, and accuracy drops immediately.
- More than one person is talking. Voice typing does not separate speakers; a five-person meeting becomes one undifferentiated block you cannot attribute.
- The audio is long. An hour of meeting means an hour with the microphone open, with your computer tied up.
If your situation is “I have a file and I want the text”, Voice Typing is not the route. It is the route for someone who is about to speak.
What Google does offer for audio you already recorded
There is one real exception: Google Meet transcribes meetings. But it is narrower than it looks.
The feature sits under Meeting tools → Transcription → Start transcription during a call, and it only works on a computer, laptop or Android device. It is not on every account: the eligible editions include Business Standard, Business Plus, Enterprise Starter, Enterprise Standard, Enterprise Plus, Teaching and Learning Upgrade, Education Plus and Workspace Individual. A free Gmail account does not have it (Google Meet Help, Use transcripts).
Other details that surprise people:
- Only spoken words are included. Chat messages are left out; to capture those, you have to record the call.
- The transcript is not necessarily yours. Meeting transcripts are saved to the meeting organizer’s Google Drive, in the “Google Meet” folder, with a subfolder for each meeting.
- There are eight languages: English, French, German, Italian, Japanese, Korean, Portuguese and Spanish.
So it works when the audio was born inside Meet and the account is a paid Workspace edition. For audio from WhatsApp, a phone recorder, an in-person class, Teams, Zoom or a YouTube video, Google offers transcription in none of those products.
The path that works for any file
For any recording that is not a Meet call, the flow is: turn the audio into text in a transcription tool, then bring the result into Docs, where the review and the sharing happen.
In Sintesy, the full route is this:
- Send the file. In the dashboard, click New → Upload file — or just drag the file anywhere on the screen. It accepts audio (mp3, m4a, wav, ogg, opus, aac, flac, amr, wma and others), video (mp4, mov, mkv, webm, avi), PDF, DOCX and TXT. Scanned PDFs go through OCR, so a photographed document also produces text.
- Get the synthesis. The output is more than a transcript: you get a summary, a mind map and, when the content is actionable, a checklist. The transcript is what you take to Docs; the summary is what you read before reviewing 40 minutes of speech.
- Bring it into the document. On the free plan, select the transcript text and paste it into Docs. On Pro, use Download → Export as DOCX, upload the file to Google Drive and open it with Docs — Google converts the
.docxinto an editable document automatically. That is the path that keeps headings and lists instead of flattening everything into one paragraph. - Shortcut for your phone. If the audio arrives on WhatsApp, forward it to the number connected to your account and get a notification with the link to the synthesis back, without touching a computer.
If the source is a meeting, the flow for transcription into summary, mind map and checklist is the same, with one difference: you start from a Meet, Teams or Zoom link instead of a file.
Voice typing, Meet transcripts or a transcription tool?
| Voice typing (Docs) | Meet transcripts | Sintesy | |
|---|---|---|---|
| Accepts an audio file | No | No | Yes (audio, video, PDF, DOCX, TXT) |
| Works with an old recording | No | No | Yes |
| Separates speakers / identifies participants | No | Yes, inside the call | No — an uploaded file does not come separated by speaker |
| Languages | Broad list, including pt-BR | 8 languages | Portuguese, English and Spanish in the synthesis |
| Where the text lives | In the document you are typing | Organizer’s Drive | Your account, with export |
| Cost | Included in Docs | Paid Workspace editions | Free plan with limits; Pro without duration caps |
The practical reading: use voice typing when you are the source of the text; Meet transcripts when the conversation happens in Meet and the company pays for Workspace; a transcription tool when the audio comes from anywhere else.
The limits you hit halfway through
Worth knowing before you start, because they all show up at the worst moment — when the meeting is over and you need the text.
On Sintesy’s free plan: 60 minutes of audio per day, up to 10 syntheses per day and files up to 20 MB. The transcript, the summary and the checklist are delivered up to 2,500 characters. For a two-minute voice message that is more than enough. For a one-hour meeting the text arrives cut short — and that is exactly where the “transcribe, then move it to Docs” flow breaks.
On the Pro plan: no 2,500-character cut, uploads up to 2 GB (PDF up to 64 MB), export to PDF, DOCX, SVG and image, and no transcription cap.
If your use is occasional — one class, one interview, one client audio a week — the free plan covers it. If this is part of your job, the character cut is the first limit you will hit.
Five mistakes that cost time
1. Hunting for an audio upload in the Docs menu. There isn’t one. The input is the microphone. Every attempt costs a few minutes of searching.
2. Playing the audio on a speaker so Docs can dictate it. Quality degrades twice over, and the transcript comes out worse than any tool reading the original file would produce.
3. Exporting to PDF and trying to paste the text into Docs. PDF does not reliably give back editable text. Use DOCX, or copy the transcript from the app itself.
4. Assuming Meet transcripts cover in-person meetings. They only exist inside a Meet call, on an eligible Workspace account. A meeting in the physical room does not qualify.
5. Leaving the text only in the app. A transcript that never becomes a reviewed, shared document dies in a history list. Docs is the right destination precisely because that is where the text gets commented on, corrected and sent to people who have no account anywhere.
Docs is the destination, not the tool
The confusion is understandable: Google ships transcription inside one product (Meet) and voice typing inside another (Docs), so expecting Docs to do the same with a file is natural. It just isn’t what it does.
The flow that does not frustrate is the reverse of what most people try: the audio becomes text in a transcription tool, and Docs receives that text for the part where it is unbeatable — reviewing, commenting, versioning and sharing with whoever needs to read it. If the recording is a meeting and you want to compare transcription options by source, it is worth seeing how to transcribe audio in Word too: the boundaries in each editor are similar, and so are the workarounds.


