What MediaInfo is

MediaArea publishes MediaInfo under its own BSD-style licence, the MediaInfo(Lib) License, in three forms: a graphical program, a command line program and a library for other software. The site lists Windows, macOS, Android, iOS and a long row of Linux distributions, plus Flatpak and Snap packages. The containers it reads include MPEG-4, QuickTime, Matroska, AVI, MPEG program and transport streams, MXF, WMV and FLV. Video codecs include MPEG-1 and 2, H.263, MPEG-4 Visual, H.264/AVC, H.265/HEVC and FFV1. Audio includes MPEG Audio and MP3, AC-3, DTS, AAC and FLAC. Subtitle formats such as CEA-608 and 708, DVB, Teletext, SRT, SSA/ASS and SAMI are recognised. Tags in ID3v1 and v2, Vorbis comments and APE are shown. Views are text, sheet, tree and HTML and the results export to text, CSV and HTML.

The forensic interest lies in the encoding details. A file carries the name and settings of the library that wrote it, encoded and tagged dates, the frame rate mode and the stream layout. A video said to have come straight from a phone but carrying the settings string of a desktop encoder needs explaining. Two files from the same DVR should share a structure, and one that differs stands out. MediaInfo reports what the container declares, which can be edited, and it does not decode frames, so it sits beside ExifTool for the metadata tags and ffprobe for frame-level timing. It is also the quickest way to document a batch of exports: the command line version runs over a folder and writes one record per file into the case. Proprietary DVR formats that are not standard containers mostly fall outside its reach.

Primary applications

Where it is used

  • Recording the technical details of a media file before examination
  • Checking the writing library and encoding settings against the claimed source
  • Comparing files from the same device for structural differences
  • Reading the frame rate mode and stream layout of CCTV exports
  • Documenting a batch of files in one command line pass
  • Confirming what codec a player will need before conversion

Who uses it

  • Video and audio forensic analysts
  • CCTV units documenting exports
  • Media archivists and broadcast engineers
  • Students of multimedia forensics

Capabilities and limits

Major capabilities

  • Container, stream, codec, bit rate, frame rate and duration reporting
  • Encoding settings, writing library and encoded and tagged dates where present
  • Recognition of MPEG-4, QuickTime, Matroska, AVI, MPEG-TS, MXF, WMV, FLV and other containers
  • Video, audio and subtitle stream details for the main codecs
  • ID3, Vorbis comment and APE tag reading
  • Text, sheet, tree and HTML views with export to text, CSV and HTML
  • Graphical, command line and library editions
  • Packages for Windows, macOS and many Linux distributions

Technical limitations

  • Reports what the container declares, which can be edited
  • Does not decode frames or show frame-level timing
  • Proprietary DVR formats outside standard containers are mostly unreadable
  • No hashing, case notes or report of its own
  • Field names and values are technical and need interpretation

Learning with DFRTI

Independent professional education covering the principles and workflows of MediaInfo. DFRTI is not a vendor training centre and its courses are not vendor certifications.

Courses that cover this tool

Product names and trademarks belong to their respective owners. DFRTI is an independent educational and research institute. Inclusion in this directory does not imply manufacturer endorsement, partnership or authorisation. Facts are checked against the manufacturer's public documentation on the date shown and may have changed since.

Go deeper with DFRTI

Free pages explain the ground. Structured courses, lab work and a mentor take you from knowing about it to doing it on a case.