Initializing... drag & drop files here
Supports: F4V
This is a conversion between two formats that outlived the software they were built for. .f4v was Adobe's second-generation Flash video container, and Adobe stopped supporting Flash Player on 31 December 2020 and began blocking Flash content from running on 12 January 2021. .asf is Microsoft's Advanced Systems Format, the wrapper behind .wmv and .wma, still readable but no longer anybody's first choice.
People arrive here for one of two reasons: a Windows-side application or capture appliance that accepts ASF and nothing else, or a batch of old Flash-era media being normalised into whatever the receiving system already ingests. Both are legitimate. If neither describes you, F4V to MP4 is the sensible destination, and it is barely a change at all — F4V is already built on the ISO base media file format that MP4 uses.
| Property | F4V | ASF |
|---|---|---|
| Owner | Adobe | Microsoft |
| Underlying structure | ISO/IEC 14496-12, the ISO base media file format | Microsoft's own object model, header GUID 30 26 B2 75 8E 66 CF 11 A6 D9 00 AA 00 62 CE 6C |
| Introduced | Playable from Flash Player 9 Update 3 (9,0,115,0), released 3 December 2007 | Late 1990s, as the wrapper for Windows Media |
| Native video coding | H.264/AVC | Windows Media Video (WMV) |
| Native audio coding | AAC family | Windows Media Audio (WMA) |
| Close relative | MP4 — same base structure | WMV, which is ASF with a Windows Media payload |
| Streaming design | Progressive download and RTMP | MMS and HTTP streaming |
| Status | Flash Player support ended 31 December 2020 | Legacy; still read by Windows and by ffmpeg-based players |
| On xconvert | Input and output | Input and output |
The Video Codec dropdown on this page is unusually long — twenty entries, from AV1 and VP9 down to H.261. What is not obvious is that picking one silently reshapes the entire File Compression group:
| Video Codec | Quality control that appears | Range | Opens at | Bitrate modes |
|---|---|---|---|---|
| H.264 (pre-selected), H.265, AV1, VP8, VP9 | Rate factor | 16–51 | 23 | All offered |
| WMV 1, WMV 2, MPEG-1, MPEG-2, MPEG-4, DivX, Xvid, MS MPEG-4, FLV, H.263 | Quantizer | 1–31 | 5 | All offered |
| MJPEG | Quantizer | 2–31 | 5 | Only Quality Preset — no bitrate modes, no Constraint Quality |
The slider is labelled CRF in every case, but on the middle row it is a quantizer, and a value that would be near-lossless overkill on H.264 is a sensible working point there. If you switch from H.264 to WMV 2 and leave the number where it was, you will not get what you expect.
H264, and ffmpeg-based players open it without complaint. But ASF's ecosystem was built around WMV video and WMA audio, and software that only ever expected those may not decode an H.264 payload. If the destination is specifically a Windows Media pipeline, choose WMV 2 and WMAv2 together.Structurally it is very close. F4V is built on ISO/IEC 14496-12, the ISO base media file format, which is the same foundation MP4 uses, and it typically carries H.264 video with AAC-family audio — the same payload combination. Adobe defined it as part of the Flash video specification alongside the older FLV format, and Flash Player has been able to play it since Flash Player 9 Update 3. In practice this means F4V to MP4 is the lightest-touch conversion available from an F4V, and it is what most people arriving at a Flash-era file actually want.
Because it is what the source already contains, and keeping the codec family constant costs the picture less. An F4V holds H.264, so choosing H.264 on the output means one re-encode within the same codec rather than a translation into a different one with different strengths. WMV is the payload ASF was designed around, so switch to WMV 2 when the file is going somewhere that expects a native Windows Media stream. For anything opened by VLC, a browser-adjacent tool or a modern editor, H.264 is the better picture for the size.
An ASF with WMV 2 video and WMAv2 audio is the combination Windows Media tooling was built for, and that is what to choose if the answer needs to be reliably yes. An ASF with H.264 inside is a legal file and ffmpeg-based players such as VLC open it happily, but you are relying on the reading software to have an H.264 decoder wired into its ASF path, which older Windows-side software may not. When in doubt, pick WMV 2 and WMAv2 and accept the picture-quality cost.
.asf and .wmv?.wmv is .asf with a Windows Media payload. The container is the same object structure with the same header GUID; the extension is a convention indicating what is inside. That is why this page and F4V to WMV produce closely related files, and why software that reads one usually reads the other. Choose the extension that the receiving application checks for, and choose the codec that matches it — WMV video for a .wmv, and either WMV or something else for a .asf depending on what will open it.
Because the underlying parameter changed. H.264, H.265, AV1, VP8 and VP9 take a rate factor between 16 and 51 with 23 pre-selected. The older codecs — WMV 1 and 2, MPEG-1, MPEG-2, MPEG-4, DivX, Xvid, MS MPEG-4, FLV and H.263 — take a quantizer between 1 and 31 with 5 pre-selected. MJPEG takes a quantizer between 2 and 31. All three are labelled CRF because one control serves every codec, and in all three cases lower means better, but the scales are not comparable. Reset the value after switching codecs.
It is a re-encode, so yes, there is a generation of loss — the AAC track in the F4V is decoded and re-compressed as Windows Media Audio. WMAv2 is a competent codec of its era but AAC is generally stronger at the same bitrate, so if nothing downstream requires Windows Media audio, choosing AAC will preserve more of the original. Choose WMAv2 when ASF-native audio is the point of the exercise, and accept the trade.
Yes — queue them and they convert with the same settings, which is the usual reason to be on this page in the first place, since ASF conversion is normally a normalisation job rather than a one-off. Because every file gets the same codec and quality settings, check them on one representative file before running the batch, particularly if the sources vary in frame size.
No. The server always decodes and re-encodes; there is no stream-copy path even when the input and output video codec are both H.264. That is worth knowing when you are normalising an archive: each pass through costs a generation. If the F4V is your only copy, keep it. If you are choosing a target purely to make files openable and want to minimise the damage, an MP4 at a high quality setting is a gentler destination than ASF.
Because both containers index their content. F4V, being an ISO base media file, carries sample tables that let a player seek; ASF carries its own index object serving the same purpose, and it is written when the file is muxed. Measured on a converted file, the ASF reports the same duration as the source and seeks normally. What does not carry across is anything Flash-specific layered on top, such as cue points.
Your .f4v is uploaded over an encrypted connection, decoded and re-encoded on our servers, then deleted automatically after a few hours along with the .asf it produced. There is no sign-up, no watermark, and nothing is shared or made public. Flash-era files tend to be small, so this conversion is usually finished quickly — the only slow combinations are the modern codecs in the dropdown, such as AV1, which are far heavier to encode than anything ASF was designed to carry.