CAVS to TIFF Converter

CAVS to TIFF — Archival Still, or Lossy by Accident?

Extracting a frame from a raw Chinese AVS (AVS1) bitstream as TIFF is the right move when the still has to survive editing, printing or long-term storage. But TIFF is a container for several different compression schemes, and the Compression Type control on this page starts on JPEG, which is a lossy scheme defined inside the TIFF format. Short answer: if you want an archival still, change that one dropdown before you convert — everything else on the page can be left alone.

TIFF Compression Types Side by Side

The dropdown also lists CCITT Fax 4 and JP2K. CCITT Fax 4 is a bilevel scheme for 1-bit black-and-white document scans and is not appropriate for a colour video frame; JP2K carries a JPEG 2000 payload for workflows that specifically require it. For a still lifted out of broadcast footage, the row you want is one of the four lossless general-purpose schemes.

When to Keep the JPEG Default

• The still is a reference or a preview, not a master, and file size matters more than fidelity.
• You are grabbing dozens of frames from a long capture and only need to look at them.
• The receiving system insists on .tif files but does not care what is inside them.

When to Switch to a Lossless Scheme

• The frame is going into print, colour grading, or any workflow that re-saves it repeatedly — each lossy save compounds the damage.
• You are archiving evidence, a title card, or a reference frame that must match the decoded source exactly.
• There is text, a graphic overlay or a hard edge in shot, where JPEG-style ringing is most visible.
• You intend to crop and re-export; lossless in means lossless out.

How to Convert CAVS to TIFF

1. Upload Your CAVS File: Drag and drop your .cavs onto the page, or click "Add Files" to browse for it. Several streams can be queued and run with the same settings.
2. Set Compression Type: Switch Compression Type from JPEG to None, LZW, Deflate or ZSTD for a lossless still. File extension writes the same data as either .tiff or .tif, whichever your software expects.
3. Choose the Frame and Size: Specific Frame is preselected — leave Time (seconds) blank for the first frame or type a moment such as 2.100. Multiple Screenshots with a Capture Rate samples a run of stills instead, and Image resolution scales the output.
4. Convert and Download: Click "Convert" and save the TIFF. No sign-up, no watermark.

TIFF vs PNG vs JPG for a Reference Still

TIFF's advantage is not compression — it is that one format covers uncompressed masters, lossless compressed archives and lossy previews, and that imaging and print software has read it reliably for over thirty years.

Frequently Asked Questions

Why is the Compression Type set to JPEG when TIFF is meant to be lossless?

Because TIFF was never a single compression scheme. The specification permits uncompressed data, lossless compression and lossy JPEG compression inside the same file structure, and JPEG-in-TIFF exists precisely because some workflows want the container without the file size. It is a sensible default for a general converter and a poor one for archiving, which is why it is the first thing to change if fidelity is the point.

Do the lossless schemes really produce identical pixels?

Yes. In our testing, an extracted frame saved with None, LZW, Deflate, PackBits and ZSTD all decoded back to pixel data identical to the source frame, while the JPEG default did not. Choosing among the lossless schemes is therefore purely a question of file size and how old the software reading it is — the image is the same image in every case.

How large will an uncompressed TIFF be?

It is straight arithmetic: width × height × 3 bytes for 8-bit RGB, plus a small header. A 720×576 standard-definition frame is 720 × 576 × 3 = 1,244,160 bytes, so roughly 1.2 MB; a 1920×1080 frame is 6,220,800 bytes, about 6 MB. LZW, Deflate or ZSTD will bring that down substantially on real footage with no quality cost, which is why "None" is worth choosing only for compatibility with very old tools.

Why did PackBits barely shrink my file?

PackBits is a simple run-length encoder: it compresses consecutive identical pixels and nothing else. Flat graphics and document scans have long runs, but a decoded video frame is full of noise and gradients where almost no two adjacent pixels match, so there is little to encode. On photographic content the result can end up marginally larger than uncompressed. Use LZW, Deflate or ZSTD instead.

Which version of the TIFF specification does this output?

Baseline TIFF conforming to TIFF 6.0, published on 3 June 1992 and still the current revision. The format was first specified by Aldus Corporation in the autumn of 1986, and the specification passed to Adobe when it acquired Aldus in 1994. That long stability is exactly why TIFF remains a dependable archival format — files written today open in software written decades apart.

Why will my TIFF not display in a web browser?

TIFF was designed for imaging and print pipelines, not for web delivery, and browsers other than Safari do not render it in a page. That is a deliberate scope decision rather than a gap: TIFF's multi-scheme flexibility is exactly what a browser does not want to implement. If the still is destined for a web page, extract it as CAVS to JPG or CAVS to WebP instead.

Will the TIFF be sharper than the original CAVS frame?

No, and this is the honest limit. A lossless TIFF stores the decoded frame verbatim, which is as faithful a copy as any format allows — but AVS1 is first-generation standard- or high-definition broadcast video, and no container reconstructs detail the original encode discarded. What you get is a pristine, re-editable copy of the frame that exists, not a higher-resolution one.

Why does my frame show thin horizontal lines or combing?

Broadcast AVS content is frequently interlaced, so a frame captured during motion can show the two fields woven together. The artefact is in the source fields rather than added by TIFF. Nudging Time (seconds) by a few hundredths usually lands on a steadier moment; for footage that is interlaced throughout, deinterlace the clip in a desktop editor first and grab the still from that progressive export — no conversion here applies a deinterlacing pass.

What happens to my files after conversion?

Your .cavs is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after the conversion finishes — never shared and never made public. There is no sign-up and no watermark.