Browser media, codec and image support checker
Test which audio codecs, video containers, next-generation image formats, and binary web APIs your current browser supports right now—100% locally on your device with zero uploads or external requests.
Live capability results for this browser
The table below queries HTMLMediaElement.canPlayType(), window.VideoDecoder / AudioDecoder (WebCodecs), window.createImageBitmap, and Web Crypto / Service Worker streaming APIs directly in your browser tab.
| Format / Codec / Web API | Category | MIME / Codec string tested | Browser result |
|---|---|---|---|
| Running local capability checks… | |||
Understanding canPlayType, WebCodecs and image decoding across browsers
When building a media player, file previewer, or client-side transcoder, relying on the browser's User-Agent string is fragile and error-prone. Feature-detecting codec support directly exposes important platform nuances:
- Why
canPlayType()returns"probably","maybe", or"": Because container formats like MP4, WebM, and Ogg can wrap many different codecs, passing a bare container MIME type such asvideo/mp4without acodecs="..."parameter can return at best"maybe". Passing an explicit RFC 6381 codec parameter (such asvideo/mp4; codecs="avc1.42E01E"for H.264 Baseline Profile Level 3.0) allows the browser to confirm hardware or software decoder availability and return"probably". - HEVC (H.265) and AC-3 hardware licensing gaps: While Apple Safari (on macOS and iOS) supports HEVC (
hvc1) and Dolby Digital AC-3 natively via hardware decoders, desktop Linux and Windows builds of Chromium or Firefox often depend on whether the underlying operating system has the HEVC Video Extensions installed. - AVIF vs. HEIC vs. JPEG XL in HTML
<img>andcreateImageBitmap: AVIF and WebP enjoy broad support across current Chrome, Edge, Firefox, and Safari. By contrast, HEIC decoding in browsers is largely restricted to Safari on macOS/iOS, and JPEG XL (.jxl) requires Safari 17+ or dedicated flags. - Download real files to verify playback: After checking the matrix above, download real test clips from MP4, WebM, Opus, FLAC, and Media Edge Cases to verify full frame decoding.
Frequently asked questions
- Does this browser support checker send any telemetry or fingerprinting data to a server?
- No. Every check calls standard DOM methods (canPlayType, window.VideoDecoder, window.createImageBitmap) inside your browser tab and renders the result directly into the table.
- What is the difference between 'probably' and 'maybe' in HTMLMediaElement.canPlayType?
- Per the WHATWG HTML specification, 'probably' means the browser is confident it can decode the exact container and codec profile specified, whereas 'maybe' means the container is recognized but playback cannot be guaranteed until the actual bitstream headers are inspected.
Operational transparency, verification and developer reference
For technical questions or feedback regarding SampleTestFiles, contact contact@sjwebtechwork.com. Every sample file, dataset, and diagnostic utility on this site follows strict reproducibility and privacy rules:
- Zero server-side file storage of visitor inputs: When you use our File Generator, Test Data Generator, Magic-Byte File Inspector, Browser Support Checker, or Developer Tools, all computation runs inside your browser's local JavaScript engine and Web Workers. No files or form inputs are transmitted to our servers.
- Deterministic provenance and public-domain licensing: All hosted fixtures under
/pub-files/and/mock-data/are synthesized from mathematical test patterns, sine waves, and invented records under our CC0 / Public Domain Licence and documented with exact commands on Methodology. - Cryptographic verification: Every file is accompanied by its exact byte length and 64-character SHA-256 digest, listed in our SHA-256 Checksum Directory, /checksums.txt, and /files.json.
You can re-run the table scan at any time after enabling or disabling experimental browser codec flags to compare how hardware acceleration affects media decoding support across desktop and mobile devices.