Chromecast Not Working or Not Showing Up? Complete Fix Guide (2026)

Q: Why is my Chromecast not showing up on my phone?

The most common reason is that your phone and Chromecast are on different Wi-Fi networks or different bands of the same router. Many routers expose 2.4 GHz and 5 GHz as separate SSIDs, and a guest network counts as a third — make sure both devices are on exactly the same SSID. The next most common cause is an active VPN on the phone, which blocks local mDNS discovery. Disable the VPN, then refresh the device list. If it still does not appear, check the router for 'AP isolation' or 'Client isolation' and turn it off, restart the Chromecast by unplugging it for 10 seconds, and try again.

Q: Why does Chromecast say 'untrusted device' or refuse to connect?

An 'untrusted device' or 'unable to verify' message usually means the Chromecast firmware is out of date or the local network is blocking the certificate check. Power cycle the Chromecast (unplug for 10 seconds), make sure the router has internet access so it can reach Google for verification, and disable any DNS-blocking app or DNS-level ad blocker (NextDNS, Pi-hole, AdGuard) for the Chromecast's IP. Then try casting again. If you set a static DNS like 1.1.1.1 on the router, briefly switch back to the ISP default while the Chromecast checks in.

Q: Why does my Chromecast keep disconnecting or buffering?

Chromecast disconnects and buffering are almost always Wi-Fi quality problems, not Chromecast hardware problems. Move the Chromecast to the 5 GHz band if your router supports it, position the router and TV so they have a clear line of sight, and switch to a less crowded Wi-Fi channel. Plug the Chromecast into the included power adapter rather than the TV's USB port — TV USB ports rarely deliver enough current for stable Wi-Fi. If buffering persists, lower the video quality variant in the casting app.

Q: Why does my Chromecast work on Wi-Fi but not on my mesh network?

Mesh systems (Eero, Google Wifi, Deco, Orbi, Asus AiMesh) often enable 'Client isolation' or place IoT devices on a separate VLAN by default. Both break Chromecast discovery. In the mesh app, find the Wi-Fi or guest-network settings and confirm that 'AP/Client isolation' is off and that the phone and Chromecast are on the same SSID, not on a separate IoT or guest network. After changing the setting, restart the Chromecast and the phone's Wi-Fi.

Q: Why does the Cast button not appear in Chrome or my casting app?

If no cast button appears at all, the page has not produced a cast-eligible video yet. Press play on the player so it actually requests the stream. If you are using Chrome on desktop and the cast icon is missing, restart Chrome and confirm Cast support is enabled in chrome://flags. In a casting app like CastBrowser, pull down on the device list to refresh and confirm at least one Chromecast is discovered. Pages that use Widevine DRM or restrict the video to native players will not surface a cast button by design.

Q: Should I factory reset my Chromecast?

Factory reset is a last resort, not a first step. Try the order listed in this guide first — same-Wi-Fi check, VPN off, AP isolation off, restart Chromecast, restart router. If everything still fails after those steps, hold the button on the Chromecast for at least 25 seconds until the LED flashes, then release. The device clears its setup and you re-pair it through the Google Home app. Reset only fixes a small subset of problems (corrupt firmware, stuck setup); it will not fix router or VPN issues.

Quick triage — try these first

Phone and Chromecast on the same SSID (not 2.4 vs 5 GHz, not a guest network)
Turn the VPN off on the phone
Unplug the Chromecast for 10 seconds, plug it back in
Disable AP / Client isolation on the router
Power the Chromecast from its wall adapter, not a TV USB port
Refresh the device list in your casting app

If those six steps do not solve it, work through the diagnoses below in order — they cover roughly 95% of remaining cases.

Symptom: Chromecast not showing up in the device list

This is the single most common Chromecast complaint. The TV is plugged in and powered on, the Chromecast logo is visible on the screen, but no casting app — Google Home, Chrome, YouTube, CastBrowser — finds it. The cause is almost always network-layer, not the Chromecast itself.

Cause 1 — Phone and Chromecast on different SSIDs

Modern routers and mesh systems often broadcast the 2.4 GHz and 5 GHz bands as separate networks (for example Home-Wifi and Home-Wifi-5G). Phones tend to prefer 5 GHz, while Chromecasts default to 2.4 GHz when signal is weak. They look like the same Wi-Fi from your perspective but are different broadcast domains, so mDNS discovery cannot cross them.

