M4A is what Apple gear and most meeting tools hand you. Drop it in as-is and it transcribes to timestamped, editable text on your device.
Half the advice you will find for "m4a to text" starts with a detour: convert your M4A to MP3 first, then feed the MP3 to some uploader. Skip all of that. This tool opens the M4A directly, pulls the audio track out of it, and transcribes it in place: no conversion step, no file sitting on someone else's server, no free-minute countdown. The recognition happens inside this browser tab on your own machine, so a meeting recording stays as private as it was on your drive.
If M4A has ever felt like a slightly mysterious format that behaves differently from MP3 and WAV, the next section clears that up, because understanding what the file actually is explains both why other apps trip over it and why a browser handles it so easily.
An M4A is not really its own kind of audio: it is a wrapper. Inside it sits AAC-encoded sound, the successor to MP3 that Apple adopted across its devices, packed into the same box design that MP4 videos use. That is the whole trick: .m4a, .mp4, and .m4v are the same container, just carrying different cargo. An M4A carries only audio; an MP4 usually carries audio plus a picture. This is why a voice memo sometimes shows up on a PC labelled .mp4 even though there is nothing to watch. The container is identical, only the extension differs.
The standalone .aac extension is the bare AAC stream without that container around it, which is why it is the odd one out here: without the wrapper's index there is nothing to stream against, so raw .aac is read through a bounded whole-file path rather than the streaming one. Keep the "no size limit" expectation attached to .m4a, not to loose .aac. Then there is .m4p, the same container again, but wrapped in FairPlay copy protection from the old iTunes Store. Those cannot be decoded by anyone but Apple's own playback, and the app says so: it detects the protection and stops with a clear "copy-protected" message rather than grinding to a confusing error.
None of this is why other desktop programs choke, though. They choke because a lot of older Windows audio software was written for MP3 and WAV and never learned to unwrap an AAC-in-MP4 container. A browser did learn (decoding AAC is table stakes for playing web video), so this tool borrows that built-in ability instead of shipping a fragile codec of its own.
The classic source is a meeting tool's "audio only" export. When you record a Zoom call and choose the audio-only output, or pull the audio track from a Microsoft Teams recording, you get an M4A, a lean file of just the conversation, ideal for turning into written minutes. Mac's QuickTime does the same when you record an audio-only clip. iPhone Voice Memos are M4A as well; if that is your source, the voice memo to text page walks through getting the recording off the phone first. WhatsApp audio you have saved to a Mac frequently lands as M4A too, ready to drop straight in.
Here is a worked example. You have a forty-five-minute Zoom call exported as audio only: a single .m4a. You drop it in, the transcript begins scrolling within seconds, and by the time the call's wrap-up is being read you have already skimmed the decisions from the first ten minutes. You export it as plain text, tidy it into minutes, and the recording of a private business call never touched a third-party server.
.m4a file in. Meeting exports, QuickTime clips, saved WhatsApp audio, all go in without any conversion. Add several and they line up in a queue.Working with a different file type? Use the full audio transcriber, or jump to a format-specific guide: