Fix Videos Not Playing in Chrome

Videos not playing in Chrome — black screen with audio, infinite loading spinner, or “this video is not available” errors on sites that work elsewhere — has one cause that accounts for the majority of cases: Chrome’s hardware acceleration is conflicting with your graphics driver. Chrome enables hardware acceleration by default to offload video decoding to the GPU. When this works, video is smooth. When the GPU driver has a bug or the GPU is older, it produces exactly the symptoms above. This fits into the wider topic we cover in our Google Chrome Errors.

The 30-second test: Settings → System → toggle off “Use hardware acceleration when available” → restart Chrome → try the video again. If it plays now, hardware acceleration was the cause. Leave it off, or update your GPU driver from the manufacturer’s site (Intel, NVIDIA, or AMD) and re-enable hardware acceleration to test if the update fixed it.

If turning off hardware acceleration doesn’t help, the next quickest check is whether videos fail on every site or only specific ones. Single-site failures are codec or DRM issues; all-site failures point to extension conflict or deeper Chrome corruption. The full diagnostic below covers each path.

Extensions First: They Block Video More Than Anything

Ad blockers, script blockers, privacy tools, and VPN extensions are collectively responsible for the majority of video playback failures in Chrome. They block JavaScript, tracking scripts, or network requests that video players depend on — sometimes intentionally, sometimes as collateral damage from overly aggressive filter rules.

The confirmation is fast: if Incognito loads the video, you have an extension problem. Go to chrome://extensions and toggle everything off. Reload the video in your normal (non-Incognito) window. When it plays, re-enable extensions one at a time. When the video breaks again, the last extension you enabled is blocking playback. For ad blockers, you often don’t need to disable them entirely — you can add the specific site to the allowlist (usually a button in the extension popup on the problem page).

Hardware Acceleration: Black Screen, Frozen Player, Won’t Start

If the video player loads but shows a black screen, or if the video freezes immediately after starting while audio continues — that’s hardware acceleration. Chrome uses the GPU for video decoding, and with certain GPU driver versions or integrated graphics configurations, the decoding silently fails and you get a black frame where the video should be.

This is particularly common after Windows or GPU driver updates. One day video works fine, the next it’s a black screen.

1. Three-dot menu → Settings → System
2. Toggle off Use hardware acceleration when available
3. Click Relaunch
4. Test the video

If it works with hardware acceleration off, update your GPU driver before turning it back on. For NVIDIA, use GeForce Experience or download from nvidia.com. For Intel integrated graphics, download from intel.com/download-center. AMD users: use the AMD Adrenalin software or amd.com/en/support. After the driver update, re-enable hardware acceleration and test again — in most cases the updated driver resolves the GPU video decoding bug.

Clear the Cache

Stale or corrupted cached data causes video players to behave oddly — attempting to load a cached version of the page that no longer matches the live site’s player code. This usually causes specific sites to fail while other sites work fine, or causes video to fail intermittently on the same site.

Ctrl + Shift + Delete → All time → tick Cached images and files and Cookies and other site data → Clear data → restart Chrome. If that fixes it: done. It’s quick, it’s harmless, it should be an early step when specific sites are having playback issues.

JavaScript — Easily Overlooked

Modern video players are entirely JavaScript applications. The HTML page just provides a container; JavaScript fetches the video stream, manages the player controls, and handles buffering. If JavaScript is disabled in Chrome or blocked for a specific site, the video player simply doesn’t load — you’ll see a blank space where the player should be or the spinning animation will run forever.

Check: Settings → Privacy and security → Site settings → JavaScript → confirm “Sites can use JavaScript” is selected. If a specific site is listed under “Not allowed to use JavaScript,” remove it from that list. Also check whether any extension you have specifically blocks JavaScript — script blockers like ScriptSafe or NoScript work by blocking JavaScript and need a site-specific allowance for video sites.

Try a Different Chrome Profile