Fix: Open the Wi-Fi settings on your phone, look at the exact SSID name, then check the Chromecast's reported network in the Google Home app under Device → Settings → Wi-Fi. They must match character-for-character.

Cause 2 — Active VPN on the phone

VPN apps route all traffic through a remote tunnel and almost always disable local mDNS discovery as a side effect. Chromecast advertises itself with an mDNS broadcast on the LAN; if the VPN swallows that broadcast, no app on your phone can see the Chromecast.

Fix: Disable the VPN entirely, then pull down to refresh the device list. If you need the VPN for browsing, look for a "LAN bypass" or "split tunnelling" option and exclude Chromecast IPs.

Cause 3 — AP / Client isolation enabled on the router

ISP-supplied routers, mesh systems and guest networks frequently enable a "Client isolation" or "AP isolation" mode that prevents devices on the same Wi-Fi from talking to each other. The Chromecast is online, the phone is online, but they cannot reach each other.

Fix: Open the router admin (often 192.168.0.1 or 192.168.1.1) or the mesh app, look under Wireless or Wi-Fi settings, and turn off "AP isolation," "Client isolation," or "Wireless isolation." If the option is only on the guest network, simply move both devices off the guest network.

Cause 4 — Multicast / mDNS blocked

Some business-grade routers, school networks and corporate Wi-Fi block multicast traffic by default. Without multicast there is no Chromecast discovery. Most home routers do not have this problem unless someone enabled IGMP snooping with strict filtering.

Fix: If you are on a managed network you do not control, this is a dead end — Chromecast cannot be discovered there. On a home router, look for IGMP snooping or Multicast filtering and either disable it or set it to permissive.

Symptom: "Untrusted device" or "Unable to verify" error

You see the Chromecast in the picker, you tap it, and the cast either fails immediately or shows an "untrusted device" warning. This is a certificate / firmware-check failure, not a discovery failure.

• Stale firmware: Power cycle the Chromecast (unplug 10 seconds). It checks for a firmware update on boot — make sure the router has internet so it can reach Google.
• DNS-level ad blocker interfering: NextDNS, Pi-hole, AdGuard Home and similar can accidentally blocklist clients3.google.com or www.google.com, which Chromecast hits during the trust handshake. Add those domains to the allowlist for the Chromecast's IP.
• Custom DNS on the router: If you set 1.1.1.1 or another upstream and the resolver is rate-limited or filtering, fall back to the ISP default temporarily until the Chromecast checks in.
• System time wrong on the phone: A wrong clock breaks TLS. Toggle automatic date and time on.

Symptom: Chromecast keeps disconnecting or buffering mid-stream

Casting starts cleanly but drops out after 30 seconds, or the video stutters and rebuffers every few minutes. This is a Wi-Fi quality problem, not a casting protocol problem.

• Power source: Plug the Chromecast into the included wall adapter. TV USB ports often supply too little current for stable Wi-Fi, especially on 4K models.
• Wi-Fi band: If your router supports both 2.4 and 5 GHz, put the Chromecast on 5 GHz when signal is strong. 2.4 GHz penetrates walls better but is heavily congested in dense housing.
• Channel congestion: Use a Wi-Fi analyser app to find the least-used channel and set your router to it.
• Distance and obstacles: The Chromecast antenna is small. If the router is on another floor or behind a metal entertainment unit, throughput collapses. Move the router or add a mesh node.
• Bandwidth contention: Backups, large downloads, or someone else streaming 4K can saturate your uplink. Pause those and retry.
• Lower the quality variant: In CastBrowser, when multiple HLS variants are available, pick a lower one to confirm whether the issue is bandwidth.

Symptom: Cast button missing or greyed out

The Chromecast is fine — discoverable in Google Home, casts from YouTube — but the cast button is missing or greyed out in the specific app or website you want to cast from.

• Stream not loaded yet: Many sites only fetch the actual video stream after you press play. Tap play, wait a couple of seconds, then check again.
• DRM-protected content: Pages using Widevine L1/L3 or FairPlay block external casting by design. Netflix, Disney+, HBO Max and similar will never expose a cast button outside their official apps.
• Iframe-embedded player: The video might be in a sandboxed iframe that hides the underlying stream. CastBrowser can usually still detect it — open the page inside the CastBrowser tab and press play.
• Ad blocker conflict: Aggressive blockers occasionally break the player's loading sequence. Toggle the ad blocker off for the site and reload.

