Initializing... drag & drop files here
Supports: MKV
This re-encodes the video inside a Matroska (.mkv) file to Motion JPEG and writes it out as a raw .mjpeg stream — a back-to-back sequence of complete JPEG images with nothing wrapped around them. That design is exactly why editors and machine-vision pipelines like MJPEG: every frame stands alone, so any frame can be decoded or scrubbed to without touching its neighbours. It is also why the output is large, silent, and carries none of the extras your MKV held. This tutorial covers the settings that matter, what the file genuinely contains when it lands, and when you should be converting to MP4 instead.
.mkv onto the page or click "+ Add Files". Several files can be queued and run with the same settings..mjpeg. No sign-up, no watermark..mjpeg File Actually IsMost formats are a container holding streams. This one is not. A .mjpeg file is the video elementary stream on its own — JPEG frame, JPEG frame, JPEG frame, with no wrapper to describe what any of it is. Three consequences follow, and all three surprise people:
| Content | Present in a raw .mjpeg? |
|---|---|
| Video frames | Yes — a sequence of complete, independent JPEG images |
| Audio | No — the file is silent |
| Frame rate and duration | No — the reader applies its own default |
| Subtitle tracks and chapters | No |
| Attachments, tags, cover art | No |
| Per-frame random access | Yes, inherently — every frame is a keyframe |
Motion JPEG is intraframe-only: there is no prediction between frames, so a static shot re-encodes the entire scene on every single frame instead of describing what changed. That lack of interframe prediction limits real-world efficiency to roughly 1:20 or lower, while modern interframe formats reach 1:50 or better — so an MJPEG export of an H.264 or HEVC MKV is normally several times the size of the original. Two levers move that number meaningfully and one barely does:
MJPEG (.mjpeg) |
H.264 / HEVC inside MKV | |
|---|---|---|
| Coding scheme | Intraframe only | Interframe prediction |
| Real-world compression | About 1:20 or lower | 1:50 or better |
| Every frame a keyframe | Yes | No — depends on GOP structure |
| Damage from an error | Contained to one frame | Can propagate across frames |
| Audio in the same file | No | Yes |
| Playback outside editors | Patchy | Effectively universal |
| Best at | Frame-accurate editing, per-frame analysis | Storage, sharing, streaming |
If your goal is a smaller, broadly playable video, MJPEG is the wrong answer on every axis: it is bigger, it is silent, it loses your subtitle and chapter tracks, and it plays reliably in fewer places. Convert to MP4 instead, or shrink the original with the video compressor. MJPEG earns its place when you specifically need frame-independent access — non-linear editing, frame-by-frame review, feeding a machine-vision or analysis pipeline that wants JPEGs. If what you really want is a handful of stills rather than a stream of them, MKV to JPG extracts individual frames at chosen timestamps, which is far more convenient than picking apart an elementary stream. And if you already have MJPEG footage that needs to be shareable, MJPEG to MP4 goes the other way.
No — the output is silent. A raw .mjpeg file is a video elementary stream: a run of JPEG frames with no container around them and therefore no audio track, no track table and no way to declare one. Whatever soundtrack your MKV carried is not in the result. Keep the original MKV, convert to MP4 when you need picture and sound in one file, or extract the audio on its own with MKV to MP3 and recombine the two in an editor.
Because there is no timing data in the file to read. Container formats store the frame rate and duration in a header; a raw MJPEG stream stores nothing but the frames themselves, so software falls back to a default rate — commonly 25 fps — regardless of what the source ran at. A 30 fps clip will therefore appear stretched. The fix is on the reading side: tell your editor or analysis tool the frame rate when you import, exactly as you would for an image sequence.
Because it stores every frame in full. Motion JPEG is an intraframe-only scheme with no prediction between frames, which caps real-world efficiency at roughly 1:20 or lower; the H.264 or HEVC stream inside a typical MKV uses interframe prediction to reach 1:50 or better. Encoding the same footage without that machinery multiplies the size several times over. The only structural fixes are fewer pixels per frame or fewer frames — resolution and trim.
Through the JPEG quantizer instead. MJPEG does not support constant-rate-factor encoding the way H.264 and HEVC do; its quality scale runs from 2 to 31, with lower numbers meaning finer quantization, better frames and a larger file. That is what "Constant Quality" is setting on this page. It behaves less smoothly than a CRF ladder — the quality falls off visibly before the size drops dramatically — which is why resolution and trim remain the more effective size controls here.
None of them come across. A Matroska file can carry many audio tracks, many soft subtitle tracks, chapter markers, attached fonts and rich metadata; a raw MJPEG stream is a bare sequence of images with no structure for any of it. If the subtitles matter, burn them into the picture in a desktop tool before uploading so they become part of the frames. If chapters or multiple languages matter, keep the MKV as your master.
Non-linear editors are the natural home — Motion JPEG is widely used by non-linear video editing systems precisely because every frame is independent — and VLC will generally play the stream too. Many tools treat it as an image sequence rather than a video, which is a reasonable description of what it is. Consumer phone players, browsers and smart-TV apps commonly refuse it. That narrow support is the trade-off you accept for frame-level access.
Choose it when per-frame independence is the point. Every frame is a complete JPEG, so any frame decodes on its own, scrubbing is instant, an editor can cut anywhere without re-encoding a group of pictures, and a corrupted frame damages only itself rather than everything predicted from it. Motion JPEG is common in capture devices such as digital cameras, IP cameras and webcams for the same reason. For sharing, streaming, phone playback, small files, audio or subtitles, MP4 or your original MKV wins outright.
Not in one place. There is no single document universally recognised as the complete Motion JPEG specification; instead it is defined per container — IETF RFC 2435 covers M-JPEG in an RTP stream, Microsoft documents its storage inside AVI, and Apple documents the MJPEG-A and MJPEG-B variants for QuickTime. Matroska, by contrast, is one open container specification. That fragmentation is a large part of why MJPEG support is inconsistent outside editing software, even though the individual JPEG frames are entirely standard.
Your MKV is uploaded over an encrypted connection, decoded and re-encoded on our servers, and the files are deleted automatically a few hours later — no sign-up, no watermark, never shared or made public. Because MJPEG output is unusually large, the download can take longer than the upload did; trimming the source first with the video cutter is the simplest way to keep both ends quick.