MediaInfo Viewer
MediaInfo Viewer
Cancel

MediaInfo Viewer

Drop an audio or video file and the browser parses MediaInfo-grade technical details locally: container, duration, bit rate, resolution, video and audio codecs, colour information, subtitle tracks and more. Four views — grouped tree / text / XML / JSON — with one-click copy. Everything runs on your machine; the file is never uploaded.

Drop or click to select a media file

How to read audio/video parameters

1. Layers first: container is not the codec

Layers of a media file: container, muxing layer, tracks, codecs and raw signals Media file = container (the box) Muxing layer: track layout · index · timestamps PTS/DTS · metadata Video track H.264 / HEVC / AV1 / VP9 Bitstream: NAL / OBU Raw signal: pixel frames YUV·RGB · sampling · depth Audio track AAC / Opus / FLAC / MP3 Frame: 1024 / 960 samples Raw signal: PCM samples Sample rate · depth · channels Text track SRT / ASS / WebVTT Image-based PGS / VobSub Text + timeline Language · default · forced

Container / muxing layer / track / codec / raw signal — five layers, top to bottom

Container and codec are different things: an MP4 can carry H.264 or H.265, and the same AAC stream can be muxed into MP4, MKV or TS. Always ask "is this a container property or a codec property?"

2. Key video parameters

AspectCommon valuesWhy it matters
CodecH.264/AVC, H.265/HEVC, AV1, VP9, MPEG-2, ProResCompression, compatibility, hardware decode
Resolution1920×1080, 3840×2160; SAR / PAR / DARPixels are not display size — watch rotation and DAR
Frame rate23.976 / 24 / 25 / 29.97 / 30 / 50 / 60, CFR vs VFRTimebase decides timestamp precision
Bit depth8 / 10 / 12 bit10-bit is the basis of HDR and high quality
Chroma subsampling4:2:0 / 4:2:2 / 4:4:44:2:0 saves bits, 4:4:4 keeps chroma for post
Colour spaceBT.601 / 709 / 2020; primaries · transfer · matrixMissing any of the three shifts colours
HDRHLG, PQ / HDR10, HDR10+, Dolby VisionNeeds depth + transfer function + metadata
Scan typeProgressive, Interlaced (TFF / BFF)Deinterlace correctly or you get combing
Profile / LevelHigh@4.1, Main10@5.1Level caps resolution, frame rate and bit rate
GOP structureI / P / B frames, keyint, IDR, closed vs open GOPAffects seeking and live latency
Bitrate controlCBR / VBR / CRF / ABR; maxrate · bufsize (VBV)CRF targets quality, VBV tames network jitter
Quality metricsPSNR / SSIM / VMAFVMAF tracks perception best; PSNR is only a number
Bitstream formatAnnex-B start codes vs AVCC / HVCC length prefixMP4 needs AVCC-formatted streams

3. Key audio parameters

AspectCommon valuesWhy it matters
CodecAAC-LC, HE-AAC, Opus, MP3, FLAC, ALAC, AC-3, DTSLossy for delivery, lossless for archival
Sample rate8k / 16k / 44.1k / 48k / 96k / 192k HzVideo usually 48k; music often 44.1k
Bit depth16 / 24 / 32 bit, int vs floatProduce at 24-bit, deliver at 16-bit
Channels & layoutmono, stereo, 5.1, 7.1; L R C LFE Ls RsA wrong layout sends dialogue to the rears
Bit rate64–320 kbps; roughly 64k per channel minimumVBR saves bits; CBR suits streaming
AAC profileLC / HE / HEv2 / ELD; ADTS vs raw (LATM)MP4 carries raw AAC; bare files use ADTS
Frame lengthAAC 1024 (960) samples; Opus 2.5–60 msDrives latency and muxing alignment
Sample formatS16 / S24 / S32 / F32; planar vs interleavedPlanar for processing, interleaved for output
LoudnessLUFS (EBU R128), True PeakStreaming targets around -14 LUFS, -1 dBTP
Lip syncA/V offset, delay, timestamp driftSync issues are usually timestamps or delay
SubtitlesSRT / ASS / WebVTT / PGS; default vs forcedForced shows only foreign-language parts

4. GOP and I / P / B frames: why decode order differs from display order

Display order versus decode order for I, P and B frames in a GOPGOP = distance between two consecutive I frames Display order · PTS I 1 B 2 B 3 P 4 B 5 B 6 P 7 Decode order · DTS I 1 P 4 B 2 B 3 P 7 B 5 B 6

I decodes standalone · P references earlier frames · B references both ways, so decode order differs from display order

A B frame needs the frame that comes after it, so that later P frame must be decoded first. That is the only reason containers carry two timestamps: PTS (when to show) and DTS (when to decode).

5. Suggested reading order for a report

  1. Container + codec combo — is it supported by the target device or browser?
  2. Resolution + frame rate + scan type — progressive or interlaced
  3. Bit depth + chroma subsampling + the three colour tags — colour shift and HDR eligibility
  4. Profile@Level — the ceiling for hardware decoding
  5. Video + audio bit rate — only meaningful next to resolution (bpp)
  6. Audio: codec + sample rate + channel layout — a wrong layout moves voices to the rear
  7. GOP / keyframe interval — seeking, precision and live latency
  8. Duration + size + per-track language / default / forced
Three classic traps: ① "MP4 won't play" is often moov at the end of the file (no faststart), or an Annex-B stream that was never converted to AVCC; ② washed-out or over-saturated picture: primaries / transfer / matrix missing or mismatched, typically BT.601 mixed with BT.709; ③ A/V drift or wrong channels: usually container timestamps or track delay, not a broken encode.