Symptom: Chromecast with Google TV not casting

Chromecast with Google TV is both a streaming box and a Chromecast receiver. Sometimes the receiver service stops responding even though the launcher works fine.

• Restart the device: Hold the power button on the remote, choose Restart, or unplug for 10 seconds.
• Check Google services: Open Settings → System → About → Status and confirm the device is online and the time is correct.
• Free up storage: A nearly-full device can cause the Cast service to crash. Uninstall apps you do not use under Settings → Apps.
• Update the system: Settings → System → About → System update. A pending update sometimes leaves casting in a degraded state.

Symptom: Chromecast built-in TV (Sony, Vizio, TCL, Hisense) not discoverable

On Smart TVs with Chromecast built-in, the Cast receiver is part of the TV firmware. If it disappears from your device list, the TV either turned off the receiver service or has not loaded it after boot.

• Wait 30 seconds after turning the TV on — receiver services cold-start.
• Check "Chromecast built-in" or "Google Cast" setting: On Sony Bravia / Google TV models it is under Settings → Apps → Chromecast built-in. Make sure it is enabled and signed in.
• Energy saver / quick start: Turn on the "Quick start" or "Always on" option so the Cast receiver stays loaded in standby.
• Update TV firmware: Vendor firmware updates frequently fix Cast receiver bugs.
• Same-SSID rules still apply: Built-in or dongle, the discovery layer is identical — see the Wi-Fi causes above.

When CastBrowser helps and when it does not

CastBrowser ships its own Google Cast implementation, so on iOS — where Google Cast is not part of the system — it lets you cast to Chromecast without an Apple TV. On Android it gives you a cast button on every site, even ones that have no native cast support.

CastBrowser does fix:

• Sites with no built-in cast button
• iPhone users with no Apple TV who want Chromecast support
• Pages that hide the underlying video stream
• Multi-protocol households (Chromecast + Roku + Fire TV + DLNA from one app)

CastBrowser does not fix Wi-Fi network problems, AP isolation, blocked multicast, broken Chromecast firmware, or DRM-protected streams. Those are issues at the network or content layer that no casting app can work around.

Last resort: factory reset the Chromecast

If everything above failed and a different phone on the same Wi-Fi cannot find the Chromecast either, factory reset is reasonable. Hold the single button on the back of the Chromecast for at least 25 seconds — the LED flashes solid white, then resets. Re-pair through the Google Home app and reconnect to your Wi-Fi.

For Chromecast with Google TV, hold the back-of-device button or use Settings → System → About → Reset → Factory reset. This wipes installed apps and accounts, so you will sign in again.

Frequently Asked Questions

Why is my Chromecast not showing up on my phone?

Almost always a network-layer issue. Confirm both devices are on the exact same SSID (2.4 GHz and 5 GHz often broadcast as separate networks), turn off any active VPN, disable AP/Client isolation on the router, and restart the Chromecast. Refresh the device list after each change.

Why does Chromecast say "untrusted device" or refuse to connect?

A certificate or firmware-check failure. Power cycle the Chromecast so it can update, make sure the router has internet, allowlist Google domains in any DNS-level ad blocker, and confirm the phone's system clock is correct.

Why does my Chromecast keep disconnecting or buffering?

Wi-Fi quality. Power the Chromecast from its wall adapter (not a TV USB port), prefer 5 GHz when signal is strong, change to a less crowded channel, and reduce distance and obstacles between the router and the TV.

Why does my Chromecast work on Wi-Fi but not on my mesh network?

Mesh systems frequently turn on Client isolation or place IoT devices on a separate VLAN. Open the mesh app and confirm both phone and Chromecast are on the same SSID with isolation off.

Why does the Cast button not appear in Chrome or my casting app?

The page has not produced a cast-eligible video yet, the content is DRM-protected, or the player is in a sandboxed iframe. Press play to load the stream, and try opening the page inside CastBrowser if a non-DRM source is available.

Should I factory reset my Chromecast?

Only as a last resort, after the Wi-Fi, VPN, isolation and power steps in this guide. Hold the device button for 25 seconds, then re-pair via Google Home.

Chromecast Not Working? Step-by-Step Fix Guide