MKA is the audio-only Matroska, which holds anything at all. MP3 is MPEG-1 Audio Layer III, lossy, and the one audio format that every device made since 1995 can play. ffmpeg sits between the two, and this page says exactly what happens to an MKA file on the way to becoming an MP3 one.
What runs when an MKA file becomes MP3
ffmpeg held to a single thread, on a machine we rent and watch. Your MKA file is uploaded once, ffmpeg runs once, the MP3 comes back, and neither file is kept. MKA to MP3 is one of the 3649 pairs that engine was probed on with a real file, which is why it has a page here and why the pairs the probe could not prove do not.
What survives from the MKA into the MP3
The running time and the channel layout. A stereo MKA comes back as a stereo MP3 of the same length: this is a re-encode, not an edit, and nothing here normalises, trims or boosts the MKA.
Everything the MKA still had. ffmpeg decodes the MKA in full before it writes a single byte of MP3, so nothing is skipped on the way in, whatever was already missing.
What MKA to MP3 costs you
Generation loss, and it is the whole story of this pair. MKA threw information away to be small, MP3 throws more away on top of what is left, and neither pass can restore what the other removed. Converting the MP3 back to MKA afterwards makes it worse a third time, not better.
Album art, where the MKA carried any. ffmpeg passes -vn on every audio target here, which counts an embedded cover as a video stream and drops it along with the film it was never part of. That is deliberate rather than careless: keeping it makes the mux fail outright on several audio containers, and hiding the choice would be lying by omission.
Any hope of MP3 sounding better than the MKA. Nothing in this pass adds information, and a bitrate higher than the MKA deserved only makes a larger file of the same recording.
Where MKA and MP3 files come from
MKA. Matroska with no video track. Like MKV it imposes nothing on what is inside: an MKA can hold FLAC, AAC, Opus or all three at once, which is why archivists like it and why some players refuse it.
If a model is going to read the MP3
An MP3 file is a waveform, and a language model reads text, so handing an assistant this MP3 directly gets you nothing. The MP3 becomes useful the moment somebody turns the sound into words, and that is a separate job with its own page here. MKA to MP3 is the step before it: get the sound out of the MKA in a container the transcriber accepts, then hand the model a transcript instead of a file it cannot open.
Running MKA to MP3 against the real engine with a real file, ffmpeg wrote 24,677 bytes of MP3 in 0.1 seconds, machine otherwise idle. That is one MKA file on one day and not an average, which is why the number is given together with the file that produced it.
The MKA to MP3 verdict was reached by ffprobe, meaning the container was actually demultiplexed, recognised under the right name, and carried at least one stream. Which check was used matters, because they do not all prove the same thing, and a status code of 200 proves nothing whatsoever about whether the MP3 file has anything inside it.
The same MKA file, sent somewhere else
Other outputs the probe measured out of an MKA file, so the cost of choosing MP3 can be read against something. Sizes do not compare across engines, because each family was probed with its own MKA witness file.
MKA to WAV: 265,422 bytes in 0.1 seconds, verified by ffprobe.
MKA to FLAC: 148,596 bytes in 0.1 seconds, verified by ffprobe.
MKA to OGG: 8,384 bytes in 0.1 seconds, verified by ffprobe.
MKA to M4A: 28,113 bytes in 0.2 seconds, verified by ffprobe.
MKA to OPUS: 30,246 bytes in 0.1 seconds, verified by ffprobe.
MKA to AAC: 27,699 bytes in 0.1 seconds, verified by ffprobe.
Other ways into MP3, and what they measured
Among the published routes into MP3, MKA is the tenth largest output of the 22 measured. The witness files differ, so this ranks the probe run and not your document.
OGA to MP3: 24,468 bytes in 0.1 seconds.
MP2 to MP3: 24,468 bytes in 0.1 seconds.
AU to MP3: 24,468 bytes in 0.1 seconds.
CAF to MP3: 24,468 bytes in 0.1 seconds.
3GP to MP3: 24,780 bytes in 0.1 seconds.
What we will not pretend about MKA to MP3
An MKA file over 150 MB is refused before the upload finishes rather than after it, so you do not wait for a rejection.
An MKA to MP3 run that passes 240 seconds is killed, and the ffmpeg process is killed with it. A run left behind would sit on one of the machine's two cores until somebody noticed.
The MKA file behind the measurement on this page was a 3 second sine wave at 440 hertz, built by ffmpeg for the probe itself. That is why MKA to MP3 came out at 0.1 seconds, and it is not what your file will do. The measurement proves the pair works and says almost nothing about how long yours will take.
MKA to MP3 costs half a credit per conversion, whatever the length of the MKA. That is the same as an image or a document here, and it is a measurement rather than a gesture: an audio target on this engine is done in under two seconds, where a video target can take minutes.
An MKA longer than 60 minutes is refused before encoding. ffprobe measures the MKA first and answers with a refusal, rather than starting a job the 240 second guard would kill halfway to the MP3.
MKA to MP3 waits at the audio door, which is 2 slots wide and gives up after 5 seconds rather than making you wait twenty times the length of the work. Until the 30th there was one door for everything, and a single video transcode starved every audio conversion for its whole duration: an MP3 that needed less than a second was answered with a refusal after twenty.
Nothing here reads what is inside the MKA. No transcription, no scene detection, no summary: MKA to MP3 is a container and codec operation, and the MP3 says exactly what the MKA said, in a different wrapper. The sound is the whole payload.
One MKA file at a time, chosen in the browser. There is nothing else to set up and nothing else on offer.
MKA to MP3: what people ask
What actually converts my MKA file to MP3?
ffmpeg does it, held to a single thread, on a machine we rent and watch. Not a browser trick and not somebody else service: the MKA file is uploaded once, ffmpeg runs once, the MP3 comes back, and neither file is kept afterwards.
How long does MKA to MP3 take?
The probe measured 0.1 seconds for 24,677 bytes of MP3, on a 3 second file. An audio target scales far better than a video one: three minutes of source through this engine takes under a second, because only the sound is encoded. Past 240 seconds any run is stopped, and an audio one does not get close.
What do I lose going from MKA to MP3?
The one to know about first: Generation loss, and it is the whole story of this pair. MKA threw information away to be small, MP3 throws more away on top of what is left, and neither pass can restore what the other removed. Converting the MP3 back to MKA afterwards makes it worse a third time, not better.
Will the MP3 sound better than the MKA?
No. Nothing in this pass adds information to the MKA, so the MP3 is at best an exact carry of what you sent and at worst one more lossy pass over it. Asking for a higher bitrate than the MKA deserved just makes a bigger file of the same recording.
Is MKA to MP3 free?
There is a free allowance every month, and one MKA to MP3 conversion costs half a credit against it however long the MKA runs. An audio target is charged per conversion and not per minute, because the engine encodes three minutes of sound in well under a second.