This is worth trying when videos fail across multiple sites and the simpler fixes haven’t helped. A corrupted Chrome profile can affect video playback by breaking saved site permissions, corrupting codec preferences, or causing resource loading failures. Creating a new profile takes 30 seconds and provides a definitive test.

Click the profile icon in the top-right corner of Chrome → Add → Continue without an account (or sign in). Navigate to the same video site that was failing. If it plays immediately in the new profile, your existing profile has the issue — not Chrome itself. You can either continue using the new profile (and sign into your Google account to restore bookmarks and passwords) or troubleshoot the original profile by clearing cookies, resetting settings, or renaming the Default folder.

Specific Situations

YouTube specifically not loading: YouTube has gone fully JavaScript-first — it does essentially nothing without JavaScript working correctly. If only YouTube fails while other video sites work, try signing out of your Google account and clearing YouTube’s cookies specifically (click the padlock icon → Cookies and site data → manage → delete YouTube entries) before clearing everything else.

Videos play on some sites but not others: Usually an extension or a JavaScript block specific to that site’s domain. The site-specific extension allowlist and site-specific JavaScript permissions are the right places to look.

Video plays but no audio: This is a different problem from video not loading — it’s usually Chrome’s site-specific audio permission. Click the padlock icon in the address bar → check whether “Sound” is set to “Mute.” Also check Windows’ Volume Mixer (right-click the speaker icon in the taskbar → Open Volume Mixer) to confirm Chrome’s volume isn’t set to zero there.

Video stutters or buffers constantly: This is typically a network speed or DNS issue rather than a Chrome settings problem. Run a speed test — if the connection speed is adequate (10Mbps+ for HD video), try switching DNS to 1.1.1.1 (Settings → Network and internet → your connection → DNS server assignment → Manual → 1.1.1.1). DNS resolution delays affect video CDN selection and can cause buffering even on fast connections.

Our guide on Chrome not loading pages covers the broader rendering failures that sometimes accompany video playback issues. If Chrome is consistently slow on all sites including video, the Chrome running slow guide addresses the performance root causes. For codec-specific video format support issues, Google’s Chrome documentation maintains a list of supported video formats and codec requirements per Chrome version.

DRM (Digital Rights Management) errors produce a specific type of video failure that’s worth distinguishing from the generic “video not playing” scenario. Netflix, Disney+, Amazon Prime Video, and other premium streaming services use Widevine DRM — a content protection system built into Chrome. When Widevine fails to initialise, you see an error code like F7701-1003 (Netflix) or a message about content protection rather than a black screen or buffer spinner. Widevine is updated separately from Chrome but usually stays current automatically. If you see DRM-specific errors, check chrome://components and look for “Widevine Content Decryption Module” — if it shows an outdated version, click Check for update. Also ensure hardware acceleration is enabled (Widevine requires GPU-based secure decryption in some configurations), and that you’re not in Incognito mode (DRM generally doesn’t work in Incognito). Signing out of Chrome and the streaming service, clearing the site’s cookies, and signing back in resolves most DRM initialization failures without any settings changes.

Video codec support varies between Chrome builds and Windows configurations. Chrome supports H.264, VP8, VP9, AV1, and WebM natively for most content. However, some enterprise or stripped-down Windows installations are missing specific codec packages that Chrome can’t supply independently — this is more common on Windows Server installations and LTSB/LTSC versions of Windows 10/11. If videos consistently fail on specific sites that use particular video formats, checking Chrome’s media internals at chrome://media-internals during a playback attempt shows the codec being requested and whether it’s being decoded successfully, which pinpoints codec issues without guesswork. The platform codec column shows whether Chrome is using software or hardware decoding, and the error column shows any codec-level failures.

