Initializing... drag & drop files here
Supports: CAVS
ASF is Microsoft's Advanced Systems Format — the container behind Windows Media, and the wrapper that .wmv and .wma files are built on. Almost nobody chooses ASF for its own sake; people choose it because a Windows-era player, a capture card's software, or an old media-server ingest path insists on it.
Which makes the default on this page worth flagging up front. Video Codec opens on H.264, not on a Windows Media codec. The ASF muxer will write H.264 without complaint and any modern player reads the result back — a test encode with these settings produced a perfectly valid single-stream ASF file — but H.264 is not one of the codecs ASF was built around, and a Windows Media-era player expecting WMV will not decode it. If Windows compatibility is the reason you are here, change Video Codec to WMV 2 before converting. If you just need the picture out of an orphaned AVS stream and any container will do, CAVS to MP4 is a better destination than ASF.
.cavs onto the page or click "+ Add Files". A .cavs is a bare AVS1 video bitstream with no container around it, which is why ordinary players refuse to open one; several can be queued and all convert with the same settings..asf extension..asf. Files are uploaded over an encrypted connection, decoded and re-encoded on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.| Codec | Why you would pick it | What it costs you |
|---|---|---|
| WMV 2 (Windows Media Video 8) | The codec ASF was designed around. Decodes in Windows Media-era players and in anything modern | Substantially less efficient than H.264 — expect a bigger file at the same visual quality |
| WMV 1 (Windows Media Video 7) | Software so old that even WMV 2 is too new for it | Weaker still; rarely necessary |
| H.264 (opens selected) | Best compression on the list, and every current player handles it | Not a Windows Media codec; a legacy ASF consumer will see a stream it cannot decode |
| MPEG-4, Xvid, DivX, MS MPEG-4 | Broad legacy compatibility on the codec side | Same problem as H.264 for a strictly Windows Media pipeline |
| MPEG-1, MPEG-2 | Feeding a hardware decoder or authoring chain that names them | Large files, no benefit here |
| VP8, VP9, AV1, Theora | Royalty-free codecs | Wrong container entirely — if you want these, use WebM or MKV instead |
Twenty entries render, but the real decision is a two-way one: a Windows Media codec, or a modern one. Everything else on the list is a codec you would be better off putting in a container that suits it.
Switching codecs does not just swap the encoder — it re-ranges the Constant Quality control, because the two families use different quality scales and the pipeline follows the codec rather than the container.
| Video Codec selected | Constant Quality scale | Opening value | Direction |
|---|---|---|---|
| H.264 | 16 - 51 (a true CRF) | 23 | Lower is better |
| WMV 1 or WMV 2 | 1 - 31 (a quantiser scale) | 5 | Lower is better |
The 1-31 scale on WMV is a real, working control, and its range is wide. On a 704x576 six-second test clip, WMV 2 encodes came out at 4,394,359 bytes at quantiser 1, 2,602,359 bytes at 5 (the value the page opens on), 1,139,959 bytes at 15 and 477,559 bytes at 31. Setting it to 5 and leaving it alone is a sensible high-quality default for standard-definition material; push it toward 15 if you need the file substantially smaller and the source is not detailed enough to punish you for it.
One thing not to do is carry a number across between the two scales. A value of 23 means "good quality" on the H.264 CRF scale and "quite poor" on a 1-31 quantiser, so if you change codec, re-set the slider rather than assuming the number still means what it meant.
| Property | .cavs source |
.asf output |
|---|---|---|
| What the file is | A raw AVS1 video bitstream — coded picture data with no container | Advanced Systems Format container |
| Standard | GB/T 20090.2, the Chinese national video standard adopted in 2006 | Microsoft's Windows Media container format |
| Standards body | The AVS Workgroup, established in June 2002 | Microsoft |
| Video coding | AVS1 (AVS1-P2, Jizhun profile) | H.264 by default; WMV 2 is the one to pick for Windows compatibility |
| Audio | None — a bare elementary stream carries no sound | None, because the source has none. WMA v2 is the nominal default but there is nothing to encode |
| Timing and seek index | None | Written by the muxer during conversion |
| Opens in ordinary players | No — most refuse a loose elementary stream | Yes, with the right codec choice |
| Role here | Decoded input | Freshly re-encoded output, one lossy generation on |
Because a .cavs file has none to begin with. It is a video elementary stream: coded picture data with no container, no audio track and no timing index. In Chinese AVS broadcast and optical-media workflows the picture was carried as one stream and the sound as another, and the two were multiplexed together only when the final container — a transport stream, an MP4, an MKV — was built. The bare .cavs you have is the picture half. The Audio Codec dropdown still renders and still nominates WMA v2, but there is nothing for it to encode, so the ASF comes out with a single video stream. If you need the soundtrack, convert the original container rather than the demuxed stream.
Only if you change the codec first. Left on its default the file contains H.264, which the ASF muxer accepts and modern players read, but which is outside the set of codecs Windows Media was built around — a Windows Media-era player will open the container and then fail to decode the video. Select WMV 2 under Video Codec and you get Windows Media Video 8 inside an ASF, which is the pairing that container exists for. WMV 1 is there for software older still.
.cavs the same thing as a .avs AviSynth script?No, and the two are easy to confuse. A .cavs file is a raw AVS1 video bitstream — actual coded picture data from the Chinese Audio Video Standard. A .avs file is an AviSynth script: a short text file of frameserving instructions that references video stored elsewhere, with no picture data inside it at all. This converter expects the bitstream. If you upload an AviSynth script by mistake there is nothing in it to encode.
No — they are three generations of the same Chinese standards family, and a .cavs file is the first one. AVS1 was adopted as national standard GB/T 20090.2 in 2006 by the AVS Workgroup, which was established in June 2002. AVS2 followed as a Chinese national standard at the end of 2016 and was later published as IEEE 1857.4. AVS3 is the current generation and was added to DVB's media-delivery toolbox in 2022. This page's decoder handles the AVS1 elementary stream that the .cavs extension denotes; the later generations use different bitstream syntax and normally arrive inside a real container rather than as a loose stream.
Re-encoded, always. ASF does not carry AVS1 under any circumstances, so there is no version of this conversion that moves your existing compressed frames into a new container untouched — the decoder reconstructs the pictures and an encoder compresses them again. That is one lossy generation, and no setting recovers what it costs. Keep Constant Quality low (which means high quality on both scales) if the AVS stream is your only copy of the material.
Because a bare .cavs has no container-level timing information — no duration field, no frame-rate declaration, no seek index. The decoder infers timing from the bitstream itself, and the ASF muxer writes whatever it is given. If the resulting file reports something unexpected, that is the missing metadata showing through rather than a fault in the encode. It is also why trimming by time on a .cavs source can land slightly off where you expected.
Leave it on Keep original unless you have a specific target. AVS1 material is typically standard-definition broadcast content, and scaling it up only enlarges what the original encoder already discarded — the re-encode then has to spend bits describing interpolated pixels. Scaling down is legitimate if you need a smaller file, and the Preset Resolutions list sets a height with the width following the source aspect ratio. Note that any resize also flattens the pixel aspect ratio to square, so if your source is anamorphic standard-definition, set an explicit Width x Height that already accounts for the display shape.
Any of the site's video targets, and the container matters more than you might think for a stream nobody's player will open loose. CAVS to MP4 is the safest general answer — H.264 in MP4 plays on phones, browsers, televisions and editors. CAVS to AVI is the choice for legacy Windows editing tools that predate MP4 support. CAVS to WMV gets you Windows Media Video under the extension Windows users expect, which for most people is a more useful destination than .asf even though the underlying container is the same.
There is no fixed per-file cap; upload size and connection speed are the practical limit, and raw elementary streams are usually modest by video standards because they carry no audio and no container overhead. Everything you send travels over an encrypted connection, is decoded and re-encoded on our servers, and both the upload and the output are deleted automatically after a few hours. Files are never shared or made public, there is no account to create and no watermark is added.