Initializing... drag & drop files here
Supports: MJPEG
MJPEG (Motion JPEG) stores video as a sequence of independently compressed JPEG frames with no inter-frame compression. That makes the source robust against frame loss but enormous on disk — a 1-minute 1080p MJPEG clip from an IP camera or microscope routinely lands at 400 MB to 1 GB. Re-encoding to MP4 with H.264 typically shrinks the file by 80-90% for the same visible quality, because H.264 only stores what changed between frames. Common reasons to convert MJPEG to MP4:
| Property | MJPEG (source) | MP4 / H.264 (output) |
|---|---|---|
| Compression | Per-frame JPEG (intra-frame only) | Inter-frame: I, P, and B frames |
| Typical 1 min 1080p size | 400 MB - 1 GB | 50-150 MB |
| Frame independence | Yes — every frame stands alone | No — most frames depend on neighbors |
| Streaming and browser playback | Limited (VLC, a few players) | Universal (HTML5 video, every device) |
| Editing in modern NLEs | Works but heavy on the timeline | GPU-accelerated decode, smooth scrubbing |
| Default audio | Often absent (security cameras) | AAC (configurable: MP3, AC3, FLAC, Opus, ...) |
| Best for | Capture, evidence review, scientific archival | Sharing, streaming, archive, mobile playback |
The defining tradeoff: MP4 / H.264 throws away frame independence to gain 5-10x compression. That's the right call for sharing and archive but the wrong call when every frame must survive standalone — for those cases, MP4 to MJPEG goes the other direction.
| Codec | Typical size vs source MJPEG | Encode speed | Compatibility |
|---|---|---|---|
| H.264 (default) | ~10-15% of MJPEG | Fast | Universal — every device since 2006 |
| H.265 / HEVC | ~5-8% of MJPEG | Medium | iPhone / Android / modern browsers, Smart TVs since 2017 |
| AV1 | ~4-7% of MJPEG | Slow | Chrome, Firefox, Edge, modern phones; older devices may not play |
| DivX / Flash / FLV | Comparable to H.264 | Fast | Legacy desktop players, embedded systems |
| CRF (H.264 Constant Quality) | Quality | File size impact | Best for |
|---|---|---|---|
| 18 | Visually lossless | ~2x larger than CRF 23 | Archival, color-graded review |
| 20-22 | High, indistinguishable on consumer screens | Slightly larger than default | YouTube uploads, polished delivery |
| 23 (default) | Good — H.264's recommended balance | Baseline | General sharing, email, cloud storage |
| 26-28 | Acceptable for preview | ~50% smaller than default | Quick previews, low-bandwidth delivery |
Typically 80-90% smaller. A 600 MB 1-minute 1080p MJPEG from a security camera usually lands at 60-100 MB as MP4 / H.264 at the "Very High" preset, and 30-60 MB at H.265 / HEVC. The exact ratio depends on motion content — a static surveillance angle compresses much harder than a busy intersection because H.264 stores only what changed between frames.
At the "Very High" preset (roughly CRF 18-20) the difference is imperceptible on a normal monitor. The size reduction comes from inter-frame compression, not quality reduction — H.264 simply doesn't repeat data that didn't change between frames. Pick "Highest" or set CRF to 18 if you need a true archival master; pick CRF 23 for sharing and CRF 28 for quick previews.
H.264 plays on every device made since around 2006 with no fuss — pick it for maximum compatibility, especially when the recipient might open the file on an older laptop or a basic media player. H.265 / HEVC produces roughly half the file size at equivalent quality and plays natively on iPhone (since iOS 11), modern Android, current macOS / Windows, and Smart TVs from 2017 onward, but older Chromebooks and some browsers still struggle. AV1 produces the smallest files but is the slowest to encode and has the narrowest device support.
Yes. The visual timestamp that Reolink, Hikvision, Amcrest, Wyze, and most NVR systems burn into the video frames is part of the image itself, not metadata, so it survives any conversion. Keep resolution at 1080P or 720P (matches most IP-camera native resolutions) so the timestamp digits remain readable; downscaling to 240P or 360P can blur small overlay text.
Most MJPEG sources (security cameras, microscopes, machine-vision rigs) record no audio at all, in which case the MP4 is silent. When audio is present (webcam, OBS capture, dashcam with mic), it's re-encoded to AAC by default — the standard MP4 audio codec that plays everywhere. MP3, AC3, EAC3, FLAC, Opus, and Vorbis are also available under Audio Codec if a downstream tool needs a specific track.
They're the same format — Motion JPEG, a sequence of independently compressed JPEG frames. Windows tools historically prefer .mjpg, while Unix and many camera vendors use .mjpeg. The internal data is identical and this converter accepts both interchangeably. Output is a standard .mp4 container regardless of input extension.
IP / security cameras pick MJPEG because every frame is independently decodable — if the network drops a packet during recording, only that one frame is lost rather than a whole group of pictures. That matters in evidentiary review where a clip might be subpoenaed. The downside is size: every frame is a full JPEG with no inter-frame savings. Converting to MP4 trades frame independence for 5-10x smaller files, which is the right call once the clip is past the review stage and you're archiving or sharing it. If the destination needs frame independence preserved, see MP4 to MJPEG.
Yes — and for MJPEG sources it's especially worth doing. Set a start time and duration under the Trim option in seconds (45.0) or HH:MM:SS.sss (00:01:30.500). Because MJPEG file sizes scale linearly with duration, cutting an hour-long camera dump to a 30-second event clip before converting can be the difference between a 36 GB upload and a 100 MB output. Trim runs entirely in your browser session.
Yes. Drop in as many .mjpg or .mjpeg files as you want; each converts in parallel within your browser session. Settings can apply to the whole batch (typical for a folder of doorbell-camera triggers or a sequence of microscope acquisitions) or be tuned per-file. Outputs download individually or as a single ZIP. For other targets, see MJPEG to AVI, MJPEG to MOV, or MJPEG to WebM.