Troubleshoot playback compatibility
Confirm whether the file is H.264, HEVC, VP9 or something else before deciding whether to transcode.
Guide
Media Info answers questions like “what codec is this file, how many frames, what bitrate?”. Once a file is selected, the panel sorts the local output of ffmpeg -i into “File”, “Video stream” and “Audio stream” groups: file name, size, container, duration and overall bitrate, plus video codec, resolution, frame rate, pixel format and video bitrate, or audio codec, sample rate, channel count and audio bitrate.
Updated 2026-09-103 min read
Media Info answers questions like “what codec is this file, how many frames, what bitrate?”. Once a file is selected, the panel sorts the local output of ffmpeg -i into “File”, “Video stream” and “Audio stream” groups: file name, size, container, duration and overall bitrate, plus video codec, resolution, frame rate, pixel format and video bitrate, or audio codec, sample rate, channel count and audio bitrate.
The panel is read-only: it produces no conversion jobs and no output files. One click copies all the information, and the full probe log can be expanded under “Raw ffmpeg -i output”; when a probe fails, “Probe again” is offered.
-i probe; a load or probe failure shows an error.| Input | Output | Notes |
|---|---|---|
sample.mkv |
Container, duration and bitrate, plus video codec, resolution and fps, plus audio codec, sample rate and channels | Only fields parsed successfully from the log are shown |
podcast.m4a |
M4A container, duration, AAC codec, sample rate, channels and bitrate | No video stream group |
-i log of the current ffmpeg build and its parser, so rare containers, damaged files or codecs that build does not support may fail to probe or come back with missing fields.Confirm whether the file is H.264, HEVC, VP9 or something else before deciding whether to transcode.
Copy the resolution, frame rate, bitrate and audio sample rate for a platform or a colleague.
Expand the raw ffmpeg -i output to see how the current build identifies the streams and the container.
No. The panel only runs a probe and parses its log; it submits no conversion job.
Codec, bitrate and stream information come from ffmpeg -i inside the browser rather than from the HTML5 player alone, so the same wasm core has to be loaded.
Media content is handed to ffmpeg.wasm for the -i probe locally in the browser and is never uploaded; the first probe downloads roughly 31–32 MB of ffmpeg core from the site's asset domain or jsDelivr, and the CDN request contains no file content.
Updated 2026-09-10
Container, codec, resolution, frame rate, bitrate, sample rate, channels, duration and size, copied in one click
Everything runs locally in your browser; files are never uploaded to a server