Upload a M4A file and get a FLAC back. No signup, no watermark, no limit on how many.
M4A is an MPEG-4 container holding AAC audio — the same codec as a bare .aac file, wrapped so that players, tags and cover art all behave.
Where you run into it: iTunes and Apple Music purchases, voice memos, Zoom and Teams recordings, most phone-recorded audio.
What it costs you: Outside Apple's ecosystem support is good but not universal, and a few older tools still refuse the extension on sight.
FLAC compresses losslessly: it typically halves a WAV and gives back bit-for-bit the same audio when decoded. It is free, open, and widely supported outside Apple's world.
Where you run into it: Archived rips, Bandcamp and Qobuz downloads, anyone who keeps a music library they intend to still have in ten years.
What it costs you: Half of enormous is still large, and some hardware — car head units especially — will not touch it.
Worth being clear about: converting M4A to FLAC does not restore anything. What M4A threw away is gone, and wrapping the result in a lossless format simply preserves the damaged version perfectly. The file will get several times larger for no gain in sound. Do it when a tool or a workflow demands FLAC input — many editors and DAWs do — and not in the hope of better audio.
Yes, entirely, and there is no cap on how many files you convert. No account, no watermark, no trial.
It does not lose anything further, but it does not recover anything either. FLAC will store your M4A audio perfectly, damage and all. Converting this way for sound quality is the single most common misunderstanding about audio formats.
Considerably larger — usually five to ten times the M4A. A lossless format stores every sample, and it has no way of knowing that some of them were reconstructed from a lossy file.
Yes — FLAC is one of the formats this converter writes, so the reverse page exists at /flac-to-m4a/. Remember that going back and forth between two lossy formats degrades the audio a little each time.
The file is uploaded to do the conversion — nothing here runs in your browser — and both your upload and the converted result are deleted the moment the file is sent back. Nothing is stored and nothing is logged beyond the request itself.