Free online DAV to F4V converter

Security-camera recordings in DAV format often cannot be opened by standard video editors or players. Converting an exported recording to F4V can make it usable in software that accepts Flash Video containers, although F4V support is now limited.

What the DAV format is

DAV is a proprietary surveillance-video format used by many digital video recorders and network video recorders, especially systems made by Dahua and compatible OEM brands. The recorder typically stores H.264 or H.265 video in a DAV container with device-specific timestamps, audio, encryption, or authentication data.

You usually encounter DAV files after copying footage from a CCTV recorder, surveillance hard drive, memory card, or vendor export utility. Generic players may report an unsupported format even when the underlying video codec is common. Dahua Smart Player and software supplied with the recorder can usually open the file and export it to a more conventional format.

What the F4V format is

F4V is Adobe's ISO Base Media File Format-based Flash Video container. It normally carries H.264/AVC video and AAC audio, unlike the older FLV format, which commonly used Sorenson Spark or VP6 video.

F4V can retain good H.264 quality while providing a structured MP4-family container, but browser and media-player support for Flash formats has largely disappeared. Use F4V only when a specific application, legacy publishing system, or embedded player requires it; MP4 is usually the better delivery format for current devices.

How to actually convert DAV to F4V

Export the DAV file with the recorder software

1. Keep the original DAV file unchanged and install the camera manufacturer's desktop player, such as the Dahua Smart Player version intended for the recorder.
2. Open the recording through Open file or the equivalent import command. If the player cannot open it, use the recorder's own playback and export function; some DAV files are encrypted or tied to a particular device.
3. Use the player's Convert, Export, or Save as function and select MP4 if available. If MP4 is unavailable, export AVI or another format that the player provides. Select the original resolution and frame rate when the software offers those choices.

Do not simply rename recording.dav to recording.f4v; changing the extension does not change the container or decode proprietary DAV data.

Create the F4V-compatible file with FFmpeg

After obtaining an MP4 or AVI export, FFmpeg can encode H.264 video and AAC audio into an MP4-family file with an .f4v extension:

ffmpeg -i "export.mp4" -map 0:v:0 -map 0:a? -c:v libx264 -preset medium -crf 20 -pix_fmt yuv420p -c:a aac -b:a 128k -movflags +faststart -f mp4 "converted.f4v"

The -crf 20 setting gives high visual quality; use a higher value such as 23 for a smaller file or a lower value for less compression. If the vendor export already contains H.264 video and AAC audio, remux it without re-encoding:

ffmpeg -i "export.mp4" -map 0:v:0 -map 0:a? -c copy -movflags +faststart -f mp4 "converted.f4v"

Remuxing is faster and avoids another generation of quality loss. It works only when the source streams are compatible with the intended F4V player. For an AVI export, use the first command rather than stream copying.

You can also try the free converter on 101convert.com without installing software. Proprietary or encrypted DAV files may be rejected, in which case export them first with the recorder manufacturer's software.

Quality, compatibility, and limitations

A DAV-to-F4V conversion normally requires an intermediate vendor export because general-purpose converters may not decode the proprietary container. If the recorder software decrypts or re-encodes the footage during export, the resulting file may lose original surveillance metadata, authentication data, camera-specific overlays, or event indexes.

Use stream copying only for compatible H.264/AAC exports; otherwise re-encode to H.264 and AAC as shown above. Re-encoding can reduce detail, which is significant when the footage is needed as evidence, so archive the untouched DAV file and retain the vendor-exported copy.

F4V is not the same as an ordinary modern MP4 workflow. Some players identify the output only by its MP4 structure, while others require a specific F4V-compatible implementation. Test the result in the target application; if it accepts MP4, use converted.mp4 instead and avoid the legacy F4V restriction.