How to convert M4A to MP3 on a Chromebook
They are on ChromeOS, cannot install the .exe every guide recommends, and may be on a school-managed device where extensions are blocked and uploads to unknown sites are filtered. No dedicated article for this exists anywhere.
ChromeOS has no audio converter built into it, and it cannot run the Windows or Mac software that every other guide recommends. So the answer on a Chromebook is to convert in a browser tab: open the M4A to MP3 converter, drop the .m4a on it, choose MP3, and save what comes out. The encoder is FFmpeg compiled to WebAssembly, running inside the page on your own processor, so there is nothing to install and nothing is sent anywhere. On ChromeOS that is not a workaround for the lack of a real app. It is the shortest route that exists.
One thing to accept before you start: M4A to MP3 decodes one lossy format and re-encodes into another, and no tool on any platform can put back what the AAC encoder already discarded. Pick 192 kbps, or the variable-bitrate option, and stop thinking about it — at that setting almost nobody picks the MP3 out from the source in a blind test. M4A vs MP3 has the longer version.
Why the desktop guides are useless here
Search for this and you get pages telling you to install Audacity, VLC, fre:ac or a £30 converter. None of those has a ChromeOS build. There is no .exe to run, no .dmg to mount, and the Files app will not do anything useful with either if you download one. iTunes, the answer half the internet still gives, has not existed on any platform Chromebooks can reach.
Nothing in ChromeOS itself converts audio either. The Gallery app plays an .m4a perfectly well, because Chrome decodes AAC natively — which is why Chromebook users usually discover the problem only when something else refuses the file. Drive and Docs do not convert audio, and there is no right-click Convert to anywhere in the Files app.
That leaves four real routes, and they differ mostly in what your Chromebook is allowed to do.
| Route | Needs installing | On a managed Chromebook | Whole folder at once |
|---|---|---|---|
| Browser converter | Nothing | Works, unless the domain itself is filtered | No, one file at a time |
| Android app from Play | The app | Only if the Play Store is enabled | No |
Linux (Crostini) with ffmpeg | Linux, then ffmpeg | Only if policy allows Linux | Yes, one command |
| A Chrome Web Store extension | An extension | Rarely — extensions are allowlisted | Varies |
| Desktop converters | — | Will not run at all | — |
Converting in the tab, and where the file lands
- Open the converter and drag the file onto it. The ChromeOS file picker is the Files app, so you can reach anything in My files, Google Drive, Play files or a plugged-in SD card from the same dialog.
- The page reads the file first and tells you what is really inside it. An
.m4ausually holds AAC, but it can hold Apple Lossless, and the extension does not say which — the two differ in size by roughly five times. - Choose MP3 and a bitrate. 192 kbps is the default. For a lecture or an interview, 128 kbps folded to mono is smaller and sounds no worse on speech.
- Convert. The result is saved through Chrome's normal download path, which by default is My files > Downloads.
If you would rather each file went straight to Drive or to a USB stick, turn on Settings > Downloads > Ask where to save each file first. Chrome then opens the Files app every time and Drive is one of the destinations, which saves the usual dance of converting into Downloads and dragging it across afterwards. Worth doing on a 32 GB Chromebook, where Downloads fills up faster than anyone expects.
Two honest caveats. The first visit fetches a 32 MB engine, cached for a year afterwards, so do it on the school or home Wi-Fi rather than a phone hotspot. And M4A to MP3 can never be a stream copy — only a copy is close to immediate, and this job has to decode and re-encode every sample. Entry-level Chromebooks are not fast, so budget a fraction of the recording's length: a three-minute song is a few seconds of work, a 45-minute lecture is long enough to go and do something else.
Chromebooks play M4A fine, so you are converting because something else demanded MP3. Plenty of things that look like they demand it do not — Google Drive, Classroom, most transcription services and most learning platforms take M4A directly. If you convert anyway you pay a generation of quality for nothing. Try the original once before you re-encode it.
A Chromebook-specific bonus: ChromeOS's own screen recorder (Ctrl + Shift + Show windows, then the record button) writes a .webm into Downloads, and its audio is normally Opus. That decodes here without complaint, even though this build cannot write Opus back out, so a recorded call or lesson can become an MP3 with the same drag. The extract audio from video tool takes the soundtrack out and leaves the picture behind.
Managed and school Chromebooks
If your Chromebook was handed to you by a school or an employer, half the advice on the web is already off the table. Administrators routinely switch off the Play Store, block the Linux development environment, and allow only an approved list of extensions — settings pages show a small building icon and the words managed by your organisation where the control used to be.
A page that does its work in the tab survives most of that, because it needs no install and no permission. It also sidesteps the other thing school networks do: filters are usually pointed at file-sharing and storage categories, and there is no transfer here to be caught by one. Nothing is uploaded, no request goes out during the conversion, and you can watch that for yourself with the developer tools Network panel — how to prove it yourself walks through the check, which takes about a minute and works on a locked-down machine.
If the filter blocks the site's domain outright, the page never loads, and no clever local trick changes that. The honest answer then is to ask whoever runs the network, or to do the conversion on a personal device and bring the MP3 in. Anything promising to get around a school filter is either lying to you or getting you into trouble.
Doing several files at once
The browser converter handles one file per run, which is fine for the two or three most people have. For a folder, you have two options.
The first is to stop converting altogether. If what you actually need is one file rather than many — a set of recorded lecture parts, or a podcast in segments — joining them and converting the result once is both quicker and cheaper in quality than converting each piece separately.
The second is Linux, below. No ChromeOS route batches without it.
Linux (Crostini) and ffmpeg, if you can turn it on
Every Chromebook released in the last several years can run a Debian container, and it comes with a real package manager. Turn it on in Settings > About ChromeOS > Developers > Linux development environment. Setup takes a few minutes and carves out disk space of its own, which is a genuine consideration on a small eMMC drive.
Then, in the Terminal app:
sudo apt update && sudo apt install ffmpeg
And in the folder holding the files:
for f in *.m4a; do ffmpeg -i "$f" -c:a libmp3lame -q:a 2 "${f%.m4a}.mp3"; done
-q:a 2 is LAME's variable-bitrate quality 2, which averages somewhere near 190 kbps and spends the bits where the music needs them. Use -b:a 192k instead if something downstream specifically wants a fixed rate — some older car head units and transcription pipelines are happier with it.
This is the twenty minutes everybody loses. The container starts with access only to Linux files, so ls in your home directory shows nothing you recognise. Either copy the audio into Linux files in the Files app, or right-click the folder it lives in and choose Share with Linux — shared folders then appear under /mnt/chromeos/. Files converted inside the container also have to be moved back out before Chrome or Drive can see them.
The Android app route, and when it is worth it
Most Chromebooks can install Android apps, and our own Audio Converter is free on Google Play. On a Chromebook it is usually the long way round, though, and it is worth being straight about why: it is a phone app in a window, Android apps reach ChromeOS storage through the Play files sandbox rather than seeing your folders directly, and the browser route needs nothing installed at all.
Where the app genuinely wins is when the recording is on your phone rather than the Chromebook. Converting it there and sending the MP3 skips the step where you get the file onto ChromeOS in the first place, which for iPhone voice memos usually means a trip through Drive or email. The app also works offline once installed and does not fetch an engine over cellular, and it keeps a history so a finished file can be shared again later.
Two files defeat every route on this page. A file with DRM on it, such as a purchased track from the old iTunes Store, cannot be converted by this or by anything else whatever the ads say. Neither can a zero-byte file left behind by a sync that never finished, so check the size in the Files app before blaming the converter.
The converter on the home page handles this. Free, no upload, no sign-up.