Initializing... drag & drop files here
Supports: MPG, MPEG
This converter pulls a single still frame out of an MPG (MPEG-1 / MPEG-2) video and saves it as a static WebP image — it does not build an animated WebP. This walk-through shows how to land on the exact frame you want, how to keep the picture sharp, and what to do when a frame comes out blurry or interlaced.
.mpg or .mpeg clip onto the page, or click "+ Add Files." Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion.2.100 for the frame at 2.1 seconds). That single frame becomes your WebP.The whole game with a video-to-image grab is the timestamp. MPG runs at a fixed frame rate (usually 25 fps for PAL-sourced files or ~29.97 fps for NTSC), so each frame is roughly 0.033–0.040 seconds apart. The Time (seconds) field accepts decimals, which is how you target one frame instead of the rough second.
10.4.120 or similar and re-run if it's off by a frame.If you need several stills from the same clip, the converter also exposes a Multiple Frames mode that samples frames across the video instead of a single timestamp — useful for a contact sheet of thumbnails.
If you actually want motion — a short looping animation rather than one frozen frame — this tool is the wrong fit, because it only outputs a static WebP. Cut the segment you want with Video Cutter and keep it as video, or export a GIF instead. This converter also can't read DRM-protected or corrupted MPG files: if the upload fails or the preview is black, the source stream is likely encrypted or truncated, and no online frame-grabber can recover it.
A single still image. This converter captures one frame at the timestamp you enter in Time (seconds) and encodes it as a static WebP. WebP can hold animation, but this tool does not build animated WebP — for motion, keep the clip as video with Video Cutter.
For a pixel-exact still — archiving, editing, or any image you'll re-edit — set Lossless? to Yes. For a web thumbnail or preview where small file size matters more than perfection, leave it on the default (lossy): Google measures lossy WebP at 25–34% smaller than an equivalent-quality JPEG, so a lossy still is usually the right call for the web.
Two common causes. Blur comes from grabbing a frame during fast motion — shift the Time (seconds) value a few hundredths of a second to find a still moment. Horizontal "combing" lines come from interlaced MPEG-2 source (common on DVD and camcorder footage); choose a frame where the subject isn't moving, which minimizes the comb artifact in a single field-paired frame.
In modern browsers, yes. WebP is supported in Chrome 32+, Firefox 65+, Edge 18+, and Safari 16+, which together cover roughly 96% of global browser usage per caniuse.com. Older desktop image viewers and some legacy editing apps may not open WebP — if you need maximum compatibility, grab the frame as JPG instead via Convert MPG to JPG.
The frame is captured at the video's native resolution (for example 720×480 for NTSC DVD-quality MPEG-2, or 1920×1080 for HD MPG), and you can scale it down with Resolution Percentage. The WebP format itself caps out at 16,383 × 16,383 pixels per Google's spec, which is far larger than any standard-definition or HD MPG frame, so the format is never the limiting factor here.
No — video frames are fully opaque, so there's no alpha channel to preserve. WebP does support transparency, but a frame grabbed from MPG will be a solid rectangular image. In our testing, a 720×480 PAL MPEG-2 frame exported at the Very High preset produced a roughly 25–40 KB lossy WebP, with the lossless version several times larger.