Free online BIK to M2T converter

What the BIK format is

BIK is the filename extension commonly used for Bink Video, a game-focused video format developed by RAD Game Tools. Game studios use it for cutscenes, menus, trailers, and other pre-rendered sequences because Bink supports platform-specific decoding and can combine video with compressed audio in one file.

BIK files are commonly found inside PC and console game installation folders or asset archives. RAD Video Tools can play and convert them, and FFmpeg builds with Bink decoder support can often read them directly. A BIK file may use different Bink generations, frame rates, dimensions, and audio streams, so compatibility depends on the file and the installed decoder.

What the M2T format is

M2T is a filename extension generally used for an MPEG-2 transport stream. HDV camcorders commonly record video as M2T, and video-editing applications use the format for transport-stream import, capture, and interchange.

An M2T file normally contains MPEG-2 video with MPEG audio or another supported audio stream inside an MPEG transport stream container. The extension alone does not guarantee strict HDV compliance: resolution, frame rate, bitrate, audio codec, transport-stream parameters, and interlacing must match the receiving device or editor.

How to convert BIK to M2T

FFmpeg is the most direct desktop method when its build can decode the BIK file.

1. Install a current FFmpeg build and place the BIK file in an accessible folder.
2. Check whether FFmpeg recognizes the streams with ffprobe cutscene.bik. Look for a Bink video stream and any audio stream.
3. Perform a general MPEG-2 transport-stream conversion with:
   ffmpeg -i cutscene.bik -c:v mpeg2video -q:v 2 -c:a mp2 -b:a 384k -ar 48000 -f mpegts cutscene.m2t
4. Open cutscene.m2t in the target application and verify playback, audio synchronization, frame size, and interlacing.

If the target is an HDV workflow, use parameters matching the required HDV profile rather than the general command. For example, a 1080i25-style transport stream can be produced with:

ffmpeg -i cutscene.bik -c:v mpeg2video -b:v 25M -minrate 25M -maxrate 25M -bufsize 17825792 -s 1440x1080 -r 25 -flags +ildct+ilme -top 1 -c:a mp2 -b:a 384k -ar 48000 -f mpegts cutscene.m2t

Change -s, -r, field order, bitrate, and audio settings for the required 720p, 1080i29.97, or other specification. Do not force these HDV values onto a source or device that expects a different format.

When FFmpeg reports that it cannot decode the BIK file, use RAD Video Tools to open the file and export an intermediate AVI, then encode that AVI with FFmpeg using the commands above. In RAD Video Tools, select the file, choose Convert a file, and select an AVI output if that option is available in the installed version. The intermediate file must contain decoded video; simply renaming .bik to .m2t does not convert it.

You can also convert the file for free on 101convert.com without installing software; the service still has to decode the particular Bink variant and encode an MPEG-2 transport stream accepted by your target.

Quality, compatibility, and limitations

This conversion normally requires full re-encoding because Bink video and MPEG-2 video use different codecs. The M2T file can therefore lose detail, introduce block artifacts, and become much larger than the original game asset. Increasing MPEG-2 bitrate reduces additional loss but cannot restore detail already absent from the BIK source.

Use the source frame rate and dimensions when the destination does not require a fixed HDV profile. Scaling or converting progressive footage to interlaced MPEG-2 can reduce quality and may create combing artifacts if field order is wrong. Check the result with ffprobe cutscene.m2t before transferring it to a camera, recorder, or restricted editor.

Some BIK files contain audio formats or features that a particular FFmpeg build cannot decode. If the converted file has no sound, inspect the audio stream separately and use RAD Video Tools or a current FFmpeg build. M2T is a container convention rather than a single complete specification, so an extension change alone cannot make a file compatible with an HDV device.