Initializing... drag & drop files here
Supports: MJPEG
.mjpeg, .mjpg, or .mj2 clip into the converter, or click "Add Files" to select from disk. Batch conversion is supported for processing many security-camera or microscope captures at once.HH:MM:SS.sss to clip to a specific incident or sample window.Motion JPEG (MJPEG) compresses each frame as an independent JPEG image with no inter-frame prediction. That intra-only design is loved by IP cameras, microscopes, and machine-vision rigs because every frame is a keyframe — you can scrub, cut, or pull a still without decoding a GOP — but it produces files roughly 2-3× larger than H.264 at matched quality (Wikipedia notes typical compression ratios near 1:20 vs 1:50+ for modern codecs). Repackaging to MOV with H.264 or H.265 unlocks Apple-native playback in QuickTime Player, Final Cut Pro, and iMovie, slashes storage, and produces files that stream cleanly over the open web.
| Property | MJPEG | MOV (H.264) |
|---|---|---|
| Compression scheme | Intra-only — every frame is a JPEG | Inter-frame (I/P/B GOP structure) |
| Typical compression ratio | ~1:20 | ~1:50 or better |
| 1 minute, 1080p file size | ~500 MB-1 GB | ~50-150 MB |
| Frame-accurate cuts | Yes — every frame is a keyframe | Requires GOP decoding or re-encode |
| CPU/memory at encode | Low | High (motion estimation) |
| Native macOS/iOS playback | Limited (Safari + plugin) | Universal (QuickTime, all browsers) |
| Standards body | None — no universal spec | ITU-T H.264 / ISO MPEG-4 Part 10 |
| Common sources | IP cameras, microscopes, webcams | iPhones, mirrorless cameras, NLE exports |
| Codec | Best for | Size vs MJPEG | Compatibility notes |
|---|---|---|---|
| H.264 (default) | Web, social, iPhone, all NLEs | ~3-5× smaller | Universal — Chrome, Firefox, Safari, Edge, QuickTime, every iOS/Android device |
| H.265 (HEVC) | 4K archival, smaller masters | ~6-10× smaller | macOS High Sierra+, iOS 11+, Edge; Chrome 107+ on supported hardware |
| MPEG-4 (Part 2) | Legacy QuickTime, older players | ~2-4× smaller | Broad but dated; pick when targeting pre-2010 software |
| MJPEG | Frame-accurate editing, science work | Similar size (high-quality re-encode) | Keeps intra-only JPEG structure inside a MOV container |
MJPEG encodes each frame as an independent JPEG with no inter-frame prediction, so a static scene takes the same bits as fast motion. H.264 only encodes the differences between successive frames (motion compensation plus residual coding), which is why a typical 1-minute 1080p clip drops from ~500 MB-1 GB as MJPEG to roughly 50-150 MB as MOV/H.264.
H.264 is the safer default — it plays in every browser, every iPhone, every NLE. Pick H.265 if you have a lot of 4K source, want the smallest files, and your viewers are on macOS High Sierra+, iOS 11+, recent Edge, or Chrome 107+ with hardware decode. For mixed audiences, stick with H.264.
Yes — pick MJPEG under Video Codec and the converter keeps each frame an independent JPEG inside the MOV, re-encoding with the intra-only MJPEG codec at high quality rather than switching to interframe H.264. That keeps the frame-accurate cut points and stays visually very close to the source — useful for scientific or forensic workflows — though it is a re-encode, not a bit-for-bit copy, so set the quality high when frame fidelity is critical.
Yes. MOV is Apple's native QuickTime container, and H.264, H.265, and MPEG-4 are all first-class in QuickTime Player, Final Cut Pro, iMovie, and DaVinci Resolve. If you also need it on Windows, modern Windows 10/11 plays MOV/H.264 natively in the Movies & TV app — no QuickTime install required.
IP security cameras (Axis, Hikvision, Dahua), USB UVC webcams, older Canon/Nikon DSLRs in movie mode, industrial machine-vision frame-grabbers, microscopes, endoscopes, and many fundus and IVD imaging systems. The format is favored anywhere frame-accurate access matters more than storage efficiency.
Open Trim in Advanced Options, set Start to the incident time (e.g. 00:14:32.000) and Duration to how much you want (e.g. 45 for 45 seconds or 00:00:45.000). Only that segment is decoded and re-encoded — the rest is skipped, which is much faster than converting the whole hour-long capture.
Both MJPEG and H.264/H.265 are lossy, so transcoding adds a small amount of generation loss. With Quality Preset set to Very High or Highest the result is visually indistinguishable from the source on normal viewing. If you want to stay closest to the source, choose MJPEG under Video Codec — it re-encodes each frame with the intra-only JPEG codec at high quality (no interframe prediction), which stays visually nearest the original short of a raw stream copy.
Yes — use MJPEG to MP4 for that direction. MP4 and MOV are closely related (the ISO standardised the QuickTime file format as the basis for MP4), so the resulting files are similar in size and quality; pick MOV for Final Cut and Apple-centric pipelines, MP4 for broadest cross-platform delivery.
Either re-run with the Medium or Low Quality Preset, drop the resolution to 720p, or send the output through Compress MOV for fine-grained file-size targeting. For frame-accurate cutting, our Video Cutter trims MOV files keyframe-aware.