Initializing... drag & drop files here
Supports: OGV
This conversion sits between two formats with opposite problems. OGV is an Ogg container holding Theora video, and no current desktop browser will decode it any more. HEIF is the still-image format built on the same compression technology as HEVC, and only Safari decodes it. Extracting a frame from one and saving it as the other therefore makes sense in a narrow set of cases — an Apple-centric workflow, or an archive that has standardised on HEIF — and is the wrong move for anything web-facing. This page explains where the line is.
| Property | OGV (.ogv) |
HEIF (.heif) |
|---|---|---|
| What it is | Ogg container carrying video, usually Theora | Still-image container built on the ISO base media file format |
| Compression | Theora, derived from On2 VP3; the bitstream was frozen in June 2004 | HEVC-coded image items |
| Reference library | libtheora — 1.0 in November 2008, 1.1.1 in January 2010, 1.2.0 in March 2025 | libheif, with an HEVC encoder behind it |
| Motion | Yes, it is a video | No. One picture per file here |
| Audio | Usually a Vorbis track alongside the video | None. Discarded in this conversion |
| Browser support | Chrome disabled Theora by default in 120 and Chromium removed it in 123; Firefox disabled it by default in 126; Safari never shipped it | Safari 17 and later only. Around 15% of global traffic; Chrome, Edge, Firefox and Opera do not decode it |
| Licensing | Royalty-free | Patent-encumbered, which is the main reason other browsers declined it |
| Best for | Nothing new. Legacy Wikimedia and open-source project media | Apple photo libraries and archives that have committed to it |
.ogv onto the page or click "+ Add Files"; several files can be queued and share the same settings. They are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.0 — the opening frame, which on a screencast or a converted broadcast clip is frequently black. Type a timestamp; decimals are accepted. "Multiple Screenshots" instead captures a run of frames at a rate you choose.On the same 640 × 360 frame, at each rung:
| Quality Preset | Encoder quality | File size |
|---|---|---|
| Highest | 100 | 39,580 bytes |
| Very High (the default) | 95 | 39,580 bytes — identical |
| High | 90 | 35,964 bytes |
| Medium | 80 | 27,046 bytes |
| Low | 70 | 20,423 bytes |
| Very Low | 60 | 15,452 bytes |
| Lowest | 50 | 10,961 bytes |
Highest and Very High produced byte-identical files, so moving the dropdown to the top rung is a no-op — the encoder is already at its ceiling for this content at 95. High is the first setting that changes anything. Below Medium you are stacking HEVC artefacts on top of Theora's, which on an already-soft source is rarely a good trade.
.heif file I get the same thing as a .heic?Structurally, yes. We checked the output and it declares the major brand heic — an HEVC-coded still image — which is exactly what an iPhone writes. The two extensions describe the same container with the same codec inside; .heic is the name Apple popularised and .heif is the more general one. If a tool refuses the file, renaming it to .heic is usually all it takes.
Because Theora support has been withdrawn. Chrome disabled it by default in version 120 and Chromium removed the decoder entirely in 123; Firefox disabled it by default in 126; Safari never had it. An .ogv served to a modern browser simply does nothing. That is a good reason to pull the frames you care about out of an OGV archive while desktop tooling still decodes it.
No, and the confusion is worth clearing up. The Theora I bitstream was frozen in June 2004 and has not changed since — that is by design, so that decoders stay compatible. The reference library, libtheora, kept moving: 1.0 arrived in November 2008, 1.1.1 in January 2010, and 1.2.0 in March 2025. What ended was browser support, not the project.
On a Mac or an iPhone, yes — Apple's frameworks handle HEIF natively. On Windows 10 and 11 you may need the HEIF Image Extensions from the Microsoft Store, plus a codec package for the HEVC data. In a browser, only Safari 17 and later will display it, which is around 15% of global traffic; Chrome, Edge, Firefox and Opera do not decode HEIF at all.
The first one. Frame Selection opens on "Specific Frame" with "Time (seconds)" at 0, and frame zero is a poor choice for a lot of real material — black leaders, the first frame of a fade, a camera still finding focus. Enter a timestamp in seconds, decimals included, to land where you actually want.
Not from this page. The conversion is a single frame grab; the motion and the Vorbis audio track are both discarded. HEIF can in principle hold an image sequence, but that is not what this route produces. If you want the motion preserved, convert the video itself with OGV to MP4 instead.
Not necessarily. Ogg is a container, so an .ogv can carry Theora or VP8, and files written by different tools at different times vary. It makes no difference to a frame grab — either way the picture is decoded and re-encoded as a still — but it does explain why some .ogv files open in tools that reject others.
Very often, yes. AVIF stores an image with comparable efficiency but is royalty-free, and Chrome, Firefox, Edge and Safari all decode it — the licensing problem is precisely why HEIF never spread beyond Apple. OGV to AVIF is the same frame grab with a far more portable output. Choose HEIF only when the receiving system is Apple-based or has already committed to the format. For maximum compatibility with no thought required, OGV to JPG still opens everywhere.