Initializing... drag & drop files here
Supports: MP4, M4V
This walks through turning an Apple M4V clip (H.264 video, usually with AAC audio) into Motion JPEG — and, more importantly, when that trade is worth it. The headline you need up front: MJPEG re-encodes every frame as a standalone JPEG, so the output is normally several times larger than the M4V, not smaller. You do it for frame independence (clean per-frame seeking and extraction), not for file size.
.m4v clips. iPhone/iPad exports, iMovie outputs, screen recordings, and DRM-free iTunes/Apple TV files all work. Batch is supported. FairPlay-DRM purchases will not convert (see "When This Doesn't Work").MJPEG file size scales with three things you control here — preset, resolution, and duration — and because there is no inter-frame compression, every one of them multiplies linearly. A one-minute 1080p M4V that sits at 40-80 MB as H.264 can land anywhere from a few hundred MB to over a GB as MJPEG, depending on these settings. Set them deliberately:
DRM-protected iTunes and Apple TV purchases are wrapped in Apple's FairPlay encryption, and no online tool can convert them — the conversion will fail or hand back an empty file. This is a hard limit, not a quality setting; only DRM-free M4V (your own iPhone/iPad exports, iMovie projects, screen recordings, and most non-purchased clips) converts. Separately, if your real goal is a smaller, broadly playable file rather than frame independence, MJPEG is the wrong target entirely — convert to M4V to MP4 for an efficient H.264 file that plays nearly everywhere, or use MP4 to MJPEG if you are starting from a plain MP4 instead.
That is expected and unavoidable. M4V carries H.264, which reuses pixels across frames; MJPEG compresses each frame as a standalone JPEG with no inter-frame savings, so its real-world efficiency is only around 1:20. A one-minute 1080p clip that fits in 40-80 MB as H.264 commonly lands at several hundred MB to over a GB as MJPEG. If size matters, lower the preset, reduce resolution, or trim to only the seconds you need — or reconsider whether you actually need MJPEG at all.
No. Movies and TV shows purchased from the iTunes/Apple TV store may be wrapped in Apple's FairPlay DRM, which prevents conversion by any online tool — the job fails or returns an empty file. DRM-free M4V (iPhone/iPad exports, iMovie outputs, screen recordings, and clips you produced yourself) converts without issue. There is no setting on this page that bypasses FairPlay.
The MJPEG codec itself is video-only — it describes frames, not sound. Audio, when it survives, is carried by the container around the frames rather than by MJPEG. For machine-vision, surveillance, or capture pipelines this silence is usually fine. If you need the audio guaranteed alongside the video, keep an MP4/MOV copy — M4V to MP4 preserves the AAC track in a far smaller file.
If you need a playable clip for a legacy editor, capture card, NVR, or machine-vision rig that expects frame-independent video, choose MJPEG. If you only need still images for analysis, training data, or a thumbnail, skip the video step and use M4V to JPG — the JPEG pixel data is identical either way, and the still output is dramatically smaller than a full MJPEG video.
For one property H.264 can't match cheaply: every frame is a self-contained image with no dependency on its neighbors. That makes seeking instant, frame-accurate cuts clean, and per-frame extraction reliable — which is exactly why older non-linear editors, capture cards, IP cameras, webcams, and scientific/forensic pipelines standardized on it. In our testing, a 720P MJPEG proxy scrubbed frame-by-frame in an older editor with none of the GOP-decode lag the original H.264 M4V showed. You are buying frame independence and paying for it in bytes — a deliberate trade, not an upgrade.
Your file is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after the conversion — no sign-up, no watermark, never shared or made public.