Free online BIK to M1V converter

What the BIK format is

BIK is the filename extension commonly used for Bink Video, a proprietary codec and container developed by RAD Game Tools. Video games use it for cutscenes, menus, loading screens, and other prerecorded sequences because Bink supports configurable compression and playback optimized for game engines.

You usually encounter BIK files in a game's installation directory, a game-development asset pipeline, or an archive of older game media. RAD Video Tools can inspect and convert Bink files. BIK files may contain Bink 1 or Bink 2 video and can also include audio streams, depending on how the original asset was made.

What the M1V format is

M1V normally identifies an MPEG-1 video elementary stream. It contains only MPEG-1 video, without the audio and system-level multiplexing found in formats such as MPEG program streams or MPEG-1 video files with an .mpg extension.

M1V is useful when an authoring application, broadcast workflow, testing tool, or older editor specifically accepts MPEG-1 elementary video. Its relatively simple structure is supported by many legacy tools, but MPEG-1 provides lower compression efficiency and generally lower quality than modern codecs at the same bitrate.

How to actually convert BIK to M1V

Using FFmpeg

FFmpeg can decode Bink files when the installed build includes the required Bink decoder and can encode MPEG-1 video. Place input.bik in a working folder, then run:

ffmpeg -i input.bik -map 0:v:0 -an -c:v mpeg1video -q:v 2 -f mpeg1video output.m1v

• -map 0:v:0 selects the first video stream and avoids accidentally selecting Bink audio.
• -an explicitly removes audio, which M1V cannot store.
• -c:v mpeg1video selects the MPEG-1 video encoder.
• -q:v 2 requests high variable-quality output; use a bitrate instead when a delivery specification requires one.
• -f mpeg1video writes an MPEG-1 elementary stream rather than a multiplexed MPEG container.

For a fixed bitrate, replace the quality option with a setting such as -b:v 3000k. To inspect the source before conversion, run ffprobe input.bik and check the resolution, frame rate, stream count, and codec name.

Some FFmpeg builds cannot decode Bink 2 or particular Bink variants. If FFmpeg reports an unsupported codec, open the file with RAD Video Tools, export it to an intermediate AVI or another FFmpeg-readable video file, and then encode that intermediate file with the command above. Use the original frame rate and dimensions unless the target application requires specific MPEG-1 limits.

Using the online converter

You can also convert the file for free on the 101convert.com website without installing software: open the converter for BIK and M1V, add the BIK file, select M1V as the output, start the conversion, and download the resulting file. This route is suitable for non-sensitive files; large game assets, proprietary footage, and files subject to licensing restrictions are better handled locally.

Quality, compatibility, and limitations

The conversion is a lossy re-encode: Bink frames are decoded and compressed again as MPEG-1, so the M1V cannot preserve the original Bink quality bit-for-bit. Avoid repeated intermediate exports, and keep the source resolution and frame rate when the receiving software supports them.

M1V contains no audio. If the BIK includes sound, export or encode that track separately, then use an application that can combine the audio and M1V into the container required by the final workflow. Renaming .bik to .m1v does not convert the codec or the container.

MPEG-1 has practical compatibility limits, including restricted chroma formats and frame-size expectations in older decoders. If the target program rejects the output, try a standard MPEG-1-compatible size, constant frame rate, and a conventional bitrate, or create a multiplexed MPEG file instead if the program expects audio and video in one file.