Initializing... drag & drop files here
Supports: MJPEG
Motion JPEG stores video the simplest way anyone has thought of: every frame is a complete, independent JPEG. Nothing is shared between frames, which is why IP cameras, machine-vision rigs, microscopes and older digital cameras like it — drop a frame and the rest of the recording is still perfectly decodable — and why the files are enormous.
F4V is Adobe's H.264-era video format. Underneath it is an ISO base media file, the same family as MP4 and MOV; we confirmed a finished output probes as mov,mp4,m4a,3gp,3g2,mj2. Converting from one to the other therefore does something dramatic to the file size, because H.264 stores only what changed between frames while Motion JPEG stores everything, every time. On a six-second 640 × 480 test clip we measured 3,575,215 bytes of MJPEG becoming 736,663 bytes of F4V at default quality — a little under a fifth of the original.
.mjpeg onto the page or click "+ Add Files". IP-camera exports, webcam captures, microscope acquisitions and old camcorder clips all work, and several can be queued with the same settings..f4v. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark.| Property | MJPEG (source) | F4V (output) |
|---|---|---|
| Coding | Every frame a full, independent JPEG | H.264, storing only what changed between frames |
| Container | Often none at all — a bare stream of JPEGs | ISO base media file, the MP4/MOV family |
| Frame rate stored? | Not in a raw stream; a nominal rate is assumed | Yes, written into the container |
| Duration stored? | No | Yes |
| Seekable? | Not in a raw stream — no timestamps to seek against | Yes |
| Audio | None in a raw stream | AAC (preselected) or MP3, when the source has a track |
| Measured, 6 s at 640 × 480 | 3,575,215 bytes | 736,663 bytes |
Six modes is more than most people need, and the right one depends on what constraint you are actually under.
Whichever you choose, remember that the source is intra-frame-only. Motion JPEG has no motion prediction at all, so almost any H.264 setting will produce a much smaller file — the interesting question is usually how much further you want to go, not whether it will shrink.
| Mode | What you specify | Size is | Quality is |
|---|---|---|---|
| Quality Preset | One of seven named steps | Whatever results | Consistent |
| Constant Quality | A CRF, 16–51, opening at 23 | Whatever results | Consistent, and precisely dialled |
| Specific file size | A byte budget | Guaranteed | Whatever fits |
| Constant Bitrate | Bits per second | Predictable per second | Varies with scene difficulty |
| Variable Bitrate | A target plus a floor and ceiling | Roughly predictable | Mostly consistent |
| Constraint Quality | A CRF plus a maximum bitrate | Capped at the peaks | Consistent below the cap |
.mjpeg name do not have this problem, because those containers record the rate..mp4. The container is an ISO base media file with H.264 inside, so most players will handle the bytes perfectly well once the extension stops confusing them.Two situations are worth recognising before you spend time on them. First, if your "MJPEG file" is really an AVI, MOV or MKV that was renamed, it will convert here — files are demuxed by their contents rather than their extension — but you will get better results from the page matching its real name, because those containers carry frame rate and audio that a raw stream cannot. MJPEG to AVI and the other container targets are worth comparing.
Second, F4V is a format whose reason for existing has largely gone: Adobe stopped supporting Flash Player on 31 December 2020 and began blocking Flash content on 12 January 2021. Unless a legacy media server, a courseware package or an archive specifically wants .f4v, MJPEG to MP4 gives you the same H.264 video in a container that everything opens today.
Substantially, and the exact figure depends on how much movement is in the shot. Our six-second 640 × 480 sample went from 3,575,215 to 736,663 bytes at the default quality — about a fifth. Static camera footage with little motion compresses far harder than that, because H.264 can describe an unchanged frame in a handful of bytes while Motion JPEG has to store a whole JPEG for it.
Because the control is there for sources that do have audio, and many files reaching this page do. A raw Motion JPEG stream cannot carry an audio track, so the setting has nothing to act on — the output simply has one video stream, which we confirmed on a finished conversion. A renamed AVI or MOV source will use the setting normally.
No. They are two different containers from the same vendor. FLV is Adobe's original Flash Video container, a simple tag-based structure; F4V is built on the ISO base media file format, the same foundation as MP4 and MOV — we confirmed an F4V output probes as part of the MP4/MOV family, which an FLV does not. Both can carry H.264, so the choice between them is about what the receiving system expects, not about picture quality.
Not on this page. The output keeps whatever rate is read from the source, and for a raw Motion JPEG stream that means the assumed default rather than a recorded value. If exact timing matters, convert from the original container rather than a raw stream export.
Because H.264 is what F4V-aware software expects to find inside one. Offering H.265 or AV1 here would produce a technically valid ISO base media file that no player looking for an F4V would decode, which is worse than not offering them. If you want a more modern codec, use an MP4 or MKV target where both the container and the players around it permit it.
For evidence, scientific and machine-vision footage, yes — Keep original is preselected for exactly that reason, and upscaling or downscaling introduces resampling you probably do not want in the record. For sharing or review, dropping a 1080p capture to 720p roughly halves the pixel count and the file with it, and the difference is invisible on a phone.
No, but you have to trim from the beginning. Set the Trim duration to the length you want and leave the start at 0, then cut the front off afterwards with a tool that works on the converted file. That is awkward, and it is a genuine consequence of raw Motion JPEG having no seek information — not a restriction we chose.
It re-encodes. Motion JPEG and H.264 are entirely different coding schemes, so every frame is decoded and re-compressed. That is where the size reduction comes from, and it also means the output is one generation removed from the source — worth keeping the original if the footage is evidential.