Browser Video Metadata Inspector
Browser Video Metadata Inspector: Loads video via HTML5 video element, queries videoWidth, videoHeight, duration, and container MIME type.
About this browser video metadata inspector
Report duration, decoded width, height, aspect ratio, and MIME type exposed by the browser; container atoms are not parsed.
How this tool works
Implements client-side Browser Video Metadata Inspector operations. Loads video via HTML5 video element, queries videoWidth, videoHeight, duration, and container MIME type specifically designed for a video editor inspects frame dimensions, container format, and audio stream properties of a video clip.
- Binary Atom / EBML Traversal: Reads binary headers, identifying top-level container structures and track description tables.
- Stream Metadata Extraction: Extracts video codec fourCC codes (avc1, vp09, av01), audio channels, bit depths, and natural pixel dimensions.
- MediaRecorder Stream Ingestion: Captures microphone or screen display streams via navigator.mediaDevices.getDisplayMedia into WebM blobs.
- Diagnostic Reporting: Outputs comprehensive codec inspection reports and downloads clean WebM or WAV recordings.
Worked example
Scenario: An editor checks browser-exposed metadata for a local short video.
Sample input:
Processing: HTMLVideoElement reports durationSeconds, decoded width and height, aspectRatio rounded to four decimals, and File.type; it does not parse stream codecs or container atoms.
Illustrative output:
Limits and verification
Screen and webcam recording require explicit user browser permission prompts. Proprietary container formats lacking standard browser demuxing support are flagged with format advisories.
Examples demonstrate an expected workflow; they do not prove every input or every branch of an external specification. Check important results with an independent source before using them for money, security, compliance, safety, or irreversible file changes.
Browser processing boundary
Tool input is processed by code running in the browser and is not intentionally sent to a CZOA processing API. The page can still request ordinary site assets, analytics, or advertising when those services are enabled. Browser extensions and managed-device software remain outside this tool's control.
Relevant references
These references govern or help explain the format, protocol, or calculation used here. Listing a reference does not claim certification or complete implementation of every optional feature.
Content owner: CZOA Tools · Last reviewed: 2026-09-15 · Review methodology
How to use it
- Enter, paste, or select your input data into the Browser Video Metadata Inspector workspace controls.
- Review available parameter fields, units, formats, or options configured for your task.
- Click the action button or observe immediate live calculations rendered in your browser runtime.
- Inspect the resulting output and any diagnostic messages, then copy or download the result if needed.
Frequently asked questions
How does Browser Video Metadata Inspector process the selected source?+
It loads one browser-decodable video through an HTMLVideoElement and returns durationSeconds (or null for non-finite duration), decoded width, height, aspectRatio rounded to four decimals, and the File.type MIME string or "video".
Which inputs and controls does Browser Video Metadata Inspector provide?+
The only input is one video. It has no edit, export, track, codec, bitrate, frame-rate, checksum, container-atom, subtitle, or repair control.
What limits apply to Browser Video Metadata Inspector?+
The values are browser-exposed metadata, not a container or codec parser. Browser support and the supplied MIME can differ from actual streams; duration, dimensions, MIME, precision, metadata completeness, and corrupt-file handling are not guaranteed.
What does browser-isolation evidence establish for Browser Video Metadata Inspector?+
Recorded browser requests contained no selected-video payload. This covers the observed tested-browser tool-value request path only; normal assets and the user environment are separate.
