Recommended Free Tools
Media Err Src Not Supported is the browser’s broad HTML5 media error (MediaError code 4). It means the browser rejected the requested media resource or provider as unsuitable; it does not identify one specific fault. The fastest reliable fix is to determine whether the failure is caused by the URL or HTTP response, the file’s container and codecs, the browser session, or missing operating-system media components.
Work through the checks below in order. They separate a broken or blocked source from an encoding problem and from a Windows configuration issue, so you change only the layer that is actually failing.
As an Amazon Associate I earn from qualifying purchases.
What “Media Err Src Not Supported” means
MDN defines MediaError.code 4, commonly exposed as MEDIA_ERR_SRC_NOT_SUPPORTED, as a case where “the associated resource or media provider object … has been found to be unsuitable.” The message is therefore a category, not a diagnosis such as “your MP4 is corrupt.” The same code can appear when a URL returns an error page, when a server advertises the wrong media type, when the file contains an unsupported codec, or when the operating system lacks a decoder.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →The API has been broadly available since July 2015; MDN’s reference was last modified April 10, 2025. A browser can support the HTML5 video element and still reject one particular source because compatibility depends on the complete resource, not just the player control.
#1 Best Overall
An extension does not tell you the codecs
.mp4, .webm and .ogg describe containers. A container can hold different video and audio codecs, and browser support varies by browser, operating-system edition and hardware-acceleration path. Even the MIME type video/mp4 identifies the container level; it does not reveal which codecs are inside. Renaming a file from one extension to another cannot change those codecs.
Use the scope of the failure as evidence
| What you observe | Most likely layer | First check |
|---|---|---|
| Only one browser fails | Browser version, extension, setting or browser-specific codec support | Repeat in a private window, then test a current second browser |
| Every browser fails on the same page | URL, server response, encoding, network policy or operating system | Inspect the request and open the media URL directly |
| The request is 4xx/5xx, redirects to sign-in, or returns HTML | Availability or authorization | Fix the URL, permissions, redirect or hotlink rule |
| The request succeeds but the MIME type is generic or wrong | Server metadata | Configure the server to send the media’s actual type |
| The response is valid but the codec is unsupported | Encoding compatibility | Transcode and publish a browser-compatible version |
| Several browsers fail only on Windows N or KN | Missing Windows media components | Install the matching Media Feature Pack |
1. Reload and test the actual media URL
Start with the least invasive check: reload the page once, then locate the URL used by the video. In the page source, the HTML, or developer tools, look for the src attribute and each <source> element. Open the media URL in a new tab. A direct request that downloads an HTML error page, asks you to log in, or returns “not found” proves that the player is not receiving a usable media file.
Inspect the request in developer tools
- Open the browser’s developer tools and select the Network panel.
- Reload the page with the panel open. Filter by “media” if the browser offers that filter, or search for the filename.
- Check the request’s status. A successful media response normally has a 2xx status. Investigate 301/302 chains, 401 or 403 authorization failures, and 404 or 5xx errors before changing codecs.
- Open the response headers. Confirm that
Content-Typematches the file, such asvideo/mp4,video/webmoraudio/mpeg, rather thantext/htmlor an unexplained generic type. - Preview or download the response and verify that its body is actually media. A server can return a page saying “access denied” while keeping an
.mp4suffix in the URL. - Look for failed redirects, authentication requirements, referrer or hotlink protection, proxy intervention and CORS errors. Resolve those at the server or network layer; transcoding cannot repair a blocked request.
If the URL works only while you are signed in, the player must send the required credentials and the server must authorize that request. If a content-delivery or hotlink rule rejects the page’s referrer, permit the legitimate playback origin or use a URL intended for embedding.
2. Compare browsers and use a clean session
Try the same page in a current second browser. Then open a private or incognito window, where extensions are normally disabled or isolated, and test again. This comparison tells you whether the source is broadly unusable or whether one browser profile is interfering.
If only one browser fails
- Update that browser to its current release, then restart it.
- Repeat in a private window. If playback works there, disable extensions one at a time in the normal profile; privacy filters, download managers and media-altering extensions can block requests or replace response headers.
- Review the browser’s site permissions and hardware-acceleration setting. Test the opposite acceleration state once, because a graphics-driver path can affect decoding even when the file is valid.
- Clear the site’s cached data only after recording the request details. Clearing everything can remove useful login and diagnostic information without fixing a server-side problem.
If every browser fails
Prioritize the network response, container and codec, firewall or proxy rules, and Windows media components. Reinstalling a browser is unlikely to help when all browsers receive the same unsuitable resource.
3. Verify the container, video codec, audio codec and MIME type
Do not infer compatibility from the filename. Inspect the file with a media-information utility and record the container, video codec, pixel format, frame rate and audio codec. A command-line inspector such as ffprobe can expose stream details; the important result is the actual codec names, not the extension.
ffprobe -v error -show_entries stream=codec_type,codec_name,pix_fmt -of default=noprint_wrappers=1 input.mp4Compare those details with the browsers and devices your audience must support. A commonly deployable baseline is an MP4 container with H.264 video and AAC audio, but you should verify the target browser matrix rather than treating any combination as universal. WebM with VP8 or VP9 video and Vorbis or Opus audio is another common browser format. Older or unusual codecs inside those containers can still produce code 4.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Match the server’s MIME metadata
| Resource | Typical MIME type | What to verify |
|---|---|---|
| MP4 video | video/mp4 |
The response is the MP4 file and the codecs are supported |
| WebM video | video/webm |
The response is WebM, not an HTML error document |
| Ogg media | video/ogg or audio/ogg |
The container and streams match the declared type |
| MP3 audio | audio/mpeg |
The server does not fall back to application/octet-stream |
The MIME value must describe what is returned, not what the URL happens to be called. If your web server sends a generic binary type, configure its media mappings and test the response again. A correct MIME type cannot make an unsupported codec playable, but an incorrect type can prevent a supported file from being selected.
4. Transcode an incompatible source
Convert the file only after the request is available and you have confirmed that the codecs or container are outside your target browsers’ support. Produce a new file, upload it under a new name, set the matching MIME type, and update the page to point to it. Keep the original until the replacement has been verified.
ffmpeg -i input-video.ext -c:v libx264 -pix_fmt yuv420p -c:a aac -movflags +faststart output-video.mp4This example creates an MP4 using H.264 video, AAC audio and a fast-start layout that places metadata near the beginning for progressive playback. Confirm that the encoder is available in your installation and that your licensing and distribution requirements permit the chosen codecs. Inspect the output again, then test it in the browsers and operating systems that matter.
Conversion is not a cure for a 404, 403, login redirect, CORS rejection, broken URL or firewall block. Solve availability first; otherwise you will simply have a compatible file that the browser cannot fetch.
5. Check Windows N and KN editions
Windows editions designated N and KN omit Windows Media Player and related decoding technologies. Mozilla says these components are needed to decode and play videos and music properly. If the same media fails in multiple browsers on one of these editions, install Microsoft’s matching Media Feature Pack.
Best Value
Windows 11
- Open Settings > Apps > Optional features.
- Select View features.
- Find and select Media Feature Pack, choose Next, and install it.
- Restart Windows, then test the video again in a current browser.
Windows 10 version 1903 and later
- Open Settings > Apps > Apps & Features.
- Choose Optional features, then Add a feature.
- Select Media Feature Pack and install it.
- Restart and retest the original page.
Choose the pack that matches the installed Windows release. Mozilla notes that upgrading Windows can require installing the newer matching pack again. A Mozilla Support forum thread dated February 17, 2021 documents this exact error in a Windows 10 case; the selected solution attributed it to the missing Media Feature Pack, and the question owner reported that the issue was fixed.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.6. Check the page’s HTML and source selection
If you control the page, inspect the markup as well as the file. A minimal, valid source list looks like this:
<video controls>
<source src="/media/video.mp4" type="video/mp4">
<source src="/media/video.webm" type="video/webm">
Your browser does not support HTML5 video.
</video>- Make sure every URL is correct, reachable and free of accidental whitespace or URL-encoding errors.
- Set the
typeattribute to the resource’s real MIME type. Do not label WebM as MP4 or use a guessed codec string. - Place the most broadly supported source first, while retaining a properly encoded alternative when your audience needs one.
- Check that the server permits byte-range requests when your delivery setup relies on seeking or progressive playback.
- Use the browser console and the network panel together. A JavaScript error, failed authentication request or service-worker response can change which source the player receives.
When script assigns video.src, log the final URL rather than assuming it is the value in a configuration file. A stale service-worker cache can continue serving an old or incomplete asset; update or unregister the worker during diagnosis and then retest in a clean session.
7. Work through network and security blockers
Corporate proxies, VPNs, firewalls and security gateways can replace media responses, block large files or deny a cross-origin request. Test from a different network only as a diagnostic comparison and follow your organization’s policy. If playback works elsewhere, ask the network administrator to allow the media host and the required request method rather than weakening security controls globally.
For cross-origin playback, configure the media server to send an appropriate CORS policy for the site that embeds it. Also check referrer restrictions, signed URL expiry and clock differences that can make a valid link appear unauthorized. A response that expires between page load and playback can produce the same code 4 as an actually unsupported file.
8. Diagnose by symptom before repeating fixes
| Symptom | Interpretation | Next action |
|---|---|---|
| Direct URL shows a sign-in page | The player is receiving HTML, not media | Provide an authorized playback URL and confirm credentials are sent |
| Direct URL returns 404 or 403 | The resource is missing or access is denied | Correct the path, permissions, expiry or hotlink policy |
Network status is 200 but Content-Type is wrong |
Metadata prevents reliable media selection | Fix the server mapping and retest headers |
| Response is valid and all browsers fail | Encoding, platform component or network interception is likely | Inspect codecs, install the N/KN pack if applicable, and compare networks |
| Only one browser profile fails | Extension, cache or browser setting | Use private mode, disable extensions and update the browser |
| Audio plays but video does not | The video stream’s codec or pixel format is unsupported | Transcode the video stream while retaining compatible audio |
Common mistakes that waste time
- Renaming the extension: this changes the label, not the container or codecs.
- Converting before checking the response: a new file cannot fix authorization, redirects or a 404.
- Trusting a 200 status alone: a 200 response can contain an HTML login or error page.
- Installing random codec packs: use the operating-system component required by your edition, particularly the official Media Feature Pack for N and KN.
- Changing many settings at once: compare browsers and inspect the request first so you know which change solved the problem.
- Assuming MP4 is universal: verify both streams and the target browser/device combination.
Final verification checklist
- The media URL opens or downloads the intended media resource, not HTML.
- The final request has the expected status, redirect chain and authorization.
- The response’s
Content-Typematches the container. - The file’s actual video and audio codecs are supported by the browsers you target.
- The page’s
src,<source>andtypevalues match the published files. - A private window and a second current browser both produce the expected playback.
- Windows N or KN systems have the matching Media Feature Pack installed and have been restarted.
- Network, CORS, referrer, proxy and firewall rules allow the request.
As an optional shortcut after the manual checks, Outbyte PC Repair can address more than 100 common Windows issues, adjust settings that load CPU, RAM or disk, clean temporary and cache files, check selected Windows settings and missing updates, and record app crashes. It runs on Windows 11, 10, 8 and 7, offers a category-based free trial of at least two days, and then requires a subscription. It complements an antivirus rather than replacing one; results vary, and no tool repairs every crash.
Bottom line
Code 4 is resolved by fixing the layer that failed: make the URL return the real media, publish accurate MIME metadata, use codecs your audience’s browsers support, and install the Media Feature Pack on Windows N or KN. The network response and codec inspection tell you which remedy applies; changing unrelated browser settings does not.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
