Convert IRF to AVI

Older Windows editors, evidence-review systems, or media players may require AVI when a DVR recording is stored as IRF. Converting it also provides a shareable viewing copy when the recorder’s proprietary player cannot be installed on the receiving computer.

What the IRF format is

IRF is an ambiguous file extension, but it commonly identifies proprietary surveillance video exported by i3 International and other DVR/NVR systems. Depending on the recorder, an IRF package may include video, audio, timestamps, camera identifiers, encryption, or authentication data that ordinary media players cannot decode.

The exact IRF variant depends on the recorder model and firmware. Identify the source device before choosing software; an IRF file from one manufacturer may be unrelated to an IRF file from another. i3 recordings are typically opened with the matching i3 DVR Player, IRF Player, or an IRF Tool supplied with the recorder or obtained from the manufacturer’s support channel. Keep all files from the export together because some players require accompanying indexes, configuration files, or a complete export folder.

What the AVI format is

AVI is a Microsoft multimedia container that can hold video and audio encoded with different codecs. It remains compatible with many older Windows applications, surveillance-analysis programs, and media players, although modern software often prefers MP4 because AVI files can be larger and have less consistent codec support.

The codec selected during export determines practical compatibility. Motion JPEG plays in many legacy applications but creates large files; MPEG-4 produces smaller files but may fail in software that supports only specific AVI codecs. AVI is useful when the destination explicitly requires it, not as a universally better archive format.

How to convert IRF to AVI

1. Find the DVR/NVR manufacturer, model, firmware version, and the software included with the export. Do not select a converter based only on the .irf extension.
2. Install the matching vendor player or IRF utility on Windows. For i3 footage, use the player or export utility intended for that recorder generation. Renaming recording.irf to recording.avi changes only the filename and does not convert the data.
3. Open the export through File → Open or the player’s equivalent. If the software expects a folder, select the folder instead of an individual file.
4. Use the player’s export command, commonly Export → AVI, Save As → AVI, or Convert → AVI. Select the camera, time range, destination, frame rate, audio, and codec when those controls are available.
5. Open the resulting AVI in VLC or the intended destination application. Check the beginning, middle, and end, including timestamp overlays, camera identity, audio, and the requested time range.

There is no dependable universal desktop converter for proprietary IRF. If the vendor player can play the recording but has no export function, capture its playback with OBS Studio. Capture only the player window when possible, disable unrelated notifications, and use the original playback resolution and speed. OBS normally records to MKV or MP4, not AVI; convert that standard recording locally with FFmpeg if AVI is mandatory:

ffmpeg -i recording.mkv -c:v mjpeg -q:v 3 -c:a pcm_s16le output.avi

This creates a broadly compatible Motion JPEG AVI with uncompressed PCM audio. For a smaller AVI, use an MPEG-4 video stream, but confirm that the receiving application supports that codec:

ffmpeg -i recording.mkv -c:v mpeg4 -q:v 4 -c:a mp3 -b:a 128k output.avi

Do not pass the proprietary IRF directly to FFmpeg unless the exact build documents support for that recorder’s variant; unsupported input will not become readable through a filename change or a generic conversion command.

Online conversion options

Services such as CloudConvert and Zamzar can convert a standard intermediate file such as MP4 to AVI, but they generally cannot decode manufacturer-specific IRF. First export or capture the footage locally, then upload only the standard file if the recording is not confidential. Avoid uploading surveillance or evidentiary footage to a public conversion service unless the organization’s security and legal policies permit it.

Quality and evidentiary limitations

A vendor export usually decodes and re-encodes the proprietary stream; it cannot restore detail already lost in the DVR recording. Screen capture can reduce resolution or frame accuracy, add the player interface, alter timestamps, and omit embedded metadata. Direct vendor export is preferable whenever available.

Retain the original IRF files, the complete export folder, and the exact manufacturer player or utility. Treat the AVI as a viewing or editing copy because conversion may remove digital signatures, encryption, proprietary timestamps, authentication data, audio synchronization, or other chain-of-custody information. For legal use, document the recorder, software version, export settings, conversion command, and file hashes.