About Codec Detector

Reads media metadata and checks codec support. Upload a local file or provide a direct URL. The tool uses the browser’s native HTMLMediaElement API to read container, resolution, and duration, estimates codecs from the file extension, and probes the browser’s real decode support with MediaSource.isTypeSupported and canPlayType.

• Accepts video and audio files via file upload or direct URL
• Detects container format from file extension: MP4, WebM, Ogg, AVI, QuickTime, Matroska, FLAC, WAV, and more
• Reads actual resolution and duration from browser media element metadata
• Estimates codecs from the container/extension (H.264, HEVC, VP8/VP9, Theora, AV1, AAC, Opus, Vorbis, MP3, PCM, FLAC), clearly labeled as estimates
• Checks real browser codec support via MediaSource.isTypeSupported and HTMLMediaElement.canPlayType
• File size reported for local uploads; export analysis results as JSON

Frequently Asked Questions

How accurate is the codec detection?

Container format, resolution, and duration are accurate—they come from the browser’s media decoder. Codec values are estimated from the file extension (e.g., .mp4 maps to H.264/AVC) and are labeled as estimates; they won’t distinguish H.264 from H.265 inside the same container. To read the exact stream codec, parse the container with a tool such as ffprobe.

What does the browser support section show?

It asks your browser directly—via MediaSource.isTypeSupported and canPlayType—whether it can decode each common codec. Results reflect your current browser and platform, not the uploaded file, so they can differ between Chrome, Firefox, and Safari.

Why can’t it analyze my URL?

The URL must point directly to a media file (.mp4, .webm, etc.), not a streaming page. CORS restrictions may also block cross-origin URLs. For best results, use direct file upload.