Blog

How to check media codec support after a browser update

Check whether your browser still reports support for video and audio codecs after an update, then separate codec limits from playback problems.

Jason TurnerHardware tests 5 min read

A video that played yesterday may show a black screen, stutter, or have no sound after your browser updates. That does not automatically mean the codec disappeared. The file, browser settings, operating system, or graphics driver can also affect playback.

Use the Browser Info tool to check what codecs and media features your browser reports. Then test the same media file again, so you can tell a reported support change from a problem with one file or website.

Check codec support after the update

  1. Open the Browser Info tool in the browser that updated. Note the browser version and engine, along with the codec and media-feature information it lists.
  2. Find the codec related to the problem. If you know the file's codec, compare that name with the tool's reported support. If you do not know it, note the file type and the specific symptom, such as no picture or no sound.
  3. Open the same media file that used to work in the updated browser. If you have a copy saved on your device, open that copy to reduce the chance that a website or network is causing the problem. Use the same file, not a different sample.
  4. If possible, open the file in another browser on the same computer and compare playback. You can also open Browser Info there to compare the reported codecs and browser engine.

A file extension such as .mp4 describes a container, which can hold different video and audio codecs. A container name alone does not tell you which codec the file uses. If you cannot identify the codec, compare what happens with the exact same file rather than guessing from its extension.

What the result means

The codec is listed and the file plays

The updated browser reports support and can play this file in your current setup. If a particular website still fails, focus on that site, its player, or the connection. A local file playing correctly does not prove every profile or version of that codec will work.

The codec is listed, but the file does not play

A reported capability is a useful clue, not a guarantee that every file using that codec will decode. The file may use a profile, resolution, or audio format your setup cannot handle, or the file may be damaged. Try another known-good file with the same codec before blaming the update.

The codec is not listed, or the report changed

The browser may no longer report support for that codec, or the update may have changed what the page can detect. Compare another browser on the same computer. If the second browser reports support and plays the file, the issue may be specific to the updated browser. If neither browser plays it, the file or operating system may be the cause.

The video plays but has no sound, or the sound plays without a picture

Video and audio use separate codecs, even when they are inside one file. A picture without sound points toward the audio stream, while sound without a picture points toward the video stream. Check the relevant audio or video codec separately if the file's details are available.

Playback stutters, but the file starts

The browser can begin decoding, but that does not confirm smooth playback at every resolution or frame rate. High-resolution video, background activity, and graphics acceleration can affect performance. Compare the same file with other demanding tabs and applications closed.

How to fix playback after the update

  1. Check whether the problem affects one file or all media. Try another file you already know plays in the same browser. If only one file fails, it may be damaged or encoded in a format your setup does not support.
  2. Reload the page and restart the browser. Close all browser windows, reopen the browser, and test again. For a streaming site, reload the page and sign in again if needed.
  3. Test without extensions. An extension that blocks scripts or changes playback can interfere with a site's player. Try a private window if extensions are disabled there, or temporarily turn off extensions one at a time, then repeat the test.
  4. Compare graphics acceleration settings. In Chrome, open Settings › System. In Edge, open Settings › System and performance. If Use graphics acceleration when available is shown, switch it and relaunch the browser to see whether playback changes. This setting can affect decoding, but turning it off is not always the better choice.
  5. Install pending system updates. On Windows 11, open Settings › Windows Update and check for updates. On macOS, open System Settings › General › Software Update. Updates can include changes to media components or graphics support used by the browser.
  6. Check the file's format before converting it. Confirm the video and audio codecs if your file details show them. If the file uses a codec your browser does not support, make a copy in a widely supported format rather than overwriting the original.

A browser update does not usually mean you need to install a random codec pack. Avoid installing software from unknown sources, especially when the browser report already shows support and only one file has a problem.

What a browser codec report can tell you

Browsers expose information about media formats and features they claim to support. That report helps you spot a missing capability or compare browsers, but it does not certify that every media file will play correctly. It also does not identify a damaged file or prove that hardware decoding is working well.

For a useful comparison, keep the computer, file, and playback conditions the same. Record the browser version and the codec information before making more changes. If the problem began with one update and persists across known-good files, check the browser's release notes or report the issue to its support team with the version and test results.