All tools

MP4/WebM Video Info

Data

Read duration, resolution, and video/audio codec identifiers from an MP4 or WebM file's container header, without decoding any frames or transcoding

Drop in an MP4 or WebM file and get its duration, resolution, and video/audio codec identifiers straight from the container's own header boxes: the moov/mvhd/trak boxes for MP4 (ISO BMFF), or the Segment/Info/Tracks elements for WebM (EBML/Matroska). Nothing here decodes a single frame, demuxes sample data, or transcodes anything, so it works the same way whether the file is 2MB or 2GB and finishes instantly regardless of length. It reads exactly what the encoder wrote into the header: an MP4 muxed with the moov box at the end of the file (the common default before a faststart pass) still parses correctly since the whole box tree is scanned, not just the first few kilobytes.

videomp4webmmetadatacodeccontainer

How to use MP4/WebM Video Info

  • 1.Drop an MP4 or WebM file onto the upload area, or click to browse for one.
  • 2.Read the duration, resolution, and video/audio codec identifiers pulled from the container header.
  • 3.Use the REST API or an SDK to extract the same metadata from a server-side upload pipeline without a video processing dependency.

Frequently asked questions

Does this decode any video or audio?
No, it only reads the container's header boxes (moov for MP4, Segment/Info/Tracks for WebM). No frame is ever decoded, no sample data is demuxed, and nothing is transcoded.
What codec formats does it recognize?
It reports whatever four-character code (MP4) or CodecID string (WebM) the encoder wrote, such as avc1/hev1/av01 for MP4 video or V_VP9/V_AV1 for WebM video. It doesn't validate that the code is a real, decodable codec, it just reports what the header says.
Does file size or duration slow it down?
No, since only the header boxes are parsed, a two-hour 4K file returns just as fast as a two-second clip. The one exception is an MP4 whose moov box sits at the very end (not faststart-optimized), which the browser tool still handles correctly since it reads the whole file into memory first.
What if the file has no audio track, or no video track?
Whichever track type is present is reported; a silent screen recording with no audio track simply omits audioCodec, and an audio-only MP4/WebM omits width, height, and videoCodec.

Use via API, SDK, or MCP

cURL# Free: 1,000 req/day · Pro: 10,000 req/day
curl -X POST https://api.utilix.tech/v1/tools/mp4-webm-video-info \
  -H "Authorization: Bearer utx_live_..." \
  -F "file=@clip.mp4"

Get an API key from your dashboard · Full API docs →

Related tools

Docker Image ParserParse docker image references into registry, namespace, tag, and digest componentsCodeDockerfile Generator (AI)Describe your app in plain English and get a production-ready Dockerfile back, with multi-stage builds, layer caching, and a non-root user, powered by GPT-4o miniCodeEXIF ViewerRead camera make/model, orientation, timestamps, exposure settings, and GPS coordinates directly from a JPEG's EXIF dataImage