Add your MKV file
Drop one or more .mkv 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 .mkv video into .mpeg 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 .mkv video into .mpeg audio keeps what you can hear and drops the picture entirely. An .mkv file uses the Matroska container, an open format designed to hold an unlimited number of video, audio, and subtitle tracks in one file. Collectors of high-quality rips and archival copies favor .mkv because it keeps every language track, chapter marker, and font attachment together.
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. For this route the practical draw is universally decodable, with all underlying patents expired and simple, robust structure that tools have parsed for thirty years — balanced against mPEG-1 and MPEG-2 need roughly twice the bitrate of H.264 for comparable quality, which is worth knowing before you commit a large batch.
The usual reason to take .mpeg audio out of a .mkv 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, safari and iOS refuse the container outright; on the target side, the payoff is universally decodable, with all underlying patents expired, which is exactly what you want for handling digitized VHS or Video CD content.
| Aspect | Matroska video (.mkv) | MPEG video (.mpeg) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Container — quality depends on the codecs and settings inside |
| How it stores data | built on EBML, a binary XML-like structure that lets the container gain features without breaking older parsers | program streams were engineered for reliable storage media, in contrast to the error-hardened transport stream used for broadcast |
| Strongest at | archiving discs while preserving every audio track and subtitle stream | handling digitized VHS or Video CD content |
| Weak spot | safari and iOS refuse the container outright | mPEG-1 and MPEG-2 need roughly twice the bitrate of H.264 for comparable quality |
| Metadata | matroska tags cover title, cast, and arbitrary key-value pairs, and the container can embed cover art and other files as attachments | the program stream carries essentially no descriptive metadata; the specification predates any notion of embedded titles or tags |
Drop one or more .mkv 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 .mpeg in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if MPEG 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 MPEG file. Outputs keep the original filename with the .mpeg extension.
Since mkv is container-oriented and mpeg is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .mpeg itself requires.
Yes — the .mkv 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.
Desktop players on every operating system decode MPEG-1 and MPEG-2 program streams, and no licensing barriers remain. Browsers never adopted the format for the HTML5 video element, so web delivery requires conversion first.
Much smaller — the video stream is usually 80–95% of a .mkv 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, matroska tags cover title, cast, and arbitrary key-value pairs, and the container can embed cover art and other files as attachments; none of it is transmitted anywhere because the file never leaves your browser.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .mkv → .mpeg → .mkv is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.