Converting M4A to MP3 without iTunes

The query is explicitly an anti-install query, and every page ranking for it is a download funnel for paid desktop software. They want the job done without adding anything to their machine.

Open the M4A to MP3 converter in a browser tab, drop the file on it, pick MP3, save the result. Nothing is installed, no admin rights are needed, and the file never leaves your machine — the encoder is FFmpeg compiled to WebAssembly, running inside the page you are looking at. That is the whole answer for one file or a handful. If you have hundreds, there are two other genuinely no-install routes and a couple of installs worth making an exception for, all ranked below.

Worth saying early: most pages that rank for this query answer "without iTunes" by handing you a different installer, usually a paid one with an affiliate link attached. Swapping Apple's software for someone else's software is not what the question asked.

What "without iTunes" usually means

Three different problems arrive at this search, and they need different answers.

• There is no Apple software on the machine and you do not want any. Fair. iTunes for Windows is a multi-hundred-megabyte download that adds several background services alongside the player. For one voice memo, that is an absurd trade.
• Apple's software is right there but the conversion option is missing or greyed out. On macOS, iTunes has not existed since Catalina in 2019; the Music app inherited the job, and its Convert menu goes grey for reasons that have nothing to do with the file you selected. That specific dead end is unpicked in why "Create MP3 Version" is greyed out.
• You are not allowed to install anything. A managed work laptop, a school machine, a library PC, a Chromebook that will not run a Windows installer at all. This is the strictest version of the question, and it has the cleanest answer, because a browser tab is not an install.

The no-install routes, ranked

"Installs nothing" should mean something specific: no administrator prompt, nothing added to Program Files or Applications, no entry in the uninstall list, no background updater left running afterwards, and nothing to remove later.

The second row is the one most "no install" articles recommend without mentioning the trade. A server-side converter installs nothing because your audio does the travelling instead: it is copied to a machine you do not control, converted there, and held for some period before deletion. For a lecture recording that is fine. For a client call, a therapy session or a doctor's appointment it is a decision worth making deliberately rather than by default.

Route 1: the browser tab, step by step

This works the same on Windows, macOS, a Chromebook and a phone, because the work happens in the browser rather than the operating system.

1. Open the converter and drag the .m4a in, or click to browse for it.
2. It inspects the file first and reports what it found — codec, length, sample rate, bitrate. That alone is useful when a file is misbehaving.
3. Choose MP3, then a bitrate. 192 kbps is the default and is where most listeners stop being able to pick the copy from the original in a blind test. There is a VBR setting too, which lets the bitrate move with the material.
4. Convert, then save the file wherever you want it.

Three honest caveats. The first visit fetches a 32 MB engine, cached for a year afterwards, so the second file costs nothing — but it is not the route to choose on a metered mobile connection.

M4A to MP3 is always a real encode. The AAC audio inside the M4A has to be decoded to raw samples and re-compressed as MP3, so it takes processing time proportional to the length of the recording. A three-minute song is quick. A two-hour meeting is a cup of tea. Only a stream copy — moving an existing audio stream into a different container without touching it — finishes almost instantly, and MP3 is never on the receiving end of one from an M4A.

And it is one file at a time. There is no limit we impose on size — the ceiling is the browser tab's own address space, which tops out near 2 GB, and audio rarely goes near it, since three hours at 128 kbps is roughly 170 MB. If you are holding a folder of two hundred files, skip to the command line below.

Route 2: something already on the machine

Using software already on the machine is not installing software, and two things are worth checking for before you conclude you have nothing. VLC is on a surprising number of machines, and its converter is hidden where nobody looks: Media > Convert / Save on Windows, File > Convert / Stream on macOS. Choose the Audio - MP3 profile, and type the .mp3 extension yourself in the destination box, because VLC does not add it for you. The full walkthrough, including the split-button trap that catches everyone, is in the Windows 11 guide.

FFmpeg may also already be present, dragged in as a dependency of something else. Open a terminal and type ffmpeg -version. A version banner rather than "not recognised" means you already have the tool the paid converters are wrapping, and one line does the whole folder.

What is not a route, despite being suggested constantly: macOS's built-in afconvert. It is genuinely installed on every Mac and it genuinely converts audio, but Apple's audio framework ships an MP3 decoder rather than an MP3 encoder, so afconvert will happily produce AAC, ALAC, WAV or AIFF and refuse the one format you came for. Windows has no equivalent built-in at all — there is no Convert to MP3 anywhere in File Explorer's right-click menu.

The installs that are worth an exception

If this is going to happen weekly, installing something once is the right call. In rough order of how much they ask of you:

• FFmpeg — one winget install Gyan.FFmpeg on Windows or brew install ffmpeg on a Mac, then one line converts an entire directory. No interface to learn beyond that line, and it is the engine underneath most of the alternatives.
• fre:ac or foobar2000 — free, with a window and a progress bar, for batch work without a terminal.
• Audacity — the right tool if you also need to edit, and it exports MP3 without a separate encoder these days. Importing an M4A, though, needs its optional FFmpeg library, which is a second download; a bare Audacity install refuses the file outright.

What Apple's software still does better

It is only fair to say where iTunes and the Music app win, because for some people they genuinely do.

They manage a library. If your goal is not "produce an MP3 file" but "have an MP3 copy sitting in my library beside the original, tagged, with artwork, ready to sync", Apple's converter puts the new file exactly there and updates the database in the same motion. Every route on this page produces a loose file in a folder instead, and reimporting a few hundred loose files is its own afternoon. Apple's route also takes a whole selection at once, keeps the metadata it already holds, and lets you set the encoder once in Import Settings.

One thing they cannot do, and neither can anything else: a track from an Apple Music subscription is DRM-protected and will not convert, on any tool, free or paid, whatever the affiliate reviews imply. The same goes for an old .m4p purchase from the original iTunes Store and for a protected .aa or .aax audiobook.

Doing it without an account or an email address

"Without iTunes" is often shorthand for "without anything asking me for something", and the sign-up wall is the other tax. Free web converters do not have one shape of limit, they have several, and they change them without notice: a cap on how large a single file may be, a count of how many jobs you get in a day, a queue that lengthens when the service is busy, and a registration wall placed at whichever of those thresholds it was set to appear at. Do not trust a figure quoted in a blog post, including one quoted about a competitor — several of the ones we checked were already out of date. What free audio converters actually limit goes through the shapes rather than the numbers.

A converter that runs in your own tab has a different set of constraints, worth stating plainly so you can compare like with like: it is single-threaded, so a long file takes real time; it handles one file per run; and the first visit pulls that 32 MB engine. What it does not have is an account, an email field, a daily counter, a queue or a watermark, because there is no server keeping score.

What you lose, whichever route you pick

Every route here decodes lossy AAC and re-compresses it as lossy MP3. Nothing on this page, and nothing you can buy, gets back the detail the first encoder discarded when the recording was made — a second encode can only work from what survived the first. In practice this matters less than the forums suggest: at 192 kbps a single re-encode of speech or ordinary music is not something most people can pick out in a controlled test, and asking for 320 kbps because the file "deserves" it only makes a bigger file out of the same surviving audio. Where it does matter is a chain — one recording converted three or four times as it passes between tools. Keep the original M4A and convert from it each time rather than from the previous MP3.