VPN extensions and proxies affect video in ways that differ from how they affect normal browsing. Video CDNs (Content Delivery Networks) serve video files from the server geographically closest to the viewer. When a VPN routes traffic through a different country, the CDN serves content from a server far from the VPN exit node, which can cause high latency that manifests as buffering or failed video loads. Some streaming services also geo-block content and will serve an error when accessed through a VPN exit node in a different country. If videos started failing after installing or activating a VPN extension, disable it for video streaming or switch to a VPN server in the same region. Native VPN applications (as opposed to browser extensions) generally interfere less with video CDN selection than browser-extension VPNs because they operate at the OS network level rather than intercepting browser traffic selectively.

Chrome’s HTTPS-First Mode (Settings → Privacy and security → Security → Always use secure connections) occasionally breaks video on legacy sites that serve video files over HTTP rather than HTTPS. When Chrome upgrades an HTTP video URL to HTTPS and the video server doesn’t support HTTPS, the video request fails silently — you see a player but no video. If you’re experiencing video failures specifically on older or less well-maintained sites, temporarily disabling HTTPS-First Mode and testing confirms whether mixed-content blocking is the cause. The longer-term fix is for the site to serve video over HTTPS, but for sites you can’t control and need to use immediately, disabling the HTTPS upgrade for that specific site via the padlock icon → Site settings is the practical workaround.

Chrome’s site permissions for cameras and microphones are occasionally misconfigured in ways that affect video playback on conferencing platforms. Sites like Google Meet, Zoom web, and Microsoft Teams Web Client need explicit browser-level permission to access media devices. If these permissions are set to “Ask” or “Block” in Chrome’s site settings, joining a video call or starting video playback on these platforms may fail with confusing error messages or a blank video area. Check Settings → Privacy and security → Site settings → Camera and Microphone, and review whether the problematic video site is listed under blocked permissions. Granting explicit permission for the site and refreshing the page typically resolves media device access failures on conferencing platforms without any other changes needed.

Background tab throttling is a Chrome performance feature that can interfere with video playback in unexpected ways. Chrome reduces CPU and resource allocation for tabs that have been in the background for a while — a sensible optimization that reduces battery drain and system load. But if a tab is playing video while in the background (streaming music video, leaving a tutorial running, or playing a live stream while working in another tab), the throttling may reduce the resource allocation enough to cause buffering or playback interruptions. Chrome’s throttling behaviour changed significantly in versions 86 and above, becoming more aggressive. If background video playback is important to your workflow, you can use the Performance settings (Settings → Performance → Performance) to adjust how Chrome handles inactive tabs, or use a browser flag at chrome://flags/#intensive-wake-up-throttling to adjust the throttling behaviour. Tab groups can also help by keeping related tabs active rather than treating them as background tabs.

For developers or users encountering video failures on locally hosted web applications, CORS (Cross-Origin Resource Sharing) policy violations are a common cause of video not loading. When a video file is hosted on a different domain or localhost port from the page requesting it, the browser enforces CORS restrictions that can prevent the video from loading. Chrome’s DevTools console (F12 → Console) shows CORS errors with a specific “blocked by CORS policy” message — this is different from the standard user-facing video failure and requires a server-side configuration change (adding appropriate CORS headers to the video server’s responses) rather than any Chrome setting adjustment. This is worth mentioning because CORS failures can look identical to hardware acceleration failures from the user’s perspective — a video player that loads but shows a blank area — and the usual hardware acceleration and extension fixes won’t help.

Chrome’s Safe Browsing feature occasionally flags video streaming URLs from less well-known sites and blocks the video resource request, resulting in a failed video load. This is more common on entertainment aggregator sites, unofficial streaming sites, and sites with embedded videos from multiple third-party sources. If Chrome shows a “dangerous site” warning or the video URL is blocked without a clear error, Safe Browsing protection may be blocking the video CDN. Check Settings → Privacy and security → Security and consider whether Enhanced Protection mode is overly aggressive for your browsing patterns. Standard Protection is adequate for most users and is less likely to produce false positives on legitimate video content from non-mainstream CDNs.