Firefox not playing videos is one of those problems where the fix is usually fast — but only if you pick the right fix first. Videos failing to load at all, videos loading but showing a black screen, and videos playing but producing no audio are three different problems with different causes. The troubleshoot-one-and-try is much faster than working through every possible fix sequentially. For the bigger picture, our Google Chrome Errors pulls everything together.
The 60-second test that reveals the most: open a Private Window in Firefox (Ctrl + Shift + P) and try the same video. Private windows disable all extensions by default. If the video plays in a Private window but not normally, an extension is blocking it — this is the most common cause of video failures in Firefox. If it also fails in a Private window, the problem is deeper: codec support, Firefox settings, or the site itself.
Fix 1: Extensions Blocking Video
Ad blockers, privacy extensions, and script blockers are the most common cause of videos not playing — they block JavaScript, tracking scripts, or network requests that video players depend on. An ad blocker in strict mode can block the video CDN (Content Delivery Network) request that delivers the actual video file, while still letting the page load normally.
If Private window confirms an extension is involved: open Firefox menu → Add-ons and Themes → Extensions → toggle every extension off → reload the page with the video. If it plays with all extensions disabled, re-enable them one at a time — when the video stops playing after enabling a specific extension, that’s your culprit.
For ad blockers specifically: the fix is usually adding the site to the ad blocker’s allowlist (usually a button in the extension popup when on the affected page) rather than permanently disabling the extension. This lets the video load while keeping the blocker active everywhere else.
Fix 2: Hardware Acceleration — Black Screen With Audio
A video that plays audio but shows a black screen, or a player that loads but the video never appears, almost always indicates a hardware acceleration problem. Firefox uses the GPU to render video frames, and when the GPU driver has a bug in a specific decoding path Firefox uses, the video decode fails but the audio plays normally (because audio decoding is separate).
This pattern is especially common after GPU driver updates and after major Firefox updates that change how video is decoded.
Disable hardware acceleration: Firefox menu → Settings → General → scroll to Performance → uncheck “Use recommended performance settings” → uncheck “Use hardware acceleration when available” → close and reopen Firefox. Test the video. If the black screen is gone, the GPU driver is the underlying issue.
After confirming hardware acceleration is the cause, update the GPU driver from the manufacturer’s website (NVIDIA/AMD/Intel). After the driver update, re-enable hardware acceleration — the updated driver usually resolves the specific rendering bug.
Fix 3: DRM Content — Netflix, Disney+, Streaming Services
Premium streaming services use DRM (Digital Rights Management) to protect their content. Firefox uses Widevine Content Decryption Module (CDM) for DRM — when this isn’t enabled or installed, DRM-protected video fails to play with a “Playback error” message rather than just not loading.
Enable DRM support: Firefox menu → Settings → General → scroll to “Digital Rights Management (DRM) Content” → ensure “Play DRM-controlled content” is checked. If it’s already checked but streaming services still fail, the Widevine CDM may need to update.
Force-update Widevine: type about:addons in the Firefox address bar → Plugins → find “Widevine Content Decryption Module” → click the gear icon → Check for Updates. After the update, restart Firefox and test the streaming service again.
Note: DRM content genuinely doesn’t work in Private Browsing on many streaming services. If your Private window test showed the video failing on Netflix or Disney+, that’s expected behavior rather than a Firefox problem — DRM requires persistent storage that Private mode deliberately limits.
Fix 4: Enhanced Tracking Protection Blocking Video Players
Firefox’s Enhanced Tracking Protection in Strict mode blocks more than just ads — it also blocks cross-origin tracking scripts that some video players use for analytics and DRM authentication. When this blocking intercepts something the video player needs, the player loads but refuses to start video playback.
Test this without disabling the whole protection system: click the shield icon in the Firefox address bar on the failing video page → click the toggle “Turn off for this site.” If the video plays after doing this, Enhanced Tracking Protection was blocking a resource the player needs. Rather than leaving protection off for that site permanently, switch Firefox’s overall protection level from Strict to Standard: Firefox Settings → Privacy and Security → Enhanced Tracking Protection → select Standard. Standard mode is still effective at blocking actual tracking while being less aggressive about blocking resources that video players legitimately need.
Fix 5: Autoplay Policy
Firefox has an autoplay blocking policy that prevents videos from automatically playing with sound, and occasionally this policy prevents videos from playing at all on sites that depend on autoplay to initialise their player. The player loads, you click play, and nothing happens — Firefox is blocking the play because its autoplay detection classifies the attempt as automatic rather than user-initiated.
Check for blocked autoplay: look for a notification in the address bar or near the video player indicating blocked autoplay. Allow it for the specific site. For a permanent fix for specific sites: click the padlock icon → Connection secure → More information → Permissions tab → Autoplay → Allow Audio and Video.
Adjust the global autoplay setting: Firefox Settings → Privacy and Security → Permissions → Block websites from automatically playing sounds → Exceptions → add sites where autoplay should be permitted. The policy is site-specific, so you can allow autoplay on video platforms while keeping it blocked on news sites with autoplaying ads.
Fix 6: Clear Cache and Cookies for the Specific Site
Cached broken video player resources or corrupted cookies cause specific sites to fail repeatedly while the same videos work fine on other sites. Clearing cache for the whole browser is effective but inconvenient. Clearing for a specific site only is faster:
Firefox address bar padlock icon → Connection secure → Clear cookies and site data → Clear. This removes only that site’s cached data. Reload the page and test. If it works after clearing, the cached data was broken. Going forward, that site’s cache rebuilds cleanly.
Fix 7: Firefox Refresh
When videos fail across multiple sites and the Private window test shows the problem persists without extensions — meaning hardware acceleration, DRM, and cache are all ruled out — the Firefox profile has accumulated enough corruption to warrant a reset. The Firefox Refresh function rebuilds the profile while keeping bookmarks, saved passwords, and browsing history:
Firefox menu → Help → More Troubleshooting Information → click “Refresh Firefox” on the right side → confirm. Firefox restarts with a clean configuration. Extensions are removed (reinstall the ones you need) and custom settings are reset. After the refresh, test video on the sites that were failing — a clean profile resolves the configuration corruption that caused the failures.
Media Source Extensions (MSE) Setting
Modern video streaming relies on Media Source Extensions — a browser API that allows adaptive bitrate streaming (where video quality adjusts based on connection speed). If MSE is disabled in Firefox, most video sites either fail to load video or load only at a fixed low quality.
Check: type about:config in the Firefox address bar → accept the warning → search for media.mediasource.enabled. The value should be “true.” If it shows “false” — set it back to true by clicking the toggle. This setting rarely changes on its own, but some older about:config guides instructed users to disable it for unrelated reasons, leaving it incorrectly set.
Our guide on videos not playing in Chrome covers the equivalent Chrome-side fixes — DRM configuration, hardware acceleration, and extension interference work similarly in both browsers. For Firefox audio specifically when video loads but produces no sound, our no sound on Windows 11 covers the Windows audio device selection issue that affects all browsers. Mozilla’s Firefox media documentation covers codec support by platform and the specific H.264/H.265 licensing considerations that affect video format support depending on the Windows version.
H.264 and H.265 Codec Availability
Firefox on Windows uses the operating system’s codec libraries for some video formats. H.264 (the most common video format used by streaming sites) is licensed and available on Windows through the Media Feature Pack. H.265/HEVC is supported on Windows 11 but may require the “HEVC Video Extensions” from the Microsoft Store on some Windows installations.
If videos fail on specific sites while working on others, and the failing sites use a specific video format, codec availability may be the issue. Check: open about:support in Firefox → Media section → Hardware Video Decoding shows which codecs Firefox can use with hardware acceleration. If H.264 shows “Unsupported” or “Not available,” the Windows Media Feature Pack may need to be installed. On LTSC or Server versions of Windows where the Media Feature Pack is not included by default, this is a real cause of video failures that affects all browsers, not just Firefox.
WebRTC and Video Conferencing in Firefox
Firefox’s WebRTC implementation handles browser-based video calls (Google Meet, Jitsi, browser-based Zoom). When WebRTC video fails in Firefox, the cause is often different from standard video playback failures: camera permission blocking, WebRTC IP leakage prevention settings, or Firefox’s media.peerconnection settings being disabled for privacy reasons.
Check WebRTC is enabled: about:config → search for media.peerconnection.enabled → should be “true.” If disabled (perhaps by a privacy-focused user.js configuration or by a browser hardening tool), re-enable it. Also check Firefox Settings → Privacy and Security → ensure the camera permission is allowed for the conferencing site. Firefox has per-site camera permissions accessed via the padlock icon, and a previously denied camera permission for a Meet or Jitsi site produces video call failures that look like a Firefox problem but are actually a permission issue.
Firefox Container Tabs and Video Site Isolation
Firefox Multi-Account Containers (a Mozilla extension) isolates sites into separate containers with separate cookies and cache. This is great for privacy but occasionally breaks video playback on sites that require cross-origin resource sharing — the video file is served from a different domain than the player page, and the container isolation prevents the cross-origin request from completing.
If video fails on a site you’ve assigned to a container, try opening the video in a regular (non-container) tab. If it plays there, the container is isolating a resource the video player needs. You can configure per-site container exceptions in the Multi-Account Containers extension settings, or adjust the container’s cross-site cookie permissions to allow the video CDN domains that the player depends on.
Firefox’s built-in video diagnostic: about:media-internals
When you cannot tell what is failing, Firefox has a diagnostic page most people never open. Go to about:media-internals while a video is playing or trying to, and click the active entry to see the codec in use, whether decoding is hardware or software, the buffering state, and any errors. A “decode error” or “media not supported” points to a codec or container problem; the right codec with mismatched audio and video streams points to container parsing; and a pipeline stuck on “buffering” points at the network or CDN rather than Firefox itself.
Antivirus HTTPS inspection breaking the stream
Security suites that scan HTTPS traffic do it by intercepting the connection and presenting their own certificate. Because Firefox keeps its own certificate store rather than using Windows’, it can reject that antivirus certificate outright — the player loads, but the stream request fails with an SSL error the player reports as missing content. If about:media-internals shows network errors on the failing stream, try disabling HTTPS or SSL scanning in your security software, or adding Firefox as an exception, and reload.
DNS-over-HTTPS sending you to the wrong CDN
Streaming sites serve video from CDN edge servers, and Firefox’s DNS-over-HTTPS (DoH) resolves those addresses through Cloudflare or NextDNS rather than your system resolver. When the DoH resolver hands back different CDN servers than your ISP would — sometimes geographically distant ones — you get buffering or failed loads. To test, go to Settings → Privacy and Security → DNS over HTTPS, switch from Increased Protection to Default Protection so it uses system DNS, and reload the failing site.
Video Playback on Slow or Unstable Connections
Some video loading failures are actually buffering failures disguised as errors. When the connection is too slow to buffer video as fast as the player tries to play it, some video players show an error rather than the buffering spinner. This is especially common on sites that don’t handle slow connections gracefully.
Test: run a speed test and check your download speed. For HD (1080p) video, you need at least 5–10 Mbps; for 4K, 25 Mbps or more. If your connection is near these limits during peak hours, try selecting a lower video quality option (usually available in the video player’s settings gear icon). Also try switching DNS servers — slow DNS resolution adds latency to every CDN connection and can cause video loading to time out before the player establishes a stream. Switching to 1.1.1.1 (Cloudflare) reduces DNS lookup time and occasionally resolves video loading failures on sites with many CDN domains.
Comparing Firefox and Chrome for Specific Sites
If videos play correctly in Chrome but not in Firefox on specific sites, the cause is usually one of three things: the site is not optimised for Firefox, the site uses a specific video format that Firefox handles differently from Chrome, or a Firefox-specific security feature is blocking something the site depends on. Testing in Chrome is a useful diagnostic — it isolates whether the issue is Firefox-specific or general.
Site-specific Firefox failures that don’t occur in Chrome are worth checking in Firefox’s Developer Tools (F12 → Console) — error messages there often name the specific resource that failed to load or the specific JavaScript error that prevented the video player from initialising. These error messages are the most direct path to understanding what Firefox is doing differently from Chrome on a given page, and they often point to a specific extension, a privacy setting, or an Enhanced Tracking Protection rule as the cause. See also Firefox Video Not Playing for a related case.
