How is this different from a player's info panel?

Player panels vary by implementation and often omit fields; the inspector parses container and streams directly and runs right in the browser.

Specs look fine but it still stutters — why?

The file is healthy; the playback side is the limit. Follow the three-step stutter playbook: lower bitrate, resolution, then codec.

Can I inspect files in batch?

Add files one after another; inspection is pure parsing with no output render, so a library sweep goes quickly.

Workflows 5 min read

Read Your Video's Specs: Codec, Bitrate, Frame Rate

Nine out of ten video problems are parameter problems: playback fails because the codec lacks hardware support, compression disappoints because the bitrate was already low, edits jitter because frame rates mismatch. Read the specs first — the inspector parses the file locally and lays out codec, resolution, bitrate, frame rate, and tracks.

Codec first: the compatibility answer

The codec decides whether a device can hardware-decode: H.264 plays everywhere modern; HEVC and AV1 may not on older hardware. When a file refuses to open on a TV, car unit, or old phone, check the codec — converting HEVC/AV1 to H.264 beats swapping players.

Then bitrate and resolution: the compression decision

Bitrate tells you the compression headroom: a 40 Mbps 1080p source has room to spare; a 5 Mbps one has almost none. Resolution sets playback compute demand — 4K stutter means check the device before deciding between 1080p and a codec swap.

Won't play / stutters: check codec and resolution, then lower bitrate, resolution, or switch codec
Before compressing: check bitrate to judge the headroom
Before editing: align project settings with the source frame rate

Frame rate and audio: the easy misses

Frame-rate mismatch makes speed changes and interpolation jitter in editors; project settings should match the source. Audio track info (codec, channels, sample rate) tells whether a sound problem lives in the file or the player. Inspection is fully local.