Initializing... drag & drop files here
Supports: OGV
This is a frame-grab tool, not a video-to-image-sequence dump in disguise. It decodes one moment from your OGV (Ogg) video and saves that single still picture as a JFIF image; by default it captures the opening frame at time 0, and you can point it at any timestamp or pull a set of screenshots instead. This page walks through choosing the frame, controlling quality, and the edge cases where a Theora source fights back.
.ogv file onto the page, or click "Add Files" to browse. You can queue more than one clip.0, the opening frame), or switch to "Multiple Screenshots" to pull several stills across the clip.The default grabs the very first frame (time 0). That frame is often a black lead-in or a fade, so for a usable picture you almost always want to set a timestamp.
12.5 for the picture 12.5 seconds into the clip. The decoder seeks to that point in the Theora timeline and saves the single nearest frame.0, which is often a lead-in or fade. Set a "Time (seconds)" a few seconds into the clip and re-run..jfif is byte-for-byte the same JPEG as a .jpg. Rename the extension, or relabel it with our JFIF to JPG converter.If the OGV is corrupted or truncated mid-stream, the decoder may not reach your chosen timestamp and will fall back to the last readable frame. DRM-wrapped or non-Theora Ogg payloads (rare, since most .ogv files are Theora + Vorbis) can also refuse to decode. In those cases, repair or re-export the source in a player like VLC first, or — if you actually want a sequence of stills rather than a single picture — use OGV to JPG and its "Multiple Screenshots" mode to pull the full set.
No. It is a frame grabber: it decodes one moment from the video and saves that single still as a JFIF. The default is time 0 (the opening frame); set a "Time (seconds)" to choose a different moment, or use "Multiple Screenshots" to get several stills. There is no motion or animation in the output, and converting cannot raise detail beyond the source frame's resolution.
Yes — the image data is identical. JFIF (JPEG File Interchange Format) is the wrapper that defines how JPEG-compressed data is stored, standardized as ITU-T T.871 (2011) and ISO/IEC 10918-5 (2013). A .jfif and a .jpg saved at the same quality contain the same lossy JPEG picture; only the extension and APP0 header differ. If a program refuses a .jfif, rename it to .jpg or run it through our JFIF to JPG converter.
Theora — the video codec inside almost every .ogv file — has been deprecated. Google disabled it in Chrome 120 (December 2023) and removed it by Chrome 123 (March 2024); Firefox dropped Theora in version 130, and Safari never shipped it. Our server still decodes Theora to pull your frame, so the conversion works even when in-page playback does not.
By default the still matches the video's frame resolution — a 720p OGV yields roughly a 1280x720 image, and a 1080p source yields about 1920x1080. You can scale it down with the Image resolution preset or percentage if you need a smaller file. Because both Theora and JFIF are lossy, the frame keeps the source's existing compression artifacts; the converter cannot invent detail the original video never recorded.
No. A JFIF is a single still photograph and has no audio track, so the OGV's Vorbis audio is discarded when you grab a frame. If you need the sound, extract it separately rather than expecting it inside the image.
Functionally they are the same operation — both decode the chosen frame(s) and encode them with JPEG compression. The only difference is the output extension (.jfif versus .jpg) and the JFIF APP0 header. If your target program expects .jpg, use the OGV to JPG converter; if you specifically need the .jfif extension, stay here.
Your file is uploaded over an encrypted connection, processed on our servers, and the JFIF result is returned to you. Uploaded files and outputs are deleted automatically a few hours after conversion. There is no sign-up, no watermark, and files are never shared or made public.