BIF File

What are BIF files and how to open them

Are you having problems opening a BIF file or are you simply curious about its contents? We're here to explain the properties of these files and provide you with software that can open or handle your BIF files.

What is a BIF file?

BIF files have multiple uses, and Boot Information is one of them. Read more about the other uses further down the page.

Boot Information File

Files with the .bif extension contain boot information files. These files are used to boot computers from a bootable CD or DVD. These files are commonly created by the MagicISO and UltraISO disc authoring applications.

How to open BIF files

We have identified three BIF openers that are compatible with this specific type of BIF file.

Programs that open Boot Information files

Last updated: August 24, 2026

All known file formats using extension .BIF

While Boot Information File is a popular type of BIF-file, we know of 6 different uses of the .BIF file extension. Different software may use files with the same extension for different types of data.

BIF Bitmap Info File

These files are part of the Binary Information Files format and to a corresponding .raw file with the actual image data.

While we have not verified the apps ourselves yet, our users have suggested six different BIF openers which you will find listed below.

ByLight Image Format Bitmap File

ByLight Image Format bitmap files are image files created by the 20/20 graphics application developed by byLight Technologies. These files store raster (bitmap) image data for display, annotation or capture tasks within 20/20. The format is obsolete and was mainly used on 32-bit Windows systems.

The format was produced by the 20/20 program and intended for viewing and editing images inside that environment. Images in this format are not widely supported by modern image tools, and the format is typically encountered when older 20/20 projects or image archives are opened.

Files begin with a specific byte signature: the first two bytes are 0xFA and 0xBA at offset 0, and there is a byte 0x04 at offset 3. These values help identify ByLight Image Format bitmaps even when file name extensions or other metadata are missing or ambiguous.

Infinity Engine Archive File

Infinity Engine archive files are bundles storing many game resource files together, e.g. graphics, sounds, dialogue trees, tile-sets, models, etc., packaged by BioWare's Infinity Engine games such as Baldur's Gate, Icewind Dale, and Planescape: Torment. They group disparate assets into one data archive to make game data easier for the engine to load and distribute.

These archives are created by the game (or by modding tools) in a private binary format called BIF (sometimes called BIFF in some sources). A companion index file, often named KEY, provides searchable names, types, and locations for the resources inside. When the game runs, it uses the namespace from the KEY file to look up resource entries inside the archive by their offsets, sizes and type codes. Modding tools can also write or read BIF archives, repacking resource tables and payloads. In newer editions there are three variants of BIF‐type archives: uncompressed (BIFF V1), compressed as a single zlib stream (BIF V1.0), or compressed in chunks with zlib (BIFC V1.0).

The archive begins with a 4-byte signature "BIFF" followed by a version tag such as "V1 ". After that comes metadata including the number of resources and pointers to tables listing each resource's ID, type, offset, size. The payload data for each resource follows elsewhere in the file. Offsets are used literally; exact matching of offset values is essential when creating or modifying an archive to avoid broken or corrupted resources. All numeric values are little-endian.

Roku Base Index Frames Container File

Roku Base Index Frames Container files store a sequence of thumbnail images and timing information used by Roku devices to support previewing video content (such as fast-forward, rewind, or scrubbing in the timeline). They are generated by Roku's official BIF tool from a source video and provide quick visual feedback during trick-mode navigation.

These files are created by content developers using Roku's command-line "biftool" available for Mac, Linux, and Windows. The tool takes video or extracted frame images and builds a BIF archive, often providing separate versions for standard definition and high definition. At runtime, Roku players reference these BIF files when the video's metadata indicates scene-based trick-mode support; otherwise Roku may fall back on time-based seek behavior.

Internally the file begins with an 8-byte magic number '0x89 0x42 0x49 0x46 0x0d 0x0a 0x1a 0x0a' at offset zero, followed by a version number, a count of images (N), a timestamp multiplier, and reserved space. An index table of N+1 entries gives for each a timestamp and file offset, with the final index marking end-of-data. The image data section follows, holding each frame so it starts at its listed offset. All multibyte integers are stored little-endian.

TomTom Data File

The "TomTom Data File" named here as TomTom Navigator general info format is a settings-style file written by the device itself to record metadata and device-specific configuration. It stores information about the hardware, firmware, installed maps, active features, and personalized settings. TomTom Navigator creates it during boot so that it reflects exactly what the device currently has (maps, voice-packs, version numbers and so on). It is used by the device internally - for example, to identify device serials, map versions, hardware identifiers or configuration preferences. Other programs internal to TomTom may read it when updating or checking installed content.

Typical contents are human-readable text divided into name-value pairs under labeled sections, such as DeviceName, DeviceVersionHW, DeviceSerialNumber, MapVersion, CurrentMap, UserLanguage, UserName, Features etc. The file is plain ASCII or similar text, with each setting on its own line. One example file begins with "[TomTomGo]" as header for the first section.

This file is not a navigational map database or image/bitmap archive; it does not contain routing geometry or map tiles. It also is not intended to be edited casually since its contents are used for licensing, version checks and internal correctness.

Files typically start with a section header line (such as "[TomTomGo]") followed by multiple lines each with a key, an equals sign, and a value. Newline separators are used. The DeviceUniqueID entry uniquely identifies that unit. MapVersion entries record which version of map files are installed. Hardware version entries such as DeviceVersionHW and BootLoaderVersion record firmware/hardware status.

Various apps that use files with this extension

These apps are known to open certain types of BIF files. Remember, different programs may use BIF files for different purposes, so you may need to try out a few of them to be able to open your specific file.

Help us help others

File.org helps thousands of users every day, and we would love to hear from you if you have additional information about BIF file formats, example files, or compatible programs. Please use the links below or email us at submit@file.org to discuss further.