MJPEG to AV1 Converter

Convert MJPEG to AV1: What This Actually Produces

Motion JPEG stores every frame as a complete, standalone JPEG with no compression between frames, which is exactly why footage from IP cameras, capture cards, webcams and machine-vision rigs gets so bulky — surveillance vendors put MJPEG at roughly 5-20x the storage of H.264 for the same recording. AV1, the royalty-free AOMedia codec, adds the inter-frame compression MJPEG never had, so the same clip lands dramatically smaller. Two things to know before you start: the .av1 file you download is a Matroska container under a codec-style extension (rename it to .mkv and everything opens it), and a bare .mjpeg stream carries no audio track, so the result is silent because the source is.

How to Convert MJPEG to AV1

1. Upload Your MJPEG File: Drag your .mjpeg or .mjpg onto the page, or click "Add Files" to browse. Several files can be queued and converted with one set of settings.
2. Pick a Mode Under File Compression: This group opens on Quality Preset, whose dropdown offers Highest through Lowest with Very High (Recommended) preselected. Switch to Constant Quality if you would rather set an explicit CRF (AV1's slider runs 16-63, lower being better), or Specific file size to name a megabyte target.
3. Set Video Resolution or Trim (Optional): Video resolution starts on Keep original; Preset Resolutions picks a height and lets width follow the source aspect, and Width x Height takes exact pixels. Trim exports only a time range.
4. Convert and Download: Click Convert and save the file. Uploads travel over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours. No sign-up, no watermark.

Walk-through: Which Rate-Control Mode to Use

The File Compression group is where this conversion is won or lost, and the modes are not interchangeable. AV1 is a true CRF codec here, so all of them work — unlike the older MPEG-4 targets, where the quality slider degrades into a qscale.

• You just want it much smaller: leave Quality Preset alone. It maps your chosen preset to a CRF value that is also aware of the output resolution, so a downscaled clip is not over-compressed twice.
• You are comparing encoder settings across clips: use Constant Quality and set the CRF yourself. AV1's range on this page is 16-63; lower numbers mean better quality and a bigger file. Do not carry over an x264 habit of "23" — on a 0-63 scale that is a much higher quality point than it is on 0-51.
• You need a hard ceiling: Constraint Quality pairs the CRF field with Max bitrate, plus Qmin and Qmax bounds, so quality floats but the stream never exceeds your cap.
• You need an exact deliverable size: Specific file size takes a value in bytes, kilobytes or megabytes. Combining an aggressive size target with a big downscale is where visible damage starts — change one variable at a time.

Whatever you pick, the server re-encodes the video; there is no stream-copy path from JPEG frames into AV1, because the two have nothing in common at the bitstream level.

MJPEG vs AV1 at a Glance

What the .av1 File Really Is

Common Errors and How to Fix Them

• "My player won't open the .av1 file" — Most software dispatches on file extension, and almost nothing registers .av1. Rename it to .mkv; the bytes are already a valid Matroska file.
• "The video is silent" — Expected. A bare Motion JPEG stream has no audio track, so there is nothing to encode. If your footage lives in an AVI or MOV that does have sound, convert that file instead.
• "Playback runs too fast or too slow" — Raw MJPEG stores no frame timing at all, so decoders fall back to a default of 25 fps. If your camera actually recorded at 15 or 30 fps, the duration will not match what you expected.
• "The conversion is taking a long time" — AV1 evaluates far more prediction modes and partition shapes than H.264 does. Long or high-resolution clips take real time; MP4 with H.264 finishes much faster if speed matters more than the last few percent of size.
• "The output still looks soft" — The source frames were already JPEG-compressed by the recording device. This is a lossy-to-lossy re-encode, so it can preserve detail but never restore it.

Frequently Asked Questions

Why does my downloaded file have a .av1 extension instead of .mkv?

Because .av1 names a codec, not a container, and AV1 has no elementary-stream file format that ordinary players read. Our pipeline maps AV1 output to a Matroska container, so the file you get is a real MKV that simply carries a codec-style extension. Rename it to .mkv and VLC, mpv, MKVToolNix and MKV-aware editors will treat it exactly like any other Matroska file — nothing is re-encoded by renaming.

How much smaller will my MJPEG file get as AV1?

Usually a lot, and the reason is structural rather than a matter of tuning. MJPEG never compares one frame to the next, so a hallway camera pointed at an empty corridor spends the same bits every frame as it would on fast action. AV1 removes exactly that redundancy, so near-static surveillance and microscope footage shrinks the most, while high-motion handheld video saves less. Independent surveillance guidance puts MJPEG at roughly 5-20x the storage of an inter-frame codec, and AV1 sits at the efficient end of that comparison.

Will converting to AV1 make the picture sharper?

No. Every frame in your source is already a JPEG, which means high-frequency detail was discarded when the camera encoded it. AV1 is a second lossy pass, so it can hold on to what survives but cannot rebuild what was thrown away. The gain here is size and portability at comparable perceived quality. If you want to give up as little as possible, use Constant Quality with a low CRF value and keep the original resolution.

What can actually play an AV1 file?

Per caniuse, AV1 video decoding reaches about 94% of tracked browser usage when partial support is counted: Chrome 70 and later, Firefox 67 and later, and Edge 121 and later have it, while Safari 17 is listed as partial. On the desktop, VLC and mpv decode AV1 regardless of browser support. For playback on older phones, TVs and set-top boxes that predate AV1 hardware decode, MJPEG to MP4 with H.264 is the safer target.

Why is there an Audio Codec dropdown if the output has no sound?

The Audio Codec control is shared by every video target on the site, so it renders here too. It has nothing to act on: a raw Motion JPEG elementary stream is a sequence of JPEG images with no audio substream, so no matter what you select, the encoder has no samples to compress and writes a video-only Matroska file. That is a property of the source format, not a limitation of the AV1 output — the container would carry a soundtrack perfectly well if one existed.

Why does my converted clip have a different duration than I expected?

Raw MJPEG carries no timestamps. The format simply concatenates JPEG frames, so a decoder has no way to know the capture rate and falls back to an arbitrary default — commonly 25 fps, which is the value FFmpeg assumes when nothing else specifies one. A 300-frame capture recorded at 15 fps therefore reports 12 seconds rather than 20. If exact timing matters, record or export into a real container such as AVI, MOV or MKV instead of a bare stream.

Should I convert to AV1, HEVC, or plain H.264?

Pick AV1 for the smallest file when your playback targets are current — modern browsers, recent phones, or your own archive. Pick HEVC when you want most of the size benefit with faster encoding and broad hardware decode on 2017-and-later devices, accepting that it is patent-encumbered. Pick MP4/H.264 when the file has to open on absolutely anything without a second thought. All three beat MJPEG on size by a wide margin, so the choice is really about compatibility and encode time.

What happens to my file after the conversion finishes?

It is uploaded over an encrypted connection, converted on our servers, and then deleted automatically after a few hours along with the output. Nothing is shared, published or indexed, there is no sign-up, and the result carries no watermark. Because processing happens server-side, the practical limit on a very long capture is upload time rather than anything on your end — a multi-gigabyte MJPEG recording is best trimmed with the video cutter first, or scoped with the Trim control before you convert.