Initializing... drag & drop files here
Supports: MJPEG
A raw .mjpeg file is just a back-to-back string of JPEG frames with no container, no seek index, and no audio track — which is why footage dumped from an IP camera, webcam, or machine-vision rig often plays as an unscrubbable blob, if a player opens it at all. This walk-through shows how to wrap that stream into a standard MKV (Matroska) container so it opens, seeks, and trims like a normal video, and how to decide between a lossless rewrap and a smaller re-encode.
.mjpeg file or click "+ Add Files". Batch upload is supported, so a folder of camera or capture dumps can go through in one pass.The whole conversion comes down to step 2, because a raw MJPEG stream carries no audio — the MKV is silent either way (see below), so the only real decision is what happens to the picture. MJPEG compresses each frame independently as a full JPEG with no interframe prediction, which is why the files are large but every frame is a clean, self-contained still.
.mjpeg, not the converted MKV. MKV writes a seek index (Cues), so scrubbing works once you play the downloaded .mkv, not the original dump.This converter wraps the single video stream you upload, so it can't recover audio that was never in the file. Raw .mjpeg captures from IP cameras, webcams, and vision systems are typically video-only; when those devices record sound at all, the audio is usually stored separately, so the MKV comes out silent. If you have a matching audio file, it has to be muxed in as a distinct step. The tool also can't open a corrupted or partial stream — if a camera dump was cut off mid-write, a player like VLC may still scrub what's there even when a clean re-wrap fails.
Because a raw .mjpeg elementary stream contains only video frames — there is no audio track in the source to carry over, so the MKV comes out with picture only. This is normal for IP-camera, webcam, and machine-vision captures, which record MJPEG video separately from any audio. If your audio lives in a separate file, it has to be muxed in as its own step; this converter wraps the video stream you upload.
Only if you choose the MJPEG codec, which copies the original JPEG frames into the MKV without re-encoding — pixel-for-pixel identical to the source. The default re-encodes to H.264, which adds one lossy generation on top of the JPEG compression already in the frames. For forensic, archival, or machine-vision footage where frame fidelity matters, pick MJPEG; for everyday playback where a smaller file is worth a slight quality cost, keep the H.264 default.
Renaming .mjpeg to .mkv doesn't work — the bytes inside are a bare JPEG sequence with no Matroska structure, so a player either rejects it or refuses to seek. The conversion actually rebuilds the file with a real container: timing, a seek index, and track metadata. Per the Matroska specification (IETF RFC 9559, published October 2024), MKV stores Cues and SeekHead elements that let players jump instantly to any timestamp — exactly what a raw stream lacks.
It depends on the codec. Keeping MJPEG produces a file about the same size as the source, because the frames are copied unchanged. Re-encoding to H.264 is dramatically smaller because interframe coding reaches real-world ratios around 1:50 versus MJPEG's roughly 1:20. In our testing, a 30-second 720p MJPEG capture re-encoded to H.264 came out roughly four to five times smaller than the rewrapped MJPEG-in-MKV version; a longer, mostly-static surveillance clip compresses even further.
Use MKV when you want an open, archival-friendly container that can later hold multiple audio tracks, subtitles, and chapters — it's a royalty-free open standard (now IETF RFC 9559) and is widely used for archiving footage frame-for-frame. Choose MJPEG to MP4 instead when the priority is playback on phones, smart TVs, and browsers, where MP4 support is more universal than MKV. Going the other way, convert MKV to MJPEG to pull an existing MKV back to independent JPEG frames.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public. Nothing is kept beyond the short processing window, so security-camera and other sensitive footage is not retained.