Skip to content

Video codec, bitrate, and container inspector

Reveal container atoms, codec profiles, bitrates, and privacy-sensitive GPS or creation tags with lossless metadata removal.

Your files are open only in this tab. Nothing is uploaded.

Video container input

Inspect MP4, MOV, and WebM codecs, bitrates, fast-start status, creation timestamps, and GPS tags offline.

Drop a video file here

MP4, MOV, M4V, or WebM parsed in memory.

How to use Video metadata viewer

  1. Open a local video container. Drop an MP4, MOV, or WebM recording onto the upload area, or click Load sample MP4 video to inspect synthetic tracks offline.
  2. Review privacy and codec panels. Check Privacy & GPS location for geographic coordinates, then expand Container summary, Video tracks, Audio tracks, and Container metadata tags.
  3. Strip GPS location and creation timestamps locally. Click Strip GPS & metadata to drop descriptive boxes, zero clock fields, and patch chunk offsets without altering video pixels.
  4. Download JSON inspection report or clean video. Click Download JSON report for structured metadata records, or click Download clean after verifying Removed fields.

Your camera, microphone and recordings stay on this device. Nothing is uploaded or streamed anywhere.

Inspecting MP4, MOV, and WebM container atoms

Smartphones, screen recorders, and editing tools store technical stream headers alongside geographic coordinates and encoder timestamps inside video wrappers. Using a browser-based Video Metadata Viewer gives you lossless metadata removal without re-encoding video bytes on third-party servers.

Reading video codec profiles, bitrates, and color space

Dropping an MP4, MOV, or WebM recording launches zero-copy binary parsing inside a background Web Worker, or you can click Load sample MP4 video to generate a 320 × 180 px test clip locally. Container summary reports format type, exact size in bytes, total clip duration, and whether the moov index arrives before mdat for Fast-Start streaming.

Under Video tracks and Audio tracks, this local metadata inspector decodes avc1, hvc1, vp09, and av01 codec tags alongside mp4a AAC or Opus streams. When colr nclx or nclc atoms appear, the inspector translates color primaries and transfer matrices across BT.709, BT.2020 PQ/HLG, sRGB, and BT.601.

Finding ISO 6709 GPS tags and encoder strings

Media containers defined by the Library of Congress MPEG-4 File Format specification nest descriptive user blocks inside hierarchical atoms. Privacy & GPS location highlights ISO 6709 coordinates stored inside ©xyz and loci boxes, plus Apple keys/ilst metadata and encoder identifiers inside udta or meta.

Timestamps inside mvhd, tkhd, and mdhd convert from the 1904 Mac HFS+ epoch (2,082,844,800 seconds before 1970) into readable UTC strings, while Matroska timestamps convert from 2001-01-01. Audio-only editors needing similar tag checks can switch to our ID3 and FLAC audio tag inspector.

How does lossless scrubbing strip GPS tags without re-encoding?

Binary scrubbing removes metadata boxes directly in memory while keeping raw mdat video frames and Opus or AAC packets untouched. Because no transcoding pipeline decodes or re-compresses media samples, output visual sharpness stays identical and scrubbing completes in milliseconds inside your browser.

Rebuilding ISO-BMFF boxes and patching stco offsets

Clicking Strip GPS & metadata invokes rebuildIsoContainer inside everyday.worker.ts, guided by the MDN Web Workers API architecture so multi-megabyte containers never freeze UI controls. The builder drops udta, meta, and uuid boxes completely from the header tree.

Dropping header bytes shifts every downstream media sample position, which breaks unpatched players. The worker therefore recalculates byte deltas and patches 32-bit stco, 64-bit co64, and fragmented tfhd base-data offsets so keyframes remain aligned down to the byte.

Zeroing timestamps and writing WebM EBML Void padding

On MP4 and MOV containers, the scrubber zeroes creation and modification fields inside mvhd, tkhd, and mdhd headers, removing camera clock traces without altering duration ticks. Removed fields lists every erased tag key alongside the exact byte reduction achieved.

For WebM files beginning with EBML signature 0x1A 0x45 0xDF 0xA3, the worker overwrites Tags, MuxingApp, WritingApp, Title, and DateUTC in-place using EBML Void (0xec) padding bytes. You can also extract still frames and contact sheets from scrubbed footage afterwards without leaking thumbnail GPS tags.

Fast-Start moov order, color tags, and container specs

Comparing container structures helps troubleshoot streaming stalls, HDR color shifts, and lingering encoder fingerprints before publishing exports. Inspecting clips created via MDN MediaRecorder API reference streams shows how browsers pack codec headers versus phone cameras.

