Understanding media codecs in a browser test

A video file can open in one browser and fail in another, even on the same computer. The filename may look familiar, but the browser still needs to understand the audio and video encoded inside it.

The Browser Info tool checks browser capabilities, including media codecs. Use it to see what your current browser reports, then use the result to narrow down why a particular file or website will not play.

Check codec support in your browser

1. Open Browser Info in the browser where playback fails.
2. Find the media codec and supported feature information. Note the browser name, version, and engine shown in the report, since support can differ between browsers and versions.
3. Look for the codec used by the media you need to play. A file extension such as .mp4 names a container, not necessarily the codecs inside it.
4. If the result is unclear, check the same report in another browser on the same device. This helps separate a browser limitation from a problem with the computer or file.

Browser Info reports browser capabilities. It does not inspect a specific video file or prove that a streaming service will play it. Treat its results as a useful compatibility clue, then test the actual file or page that is causing trouble.

What the result means

The codec is reported as supported

The browser reports that it can handle that codec in at least some circumstances. This does not guarantee every file using it will play. A codec can have different profiles, levels, bit depths, or other settings, and a particular file may use one the browser or device cannot decode.

Check whether the website or player gives an error, and try another known compatible file. If other files play, the problem may be that file's encoding rather than basic browser support.

The codec is reported as unsupported

The browser does not report support for that codec through the features being checked. A browser update or a different browser may support it, but availability can also depend on the operating system and device. If the file is important, ask the sender for a version encoded with a more widely supported option.

The result is missing or uncertain

A blank or unclear entry is not proof that the codec cannot work. The browser may not expose a definitive answer, or support may depend on the media profile or playback method. Try the actual media in another current browser, and compare the results before changing system settings.

Audio works, but video does not, or the reverse

Audio and video can use different codecs inside the same file. For example, an MP4 container may hold H.264 video and AAC audio, but another MP4 could use a different video codec. One track can be compatible while the other is not. If you can hear sound but see no picture, or see a picture without sound, check both tracks rather than relying on the file extension alone.

What to check when playback fails

1. Check the exact file or stream. Confirm that the file finished downloading and try playing another file from the same source. A damaged or incomplete file can fail even when its codecs are supported.
2. Update the browser. Install the current stable version and reopen the page. On Windows 11, check Settings › Windows Update for system updates too. On macOS, check System Settings › General › Software Update. Updates can add browser features or system media support.
3. Try another browser on the same device. If the same file plays there, the difference points toward browser support or settings. If it fails in both, the file, operating system, or playback service may be involved.
4. Check the website's playback requirements. Some services need more than codec support, such as a supported browser version, a protected-content feature, or an account with permission to view the media. A codec report does not test those service requirements.
5. Ask for a compatible export. For a video file, request a commonly supported format and encoding, such as MP4 with H.264 video and AAC audio. The container alone does not guarantee compatibility, so include both codec names when asking.

If this started after a browser update, compare the current browser report with another browser and follow these checks for codec support after a browser update. A changed report can help identify a compatibility change, but it does not by itself prove the update caused the playback failure.

Codec, container, and file format are different

A codec compresses and decompresses a media track. H.264 and VP9 are examples for video; AAC and Opus are examples for audio. The codec affects how the media is encoded and what a browser or device must support to decode it.

A container packages tracks and related information together. MP4, WebM, and MOV are container formats. One container can hold different codec combinations, so two files ending in .mp4 may not play the same way. A file extension is a convenient label, but it is not a full compatibility report.

Playback also depends on details such as the codec profile, resolution, frame rate, and device decoding support. Streaming services may add requirements such as digital rights management, which controls access to protected media. That is separate from whether the browser can decode an ordinary file using a given codec.

When you report a playback issue, note the browser and version, the codec if known, and whether the same media works in another browser. That information makes the next troubleshooting step more precise.