Free online BIK to F4V converter

What the BIK format is

BIK is the filename extension commonly used by Bink Video, a proprietary video codec and container developed by RAD Game Tools. Game developers use it for cutscenes, intro movies, menu animations, trailers, and other pre-rendered video packaged with Windows, console, and other game releases.

BIK files are often created with RAD Video Tools and are usually encountered inside a game's installation directory or an extracted game asset archive. They are not normally camera recordings or standard editing files. A BIK file may contain Bink video with one or more audio streams, and its frame rate, resolution, and audio format vary by game.

The extension alone does not identify a modern web-compatible codec. Renaming movie.bik to movie.f4v changes only the filename and does not convert the encoded streams.

What the F4V format is

F4V is an Adobe Flash Video container based on the ISO Base Media File Format, closely related to MP4. It is designed primarily for H.264 video with AAC or other supported audio rather than the older FLV codecs.

F4V was used by Adobe Flash Player, Flash Media Server, and legacy web-video systems that required an MP4-derived Flash container. H.264/AAC generally provides better quality and broader compatibility than older Sorenson Spark or VP6-based FLV video at comparable bitrates.

Flash Player was discontinued at the end of 2020, so F4V is now mainly relevant to an existing archival, broadcast, authoring, or playback workflow. If the destination does not explicitly require F4V, standard MP4 is usually the more compatible target.

How to actually convert BIK to F4V

Convert directly with FFmpeg

Recent FFmpeg builds include Bink demuxing and decoding support. After installing FFmpeg, place the input file in a working folder and inspect its streams:

ffmpeg -i movie.bik

Convert the video to H.264 and the audio to AAC while writing an F4V container:

ffmpeg -i movie.bik -c:v libx264 -pix_fmt yuv420p -c:a aac -b:a 160k -movflags +faststart -f f4v movie.f4v

-c:v libx264 re-encodes Bink video to H.264, -c:a aac re-encodes audio for common F4V playback, and -f f4v explicitly selects the F4V muxer. -movflags +faststart moves the metadata to the beginning of the file, which can improve progressive playback where the receiving software supports it.

To preserve the source dimensions and frame rate while choosing a quality-based H.264 encode, use a constant-rate-factor setting:

ffmpeg -i movie.bik -c:v libx264 -crf 18 -preset medium -pix_fmt yuv420p -c:a aac -b:a 192k -f f4v movie.f4v

Lower CRF values produce larger files and higher visual quality; values around 18–23 are common starting points. If the BIK file has multiple streams, list them with ffprobe movie.bik and select the required streams explicitly, for example:

ffmpeg -i movie.bik -map 0:v:0 -map 0:a:0 -c:v libx264 -c:a aac -f f4v movie.f4v

Use RAD Video Tools as an intermediate step

If the installed FFmpeg build reports that Bink is unsupported, use RAD Video Tools to open the BIK file and export it to an intermediate format such as AVI, when the tool and the file permit that operation. Then encode the intermediate file with FFmpeg:

ffmpeg -i intermediate.avi -c:v libx264 -pix_fmt yuv420p -c:a aac -b:a 160k -f f4v movie.f4v

RAD Video Tools may not be able to decode every Bink variant or export every game asset correctly. Do not redistribute game footage or proprietary codec tools unless the relevant license permits it.

Convert without installing software

You can use the free converter on 101convert.com: choose the video conversion function, upload the BIK file, select F4V as the output format, start the conversion, and download the resulting file. Upload limits, retention rules, and supported Bink variants can affect the result, so verify the converted file before deleting the source.

Quality, compatibility, and limitations

This conversion normally involves lossy re-encoding. Bink video is decoded and then compressed again as H.264, so some detail can be lost; increasing the bitrate or using a lower CRF value reduces additional loss but does not restore information already discarded by the original Bink encode.

F4V playback requires software that supports both the F4V container and the selected H.264/AAC profiles. Modern browsers generally do not provide native F4V playback because Flash support has ended. Test the output in the exact legacy player or application that requires it.

Game BIK files can contain unusual frame rates, nonstandard resolutions, multiple audio tracks, or files that depend on game-specific playback behavior. Check the converted duration, synchronization, aspect ratio, and audio channels. If the target application rejects F4V despite valid H.264/AAC streams, create a standard MP4 with the same encoding settings instead:

ffmpeg -i movie.bik -c:v libx264 -pix_fmt yuv420p -c:a aac -b:a 160k -movflags +faststart movie.mp4