Container and codec
A container such as MP4, MKV or WebM packages tracks; a codec such as H.264, VP9, AAC or Opus defines how a track is encoded. Do not use the terms interchangeably.
1. Select media source
Drop a video or audio file here
or click to browse
Supported formats: MP4, MOV, MKV, WebM, MP3, WAV, FLAC, Ogg, AAC. Max file size:100 MB.
Sample file:
2. Extract metadata
3. Review results
Metadata report
Choose a media file or enter a direct URL.
What information can metadata extraction reveal?
It can report file and container information, video and audio tracks, codecs, dimensions, frame rate, bitrate, sample rate, language, subtitles, descriptive tags and embedded artwork when those fields are present and supported by the parser.
Metadata extraction reads what a file contains; it does not edit it
The tool parses supported container structures, track headers, descriptive tags and embedded artwork and presents them as a report. It should not rewrite, transcode or remove anything from the source file.
Who uses metadata extraction?
Developers, QA engineers, editors, archivists, support teams, media operations and researchers inspect metadata to diagnose playback issues, verify deliverables, inventory libraries and understand unfamiliar files.
Practical metadata inspection tasks
- Confirm container, codec, duration, resolution and frame rate before processing.
- Check audio sample rate, channels, bitrate and language.
- List subtitle or alternate audio tracks in a deliverable.
- Inspect title, artist, description, copyright and encoder tags.
- Extract or verify embedded cover artwork.
- Compare a file before and after conversion or metadata editing.
How to extract media metadata
Choose a local file or enter a direct media URL the browser is allowed to read.
Select standard or detailed parsing based on how much technical data you need.
Run extraction and review overview, tracks, tags, artwork and raw fields.
Pay attention to warnings and distinguish missing data from unsupported parsing.
Copy individual values or export a structured report, then keep the source unchanged.
How to read the metadata report
Bitrate and file size
Bitrate describes data per unit time for a track or file estimate. File size also depends on duration, overhead and multiple tracks.
Frame rate
A reported nominal or average frame rate may not prove constant-frame-rate behavior. Preserve raw time-base and per-sample information when available.
Tags and technical properties
Title, artist and comment are descriptive tags. Resolution, channels and codec are properties of the actual media streams.
Raw fields
Container-specific identifiers are useful for developers but can be cryptic. Show a human label when known and preserve the original key for reproducibility.
Metadata, filename and visible content are separate
A filename can be changed without modifying embedded metadata. A visible watermark or title card is pixel content, not a hidden tag. Metadata extraction should report what is stored in the file and avoid inferring information only from the filename or picture.
How inspection is handled
If verified, local files are parsed in the browser and do not need to be uploaded. A direct URL still sends a request to the source host and may require CORS, range, authorization or a valid token. Deep parsing can still use significant local memory.
Metadata extraction limitations
- A parser can only report fields present in the file and formats it understands.
- Different tools may label or normalize the same container field differently.
- Some technical values are estimates or derived from headers rather than full decode.
- Encrypted, malformed or fragmented media may yield partial results.
- Absence of a tag does not prove absence of ownership, copyright or other real-world rights.
Common inspection problems
The result says Unknown
The field may be absent, use an unrecognized identifier or require a parser the current build does not include. Preserve the raw value when possible.
The player reports a different duration
Players and parsers may use different tracks, edit lists, time bases or rounding. Show both raw units and normalized time when available.
A URL works in the player but extraction fails
The parser may need CORS access, byte-range requests or additional segments that playback obtained through another path.
Some tags are missing after conversion
The converter may not copy every tag namespace. Compare source and output reports and configure explicit metadata preservation when supported.
Metadata extraction FAQ
What is media metadata?
It is information stored with a media file, including descriptive tags and technical details about its container and tracks.
What is the difference between a container and a codec?
The container organizes one or more tracks and metadata; a codec defines how an individual video or audio track is compressed or represented.
Can the tool read both video and audio files?
Yes for the formats implemented by the current parser. The visible supported-format list must come from source capabilities.
Does extraction change the source file?
No. A metadata inspector should read and report data only.
Can it show subtitles and alternate audio tracks?
Yes when the parser recognizes those tracks and the file exposes their descriptors.
Can it extract cover artwork?
It can preview or download embedded artwork when present, decodable and allowed by the current implementation.
Why is some information missing?
The field may not exist, the container may store it differently, or the parser may not support that structure.
Can I inspect a file from a URL?
Only when the URL is a direct media resource and the host permits browser access. CORS, authentication, expiry and byte-range behavior can block parsing.
Does metadata prove who owns a file?
No. Tags can be absent, incorrect or modified. They are useful evidence about the file, not definitive legal proof.
Can I change the fields here?
Use Media Metadata Editor for writable supported fields. Extraction should remain read-only.
What output format is best for developers?
JSON preserves structure and data types. Markdown is convenient for human review. Include units and raw field paths in exported reports.
Why can two tools report different values?
They may use different parsers, normalization rules, tracks, rounding or interpretations of container-specific fields.
Related metadata and media tools
Media Metadata EditorUpdate supported writable tags, then return here to verify the result.Video ConverterChange the actual container or codec after inspecting compatibility.Video Thumbnail GeneratorExtract visible frames rather than hidden file information.AI Scene DetectionAnalyze visual changes after confirming source timing and codec details.