OGV to WebP Converter

OGV to WebP — Is WebP the Right Target for a Video Frame?

If you are pulling a still out of an .ogv (Ogg/Theora video) for a web page, WebP is almost always the smaller file and the one worth choosing. If the still is going into an editor, a print job, or anywhere that will re-save it repeatedly, a lossless format is the safer landing spot. The short answer: publish it → WebP; keep editing it → PNG; email or message it → JPG. This page compares the three properly, then walks through the settings that actually change the result.

Side-by-side: WebP vs PNG vs JPG for an Extracted Frame

When to Pick WebP

• The still is going on a web page, in a CMS, or into an app that already serves WebP.
• You want the size win without dropping to JPG's quality floor — WebP's lossy mode holds up better at small sizes than JPEG does.
• The frame is going to be displayed once and not edited again.
• You need a small file with soft or masked edges — WebP keeps an alpha channel where JPG cannot, though a Theora frame arrives fully opaque so there is no transparency to carry over.

When to Pick PNG or JPG Instead

• Choose OGV to PNG when the still enters an edit-and-re-save loop, when you need it readable by every image viewer ever written, or when it is a screenshot of text or UI where PNG's lossless coding beats WebP's blur.
• Choose OGV to JPG when the recipient is a person rather than a browser — email clients, messaging apps and older photo software handle JPG without a second thought.
• Choose a moving format if a single frozen frame was never the goal: OGV to GIF makes a short loop, and OGV to MP4 keeps it as playable video. This page produces a single still image and has no motion output.

How to Convert OGV to WebP

1. Upload Your OGV File: Drag your .ogv onto the page or click "Add Files"; several clips can be queued on the same settings. 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.
2. Set Time (seconds) under Frame Selection: Specific Frame is preselected and its Time (seconds) box opens at 0, which on real footage is often a black leader or fade-up. Type the moment you want — decimals such as 7.4 are accepted — or switch to Multiple Screenshots and choose a Capture Rate to sample the clip.
3. Choose Lossless? and Quality Preset: Lossless? ships on No (Recommended) and Quality Preset on Very High (Recommended). Set Lossless? to Yes for a pixel-exact copy of the decoded frame, or leave it lossy and move the preset down for a smaller file. Specific file size with Auto Scale is there if you need to hit a byte budget instead.
4. Convert and Download: Click Convert. A Specific Frame run downloads one .webp; a Multiple Screenshots run returns each captured frame as its own .webp inside a ZIP.

Lossy vs Lossless on This Page

Frequently Asked Questions

Does this produce a moving image or a single picture?

A single picture, always. The frame-extraction path on this converter has exactly two modes: Specific Frame writes one still .webp from the timestamp you type, and Multiple Screenshots writes several separate still .webp files spaced across the clip and returns them as a ZIP. There is no motion branch — the WebP format can carry a sequence, but this pipeline does not assemble one. If you want the frame sequence to play back, use OGV to GIF for a short loop or OGV to MP4 for real video.

Is WebP genuinely smaller than PNG for a frame like this?

Yes, and the gap holds even in lossless mode. Google publishes 26% smaller than PNG for lossless WebP and 25–34% smaller than JPEG for lossy WebP at an equivalent SSIM quality index. In our own end-to-end check of the extraction chain on a detailed 640 × 480 frame, lossless WebP came out around 33% smaller than the PNG of the same frame — consistent with Google's figure, and with the usual caveat that the exact ratio moves with image content. Flat, graphic frames compress better than noisy, detailed ones in every format here.

Should I turn Lossless? on?

Only if the still is going somewhere it will be re-encoded. Lossless? = No is the default and is the right answer for anything you are publishing: it uses VP8 intra-frame coding, respects the Quality Preset, and produces a much smaller file. Lossless? = Yes switches to VP8L and stores the decoded frame pixel-for-pixel, which matters when the frame is heading into an editor and will be saved again. Note that with Lossless? on, the Quality Preset no longer trades quality for size, because there is no quality left to trade.

Will the WebP look softer than the original video frame?

It can, and there are two separate reasons. Theora is itself a lossy codec, so the decoded frame already carries whatever artefacts the original encode introduced — most .ogv files are standard definition from the pre-H.264 era, so the starting quality is modest. Encoding that frame as lossy WebP then adds a second pass. Raising the Quality Preset reduces the second effect, and setting Lossless? to Yes removes it entirely. Neither can undo the first: no output format recovers detail Theora never stored.

Which browsers will actually display the file?

Per caniuse, WebP has full support from Chrome 32, Firefox 65, Edge 18, Safari 16.0 and iOS Safari 14, covering roughly 96% of global browser traffic. MDN now lists WebP support across all current versions of Chrome, Edge, Firefox, Opera and Safari. The remaining risk is not browsers but desktop software — a number of older image viewers and editors still refuse .webp. If you are handing the file to a person rather than a web page, PNG or JPG is the safer delivery format.

Does the WebP keep the transparency the video had?

There is nothing to keep. Theora carries no alpha channel, so the frame this converter decodes is fully opaque and the output is a solid rectangle. WebP does support 8-bit alpha in both its lossy and lossless modes — Google notes lossy WebP with transparency is typically three times smaller than the equivalent PNG — so if you add transparency later in an editor, the format can hold it. It just will not arrive with any.

What timestamp should I use, and why is second zero a bad idea?

The seek value goes to the decoder literally, so leaving Time (seconds) at its 0 default gives you the very first coded frame — routinely a black leader, a fade-up, or a title card on real footage. Type the second you actually want; decimals work, so 61.25 lands a quarter-second past the one-minute mark. If you do not know which moment to ask for, run Multiple Screenshots first with a Capture Rate of one second per frame, pick the still you like from the ZIP, then re-run Specific Frame at that timestamp.

My .ogv no longer plays in my browser — will this still work?

Yes. Chrome 120 disabled Theora by default and Chromium removed it around version 123 in 2024, with Firefox disabling it by default in version 126, so .ogv playback inside a web page has largely gone away. That has no bearing on this converter: the decoding happens on our servers with standalone Ogg and Theora decoders that still read the format. If you already have a .webp and simply want it smaller, compress WebP re-encodes an existing file without going back to the video.