OGV to TIFF Converter

OGV to TIFF Converter

.ogv is Xiph.Org's video profile of the Ogg container — a royalty-free wrapper standardised as RFC 3533 in May 2003, holding a video bitstream that is almost always Theora. .tiff is the opposite kind of thing: a single-image raster file defined by the TIFF Revision 6.0 specification (Aldus, 3 June 1992), built for archiving, print and precision editing rather than delivery. This converter bridges the two by decoding one frame out of the Ogg bitstream and writing it as a TIFF. It is the same job macOS Photos does when you choose File > Export > Export Frame to Pictures, which also writes a TIFF — which is why "video frame to TIFF" is a search people run at all.

The OGV Source at a Glance

The TIFF This Tool Writes

How to Convert OGV to TIFF

1. Upload Your OGV File: Drag your .ogv onto the page or click "Add Files". Queue several clips and they run with identical 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 but its Time (seconds) box starts at 0, which is often a black leader. Type a real timestamp — decimals such as 18.75 are accepted — or switch to Multiple Screenshots and set a Capture Rate.
3. Choose Compression Type and Confirm the Extension: Compression Type opens on JPEG, which is lossy; pick LZW, Deflate, ZSTD or None for a lossless TIFF. The File extension control offers TIFF and TIF with neither preselected, so set it if the receiving software cares. Scale with Resolution Percentage, Preset Resolutions or Width x Height.
4. Convert and Download: Click Convert. One frame downloads as a single .tiff; a Multiple Screenshots run returns each frame as its own .tiff inside a ZIP.

Compression Schemes Defined for TIFF, and What They Do Here

Frequently Asked Questions

Is the TIFF specification still maintained, and which revision does this output match?

TIFF 6.0, finalised on 3 June 1992 by Aldus, is still the operative baseline — Aldus merged into Adobe in September 1994 and a 1995 reissue changed only the administrative front matter, not the technical content. Nothing since has replaced it as the general-purpose revision, so what you get here is a baseline TIFF 6.0 file: a header, one Image File Directory, and RGB pixel data. Later work such as BigTIFF and the TIFF/EP and TIFF/IT profiles are separate specifications for other problems, and this converter does not produce them.

Does the output contain one image or several?

Exactly one. TIFF's IFD chain can in principle link many images inside a single file — that is how multi-page scans work — but the file written here terminates the chain immediately, with a next-IFD pointer of zero. Multiple Screenshots does not change that: it produces N separate single-page .tiff files and delivers them in a ZIP. If you specifically need one file containing every frame, that is a desktop job for ImageMagick or a full image editor.

What is the difference between the .tiff and .tif pages?

Only the extension on the output file. .tif is the three-letter spelling forced by the old DOS/Windows 8.3 filename limit and .tiff is the four-letter one; the header, the IFD and the pixels are identical. This page writes .tiff and covers the format specification; OGV to TIF writes .tif and is structured as a step-by-step with a troubleshooting section. Both expose the same File extension control with TIFF and TIF available and neither preselected, so you can override the spelling from either page.

Why does the file default to lossy JPEG compression inside a lossless format?

Because TIFF 6.0 defines JPEG as one of its legal compression schemes, and this pipeline's shared image writer defaults to it for size. It is a genuine mismatch with why most people reach for TIFF, so it is worth changing deliberately: LZW, Deflate, ZSTD and None all reproduce the decoded frame pixel-for-pixel. Watch out for the separate LOSSY entry too — it is a duplicate label that resolves to the same JPEG encoder, not a third alternative.

Can a TIFF from a Theora frame ever be higher quality than the source?

No, and the ceiling is set by the codec, not the container. Theora is derived from On2's VP3, codes no more than 8 bits per component, and uses chroma subsampling, so the decoder hands over an 8-bit RGB frame with whatever detail the original lossy encode preserved. A lossless TIFF stores that faithfully and stops any further generation loss during editing — which is the real reason to use it — but it cannot add information. Theora also does not support interlacing, so a genuine Ogg/Theora source has no field structure to worry about; any comb artefacts you see were baked in before encoding, and there is no deinterlacing stage in this pipeline to remove them.

What DPI will the TIFF be, and can I set it for printing?

There is no DPI control on this page. In our own end-to-end check of the extraction chain, the emitted TIFF carried a resolution tag of 25.4 pixels per inch — the one-pixel-per-millimetre default of the imaging library that writes the file — rather than a print-ready 300. That tag is metadata only: it does not change the pixel data, and every layout and print application lets you reassign it. So set the DPI in your editor, and treat the Resolution Percentage and Width x Height controls here as the ones that decide actual pixel count.

Which colour space and bit depth does the output use?

RGB at 8 bits per channel, three samples per pixel, with the photometric interpretation tag set to RGB. There is no bit-depth selector and no CMYK or grayscale option on this path, which is a real limitation compared with a desktop converter: if your print workflow needs 16-bit or CMYK, convert here first and change the mode in an image editor afterwards. The 8-bit limit is not costing you anything from the source, since Theora cannot encode more than 8 bits per component in the first place.

Can I still read an OGV that browsers have stopped playing?

Yes. Chrome 120 disabled Theora by default and Chromium removed it around version 123 in 2024; Firefox disabled it by default in version 126. Those changes affect playback inside a web page only. The standalone decoders that run on our servers still handle Ogg and Theora, so a file that has become unplayable for viewers will still yield a frame here. If you would rather rescue the whole clip than a single still, OGV to MP4 re-encodes it to a format current players accept, and OGV to WebP gives you a compact still for the web instead of an archival one.