Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
A .m2v file is not a video file in the way an MP4 is. It is an MPEG-2 video elementary stream: the raw output of an MPEG-2 encoder, defined by ITU-T H.262, with no container wrapped around it. No audio track, no index, no metadata block, no duration field — just start codes and picture data, beginning with the sequence header 00 00 01 B3.
That is exactly why DVD authoring tools, broadcast ingest systems and hardware encoders ask for it: they want to supply the container themselves and will not accept one you built. If nothing in your workflow specifically demanded .m2v, this is almost certainly the wrong target, and the last FAQ on this page points you somewhere better.
The input side is straightforward. .jfif is an ordinary JPEG — the extension Windows Mail and a few browsers write, standardised as ITU-T T.871 — and the picker accepts .jpg and .jpeg too.
.m2v per photo instead..m2v accepts only one. MPEG-2 is preselected and is the only selection that produces a file — see the table below before you touch it..m2v. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark.The .m2v extension selects ffmpeg's raw MPEG-2 muxer, and that muxer carries MPEG-2 video and nothing else. We encoded the same still with each selection:
| Video Codec selection | What happens |
|---|---|
| MPEG-2 (preselected) | Encodes normally |
| H.264, H.265, MPEG-4, Xvid, DivX, MJPEG, H.263, H.263+, H.261 | Rejected: the muxer accepts only MPEG-2 video, and no file is written |
| MPEG-1 | Rejected earlier still — a still is encoded at one frame per second and MPEG-1 permits only the eight frame rates in its specification |
The preselected value is the working one, so leaving Video Codec alone is all you need to do. It is worth knowing why the others are there: the control is shared across every video target on the site, and .m2v is far more restrictive than most.
File Compression shows three modes — Quality Preset (preselected), Constant Quality and Constraint Quality — and on this particular route none of them does what its name suggests. MPEG-2 has no CRF mode at all, so the encoder strategy converts every quality request into a bitrate, then floors that bitrate at a resolution-derived minimum. On a still picture the requested value is always below that floor, so all three modes converge on the same number:
| Frame size | Minimum bitrate the encoder is given |
|---|---|
| Up to 1280 × 720 (≤ 921,600 pixels) | 2 Mbit/s — the absolute floor |
| Up to 1920 × 1080 (≤ 2,073,600 pixels) | Scales with pixel count; 1080p works out at about 7.5 Mbit/s |
| Larger frames | Higher again, up to a 100 Mbit/s ceiling |
In practice that ceiling is generous rather than binding: a still held for five seconds compresses to almost nothing regardless, because after the first picture every frame is a repeat. We encoded a 640 × 480 photo as a 5-second stream and got 12,196 bytes; the same photo scaled to 1920 × 1440 came back at 64,171 bytes. Frame size, not quality setting, is what moved the number — which is why step 3 above points at Video resolution.
Probing the output tells the story better than prose can. ffprobe on a finished .m2v reports format_name=mpegvideo, one stream, duration=N/A and no container bitrate. Practical consequences:
1/1 on a 1 fps encode — but there is no field saying how long the file runs.Because the file has no container to store one in. We confirmed Duration: N/A on a finished .m2v that nevertheless decoded to exactly five frames. This is normal for elementary streams and is not a sign of a bad conversion — the moment you wrap the same video in a container, the duration reappears.
No. An MPEG-2 video elementary stream is video only by definition; there is no track structure to add sound to. The DVD-era workflow that uses .m2v keeps audio in a separate file (usually .ac3 or .mp2) and multiplexes them at authoring time. If you want one file with both, use a container target such as JFIF to MPEG, which produces a program stream.
It is doing something, but not what you expect. MPEG-2 has no constant-quality mode, so the encoder strategy turns every quality request into a bitrate and then raises it to a resolution-based minimum — 2 Mbit/s for anything up to 720p. Since a quality request derived from a still picture always lands below that floor, every preset ends up at the same number. Change Video resolution instead: 640 × 480 gave us 12,196 bytes and 1920 × 1440 gave 64,171.
That depends on its rules, not on ours. Most DVD tools want MPEG-2 at a specific frame size (720 × 480 for NTSC, 720 × 576 for PAL) and a standard frame rate. This conversion writes one frame per second, which no DVD specification allows. Set Video resolution to match the standard you are authoring for, and expect the authoring tool to re-encode the timing regardless — many do that as a matter of course.
Because the source is a single photograph. Encoding 125 identical frames to fill five seconds would waste time and bytes for no visible benefit, so the image path pins the rate at 1 fps and uses Image Duration to set the length. MPEG-2 tolerates this because it can express a non-standard rate in its sequence extension — MPEG-1 cannot, which is exactly why MPEG-1 fails here.
.m2v is video on its own. .mpg and .mpeg are MPEG program streams — a container that multiplexes video with audio and carries timing information, which is why they play in ordinary media players and .m2v often does not. Same video coding underneath; different amount of wrapping around it.
Only if you change the frame's aspect ratio. JPEG has no transparency, so on a straight conversion the setting has nothing to act on. Pick a Fixed Resolution with a different shape and the picture is scaled to fit with the leftover bars painted in this colour, which is preselected to white on image sources.
No — images are normalised down to a maximum of 4096 pixels on the long edge before encoding. MPEG-2 also becomes very inefficient at large frame sizes, which is why the minimum-bitrate floor climbs so steeply above 1080p. For a still that large, .m2v is a poor archive choice in any case.
Yes, and it is almost certainly the better one. JFIF to MP4 produces H.264 in a container that phones, browsers, editors and messaging apps all open, with a real duration, a seek index and room for audio if you add it later. Choose .m2v only when a specific tool named the format.