MPG is the same program stream, under its shorter name. WMV is Windows Media Video, which Windows Movie Maker wrote by the million and very little opens today. ffmpeg sits between the two, and this page says exactly what happens to an MPG file on the way to becoming a WMV one.
What runs when an MPG file becomes WMV
ffmpeg held to a single thread, on a machine we rent and watch. Your MPG file is uploaded once, ffmpeg runs once, the WMV comes back, and neither file is kept. MPG to WMV 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 MPG into the WMV
The aspect ratio of the MPG. The engine scales to the smaller of 1280 pixels and the source width, and lets the height follow, rounded to an even number because encoders working in 4:2:0 refuse an odd one. An MPG already 1280 pixels wide or narrower is not resized at all.
The audio track, which travels into the WMV alongside the picture. That is the whole difference between this pair and sending the same MPG to an audio format, where the picture is thrown away instead.
The running time and the order of the frames. ffmpeg re-encodes the MPG, it does not re-cut it, so the WMV starts and ends where the MPG did.
What MPG to WMV costs you
Every pixel, one more time. The MPG is decoded to raw frames and re-encoded as WMV, so whatever the MPG had already lost stays lost and this pass adds its own on top. Run one file through the loop four or five times and the damage is visible without looking for it.
Any width past 1280 pixels. The engine scales the MPG down to 1280 because encoder cost grows with pixel count: a 4K source costs about sixteen times a 1080p one, for a WMV nobody asked to be that big. Below that width nothing is touched.
Subtitle and data tracks. ffmpeg passes -sn and -dn on the way into the WMV, because most of them do not fit the container and a mux that fails on a subtitle would waste a picture that converted perfectly well.
Anything past 120 seconds of MPG. ffprobe measures the duration before the encoder starts, and a longer MPG comes back as a refusal in under a second rather than as a timeout four minutes later.
Where MPG and WMV files come from
MPG. The same format as MPEG, under the extension DOS allowed. Which of the two a file carries says nothing about its content.
If a model is going to read the WMV
Nothing about MPG to WMV helps a language model, and pretending otherwise would be a sales line rather than a fact. A WMV is pixels and sound, both expensive to read and neither of them text. If what you actually want is what is said in the MPG, the useful move is not WMV at all: pull the audio out as MP3, which costs half a credit and comes back in about a second, and have that transcribed.
Running MPG to WMV against the real engine with a real file, ffmpeg wrote 180,119 bytes of WMV in 0.2 seconds, machine otherwise idle. That is one MPG file on one day and not an average, which is why the number is given together with the file that produced it.
The MPG to WMV 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 WMV file has anything inside it.
The same MPG file, sent somewhere else
Other outputs the probe measured out of an MPG file, so the cost of choosing WMV can be read against something. Sizes do not compare across engines, because each family was probed with its own MPG witness file.
MPG to GIF: 184,860 bytes in 0.1 seconds, verified by a format signature.
MPG to MP3: 24,468 bytes in 0.1 seconds, verified by ffprobe.
MPG to MP4: 49,380 bytes in 0.3 seconds, verified by ffprobe.
MPG to WAV: 265,038 bytes in 0.1 seconds, verified by ffprobe.
MPG to FLAC: 64,941 bytes in 0.1 seconds, verified by ffprobe.
MPG to OGG: 13,540 bytes in 0.2 seconds, verified by ffprobe.
Other ways into WMV, and what they measured
Among the published routes into WMV, MPG is the fifth largest output of the 9 measured. The witness files differ, so this ranks the probe run and not your document.
WEBM to WMV: 176,919 bytes in 0.2 seconds.
MP4 to WMV: 183,477 bytes in 0.2 seconds.
3GP to WMV: 183,477 bytes in 0.2 seconds.
AVI to WMV: 173,771 bytes in 0.1 seconds.
FLV to WMV: 176,809 bytes in 0.1 seconds.
What we will not pretend about MPG to WMV
An MPG file over 150 MB is refused before the upload finishes rather than after it, so you do not wait for a rejection.
An MPG to WMV 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 MPG file behind the measurement on this page was 3 seconds of 320 by 240 test pattern at 25 frames a second, with a sine wave on the audio track, built by ffmpeg for the probe itself. That is why MPG to WMV came out at 0.2 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.
Video is the one thing on this site that genuinely costs machine time, and the cost swings by two orders of magnitude with the encoder the container asks for: on this machine one minute of 720p source came out as AVI in 8.4 seconds and as WebM in 87, and the same minute in 1080p took 104. Expect a WMV to cost somewhere between a fraction of the MPG running time and twice it, not the tenth of a second the probe file took.
An MPG longer than 120 seconds is refused before any encoding starts, with an answer that names both limits, 150 MB and 120 seconds. It is not an upsell: two minutes of WMV encoding is roughly two minutes of the only machine there is, and the live traffic shares the same two cores.
MPG to WMV is the single conversion here that is not charged at the floor rate. It costs 2 credits per minute of MPG, every started minute counts, and because the engine refuses past 120 seconds one MPG to WMV run can never cost more than 4 credits. The figure is on the button before you press it.
One WMV encode at a time, and that was measured before it was decided. Two simultaneous transcodes do fit in memory, about 320 MB each, but each one goes from 104 seconds to 189: this machine is short of processor, not of memory, so throughput gains ten percent while the wait doubles. MPG to WMV therefore queues on a single slot and gives up after 25 seconds rather than piling up.
Nothing here reads what is inside the MPG. No transcription, no scene detection, no summary: MPG to WMV is a container and codec operation, and the WMV says exactly what the MPG said, in a different wrapper. The picture is the whole payload.
One MPG file at a time, chosen in the browser. There is nothing else to set up and nothing else on offer.
MPG to WMV: what people ask
What actually converts my MPG file to WMV?
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 MPG file is uploaded once, ffmpeg runs once, the WMV comes back, and neither file is kept afterwards.
How long does MPG to WMV take?
The probe measured 0.2 seconds for 180,119 bytes of WMV, on a 3 second test pattern, and that number is honest about the plumbing and useless about your file. A video target re-encodes every frame: budget somewhere between a fraction of the MPG running time and twice it. The MPG is refused past 120 seconds, so the worst case is bounded.
What do I lose going from MPG to WMV?
The one to know about first: Every pixel, one more time. The MPG is decoded to raw frames and re-encoded as WMV, so whatever the MPG had already lost stays lost and this pass adds its own on top. Run one file through the loop four or five times and the damage is visible without looking for it.
Why did my WMV come back narrower than the MPG?
Because the engine caps every video output at 1280 pixels wide. Encoder cost grows with pixel count, and a 4K MPG would cost about sixteen times a 1080p one on a machine that also serves everybody else. An MPG at or below 1280 pixels comes back at its own size, untouched.
Is MPG to WMV free?
There is a free allowance every month, and MPG to WMV is the one conversion here that is not charged at the floor rate: 2 credits per minute of MPG, every started minute counted, capped at 4 credits because the engine refuses past 120 seconds. Re-encoding a WMV costs real machine time, so it is priced on the time it costs. The number is shown before you press anything.