Add your MPEG file
Drop one or more .mpeg files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Pulling the soundtrack out of a .mpeg video into .m4a audio keeps what you can hear and drops the picture entirely. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Pulling the soundtrack out of a .mpeg video into .m4a audio keeps what you can hear and drops the picture entirely. An .mpeg file holds an MPEG program stream: video and audio multiplexed together using the original MPEG-1 or MPEG-2 standards. These files come from Video CDs, DVD-authoring workflows, and older capture hardware, and they remain readable by virtually every conversion tool.
An .m4a file is an MPEG-4 container that holds only audio, most often AAC and occasionally Apple Lossless. Apple coined the .m4a extension so audio would not be confused with .mp4 video, and it remains the default for iTunes purchases, Apple Music downloads, and Voice Memos. For this route the practical draw is real tagging and artwork support, unlike bare .aac streams and gapless playback metadata for continuous albums — balanced against the extension hides whether the contents are lossy or lossless, muddying quality expectations, which is worth knowing before you commit a large batch.
The usual reason to take .m4a audio out of a .mpeg file is that only the sound matters — a talk, interview, song, or podcast segment. Keeping the video stream would waste storage, and a dedicated audio file is easier to trim, tag, and play. On the source side, mPEG-1 and MPEG-2 need roughly twice the bitrate of H.264 for comparable quality; on the target side, the payoff is real tagging and artwork support, unlike bare .aac streams, which is exactly what you want for managing music inside iTunes and Apple Music libraries.
| Aspect | MPEG video (.mpeg) | MPEG-4 audio (.m4a) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Lossy — discards detail it judges invisible to shrink files |
| How it stores data | program streams were engineered for reliable storage media, in contrast to the error-hardened transport stream used for broadcast | an ISO base media container restricted to audio tracks, structurally a sibling of MP4 |
| Strongest at | handling digitized VHS or Video CD content | managing music inside iTunes and Apple Music libraries |
| Weak spot | mPEG-1 and MPEG-2 need roughly twice the bitrate of H.264 for comparable quality | the extension hides whether the contents are lossy or lossless, muddying quality expectations |
| Metadata | the program stream carries essentially no descriptive metadata; the specification predates any notion of embedded titles or tags | iTunes-style metadata atoms: title, album, artwork, composer, BPM, and the iTunSMPB gapless-playback data |
Drop one or more .mpeg files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .m4a in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if M4A is selectable, the route is real and validated.
Press Convert. A WebAssembly FFmpeg build demuxes the audio track and re-encodes it locally; the video stream is simply discarded.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid M4A file. Outputs keep the original filename with the .m4a extension.
Since mpeg is container-oriented and m4a is lossy-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .m4a itself requires.
Yes — the .mpeg file is processed inside your browser tab and never uploaded. A WebAssembly FFmpeg build demuxes the audio track and re-encodes it locally; the video stream is simply discarded. Close the tab and the file is gone from memory.
Browsers, Windows, Android, and every Apple device play AAC-based .m4a files without extra software. The ALAC-filled variety is slightly narrower, since some inexpensive devices decode only the AAC form.
Much smaller — the video stream is usually 80–95% of a .mpeg file's weight, and it is discarded entirely. The remaining audio is re-encoded at the bitrate implied by your quality setting.
This converter strips container metadata deliberately (the FFmpeg command runs with metadata mapping disabled) so exported files do not leak recording details. In the source, the program stream carries essentially no descriptive metadata; the specification predates any notion of embedded titles or tags; none of it is transmitted anywhere because the file never leaves your browser.