M4A to MP3 is built for audio editing and conversion jobs that fit cleanly into a browser tab. Convert Apple M4A (AAC audio) files to MP3 for universal compatibility. Pick the bitrate from 96 to 320 kbps. Runs entirely in your browser with FFmpeg WebAssembly — no uploads, no sign up. The processing runs in the page itself, which is why the controls update instantly when you change settings and why a freshly loaded page is ready to do real work the moment it becomes interactive.
Most people land on M4A to MP3 via a search at the moment they actually need the tool. That shapes the design: the page is a single screen with the input on one side, the controls in the middle, and the result on the other, so a first-time visitor can complete the job without reading documentation.
M4A to MP3 parses your file with standard browser APIs entirely inside the browser, applies the options you selected, and returns a download. The processing has no network step, which means a slow or intermittent connection does not slow down the work — once the page is loaded, only your CPU and RAM are involved.
M4A to MP3 is implemented on top of standard browser APIs. The accepted input formats are MP3, WAV, M4A, AAC, OGG, Opus, FLAC, AIFF, and WMA, decoded in the browser, processed, and re-encoded into the output format. Files up to 200 MB are well within the comfort zone of any modern browser.
The 200 MB ceiling on input size is the only fixed limit. Output files are produced in standard formats that every common viewer recognises, and the tool runs the same way regardless of how many times you have used it during the session.
The heaviest users of M4A to MP3 tend to be podcasters preparing episodes, teachers recording lessons and voice-over artists exporting takes. Each group brings slightly different expectations to the tool, but the same single-page architecture serves every one of them with the same response time.
The download is delivered as `{name}-edited.{ext}` the moment processing completes — no email link, no "your result will be ready in 5 minutes" queue, no expiry timer. The file is generated in your browser and saved by your browser's normal download flow.
If your task needs more than one step, chain M4A to MP3 with AAC to MP3, WAV to MP3, and Audio Converter. Each tool produces output that is a clean input to the next, so multi-step workflows are just a matter of opening the next tool in a new tab and continuing.
M4A to MP3 keeps the control set focused. Every option on the page is there because a real workflow needs it, and the defaults aim at the most common case so a first-time user can get the right output without changing any settings.
A short note on how M4A to MP3 came to look the way it does: every iteration started by watching how someone unfamiliar with the tool actually used it, then removing whatever got in their way. That is why the upload area dominates the screen, the run button is bigger than the secondary controls, and the result panel is unmissable when the job finishes.
As a single-page tool, M4A to MP3 stays focused on one audio editing and conversion step. Multi-step workflows are composed by chaining adjacent tools — each tool produces a standard file the next one can read directly, so a longer pipeline is just a sequence of short tab-and-tab visits.
Pro tip: M4A to MP3 works just as well in a private/incognito window as in a normal one, which is occasionally useful when you want zero browser-history footprint of the job. Another tip: if the tool ever feels slow, it is almost always because the browser tab is competing for CPU with another tab — pausing or closing the heavy ones gives the engine room to work.
If the result is not what you expected, the most common causes are easy to check. Confirm the input is under the 200 MB ceiling — files just above the cap fail silently because the engine refuses to allocate the buffer. Confirm the input is one of the supported formats. And if the page itself feels slow, try closing other heavy tabs to free up memory; the engine runs in your browser, so it competes for the same resources as everything else open.
Open the workspace above to start using M4A to MP3. The engine loads on the first interaction so the page itself stays light, and once the tool is warm it processes subsequent jobs quickly. The moment the page is interactive, the tool is ready to do real work on your file.
M4A is Apple's audio container holding AAC-encoded audio. It's used for iTunes purchases, Apple Music downloads, voice memos, and as the default recording format on iOS and macOS. While M4A plays on most modern devices, MP3 has the broadest compatibility — older phones, car stereos, and Bluetooth speakers always support MP3.
A small amount, yes — both M4A (AAC) and MP3 are lossy codecs, so re-encoding adds a generation of loss. AAC is generally a more efficient codec than MP3, so converting M4A 128 kbps → MP3 192 kbps roughly preserves quality. To minimize loss, pick the highest MP3 bitrate (320 kbps).
For voice memos and podcasts: 96–128 kbps mono is fine. For music originally at 256 kbps M4A: use 256 or 320 kbps MP3. For Apple Music files (typically 256 kbps AAC): use 256+ kbps MP3 to avoid noticeable quality loss.
Modern downloads from iTunes Store and Apple Music are DRM-free, so this tool can convert them. Legacy iTunes Store M4P files (purchased before 2009) are DRM-protected and cannot be converted by any third-party tool. Apple Music streaming files (not downloads) are also DRM-locked.
Yes — FFmpeg copies standard tags (title, artist, album, year, track number) and embedded album art from the M4A's metadata atoms into the MP3's ID3 tags. Custom or Apple-specific tags may not transfer.
Up to 200MB M4A. Conversion typically runs at several times real time on a modern laptop — most music files convert in well under a minute.
Server-side tools use multi-threaded native FFmpeg running on dedicated CPUs with fast disks and parallel pipelines. Our engine is FFmpeg compiled to WebAssembly, which runs single-threaded inside your browser tab and has no access to native hardware acceleration. That makes browser-based jobs typically 3–8× slower than a server. The trade-off is total privacy: your audio file is never uploaded, never logged, and never stored — closing the tab erases everything from memory immediately. For most clips up to a few minutes the wait is small, and for sensitive recordings (voice memos, drafts, confidential meetings) the privacy gain is well worth it.
No. Everything runs entirely inside your browser tab using FFmpeg compiled to WebAssembly. The file is read into local memory only, processed in the same tab, and the result is offered as a direct download. Nothing is transmitted to any server, no account is required, no analytics are tied to your file, and closing the tab discards every byte from memory.
The file picker accepts audio inputs up to about 1 GB, which is well above what mainstream "free tier" online converters allow. The real ceiling is your device — everything runs inside your browser tab, which shares memory with the rest of the page. Most podcasts, songs, and voice memos sit comfortably under that limit even on a phone. If a very large lossless WAV or FLAC ever fails, trim it first or transcode to MP3 / Opus to bring the size down before re-running the tool.
MP3, WAV, OGG (Vorbis and Opus), FLAC, M4A (AAC), AAC, Opus, AIFF, and WMA all decode reliably via FFmpeg WASM. Output formats depend on the specific tool — most editing tools default to MP3 (universal) or WAV (lossless) but expose a format picker so you can pick the one that fits your downstream player or DAW.
Recent Chrome, Edge, Firefox, Safari, and other Chromium-based browsers all work. The tool relies on WebAssembly and SharedArrayBuffer, which require the page to be served over HTTPS with the right cross-origin headers — this site is configured correctly by default. On phones the same code runs but is slower than on a desktop because mobile CPUs are weaker.
No. The tool is completely free, requires no account, attaches no watermark, applies no usage caps, and shows no popup ads on your output. Because the work happens on your own device, there is no per-user quota for us to enforce — your hardware and browser memory are the only limits. The download is the file you would get from running FFmpeg locally, nothing more, nothing less.
No installation is needed. M4A to MP3 runs as a normal web page, with no browser extension, no native helper, and no separate desktop client to download. That is partly a privacy choice — extensions can request broad permissions, while a regular page is sandboxed by default — and partly a convenience one: you can use M4A to MP3 on any computer you have temporary access to without leaving anything installed on it.
Desktop apps usually have more advanced features but require installation, maintenance and (often) a licence. Paid online tools are convenient but route your file through their servers and gate downloads behind accounts. M4A to MP3 sits in between: free, instant, and private, but intentionally narrow in scope. For one-off jobs and the common audio editing and conversion operations, it is usually the lowest-friction choice; for highly specialised work, a dedicated app is still the right answer.
M4A to MP3 can be used for personal and commercial work alike — there is no separate "business" licence to purchase. The output you generate is yours to use however you want, including in client deliverables, internal documents, or commercial products. Favtoo's only ask is fair, individual use; the tool is not designed to be embedded as a backend service or wrapped behind an API for resale.
M4A to MP3 is a browser-only tool by design and does not expose a hosted API. The reason is the same as the privacy story: there is no Favtoo backend doing the work, so there is no service to call. If you need to script the same transformation, the underlying engine (standard browser APIs) is open-source and can be used directly from your own code.
Most jobs finish in seconds. Speed scales with input size and with how many CPU cycles your browser tab has available — the engine runs in your browser, so it shares resources with whatever else you have open. For inputs near the 200 MB ceiling, expect anywhere from a few seconds to roughly a minute on a typical laptop. Closing other heavy tabs noticeably speeds things up.
M4A to MP3 runs in any modern mobile browser — Safari, Chrome, Firefox and the in-app browsers in most messaging apps all support the underlying APIs. Performance depends on the device: a recent phone handles typical inputs nearly as fast as a laptop, while older devices may take a few seconds longer near the 200 MB ceiling. The interface lays out cleanly on small screens, so you do not need to pinch-zoom to see the controls.
Failures usually fall into one of three buckets: the input is in an unsupported format, the input is over the size cap, or the input is structurally malformed (a truncated download, a partial export, or a stream the engine does not recognise). The first two are easy to confirm — check that your file is one of MP3, WAV, M4A, AAC, OGG, Opus, FLAC, AIFF, and WMA and that it is below 200 MB. For the third, opening the file in its native viewer first is the fastest way to confirm the source is intact.
M4A to MP3 is updated whenever the underlying engine releases an improvement or a bug fix. Because the tool is delivered as a static page, every visit fetches the latest version automatically — there is no "version" to manage on your end. If a particular release ever changes default behaviour, the change is documented on Favtoo's changelog so you can confirm what shifted.
M4A to MP3 is built to preserve quality wherever the underlying audio format allows it. Operations that are mathematically lossless (e.g. structural transformations, lossless re-encoding) round-trip with no perceptible change. Operations that involve a lossy codec inevitably introduce small artefacts at the byte level, but the defaults aim at the sweet spot where output looks or sounds the same to a normal viewer or listener while still being meaningfully smaller or faster than the input.
Audio Recorder
Record from your microphone directly in the browser. Pick quality (high, medium, low), toggle echo cancellation, noise suppression and auto-gain, then save to WebM/Opus or M4A/AAC. Audio is captured locally — nothing is uploaded.
Text to Speech
Type or paste text, pick a system voice, and listen instantly. Adjust speaking rate (0.5×–2×), pitch, and volume in real time. Uses your browser's built-in Web Speech API — no cloud TTS, no API keys, no costs.
Tone Generator
Generate a pure tone at any frequency from 20 Hz to 20 kHz. Pick a sine, square, triangle, or sawtooth waveform, choose duration, amplitude, and mono/stereo. Exports a 16-bit PCM WAV file at 44.1 kHz with built-in click-preventing fades.
Silence Generator
Generate a perfectly silent WAV file of any length from 1 second up to 1 hour. Pick mono or stereo, get a 16-bit PCM WAV at 44.1 kHz. Useful as padding between clips, intro silence, leader audio for video timing, or test material.
White Noise Generator
Generate white, pink, or brown noise as a 16-bit PCM WAV file. Pick noise type, duration up to 1 hour, amplitude, and mono/stereo. Useful for sleep, focus, masking distractions, audio testing, and as a backing layer for ambient music.
Metronome
A precise browser-based metronome powered by the Web Audio API. Set BPM from 30 to 300, choose a time signature, accent the first beat, and use tap-tempo to sync. Click timing is sample-accurate using lookahead scheduling — much steadier than typical JavaScript setInterval beats.
Audio Trimmer
Trim any audio file to a precise start and end time. Outputs a lossless stream-copy by default (no quality loss, very fast) or re-encodes to MP3, WAV, OGG, or M4A. Files are processed entirely in your browser with FFmpeg WebAssembly.
Audio Splitter
Split a long audio file into N equal-length parts and download them as a ZIP. Each part is named sequentially. Great for chapterizing audiobooks, podcasts, or long DJ mixes. Runs entirely in your browser with FFmpeg WebAssembly.