Initializing... drag & drop files here
Supports: MJPEG
This walks you through pulling a still image out of a Motion JPEG (MJPEG) video and saving it as a WebP — either a single frame grabbed at a timestamp, or a series of screenshots taken at a fixed interval. It is built for the most common MJPEG sources: IP and security cameras, webcams, and digital cameras, where each frame is stored as its own JPEG and a grabbed still comes out clean.
.mjpeg clip onto the page or click "Add Files". You can queue several clips at once; each is processed with the same settings.The whole conversion turns on one choice in Frame Selection, so it is worth getting right.
Because MJPEG is intraframe-only — every frame is a complete, independent JPEG with no reference to the frames around it — any single frame you grab is already a full, sharp image. There are no inter-frame motion artifacts to clean up, unlike grabbing a still from H.264 or HEVC where you can land on a predicted frame. That makes MJPEG one of the cleanest sources for a still grab.
There is no single universal "MJPEG" file — the same Motion JPEG frames are carried inside different containers (AVI, QuickTime .mov, Matroska, or an RTP stream per RFC 2435), and some camera exports wrap MJPEG in a container that is not a plain .mjpeg stream. If your file does not upload as MJPEG, it may actually be an .avi or .mov holding MJPEG data; convert from that container instead. For a maximally compatible still that opens everywhere with no format questions, grab a JPEG instead. To pull a WebP frame from a regular H.264 video rather than MJPEG, use MP4 to WebP.
A still image. This tool grabs one frame (or a set of separate frames via Multiple Screenshots) and saves each as its own static WebP — it does not assemble an animated WebP. Each output is a single picture you can open in any modern browser.
Usually, yes. MJPEG is intraframe-only: every frame is a complete JPEG with no dependence on neighboring frames, so the grabbed still has no inter-frame prediction artifacts. With H.264 or HEVC video you can land on a predicted frame and pick up blocking or smearing, which MJPEG avoids by design.
In the typical lossy case, yes. Google measures WebP lossy images at 25–34% smaller than comparable JPEGs at equivalent SSIM quality, so a WebP still is normally lighter than the same frame saved as JPEG. If you choose Lossless?, the WebP becomes a pixel-exact copy and can be a similar size to the source frame.
Use Lossless?: "Yes". Lossless WebP reproduces the frame pixel-for-pixel with no compression loss, which matters when the still has to hold up to scrutiny. For a thumbnail, a web upload, or anything where a slightly smaller file beats perfect fidelity, lossy at a high Quality Preset is the better trade.
Yes — choose Multiple Screenshots and a capture rate. "1 second per frame" gives one WebP per second of footage; you can go as fine as 0.1 s or as coarse as 10 s per frame. In our testing, a one-minute MJPEG at "1 second per frame" produced 60 separate WebP stills, one per second of the clip.
Your file is sent over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion. There is no sign-up, no watermark, and files are never shared or made public.