Chrome casting not working — the Cast option missing from the menu, the Cast dialog showing no devices, or the cast starting then immediately stopping — is a network and extension issue more than a Chrome problem. The fix depends on which specific symptom you’re seeing. You’ll find the complete rundown in our Google Chrome Errors.
The most important thing to check first: are your computer and the Chromecast/Google TV/smart TV on the same Wi-Fi network? This is the single most common cause of Cast not finding any devices. Separate guest networks, 5 GHz vs 2.4 GHz isolation, and network segmentation all prevent Chrome from discovering Cast-capable devices even when both appear to be on the same network.
Fix 1: Network check — same network, same band
Open the Google Home app on your phone. If your Chromecast appears there but not in Chrome’s Cast menu: the Chromecast is on a different network or isolated subnet from your computer. Check:
- Router guest network: many routers put “Guest” Wi-Fi on an isolated VLAN. The Chromecast may be on “Home” and your computer on “Home_Guest” (or vice versa)
- Band isolation: some routers isolate 2.4 GHz and 5 GHz clients from each other. If the Chromecast is on 2.4 GHz and your computer on 5 GHz with client isolation enabled: Cast discovery fails
- AP isolation: enterprise and some prosumer routers have “wireless isolation” that prevents devices from communicating directly — required for Cast’s mDNS discovery protocol
Fix: connect both the Chromecast and your computer to the same SSID, preferably the main home network rather than a guest network. Check the router’s wireless settings and disable client/AP isolation if it’s enabled.
Fix 2: Enable the Cast Media Router component
Chrome’s casting uses an internal Media Router component. Navigate to chrome://flags/#load-media-router-component-extension → enable it → Relaunch. Also check: chrome://flags/#cast-media-route-provider → enable → Relaunch. After relaunching: try the Cast option again.
Fix 3: Reset Chrome’s cast discovery
Navigate to chrome://media-router-internals/ in Chrome. This shows the current Cast discovery state, any errors, and which devices have been found. If it shows errors: click “Reset Mirroring Service” if that option appears. This restarts the Cast discovery component without restarting Chrome entirely.
Fix 4: Windows Firewall blocking Cast
Chrome’s Cast uses mDNS (multicast DNS) on port 5353 and communicates with Chromecasts over specific ports. Windows Firewall sometimes blocks these after a Windows Update or when Chrome updates its Cast component.
Windows Security → Firewall → Allow an app through firewall → confirm Google Chrome has both Private and Public checked. If it wasn’t: add it with both checked → retry casting. Also: some third-party firewalls block multicast traffic entirely — Cast won’t work with multicast blocked regardless of Chrome’s settings.
Fix 5: The Cast tab via the three-dot menu
If the Cast option disappeared from Chrome’s menu: Chrome three-dot menu → Cast. If it’s not there: right-click anywhere on the page → Cast. If neither option appears: chrome://flags → search “Cast” → look for “Enable Cast” or “Media Router” options and enable them → relaunch.
Alternatively: install the Google Cast extension from the Chrome Web Store (if you removed it previously — it was once required and later became built-in; some Chrome versions still benefit from having the extension explicitly installed).
Fix 6: Restart the Chromecast or TV
When Chrome shows Cast devices but the cast fails immediately or shows the loading screen then stops: the Chromecast itself may have a stuck state. Unplug the Chromecast for 30 seconds → plug it back in → wait 60 seconds for it to fully restart → try casting again. A Chromecast reboot also re-registers on the local network, which can fix discovery issues that appeared after a router restart or network configuration change.
Our guide on network configuration issues covers the router isolation settings that prevent Cast discovery at the network level. For Chrome flags and experimental features that affect Cast, our Chrome configuration guide covers the flags interface. Google’s Cast troubleshooting documentation covers the Cast setup process, specific router compatibility notes, and the network diagnostic tool in the Google Home app that checks whether the network is compatible with Cast devices.
Casting tabs vs casting desktops vs mirroring
Chrome supports three distinct casting modes, and they fail in different ways:
- Cast tab: sends only the current Chrome tab’s content to the TV. Best quality for web content; handles DRM-protected content on some services. Fails if the tab uses hardware acceleration that conflicts with Cast encoding
- Cast desktop: mirrors your entire screen. Uses more CPU and shows everything on screen (notifications, other windows). Useful for presentations or when tab casting doesn’t work
- Cast file: streams a local video or audio file to the Cast device. Click the Cast icon in video player controls or from the three-dot menu
If one mode fails: try a different mode. Tab casting failing while desktop casting works suggests a tab-specific encoding issue. Desktop casting failing suggests a network or firewall issue (desktop cast uses different ports).
DRM and protected content casting
Netflix, Disney+, and similar services have content protection that restricts how content can be cast. Chrome’s built-in Cast for DRM content requires:
- The streaming service’s own cast button (not Chrome’s general Cast menu) for optimal DRM casting
- Widevine DRM component in Chrome to be active (chrome://components/ → Widevine Content Decryption Module → Check for update)
If DRM content works in Chrome but casting it shows a black screen on the TV: the service’s DRM is preventing screen capture during casting. Use the in-app Cast button if available, or use the Chromecast’s own Netflix/Disney+ apps directly rather than casting from Chrome.
Cast quality — resolution and bandwidth
Chrome cast quality adapts based on available network bandwidth. On slower Wi-Fi connections: cast quality drops to avoid buffering. For reliable HD casting:
- The Chromecast and computer should both have strong Wi-Fi signal — check signal strength in the Google Home app
- During casting: minimise other network activity (downloads, video calls, large uploads)
- Wired Ethernet for the Chromecast (via a USB-C hub that includes Ethernet) provides the most stable connection for extended casting sessions
Casting fails mid-session
Cast that starts successfully then drops after 10-30 minutes: network stability is the issue. The Cast connection uses both the Wi-Fi network and occasional mDNS re-discovery. If the Wi-Fi channel changes, the router reassigns IPs, or packet loss increases: the cast session drops.
For desktop casting that keeps dropping: try switching to casting specific tabs instead — tab casting reconnects more gracefully than desktop mirroring when the connection briefly interrupts. Also: DHCP lease renewal during a cast session sometimes causes brief drops; assigning a static IP to the Chromecast in the router prevents lease renewal during sessions.
Older Chromecasts and newer Chrome versions
Very old Chromecasts (1st generation, 2013-2014) occasionally have compatibility issues with current Chrome versions. Google officially ended support for 1st generation Chromecasts in 2024. If your Chromecast is very old and newer replacement devices cast fine: the device itself may be the incompatibility rather than Chrome or the network.
Cast in enterprise/corporate environments
Corporate networks with strict VLAN segmentation, multicast filtering, or client isolation often make Cast non-functional on work Wi-Fi. Multicast DNS (used for Cast discovery) is frequently disabled on enterprise networks for security. Signs: Cast works at home but finds no devices at the office.
Solutions in corporate environments: some organisations deploy a dedicated “media” VLAN that allows mDNS for conference room casting. For individual setups: a Wi-Fi hotspot from a phone (which creates its own isolated network including both your computer and a Chromecast connected to the hotspot) bypasses corporate network restrictions for personal casting.
Chrome on non-default ports or VPNs
VPNs that route all traffic through the VPN tunnel prevent Cast discovery — the Chromecast is on the local network but Chrome’s mDNS traffic goes through the VPN, which can’t see local network multicast. Disconnecting the VPN for casting sessions is the simplest fix. If VPN is required: configure split tunneling to exclude local network traffic from the VPN tunnel — this allows Cast discovery while keeping work traffic through the VPN.
Full Chrome reinstall for persistent Cast failures
When Chrome’s Cast component is in a broken state that chrome://flags changes don’t fix: a clean reinstall resolves it. Uninstall Chrome (Settings → Apps → Google Chrome → Uninstall) → delete leftover files (%localappdata%GoogleChrome) → download and reinstall from google.com/chrome. Sign in with your Google account → sync restores bookmarks and settings → test Cast immediately before installing any extensions.
| Symptom | Most likely cause | Fix |
| No Cast devices found | Network isolation between computer and Chromecast | Same SSID; disable AP isolation in router |
| Cast option not in menu | Chrome flag disabled or component missing | chrome://flags → enable Media Router; check three-dot menu |
| Cast starts, immediately stops | Chromecast needs restart or network conflict | Power cycle Chromecast; check firewall |
| Works at home, not at office | Corporate network mDNS filtering | Use phone hotspot; request IT to enable mDNS |
| Black screen for streaming services | DRM content protection during casting | Use in-app Cast button; use Chromecast’s own apps |
Cast failures are almost always network-related rather than Chrome configuration problems. The same-network check (including guest vs main network and AP isolation) resolves the majority of “no devices found” situations. Everything else in this guide covers the less common scenarios where the network is correctly configured but something in Chrome or on the Chromecast itself is blocking the cast session.
A practical tip for checking whether the network setup supports Cast before troubleshooting Chrome: open the Google Home app on a phone connected to the same network your computer is on. If the app shows the Chromecast and can control it: the network is correctly configured for Cast. If it doesn’t show the device or shows it as offline: the network has the issue, not Chrome. This phone-based test takes 30 seconds and immediately tells you whether Chrome needs to be debugged or the router/network needs to be fixed.
Casting audio without video
Chrome’s Cast also works for audio-only content — music streaming, podcasts, and videos where you only want the audio on a Chromecast Audio or a TV being used as a speaker. Three-dot menu → Cast → click the Cast icon → the dropdown shows available devices including audio-only Cast devices. If audio Cast doesn’t appear: check that the Cast device appears in the Google Home app and supports audio casting (Chromecast Audio units do; video Chromecasts also support audio-only casting).
Google Meet and casting
Starting a Google Meet from Chrome and trying to cast it to a TV produces mixed results — the cast shows the tab, but Meet’s camera and microphone permissions in the cast context differ from the regular Chrome context. For meeting rooms where a large screen display is needed: a dedicated Chromecast with Google Meet hardware (Google Meet device or Meet-compatible hardware) provides more reliable integration than trying to cast a Chrome tab containing a Meet session.
For home theatre setups where casting is used regularly: keeping the Chromecast on the 2.4 GHz band and the computer on 5 GHz, with the router’s 2.4/5 GHz band steering disabled, provides the best stability. The Chromecast maintains its network connection on 2.4 GHz (longer range, more stable for a stationary device) while the computer gets faster 5 GHz throughput. The router should bridge both bands to the same subnet — the critical requirement is that they can see each other on the local network, not that they’re on the same band.
Cast API for developers
If you’re building a web application that should support casting: the Google Cast SDK provides the integration for making web apps Cast-ready. Cast-enabled applications appear natively in Chrome’s Cast destination picker with the correct app loaded on the receiver side. Chrome’s built-in Cast (tab and desktop mirroring) is separate from Cast-SDK applications — apps using the SDK provide a much better casting experience for their specific content than generic tab mirroring.
Peer-to-peer Cast discovery
A less-known fact about Chrome’s Cast implementation: discovery uses mDNS (multicast), but actual media transport uses peer-to-peer communication between the computer and the Chromecast. This means both devices need to be able to communicate directly — not just reach the internet. If your network has “AP isolation” or “wireless isolation” enabled: each wireless device is isolated from the others and can only reach the router, not each other. Turning this off is required for Cast to work.
This explains why Cast works perfectly through a standard home router but fails completely through some enterprise APs, hotel Wi-Fi, and even some prosumer equipment where wireless isolation is enabled by default for security. The network fix (turning off isolation) isn’t optional — Cast simply cannot function without device-to-device communication on the local network. Our guide on Chrome Password Manager Not Working covers an adjacent issue.
