✳ PIXELOKAY · VIDEO TOOLS

Video Codec Inspector

Look inside your video file without uploading it. See its real container, video and audio codecs, frame rate, resolution, duration, bitrate evidence, and what the file can—and cannot—tell you.

◈ Codec-aware◷ Read-only◎ Browser-native
Start inspecting
YOUR WORKSPACE

Inspect your media

Drop multiple files and compare their technical details.

◈ Private by design · No server required
Files0In workspace
Video tracks0Identified
Audio tracks0Identified
Needs attention0Partial or unsupported

Media library

Add a file to view its streams.

Nothing to inspect yet

Select a video and its available technical metadata will appear here.

THE ESSENTIALS

A better way to understand a video.

A video's file extension describes its container—not necessarily the codecs inside. For example, MP4 may carry different video and audio encodings, and playback support depends on the device and browser.

01

Choose a video

Inspect one file or a batch. We read a limited portion of its metadata locally without sending it anywhere.

02

Explore each track

See video and audio codecs, dimensions, available timing information and clearly labeled estimates.

03

Take the report

Download per-file or batch JSON, plus CSV for comparisons. Incomplete scans and errors remain visible.

Frequently asked questions

Is this the same as FFprobe or MediaInfo?

No. This lightweight browser-only inspector parses selected container metadata without native binaries or a server. It does not fully decode packet streams, inspect every codec property, calculate precise VFR distributions, or provide exhaustive MediaInfo/FFprobe compatibility.

Why is the bitrate sometimes missing or marked approximate?

MP4 sample tables may reveal total per-track encoded sample bytes, allowing a derived bitrate. File-wide bitrate uses total file size and duration, including overhead. WebM, AVI and MPEG-TS metadata does not always provide a dependable per-stream bitrate.

Does a successful inspection guarantee the video will play?

No. A metadata signature can exist in a corrupt, encrypted or truncated file. Browser playback support also varies across operating systems, devices and codec profiles.

Are large files uploaded or fully loaded into memory?

No. Inspection uses bounded slices of local File objects and does not upload data. Exceptionally large movie headers or unsupported structures are reported as partial. Optional video preview may cause the browser to read more data for playback.

Using Video Codec Inspector

Inspect bounded video-container and stream metadata, retain partial or unsupported fields as unavailable, and export batch findings without transcoding or uploading media.

Workflow

  1. Open a supported local video and review the detected container and stream fields
  2. inspect partial or unavailable values rather than inferring them
  3. export the metadata report or batch findings and optionally preview through the browser’s native decoder.

Example

Compare the container and stream summaries for an MP4 and a WebM file, note fields reported unavailable, and export the reports without treating them as a full codec analysis.

Limits and data handling

This is bounded metadata inspection, not full packet or frame analysis, codec conformance or decoded HDR/color truth. MP4 frame rate may be an average. MPEG-TS duration, bitrate or resolution may be unavailable. Native preview depends on browser codecs and is optional. The tool does not use FFmpeg/WASM or modify source media. Parser and preview behavior need runtime acceptance.

FAQs

Does it verify that every frame decodes correctly?

No. It inspects bounded container and stream metadata; optional native preview is not a full packet analysis.

Does reported metadata prove HDR or color values are accurate?

No. Container fields are not decoded HDR or color truth; unavailable values remain unknown.

Related tools