Initializing... drag & drop files here
Supports: AVIF
This walk-through is for anyone who has a modern AVIF still image and a pipeline — an old DVD-authoring tool, a broadcast-era editing suite, a kiosk or embedded player — that only accepts legacy .mpeg files. By the end you will have turned your picture into a short, silent MPEG clip that holds the image on screen for a duration you choose, and you will know which settings keep it as sharp as the format allows. One thing to set expectations up front: the output is one motionless frame, not an animation — the section below explains why and what to do if you need motion instead.
.avif onto the page, or click "+ Add Files". You can upload several at once; the Merge strategy control then lets you combine them into one clip ("Merge images") or output a separate video per picture ("Video per image")..mpeg. No sign-up, no watermark.The Image Duration control is the one that trips people up, because MPEG is a video format and people expect their AVIF to play. It does not. This image-to-video tool takes your AVIF, holds it as a single still picture, and repeats that one frame for the whole duration you pick — so the resulting clip looks frozen. The duration value simply decides how many seconds that one frame stays on screen before the clip ends.
A useful way to think about the dropdown: the longer values are for "show this still for a while," and the very short values are for "produce a one-frame clip at a given frame rate."
If your source is an animated AVIF, this tool still treats it as one picture rather than playing the sequence back, so you will get a single frame, not the animation. (We hedge here because behavior on multi-frame AVIF can vary.) To keep motion, start from an already-moving source instead — see "When This Doesn't Work" below.
This tool is the wrong choice when you actually need motion or modern compatibility. If your goal is a moving clip, start from a moving source — convert an existing video, or turn an animation into video with a tool like GIF to MP4 — because nothing can synthesize motion from a single still. If you just want a viewable, shareable image rather than a video at all, AVIF to JPG keeps it a picture. And if .mpeg is not a hard requirement, prefer AVIF to MP4: it is smaller, sharper, and plays on virtually every current device. MPEG only earns its place when something in your pipeline specifically demands the legacy Program Stream container. (The .mpg extension is the same format under a different name — our AVIF to MPG page covers it identically.)
No. The output is a single still frame repeated for the duration you set, so the clip looks frozen. Even when an AVIF holds an animated image sequence, this image-to-video tool treats the file as one picture rather than playing back multiple frames, so expect a single frame rather than motion. If you need movement, start from an animated source such as a GIF or an existing video.
Because the input is a still image, there is no audio to carry. The converter applies an image-to-video rule that hides the audio codec, so the .mpeg is silent by design. The Program Stream container would normally hold MP2 audio (MP2 is the default for MPEG output here), but a single picture has nothing to encode. To add sound, convert the image to video first, then attach an audio track in a video editor.
For anything modern, no — MP4 produces a smaller, sharper file that plays almost everywhere. Choose MPEG only when something in your workflow specifically demands the legacy .mpeg/.mpg Program Stream: an older DVD-authoring tool, a broadcast-era editing suite, or a player that refuses MP4. In our testing, the same AVIF still rendered to MPEG-2 came out noticeably larger and softer than the AVIF to MP4 output at matched quality and resolution.
Both are MPEG video codecs the .mpeg container can carry. MPEG-1 (ISO/IEC 11172, 1993) targeted VCD-grade quality at low bitrates; MPEG-2 (ISO/IEC 13818, first published 1995) added higher resolutions and better quality and became the codec behind DVD-Video and digital TV. This tool defaults to MPEG-2 because it generally looks better for the same file size, but MPEG-1 stays selectable for the most restrictive legacy players.
Usually pure compatibility. AVIF is efficient and detailed but young — its v1.0.0 spec only landed in February 2019 — while a lot of older or specialized software was built around MPEG Program Stream and ingests nothing but .mpeg. Wrapping your still in a short MPEG clip slots it into those workflows. It is a deliberately backwards pairing (a state-of-the-art image dropped onto a 1990s codec), so the trade is convenience for that pipeline over image fidelity. For web or everyday use there is no reason to pick MPEG over MP4.
Your AVIF is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after the conversion. There is no sign-up, no watermark, and your files are never shared or made public.