Container element Format family What it stores Scrubbing behavior Typical unit or marker
©xyz, loci, ilst MP4 / MOV (ISO-BMFF) GPS coordinates, device name, software Dropped via udta/meta/uuid pruning ISO 6709 string (+37.7749-122.4194/)
mvhd, tkhd, mdhd MP4 / MOV (ISO-BMFF) Movie and track creation clocks Creation/modification fields zeroed 2,082,844,800 seconds Mac epoch
stco, co64, tfhd MP4 / fragmented MP4 Byte offsets pointing into mdat Patched by exact removed byte delta 32-bit or 64-bit byte offsets
colr (nclx / nclc) MP4 / MOV (ISO-BMFF) Color primaries and HDR transfer curves Preserved intact for accurate color BT.709, BT.2020 PQ/HLG, sRGB
Tags, MuxingApp, DateUTC WebM (EBML) Muxer version, title, UTC timestamps Replaced in-place with Void (0xec) 0x1A 0x45 0xDF 0xA3 magic bytes

If you record browser talking-head clips directly with our Webcam Recorder, running a metadata pass afterwards confirms codec profile strings and removes browser muxer labels before distribution.

Tip: Always inspect phone captures before sharing raw .mp4 or .mov files online, because consumer messaging exports sometimes re-wrap footage while leaving ISO 6709 GPS atoms inside moov/udta intact. Click Strip GPS & metadata first, verify Removed fields, and publish the clean download.

Auditing codec bitrates and sharing clean exports

Checking stream parameters before uploading saves bandwidth and avoids platform re-compression surprises. Under the W3C MediaStream Recording specification, browser recorders may vary frame pacing or bitrate across hardware encoders.

Exporting full JSON inspection reports for pipelines

Clicking Download JSON report writes a structured JSON snapshot containing container summary fields, track codec descriptors, dimensions (px), audio sample rate (Hz), bitrate, and parsed metadata tags. Quality assurance teams attach these JSON logs alongside compliance reviews to verify BT.709 or BT.2020 conformance.

Clicking Load sample MP4 video tests the pipeline deterministically with a generated 320 × 180 px H.264 avc1.64001e High @ L3.0 stream and 48,000 Hz AAC-LC audio carrying +37.7749-122.4194/ coordinates and HandyTools Test Encoder. Scrubbing that sample in our metadata inspector proves zero location strings remain inside Container metadata tags and shows 0 ms re-encoding delay.

Verifying browser-recorded clips before publication

After running Strip GPS & metadata, clicking Download clean saves your sanitized <stem>-clean.<ext> container straight from browser RAM while retaining original video frames and audio tracks. Re-opening the clean file inside Video Metadata Viewer confirms empty GPS fields and updated byte offsets.

Teams distributing release bundles or archival assets across build environments can bundle cleaned videos offline for release alongside JSON checksums and reports. Every temporary buffer stays strictly on your device and clears when you leave the tab.

Questions

Does stripping video metadata degrade video quality?

No. Binary container scrubbing preserves mdat payloads and WebM clusters verbatim, so encoded video frames and audio packets remain bit-identical. Only metadata boxes, creation timestamps, and chunk offset tables change during lossless export.

Which GPS and camera tags can MP4 files hide?

Smartphones and editing suites frequently embed ISO 6709 coordinates in xyz and loci boxes plus software titles inside Apple keys, ilst, udta, and meta atoms. Creation and modification times also record exact shooting dates using the 1904 Mac epoch.

How does WebM metadata scrubbing protect MKV and WebM clips?

WebM scrubbing scans EBML header elements for Tags, MuxingApp, WritingApp, Title, and DateUTC records. Those elements are overwritten in-place with EBML Void (0xec) padding so muxer fingerprints disappear without disturbing audio or video playback clusters.

What codec and color space fields appear in the inspector?

Video tracks report FourCC codec strings such as avc1, hvc1, vp09, and av01 alongside coded pixel width, height, bitrate, and frame rate. When present, colr atoms identify nclx or nclc color spaces including BT.709, BT.2020 PQ or HLG, sRGB, and BT.601.

What does Fast-Start moov placement mean for web video playback?

Fast-Start means the moov index box sits before mdat inside an MP4 or MOV file. Browsers can begin streaming and seeking immediately upon reading initial bytes instead of downloading the entire media payload first.

How does Load sample MP4 video demonstrate privacy scrubbing offline?

Clicking Load sample MP4 video generates a deterministic 320 by 180 H.264 clip with 48,000 Hz AAC-LC audio inside browser memory. Its header intentionally embeds coordinates +37.7749-122.4194/ and HandyTools Test Encoder so you can test stripping safely.

Updated