How to solve 'no video with supported format and mime type found': a durable troubleshooting guide

Why this error occurs and what it means

The message no video with supported format and mime type found appears when a browser can locate a video source but cannot decode it. This usually means either the container or the video/audio codec is not supported by the current platform and browser combination. Key reasons include mismatched codecs, misconfigured servers that send incorrect MIME types, or missing codec features like hardware-accelerated decode. Understanding the media capabilities model and server configuration helps you narrow the cause quickly.

Confirm the issue with a capabilities check

Use Media Capabilities API to check support

The Media Capabilities API lets you query whether a browser can decode a specific combination of codec, resolution, and bitrate. Example: checking decoding support for H.264 video with AAC audio in MP4:

navigator.mediaCapabilities.decoderInfo({
  type: 'file',
  video: { contentType: 'video/mp4', width: 1280, height: 720, bitrate: 2000000, framerate: 30, codec: 'avc1.42E01E' },
  audio: { contentType: 'audio/mp4', codec: 'mp4a.40.2' }
}).then(result => console.log('Can decode?', result.supported));

Use the result to confirm whether the issue is a missing codec or container.

Verify server MIME types

When the server sends the wrong Content-Type, browsers may reject the file even if it is fully playable. Common correct MIME types include:

Check the response headers and ensure the declared MIME type matches the actual container. Tools like curl or DevTools Network panel can reveal mismatches.

Validate the actual codec and container

A file extension does not guarantee correct encoding. Use ffprobe or MediaInfo to inspect the true codec and container:

• Check video codec (e.g., AVC/H.264, HEVC/H.265, AV1)
• Check audio codec (e.g., AAC, Opus, MP3)
• Confirm container (e.g., MP4, WebM, MKV)

Re-encode if necessary, targeting broadly compatible settings like H.264 video with AAC audio inside MP4 for maximum support.

Common fixes and best practices

Server and delivery fixes

• Ensure correct Content-Type headers for your video format.
• Serve a valid codec configuration box (e.g., avcC for H.264, or sequence headers for VP9/AV1) so the decoder can initialize.
• Use byte-range requests (Accept-Ranges: bytes) for progressive and streaming playback.

Source and encoding fixes

• Use broadly compatible profiles: H.264 High or Main profile, AAC audio.
• Include SPS/PPS in the stream for MP4/AVC; ensure WebM files have correct EBML and codec blocks.
• Test on multiple browsers and devices; some hardware decoders require specific levels and color formats.

Browser compatibility and codec support

Support varies by platform and configuration. Commonly supported combinations include MP4 with H.264 and AAC in Chrome, Firefox, Safari, and Edge. AV1 and HEVC are widely supported on modern platforms but may require explicit codec hints or hardware enablement. Below is a concise compatibility overview:

Troubleshooting checklist

Follow these steps when you encounter no video with supported format and mime type found:

1. Check the browser console and network tab for MIME type mismatches or 4xx errors.
2. Validate the actual codec/container with ffprobe or MediaInfo.
3. Confirm the server sends the correct Content-Type and, for H.264, includes avcC in the MP4 moov box.
4. Test using the Media Capabilities API to see if the device can decode the stream.
5. Re-encode to a broadly compatible profile if necessary (H.264 + AAC in MP4).
6. Ensure byte-range requests are allowed if using HTTP progressive delivery.
7. Consider providing multiple formats (MP4 and WebM) for cross-browser reach.

When to offer alternate formats

Providing both MP4 (H.264 + AAC) and WebM (VP9 or AV1) increases compatibility. Use feature detection or the Media Capabilities API to select the best source, and include codec hints in the source type so browsers can decide quickly. This approach reduces playback failures across diverse devices and network conditions.

Key takeaways

• no video with supported format and mime type found usually means codec or MIME type mismatch.
• Always validate the true container and codecs, and ensure the server sends accurate MIME types.
• Use the Media Capabilities API to test device support and to select appropriate sources.
• Deliver correct codec configuration boxes (avcC, sequence headers) and enable byte-range requests.
• For maximum compatibility, provide MP4 (H.264/AAC) and optionally WebM (VP9/AV1).