Zoom writes meeting audio as an M4A file, and no Zoom help page offers an MP3 anywhere. The cloud recording settings article states the container in one flat sentence: "Audio files are in the M4A file format." There is no export option, no checkbox, no alternate format. If a podcast host, an editor, or some internal tool insists on MP3, the conversion is yours to do.
One FFmpeg command handles it. The part worth understanding first is that this particular conversion cannot be done the cheap way.
The command
ffmpeg -i audio98796876.m4a -c:a libmp3lame meeting-audio.mp3That input filename is not invented. Zoom's file-format article uses audio98796876.m4a as its own worked example of an audio-only recording, because Zoom does not name these files after the meeting: "M4A: Audio-only file that is named audio[random number].m4a by default."
Two Zoom pages write that placeholder differently — the file-format article says audio[random number].m4a, while the article on starting a computer recording says "The audio-only file (M4A) is named audio[number].m4a." Either way, the number is arbitrary, so copy the real name off disk rather than typing what you expect it to be.
What each flag does
-i audio98796876.m4anames the input. Quote the whole path if it contains spaces — Zoom's default folders sit underDocuments, andC:\Users\[Username]\Documents\Zoomon Windows or/Users/[Username]/Documents/Zoomon Mac is where the files land unless someone changed the storage location.-c:a libmp3lameselects the MP3 encoder. This is the flag that makes the output an actual MP3 rather than a renamed file.
You will see -vn in most examples, copied over from video-to-audio commands. FFmpeg's documentation describes it, as an input option, this way: "As an input option, blocks all video streams of a file from being filtered or being automatically selected or mapped for any output." A Zoom M4A is, in Zoom's own words, an "Audio-only file" — there is no video stream in it for anything to block.
Why you cannot stream-copy your way out of this
The fast trick with FFmpeg audio is stream copy — moving packets into a new container without touching them. FFmpeg's documentation is explicit about why that is attractive:
"Streamcopy is useful for changing the elementary stream count, container format, or modifying container-level metadata. Since there is no decoding or encoding, it is very fast and there is no quality loss."
Read the scope of that sentence carefully: stream count, container, container-level metadata. Not the codec. Stream copy can move an audio stream from one wrapper to another, but it cannot turn whatever is inside a Zoom M4A into MP3 data.
So M4A to MP3 is a real conversion: decode, then re-encode. That is a second lossy generation on top of whatever Zoom already did. It is unavoidable if you genuinely need MP3, but it is a good reason not to do it out of habit. If the destination accepts M4A, keep the M4A. The same reasoning, in more depth, is in extracting audio without re-encoding.
One more thing Zoom does not tell you: its help pages describe the M4A only as an "Audio-only file" and never name the codec inside it. Plenty of write-ups assert what it is. If that matters to your pipeline, run ffprobe on the file and read it off the output instead of trusting a blog, or check the official documentation.
If you do not want to install FFmpeg
For one meeting, a command-line install is a lot of setup. The same conversion runs in a browser tab:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
The file is read from disk, converted locally, and handed back — nothing is uploaded to a server, which matters more than usual when the file is a recording of a private meeting. It is FFmpeg compiled to WebAssembly, driven through a form instead of a shell. See all Clapr tools for the rest, or the M4A to MP3 converter on its own page.
Variations
Every participant at once. If separate audio tracks were recorded, Zoom puts them in a dedicated subfolder: "Once in the Audio Record folder, each participant's audio track will be listed as its own file. Each file name begins with the participant's name." Zoom's naming pattern for these is audio[Name][random number].m4a, with audioJohnSmith98796876.m4a given as the official example — and the file-format article scopes per-participant tracks to "(computer recording only)."
Two Zoom pages disagree on how many speakers this covers: the cloud recording settings article says it "Records up to 200 speakers individually," while the desktop app settings article says "Record separate audio files for up to 80 participants." Both pages also note that phone callers get collapsed together; the cloud page words it as "The audio for all users who join by phone will be merged into one audio file," so do not expect a track per dial-in participant.
From inside that folder:
for f in *.m4a; do
ffmpeg -i "$f" -c:a libmp3lame "${f%.m4a}.mp3"
doneRenaming the output. FFmpeg writes a new file and leaves the M4A alone, so name the MP3 whatever you like. Zoom does make one request about naming meeting files: "We recommend you do not use the words Zoom, Personal Meeting Room, or My Meeting when saving your meeting files." Zoom does not say why.
Troubleshooting
There is no M4A in the folder. The audio-only file is not guaranteed. Zoom lists the formats as "some of the following file formats," and the separate audio file is a setting: "Record audio-only files: Record the audio of the video separately. Choose to record one audio file for all participants, a separate audio file of each participant, or both."
The folder only contains .zoom files. Then the recording never finished converting. Zoom's troubleshooting page says that after a meeting ends "you should see double_click_to_convert_01.zoom and double_click_to_convert_02.zoom," and that double-clicking starts the conversion by hand. No M4A exists until that completes — see converting a Zoom recording to MP4 for the full path through that.
Do not rename anything mid-conversion. Zoom warns that if you change the name of the double_click_to_convert.zoom files while the meeting is still converting, "it may corrupt the file and not convert correctly." Wait for the M4A to appear, then rename.
FFmpeg says the file does not exist. Almost always a path problem, not an FFmpeg problem — either the shell is in the wrong directory or the filename has spaces and is unquoted. Drag the file into the terminal instead of typing its name.
FAQ
Can Zoom export audio as MP3 directly? No. Zoom's documentation names one audio container — "Audio files are in the M4A file format" — and offers no MP3 option anywhere in the recording settings. Every "Zoom MP3 export" you have read about is a conversion done after the fact.
Why is my file not called audio_only.m4a?
Because Zoom never called it that. Search results widely repeat audio_only.m4a and Zoom_0.mp4 as the default names; Zoom's actual pages say audio[random number].m4a and video[random number].mp4, with a random number that differs per recording.
Is converting Zoom M4A to MP3 lossless? No. Lossless copying only works when the codec stays the same — FFmpeg's guarantee that "there is no quality loss" applies to stream copy, which changes the container and not the codec. Going to MP3 means a decode and a re-encode.
How do I convert every participant's track?
Open the Audio Record subfolder inside the recording folder, where per-participant tracks are stored one file per speaker, and run the loop above. Note that Zoom scopes per-participant track files to computer recordings.
Should I convert at all? Only if something downstream actually requires MP3. If your editor, player, or host accepts M4A, converting just adds a lossy generation for nothing. More command-line recipes are in the FFmpeg guides.
Zoom quotes from Zoom's support articles on recording file formats, cloud recording settings, starting a computer recording, and troubleshooting computer recording issues; FFmpeg quotes from the FFmpeg documentation, sections "Streamcopy" and "Main options". All checked 16 September 2026.
