Inspect a file in three steps
Start with the file that is actually failing or being delivered, not a screenshot of an export dialog. The inspection reads its available container and stream metadata through the browser's FFprobe engine.
- 1
Choose the original media
Select one audio or video file or drop it into the tool. The file remains local to this tab. Inspection begins only when you press Inspect media, and you can cancel or reset the selection while the engine is working.
- 2
Review container and stream details
Read the container summary first, then select a stream by index. Video streams expose picture and color properties; audio streams expose sample and channel properties. Subtitle, attachment and data streams remain separate entries rather than being counted as ordinary picture tracks.
- 3
Export only what you need
Use Copy JSON, JSON download or TXT download to share the current report. Metadata tags are off by default. If you enable them, review the tag section before sharing; titles, creation dates and author fields may reveal information unrelated to the technical question.
Container and codec are different questions
A container organizes streams, timestamps and metadata. A codec describes how a particular stream is represented. Two files with the same extension may therefore need different decoders, and changing an extension does not change the encoded content. The report presents container and stream fields separately so these distinctions remain visible.
This distinction also helps avoid unnecessary transcoding. A compatible video stream may only need a different wrapper, while an unsupported codec requires actual encoding. The viewer does not make that decision automatically: it supplies evidence that you can compare against the receiving application's documented requirements.
What the report includes
The summary shows the detected container, reported duration, stream count and reported overall bitrate. Individual stream details include codec names and available profile information. Video fields include pixel format, aspect ratios, color declarations and frame-rate declarations. Audio fields include decoded sample format, reported bit depth, sample rate and layout. Cover art is identified when the attached-picture flag is present. Rotation is shown only when the probe exposes it.
Useful for delivery checks and troubleshooting
Interpret reported values in context
Overall bitrate includes container overhead and all streams, so it is not interchangeable with one video stream's bitrate. Decoded sample format is not necessarily the original recording depth. Color declarations describe signaling, not a visual HDR certification. Declared frame count is not an independently counted total. Use these fields as technical clues and verify important delivery requirements in the destination workflow.
- Compare average and nominal frame rates cautiously. Values are container or stream declarations; this tool does not decode every frame to certify constant or variable frame timing.
- Check both stored width and height and any rotation value. A phone recording can store landscape pixel dimensions while a display matrix asks players to show it vertically.
- Keep an eye on missing values. Not reported is different from zero, and absent bitrate or frame-count fields are common in some formats. Never fill an unknown field with an assumed specification.
Local inspection with deliberate report sharing
The media is read in a browser worker and is not uploaded by this tool. The analysis engine must be downloaded on first use, but that download does not transmit your source file. Reset clears the displayed selection and report. The original media on your computer is never rewritten.
Reports omit the original filename and exclude arbitrary fields outside the technical schema. Tags are removed from both copied and downloaded reports unless you enable them. This is a practical sharing safeguard, not a full anonymization service: even technical properties can reveal something about a recording, and enabled tags deserve manual review.
Three practical inspection scenarios
A video editor receives a portrait phone clip. The report shows its stored resolution, rotation side data, codec profile and audio layout, providing useful context before the clip is placed on a timeline.
A podcast producer checks a WAV master and an MP3 delivery. Sample rate, channel count and codec are visible separately, so the compressed file is not mistaken for the uncompressed master.
A multilingual MKV contains picture, two audio languages and subtitles. Select each stream by its index to see its codec and flags; enable tags only when language or title labels are needed.
Inspection limits and unsupported sources
Only local files are accepted, not streaming URLs, playlists or protected media. Supported containers and codecs depend on the pinned browser engine. Large files can exhaust tab memory because analysis requires local file copies. The optional source preview depends on browser playback support; preview failure alone does not prove inspection will fail. This page does not scan every frame, calculate loudness, validate broadcast compliance or repair broken files.
- Do not use header inspection as a complete integrity test. A file can expose readable stream information while containing damaged packets later in the recording.
- Choose a converter or editor when you need to change codec, remove tags, rotate pixels or normalize sound. Reading a report does not modify any part of the source.
Media inspection questions
Why are some bitrate or frame-count fields missing?
Not every container stores every value, and some values cannot be established from a short structural probe. The viewer displays Not reported instead of estimating a number that might be misleading. A full packet or frame scan is outside this page's scope.
Can I see every audio and subtitle track?
The selector lists streams returned by the probe, including audio, video, subtitles and attachments when present. Choose the relevant index to inspect its available fields. This does not extract, decode for playback or translate a subtitle track.
Does downloading the report remove metadata from my video?
No. Export controls create a separate report and never rewrite the source. Disabling tags only removes them from the shared report. Use the dedicated metadata-removal tool when the media file itself needs a privacy-oriented cleanup.
Does a readable report guarantee the file will play?
No. A player still needs suitable decoders and may reject a profile, pixel format, timestamp pattern or damaged section. Structural inspection narrows the investigation but cannot guarantee complete playback or compatibility with a particular application.