A video file can look simple from the outside: clip.mp4, movie.mkv, recording.mov. The useful details are inside. If the file will not play, uploads slowly, has no sound, or looks blurry after conversion, the extension is not enough. You need to inspect the container, streams, and playback-relevant metadata.

The quick answer: use a media-info viewer when you need to check the container, video codec, audio codec, resolution, frame rate, bitrate, duration, channel count, or sample rate before deciding what to do next. OnlinePlayer's media info inspector reads the file locally in your browser with MediaInfo.js, so a local file does not need to be sent to a server just to see what is inside.

What a Video Metadata Viewer Shows

A good metadata report separates the wrapper from the streams:

Field	What it tells you	Why it matters
Container	MP4, MOV, MKV, WebM, AVI, TS	The file extension may be misleading, but the container controls how streams are packaged.
Video codec	H.264, HEVC/H.265, VP9, AV1, MPEG-4 ASP	Browser support depends on the codec, not only the extension.
Audio codec	AAC, MP3, Opus, AC-3, FLAC	"Video has no sound" often comes from an unsupported audio stream.
Resolution and frame rate	1920x1080 at 30 fps, 4K at 60 fps	High resolution or high frame rate can explain stutter.
Bitrate	Approximate data rate	Useful for spotting huge files, over-compressed exports, and streaming issues.
Audio details	Channels, sample rate, bit depth	Helps explain why audio sounds wrong or fails in a destination app.

This is different from a player error message. A player may only say "cannot play this file." A metadata report tells you whether the problem is a WebM container, an HEVC video stream, AC-3 audio, an odd frame rate, or a damaged file header.

When to Check Metadata Before Playing or Converting

Check the file first when one of these is true:

• The extension says .mp4, but the file fails in a browser.
• Audio plays but the picture is black.
• The file works in VLC but not in Chrome, Safari, or a cloud preview.
• A conversion produced a much larger or blurrier output than expected.
• You need to share a video and want to catch codec, bitrate, or resolution surprises first.
• You are choosing between playing the file in the browser, converting it, or using a desktop tool.

The most common surprise is codec mismatch. For example, an MP4 can contain H.264 video, which browsers usually handle well, or it can contain HEVC/H.265, which is more limited depending on browser, operating system, and hardware. The file extension alone cannot answer that.

How OnlinePlayer Inspects the File Locally

Open the media info inspector, choose the video or audio file, and read the report. The page uses browser APIs and MediaInfo.js to parse the container and stream details on your device. For local files, the browser reads the file from disk; OnlinePlayer does not need to receive the file just to show the metadata.

That local workflow is useful for private recordings, client footage, school projects, and anything else you would rather not hand to a random upload-based checker. It is also faster for large files because you are not waiting for a multi-gigabyte video to travel over the network before seeing the codec.

There are still practical constraints. A severely damaged file may not parse cleanly. A very large file can put pressure on browser memory. OnlinePlayer focuses on playback-relevant stream details; it is not a forensic EXIF viewer and does not try to expose every proprietary camera or editor tag.

Codec Checker or Metadata Viewer?

The two queries overlap, but the job is slightly different.

Use a video codec checker when the playback question is narrow: "What codec is my video, and will this browser likely play it?" Look for the video codec, audio codec, container, profile, level, resolution, and frame rate.

Use a video metadata viewer when the question is broader: "What is inside this file, and what might affect playback or conversion?" Look for duration, overall bitrate, video details, and audio details.

In practice, a media-info report gives you both. Start with the codec fields if playback is broken, then check bitrate, resolution, frame rate, and audio fields before choosing a player or converter.

What to Do With the Result

If the file is MP4 with H.264 video and AAC audio, a browser player should usually be the first thing to try. If the file is MKV, AVI, WMV, or an MP4 carrying HEVC, the next step may be the online video player, a format-specific guide like play MKV in a browser, or conversion to MP4.

If the audio codec is the odd part, consider extracting or converting the audio with the audio converter. If the bitrate and resolution are simply too heavy for the device, changing players may not solve it; the file may need a lighter encode.

FAQ

Can this replace a full EXIF or privacy scanner? No. Some media files can carry private tags, but OnlinePlayer's current inspector focuses on stream and playback details such as container, codec, resolution, bitrate, duration, channels, and sample rate. Use a dedicated metadata removal tool if you need to strip private tags before publishing.

Is the codec the same as the file extension? No. The extension is the container. The codec is how the video or audio stream is compressed inside that container.

Can this prove a browser will play the file? It can explain the likely reason, but final playback still depends on browser, operating system, hardware, and file condition. Treat the report as a diagnosis tool, not a guarantee.

Bottom Line

When a video refuses to play or behaves strangely after conversion, inspect the file before guessing. A metadata viewer shows the container, codecs, resolution, bitrate, frame rate, duration, and audio details that the filename hides. Use OnlinePlayer's media info inspector for a local browser-based check, then decide whether to play, convert, or troubleshoot the file.