Initializing... drag & drop files here
Supports: MJPEG
A raw .mjpeg file is not really a video file — it is a bare elementary stream: a string of complete JPEG frames with no container, no index, and no audio track, which is why IP cameras, machine-vision rigs, and old digicams dump footage that many players refuse to seek or scrub. This converter wraps that stream into a standard AVI container so Windows Media Player, VLC, and ordinary editors can open, seek, and trim it. The one real decision is the codec: keep the MJPEG codec (a same-codec re-encode that preserves the intra-only, frame-accurate structure) or switch to MPEG-4 to shrink the file. Either way the output AVI is silent, because the source stream carries no audio.
| Property | Value |
|---|---|
| Full name | Motion JPEG |
| Based on | JPEG still-image coding (ISO/IEC 10918, 1992), applied per frame |
| Formal standard | No single universal spec — documented per implementation (QuickTime MJPEG-A/B, RFC 2435 for RTP) |
| Input container here | Raw MJPEG elementary stream (.mjpeg) — a sequence of JPEG frames |
| Video coding | Intra-only — every frame a complete, independent JPEG |
| Audio | None — the raw .mjpeg stream is video-only and silent |
| Compression | Spatial only, roughly 1:20 efficiency versus about 1:50 for H.264 |
| Typical source | Security cameras, NVR/DVR recorders, machine-vision and inspection rigs, UVC webcams |
| Property | Value |
|---|---|
| Full name | Audio Video Interleave |
| Introduced | Microsoft, November 1992, as part of Video for Windows |
| Based on | RIFF (Resource Interchange File Format) — data split into tagged chunks |
| Container role | Multimedia container that can carry a video track plus optional audio |
| Default codec here | MPEG-4 Part 2 (ISO/IEC 14496-2) — the DivX/Xvid-family "MPEG-4" ASP encoder |
| Alternate codec here | MJPEG — copies the source JPEG frames into the AVI unchanged |
| Large-file support | Older tools cap files near 2 GB; the OpenDML / AVI 2.0 extension (Feb 1996) lifts that |
| Native playback | VLC, Windows Media Player, and most desktop editors, no extra codec pack |
| Best for | Legacy Windows workflows and editors that reject a bare .mjpeg stream |
A raw MJPEG stream carries no audio, so the AVI is silent no matter which codec you choose; the only real decision is whether to keep the JPEG frames or convert them.
| Keep MJPEG (same codec) | Switch to MPEG-4 (default) | |
|---|---|---|
| What happens to frames | Original JPEG frames copied as-is into AVI | JPEG frames decoded, re-compressed with MPEG-4 |
| Quality | Identical to source — no generational loss | One lossy generation on top of the JPEG frames |
| File size | Large — MJPEG efficiency is roughly 1:20 | Much smaller — interframe coding reaches ~1:50 |
| Speed | Very fast — no encoding step | Slower — every frame is re-encoded |
| Best for | Forensic/archival masters, machine-vision data, frame-accurate review | Sharing, email, storage, general playback |
MJPEG compresses each frame independently with no interframe prediction, so it is inefficient but every frame is a clean, self-contained still — the property that makes it popular for cameras and vision systems in the first place. If you only need the footage to be watchable and small, the MPEG-4 default is the right call; if a frame might become evidence or a measurement, keep MJPEG.
.mjpeg file or click "Add Files". Batch upload is supported, so a folder of camera or capture dumps can go through in one pass. Files are uploaded over an encrypted connection and deleted automatically a few hours after conversion.Not bit-for-bit — every conversion here re-encodes; there is no stream-copy pass. Choosing the MJPEG codec keeps the frames JPEG-coded with no cross-codec change, so at the Very High preset the output is visually indistinguishable from the source, but it is a fresh encode rather than a copy of the original bytes. For forensic or machine-vision work that needs the exact original frames, extract them locally with ffmpeg instead; for everyday playback, the MPEG-4 default trades a slight quality cost for a much smaller file.
Because a raw .mjpeg elementary stream contains only video frames — there is no audio track in the source to carry over, so the AVI comes out with picture only. This is normal for IP-camera, webcam, and machine-vision captures, which usually record MJPEG video separately from any audio. If your audio lives in a separate file, it has to be muxed in as a distinct step; this converter wraps the video stream you upload.
MPEG-4 Part 2 (ISO/IEC 14496-2), the advanced-simple-profile encoder shared by the DivX and Xvid families. It is an interframe codec, so it removes redundancy between frames and produces a much smaller AVI than the JPEG-per-frame source. If you would rather not re-encode at all, switch the Video Codec to MJPEG and the tool copies your existing JPEG frames straight into the AVI instead.
It depends entirely on the codec. Keeping MJPEG produces a file about the same size as your source, because the frames stay JPEG-coded at a similar quality level — MJPEG's intra-only design limits efficiency to roughly 1:20. Re-encoding to MPEG-4 is dramatically smaller because interframe coding reaches real-world ratios around 1:50; a long, mostly-static surveillance clip can shrink several-fold. In our testing, a 30-second 720p MJPEG capture re-encoded to MPEG-4 came out roughly four to five times smaller than the keep-MJPEG version.
Yes. AVI is a Microsoft RIFF container that VLC, Windows Media Player, and most desktop editors open without extra codecs, which is the main reason to wrap a raw MJPEG stream at all — players that choke on a bare .mjpeg file handle MJPEG-in-AVI or MPEG-4-in-AVI cleanly. Note that older tools cap AVI files near 2 GB; very long captures rely on the OpenDML (AVI 2.0) extension that modern software writes automatically.
The per-frame image data is the same JPEG either way — the difference is packaging. Wrapping into AVI gives you a single playable clip that a legacy recorder, editor, or Windows player can scrub. If instead you only need the individual stills for analysis or a dataset, skip the video step and use MJPEG to JPG, which writes each frame as a separate .jpg file.
AVI is the right target when a legacy Windows editor, capture card, or player specifically expects it — but it is a bulky, dated container. For anything you plan to email, upload, or play on a phone, MP4 with H.264 is far smaller and more universally supported; use MJPEG to MP4 for that. Going the other way, AVI to MJPEG pulls an existing AVI back into an independent-frame stream for editing or inspection.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public. Nothing is kept beyond the short processing window, so security-camera and other sensitive footage is not retained.