AAC to MP3 is built for audio editing and conversion jobs that fit cleanly into a browser tab. Convert raw AAC files (.aac) to MP3 with selectable bitrate from 96 to 320 kbps. Runs entirely in your browser with FFmpeg WebAssembly — no uploads, no sign up, no watermarks. 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.
Under the hood, AAC to MP3 uses standard browser APIs to do the actual work. The tool accepts MP3, WAV, M4A, AAC, OGG, Opus, FLAC, AIFF, and WMA as input, with a per-file ceiling of 200 MB so memory usage stays predictable on lower-end laptops and tablets. The engine ships as part of the page bundle, so once the page is loaded the tool keeps working even if your network connection drops.
Reach for AAC to MP3 when you need a predictable result on a single file. The page works on the first visit, the controls are visible without a menu, and the output is delivered the moment the engine finishes.
AAC to MP3 is structured so the question "where is my file processed?" has a single answer: in your browser tab. The engine, the controls, and the result panel are all on one page. Navigating away or closing the tab clears the page's memory the way it does for every other tab.
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.
Even on its own, AAC to MP3 composes well with the rest of your toolkit. The output is a standard MP3 file that opens in any program that handles the format, so the result of one run can become the input to whatever step you use next.
AAC to MP3 is shaped around the recurring needs of two audiences: podcasters preparing episodes, who use it as a quick utility between bigger tools, and streamers cleaning microphone tracks, who use it as their primary way of getting the job done. Both groups get the same defaults and the same speed.
Output handling is intentionally boring: AAC to MP3 produces `{name}-edited.{ext}` and triggers your browser's standard "save" behaviour. If you have a default download folder configured, that is where it will land. There is no Favtoo-side history of jobs you have run.
AAC 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.
AAC to MP3 is one example of a broader pattern: utility software increasingly works as single-page, client-side experiences. Every page in the catalog is shaped that way, which keeps each tool fast to load and easy to recommend in a single link.
A few practical tips that experienced users of AAC to MP3 pick up over time. First, keep your default browser updated — the engine relies on standard web APIs and newer browser versions are noticeably faster than ones from a few years ago. Second, close other heavy tabs before processing a large input; the engine shares CPU and memory with whatever else is open. Third, if you re-run the same kind of job often, your last-used settings are remembered for the rest of the tab session, so subsequent runs are essentially one click.
AAC to MP3 is built around the moment of need: a focused page you open when you have a specific task, complete the task, and close. The catalog contains many adjacent tools so the same model serves the surrounding parts of a typical audio editing and conversion workflow.
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.
That is the whole tool. Use AAC to MP3 for as long as it stays useful to you, and if it does, the catalog has many more tools built the same way. Each applies the same single-purpose discipline, so the way you used this page transfers to the next one you try.
AAC is the codec; M4A is a container. A .m4a file holds AAC audio inside an MPEG-4 container with metadata and chapters. A raw .aac file holds the same AAC audio but without a container — useful for streaming. This tool handles both forms; the dedicated M4A tool is optimized for the container format.
Yes, slightly. AAC is generally more efficient than MP3, so converting AAC → MP3 means re-compressing with a less efficient codec. To minimize loss, pick MP3 256 or 320 kbps. The quality loss is small but cumulative — avoid converting back and forth multiple times.
For voice/podcast: 96–128 kbps. For typical music originally at 128 kbps AAC: 192 kbps MP3. For high-quality music originally at 256+ kbps AAC: 320 kbps MP3. When in doubt, use 256 kbps as a safe middle ground.
MP3 is the most universally supported audio format. Older devices, car stereos, simple Bluetooth speakers, and some embedded systems play MP3 but not AAC. If your target is "any device anywhere," MP3 is the safest bet. For modern phones and computers, AAC is fine as-is.
Standard metadata (title, artist, album, year, track) is copied during conversion. Embedded album art is also preserved. Some non-standard tags or chapter data may not survive — this is normal for cross-format conversion.
Up to 200MB AAC. Conversion runs at several times real time on a modern laptop — even hour-long files convert in 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.
AAC to MP3 only needs the standard web platform — file picker access for the inputs you choose to load, and optionally clipboard access if you copy the result rather than downloading it. There is no microphone, camera, geolocation or background-permission request, because none of those are needed for the work the tool does.
Inputs are capped at 200 MB per file, which keeps memory usage stable across phones, tablets and older laptops. You can run AAC to MP3 as often as you need; every run produces a full-quality result.
Favtoo keeps no copy of your file because Favtoo never receives your file. AAC to MP3 runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.
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.
Your file is processed inside your browser by standard browser APIs. The engine reads the file's bytes from your tab's memory, computes the result, and writes the result back into the tab. You can confirm what the page does by opening developer tools and watching the Network tab during a run — the requests you see are for the tool's static assets only.
No installation is needed. AAC 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 AAC to MP3 on any computer you have temporary access to without leaving anything installed on it.
AAC to MP3 is built on standard browser APIs, which is the same class of engine used by professional audio editing and conversion pipelines. For deterministic operations, the output is byte-identical to what an equivalent CLI run would produce; for operations involving a codec or a model, the result is well within the range of what comparable tools generate. If you have a specific reference output you need to match, run a small test job first to confirm the configuration produces what you expect.
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.
AAC to MP3 processes one input at a time by design — it keeps memory usage predictable on lower-end devices and makes results easier to verify. To handle a folder, run the tool once per file; the page stays loaded between runs and remembers your last-used settings, so the second run is essentially instant.
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.