WEBM Metadata Viewer
Inspect WEBM track tags, muxer info, language fields, and attachments without changing streams.
Drag & drop a file here, or click to select
Max file size: 100 MB
Looking to remove metadata instead? Go to the Metadata Remover.
Why view WEBM metadata?
Checking WEBM metadata helps you protect privacy, verify authenticity, and understand how the file was created.
Trust capture and timing
Check GPS, creation_time, rotation, and timecode in your WEBM files before sharing.
Validate streams
Review codec, bitrate, resolution, FPS, and audio layout so your WEBM meets delivery specs.
See source apps
Surface encoder/muxer tags and chapters to track edits or conversions on your WEBM.
Preview the report layout
See how we surface EXIF, PDF, and video metadata before you upload your own file.
Example Metadata Report
After uploading, you'll get a detailed breakdown of your file's hidden data, similar to the example below.
Want to check your own file's metadata? Upload it above - no signup required.
Our secure process
We show you exactly what happens when you upload a file, so you know where your data goes and what stays untouched.
Upload over HTTPS
Pick or drop your WEBM. Transfers are secure.
Parse metadata only
We read headers and metadata blocks; the file content is not changed or recompressed.
Highlight key signals
We group timestamps, authorship, location, and technical fields so you can spot what matters quickly.
Display readable results
You see structured metadata grouped by sections for fast review with no downloads required.
Delete temporary copy
The transient server copy is purged right after processing completes.
Want to try it out? Upload your file above, no signup required.
What WEBM metadata can you view?
Here are the fields you can inspect before you share or archive the file. Use them to verify provenance, quality, and privacy.
- Track tags plus encoder and muxer notes
- Language codes and attachments like cover art or previews
- Codec, resolution, and duration for VP9/AV1 streams
What metadata lives inside a WEBM
WEBM is a constrained subset of Matroska (EBML) that permits only VP8/VP9/AV1 video and Vorbis/Opus audio, so most of the Matroska metadata vocabulary applies: segment Title, WritingApp, MuxingApp, per-track language code, chapters, and tags. What WEBM files look like in practice depends heavily on their origin — MediaRecorder-produced WEBM from browser capture has a Duration element of exactly 0 and a writing app of "Chrome" or "Firefox", while FFmpeg-muxed WEBM has a non-zero Duration and writing app of "Lavf" with the libavformat version number.
The Colour element matters more in WEBM than other containers because VP9 and AV1 both support wide color and HDR, and browsers rely on the Colour element (not the bitstream) to pick the right rendering pipeline. A WEBM tagged with Primaries=9 (BT.2020) and TransferCharacteristics=16 (SMPTE ST 2084) will render as HDR in supporting browsers; the same bitstream with the Colour element stripped will render as SDR. The viewer shows every field of the Colour element so you can tell whether an exported WEBM will color-shift on upload.
Attachments are rare in WEBM (most browser encoders ignore them) but not forbidden, and the spec permits ChapterAtom elements. Screen recordings from OBS and FFmpeg-produced WEBMs typically have a single track with no chapters and a minimal Tags block containing only the encoder string. Anything more exotic — embedded cover art, multiple audio tracks, subtitles — is a signal that the file was re-muxed by a desktop tool.
WEBM metadata FAQs
Why does my browser-recorded WEBM show Duration=0?
MediaRecorder in Chrome and Firefox writes an indeterminate-length WEBM with Duration=0. This is intentional (the length is not known while recording) and some players handle it poorly. The viewer shows the stored Duration and the derived duration from the last block timestamp.
Can WEBM store HDR metadata?
Yes, via the Colour element on the video track (Primaries, Transfer, Matrix, MaxCLL, MaxFALL). AV1 in WEBM is a common HDR delivery path on YouTube. The viewer decodes these fields explicitly.
Does WEBM carry GPS coordinates?
Not natively. Matroska tags can hold arbitrary key/value pairs, but no WEBM encoder writes GPS by default. If you see a "LOCATION" tag, it was written manually or by a custom pipeline.
What is the difference between WritingApp and MuxingApp?
WritingApp is the high-level tool name (e.g., "mkvmerge", "Chrome"). MuxingApp is the library version (e.g., "libebml v1.4.2 + libmatroska v1.6.4"). The viewer shows both.
Why do my screen recordings play with wrong colors on some sites?
Usually a Colour element mismatch: the encoder tagged the file as BT.709 but the bitstream is full-range BT.601, or vice-versa. The viewer shows Colour.Range (0=unspecified, 1=broadcast, 2=full) so you can match encoder and player expectations.