MediaInfo is a free utility that reads and displays technical and tag data from video and audio files, revealing codecs, bitrates, channels, subtitles and track structure so users can verify, troubleshoot and document media collections with confidence.
MediaInfo is a media inspection tool that opens a video or audio file and reports the technical and tag information stored inside it. You drag a file onto the window, choose a view such as Basic, Tree, or Text, and immediately see container format, codec, resolution, frame rate, bitrate, duration, channel layout, language tags, and embedded subtitle tracks. The same data can be copied as text, exported to CSV, JSON, or XML, or generated from the command line for batch work. Because the report comes straight from the file's headers, it is a fast way to confirm what you actually have before editing, encoding, archiving, or troubleshooting playback.
The tool separates its output into clear groups, so you can jump straight to the video track, an audio stream, or the subtitles without scrolling through everything. Raw values sit beside their human-readable equivalents, which matters when you need to compare a file against a delivery specification or explain a playback problem to someone else. Power users rely on the command-line mode to audit entire folders, catching files that use an unexpected codec or container before they reach a client. If you are preparing footage for editing in Lightworks, reading the report first tells you whether the clips will import cleanly. Custom templates let teams save the exact fields they care about.
MediaInfo earns its place in a media toolkit because it answers a question most players ignore: what is actually inside this file? Instead of guessing from a filename or a playback glitch, you get a structured report you can act on. That shortens troubleshooting dramatically, because codec mismatches, silent audio tracks, missing subtitles, and unusual frame rates all become visible in seconds. It also prevents wasted work, since you can check a delivery against a required specification before uploading or handing it off. The information is read-only, so inspecting a file never alters it. Reports can be shared as plain text or spreadsheets, which makes them easy to paste into a ticket or attach to a project handover. Because the same engine powers both the graphical window and the command line, occasional users and automated pipelines get consistent results. For archivists, editors, support teams, and anyone who receives media from other people, that transparency replaces guesswork with evidence.
MediaInfo reads the header of a file to name its container and every codec inside it, from common H.264 video to less familiar audio formats. This removes guesswork when a file will not play or when you need to confirm exactly what a device recorded.
Switch between Basic, Sheet, Tree, Text, and HTML views depending on how much detail you need. Basic gives a quick summary for everyday questions, while Tree exposes the full structure of every track and stream when you are chasing a specific value.
Save any analysis as CSV, JSON, XML, HTML, or plain text so the findings fit into a spreadsheet, a bug report, or a script. Structured exports are ideal for comparing several files side by side or feeding results into an automated quality check.
The same engine runs from a terminal, so you can inspect a single file or sweep an entire library and log the results. Batch scanning quickly uncovers outliers such as unexpected codecs, odd frame rates, or files missing an audio track.
Every audio stream is listed with its codec, channel layout, sample rate, bit depth, and language tag, and subtitle tracks are reported alongside them. That makes it straightforward to spot a missing surround mix, a mono source, or subtitles that never made it into the final file.
Templates let you choose which fields appear and how they are formatted, so reports can match an internal checklist or a client's delivery sheet. Teams can keep one template for quick reviews and another for formal sign-off documentation.
A bundled shell extension lets you inspect a file directly from the file manager's context menu, without opening the main window. Properties such as duration, resolution, and codec appear instantly, which is convenient when sorting through a folder of mixed recordings.
Beyond technical values, MediaInfo reads embedded tags such as title, artist, album, track number, encoder, and creation date, plus chapter markers in supported containers. That helps you clean up inconsistent naming and verify that tagging survived the encoding process.
MediaInfo reads the header of a video or audio file and lists container format, codecs, resolution, frame rate, duration, bitrate, audio channels, sample rate, language tags, subtitles, and chapters. It presents the data as read-only facts, so you can confirm what a file really contains rather than trusting its filename or extension.
No. The tool only reads file headers and reports what it finds. Opening, scanning, or exporting a report leaves the original file untouched, so it is safe to inspect master footage, client deliverables, or archived media without any risk of altering them.
Yes. Besides the graphical window, MediaInfo includes a command-line mode that can process one file or an entire directory tree and log the output. That makes it practical to audit a large library for unexpected codecs, silent audio tracks, or files that fall outside an agreed specification.
Basic shows a short, plain summary of the most important values for quick checks. Tree expands the complete structure of the file, grouping parameters by general, video, audio, text, and menu sections so you can drill into any individual track or stream.
A failed import usually comes down to a codec, container, or frame rate the editor cannot handle. MediaInfo shows those values up front and can export them as text or a spreadsheet, which is useful evidence when you ask a colleague or a support team for help.
Yes. Any analysis can be exported as plain text, HTML, CSV, JSON, or XML and pasted into a message, ticket, or document. Because the report contains only the fields the recipient needs, it communicates a technical problem far more precisely than describing it in words.
Comments