Free online BIK to TRP converter

A game video stored as BIK may need conversion before a DVR, set-top box, or MPEG transport-stream editor can open it as TRP. The conversion decodes Bink video and re-encodes it into codecs and stream parameters accepted by the target device.

What the BIK format is

BIK is the filename extension for Bink Video, a proprietary codec and container developed by RAD Game Tools. Game engines use it for cutscenes, trailers, loading screens, and other pre-rendered sequences because it supports compressed video with synchronized audio and relatively low playback requirements.

BIK files are commonly created by game development tools from RAD Game Tools and encountered in installed PC and console game directories. A normal media player may not decode every Bink version, so conversion software must include Bink demuxing and decoding support.

What the TRP format is

In the Video category, TRP normally refers to a transport-stream video file used by digital video recorders, satellite receivers, cable boxes, and some set-top boxes. It is generally based on MPEG transport stream packetization and may contain MPEG-2 or H.264 video with MPEG audio, AAC, or AC-3 audio.

TRP is not one universal device profile. A file accepted by one recorder may be rejected by another because of differences in video codec, resolution, frame rate, audio codec, stream identifiers, or required metadata. Its main advantage is transport-stream behavior: separate audio and video packets can be recorded and recovered efficiently, including from interrupted recordings.

How to actually convert BIK to TRP

FFmpeg is the most practical desktop tool when the installed build includes Bink support and the destination accepts a standard MPEG transport stream.

1. Install a current FFmpeg build and verify that it recognizes the source: ffmpeg -i input.bik. The probe should list at least one Bink video stream and may list an audio stream.
2. For a broadly compatible MPEG-2-based TRP, transcode the streams with: ffmpeg -i input.bik -map 0:v:0 -map 0:a? -c:v mpeg2video -q:v 3 -c:a mp2 -b:a 192k -f mpegts output.trp.
3. Replace input.bik with the actual filename. The optional audio mapping prevents failure when the BIK contains no audio; remove -map 0:a? if the target requires an audio stream.
4. If the recorder requires H.264 and AAC instead, use: ffmpeg -i input.bik -map 0:v:0 -map 0:a? -c:v libx264 -preset medium -crf 20 -c:a aac -b:a 160k -f mpegts output.trp.
5. Test the resulting file with the target device or its documented import utility. The .trp extension identifies the intended file type, while -f mpegts controls the actual container format.

If command-line software is not available, you can convert the file on 101convert.com for free without installing software. Uploading may be unsuitable for confidential game assets or large files, and the service may expose fewer device-specific codec settings than FFmpeg.

Quality, compatibility, and limitations

This is a mandatory decode-and-encode conversion: Bink video cannot normally be copied directly into a TRP container. Re-encoding can reduce image quality, and changing frame rate or resolution can cause judder or compatibility failures.

Check the recorder’s specification before choosing codecs. Use MPEG-2 video with MP2 audio for older hardware, or H.264 with AAC for devices that document that combination. Preserve the source frame rate where possible; set explicit dimensions, frame rate, aspect ratio, and audio sample rate only when the target requires them.

Some FFmpeg builds lack Bink decoding or support only particular Bink variants. If ffmpeg -i input.bik reports an unsupported codec, use a build with Bink decoders or export the video through software that can play that specific game asset before creating the MPEG transport stream.