OGV to TIFF Converter

Grab a TIF Still from an OGV: What This Tutorial Covers

This is a step-by-step for pulling one frame out of an .ogv (Ogg video) file and saving it as a .tif. Two settings decide whether you get what you came for, and both of them open on a value that works against you: Frame Selection starts at second 0, which on most real footage is a fade-in or a black leader, and Compression Type starts on JPEG, which is lossy — inside a file that people choose specifically because it is not lossy. Everything below is about getting those two right, plus what to do when the result still looks wrong.

How to Convert OGV to TIF

1. Upload Your OGV File: Drag your .ogv onto the page or click "Add Files" to browse. Several clips can be queued and they all run with 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 the Time in Frame Selection: Specific Frame is already chosen, but its Time (seconds) box starts at 0. Type the moment you actually want — decimals are accepted, so 4.12 seeks to 4.12 seconds. Switch to Multiple Screenshots with a Capture Rate instead to sample the whole clip.
3. Change Compression Type Off JPEG: Open Compression Type and pick LZW, Deflate, ZSTD or None for a genuinely lossless TIF. Confirm File extension is set to TIF (it has no preselected value), and resize with Resolution Percentage, Preset Resolutions, or Width x Height if you need a smaller still.
4. Convert and Download: Click Convert. A single frame downloads as one .tif; multiple frames arrive together as a ZIP of separate .tif files.

Walk-through: Why Time 0 Is Almost Never the Frame You Want

The seek value is passed to the decoder as an input seek before any frames are read, so it is fast even on a long clip — but it is also literal. Leave it at 0 and you get the very first coded frame, which on real-world material is routinely a black leader, a fade-up, a slate, or a compression-heavy opening keyframe. That is not a bug in the extractor; it is simply the frame you asked for.

• You know the moment: type it directly. 93 and 93.5 both work; the second lands half a second later.
• You do not know the moment: switch to Multiple Screenshots and set Capture Rate to 1 second per frame (or as fine as 0.1s), convert once, then re-run Specific Frame at the timestamp of the still you liked.
• You want a long clip sampled sparsely: the Capture Rate list goes out to 10 seconds per frame, which turns a ten-minute video into roughly sixty contact-sheet stills.
• You want the motion, not a moment: a still target cannot animate. Use OGV to GIF for a short loop or OGV to MP4 to keep it as video.

Walk-through: Compression Type Decides Lossless vs Lossy

TIF is a container, not a compression method — the TIFF Revision 6.0 specification (Aldus, 3 June 1992) defines several schemes and the file extension tells you nothing about which one was used. That is why the Compression Type dropdown matters more here than anything else on the page, and why its JPEG default deserves a second look before you convert.

One consequence that surprises people: the Quality Preset dropdown only changes the output when Compression Type is a lossy scheme. Quality is passed straight through to the encoder, and LZW, Deflate, ZSTD, PackBits and None ignore it entirely — pick Lowest or Highest with LZW selected and the bytes are identical. If you want a smaller lossless TIF, change the compression scheme or the resolution, not the quality.

Common Errors and How to Fix Them

• "My TIF is black / just a fade-in" — Time (seconds) was left at 0. Re-run with a real timestamp.
• "The TIF looks like a JPEG" — Compression Type was left on JPEG. Switch to LZW, Deflate, ZSTD or None.
• "Lowering the Quality Preset did nothing" — expected on a lossless compression type. Quality only bites on JPEG/LOSSY and WebP.
• "The conversion failed" — check whether CCITT Fax 4 or JP2K is selected. Fax 4 encodes only 1-bit black-and-white and rejects a colour frame outright; JP2K is not written by this pipeline.
• "My browser won't open the .tif" — expected. Other than Safari, browsers do not natively support TIFF as web content. It is a download-and-edit format.
• "I expected one file with every frame" — TIF can hold multiple images per file, but this tool writes one image per file and ZIPs them.
• "PackBits made the file bigger" — also expected. Run-length coding needs long runs of identical bytes; a detailed frame has almost none, so the overhead exceeds the saving.

When This Doesn't Work

If the .ogv is truncated or partly downloaded, the decoder may never reach your timestamp — pick an earlier second, or repair the source first. If you need a genuine multi-page TIF (many images inside one file), that is a desktop job for ImageMagick or a full image editor; this converter always writes one image per file. And if the goal is a still for a web page, an email, or a chat message, TIF is the wrong target entirely: use OGV to JPG for a small photographic still or OGV to PNG for a lossless one that browsers actually display.

Frequently Asked Questions

Why does my TIF come out black when I just hit Convert?

Because Frame Selection opens on Specific Frame with Time (seconds) set to 0, and second zero of a real video is frequently a black leader, a fade-up from black, or a title slate. The extractor is doing exactly what it was asked. Type a real timestamp into the Time box — decimals are accepted, so 12.4 works — or switch to Multiple Screenshots to sample the clip and find the moment you want, then come back and name it precisely.

Is a .tif from this tool actually lossless?

Only if you change Compression Type. It opens on JPEG, which applies the same lossy DCT compression as an ordinary .jpg and merely stores the result inside a TIF wrapper. LZW, Deflate, ZSTD and None all store the decoded frame pixel-for-pixel and are genuinely lossless; the choice between them is file size versus how modern your other software is. Note that the list also contains a LOSSY entry — it is a duplicate label that resolves to the same JPEG encoder, so it is not a third option.

Will saving as TIF make my old OGV frame look sharper?

No. The video track in an .ogv is usually Theora, which is derived from On2's VP3, was released in 2004, uses chroma subsampling, and does not code more than 8 bits per component. A lossless TIF reproduces every pixel the decoder hands over, but it cannot reconstruct detail Theora never stored. What you gain is a working copy that survives repeated edits and re-saves without accumulating further loss — not a resolution or fidelity upgrade.

Why won't the Quality Preset change my file size?

Because the quality value only reaches encoders that have a quality knob. With LZW, Deflate, ZSTD, PackBits or None selected, the compression is lossless by definition and the setting is inert — the output bytes are identical whether you choose Lowest or Highest. Quality becomes meaningful only when Compression Type is JPEG/LOSSY or WebP. To shrink a lossless TIF, use Resolution Percentage or Width x Height instead, or pick a tighter lossless scheme.

Why do CCITT Fax 4 and JP2K fail on my frame?

CCITT Group 4 is a fax codec: it encodes one bit per sample, so it accepts only pure black-and-white bilevel images. A colour video frame is 8 bits per channel across three channels, and the encoder rejects it rather than silently converting to bilevel. JP2K (JPEG 2000 inside TIF) is not produced by this pipeline either. Both entries exist because they are part of the TIFF specification, but neither is a valid choice for a still pulled out of a video — treat LZW or Deflate as the practical defaults.

How big will the TIF be, and can I predict it?

For None, exactly: an 8-bit RGB TIF is width × height × 3 bytes of pixel data plus a small header, so a 640 × 480 frame is about 921,600 bytes. LZW and Deflate cut that substantially on typical footage — Deflate usually beats LZW, ZSTD usually beats both — while JPEG compression can land an order of magnitude smaller because it throws data away. PackBits is the odd one out: on a detailed frame with no long runs of identical bytes it can produce a file slightly larger than uncompressed.

My OGV won't play in Chrome anymore — can you still read it?

Yes, and that is a good reason to pull your stills now. Chrome 120 disabled Theora by default and Chromium removed it in the 123 timeframe in 2024, with Firefox disabling it by default in version 126. That change affects playback in a web page only. Standalone decoders still read Ogg and Theora, and that is what runs on our servers when your file is processed, so an .ogv that has stopped playing for viewers will still decode here for a frame grab.

What is the difference between this page and the TIFF one?

Only the extension written on the output file. .tif is the three-letter spelling left over from the DOS/Windows 8.3 filename limit; .tiff is the four-letter one, and the bytes inside are the same format either way. This page produces .tif; OGV to TIFF produces .tiff and covers the format specification in more depth. Both pages expose the same File extension control, which lets you override the spelling at conversion time — it ships with neither value preselected, so set it explicitly if the receiving software is fussy. To shrink a TIF you already have, use compress TIFF.