Chromecast cannot find a TV on the network

A TV with Wi-Fi is not automatically a Google Cast receiver. The TV maker may provide a different sharing feature, and support can vary by model, operating system, region, or accessory. Check the exact TV specifications or setup guide for built-in Google Cast. If you use a Chromecast or Google TV Streamer, confirm it is powered, completed in Google Home, and associated with the intended home and network. Google’s Cast developer troubleshooting guidance explicitly starts by confirming the receiver is an official Cast device and that both ends are on Wi-Fi.

1. Identify the receiver model and look up its setup status in the manufacturer’s or Google’s official guide.

   This distinguishes a receiver that is missing from the network from a TV that simply does not implement Cast.

   If that does not help: If Cast is not supported, use the TV’s documented sharing option or a compatible external receiver; a generic ‘screen share’ label does not establish Cast compatibility.

2. Open the receiver’s home screen or Google Home device list and confirm it appears online.

   If the receiver is offline or still awaiting setup, sender-app troubleshooting cannot make it discoverable.

   If that does not help: Complete the official first-time setup on a trusted home network before testing the Cast button.

Choose a known Cast-enabled sender app and open its device picker. Google’s developer troubleshooting page cautions against using YouTube or Netflix as the sole discovery test because they can use specialized discovery mechanisms. Try a second supported sender app. If the receiver appears in one app but not another, broad network discovery is working and the problem is more likely app-specific, account-related, or tied to that app’s current casting support. If no supported app sees it, continue with local-network checks.

1. Make sure Wi-Fi is enabled on the sender and reopen the sender app.

   A fresh app scan can recover a stale picker while leaving the TV and network untouched.

   If that does not help: If other Cast apps also show no receiver, record that before changing the router.

2. If using Chrome, open its Cast destination list separately from phone-app testing.

   A receiver found by Chrome but not an app narrows the issue to the app or phone permissions.

   If that does not help: If neither finds it, investigate whether the devices share the same local network.

For ordinary Cast discovery, being on the same internet subscription is not enough. Google’s setup guidance says the sender and Cast receiver need to communicate on the local network; guest networks, hotel or public Wi-Fi, and access-point/client isolation can block that communication. Mesh systems, extenders, VLANs, and separate SSIDs can create similar separation depending on their configuration. Do not turn off router security broadly: ask the network administrator whether local device discovery is allowed and make any router change only on a network you control.

1. Compare the Wi-Fi network name (SSID) shown by the sender and receiver; check whether one device is on guest Wi-Fi.

   Matching names are a useful starting point, though router isolation can still prevent discovery.

   If that does not help: Move only to a trusted network you control; hotel, school, workplace, or managed networks may intentionally block device-to-device traffic.

2. On iPhone or iPad, check that Google Home has Local Network permission; Google’s setup instructions also call for Bluetooth during setup.

   The setup app needs the relevant local access to configure or find a device.

   If that does not help: If permission is already enabled, avoid repeatedly resetting the receiver; continue with the app/network comparison.

3. If your router has AP isolation, client isolation, or guest isolation, consult its manual or administrator about whether the sender and receiver are separated.

   An isolated network can explain why internet access works while device discovery fails.

   If that does not help: Do not disable isolation on a shared/public network or change settings you are not authorized to manage.

Once you know the receiver is compatible and the network permits local discovery, refresh the simpler parts first. Close and reopen the sender app, then restart the phone or computer and the Cast receiver using their normal controls. If the network itself appears stuck, Google recommends rebooting the router as a later step; that briefly disconnects every device. A factory reset is not an ordinary discovery refresh: it removes the receiver’s setup and requires you to configure it again.

1. Restart the sender app and check the device list again.

   If it returns, note whether only that app needed a refresh.

   If that does not help: If not, continue with a normal restart of the sender and receiver.

2. Restart the TV or streaming receiver from its documented system controls, then reopen a Cast-enabled app.

   This refreshes the receiver’s network session without deleting its configuration.

   If that does not help: If still missing, capture receiver model, software version, SSID arrangement, and which apps were tested.

3. Reboot a home router only if you control it and other local-network devices also have discovery problems.

   If discovery returns after router restart, the network path deserves follow-up rather than a receiver reset.

   If that does not help: On managed, hotel, or public Wi-Fi, contact the network operator; do not attempt to change their configuration.

If one Cast app fails but another finds the receiver, report the app name/version and what its picker shows to that app’s support team. If all sender apps fail on one network but work on another trusted network, share the router/extender model and whether guest isolation or multiple SSIDs are enabled with the network administrator. If the receiver is absent from Google Home or repeatedly loses Wi-Fi, give Google or the TV maker its exact model and setup state. Do not factory-reset until the support instructions for that model call for it and you have the credentials needed to set it up again.

• Google Cast discovery troubleshooting — checked 2026-10-24
• Connect a Chromecast or Google TV Streamer to Wi-Fi — checked 2026-10-24

Why does my phone see the internet but not my Chromecast?

Internet access does not prove that local devices can discover each other. Check that both are on the intended network and that guest or client isolation is not separating them.

Does every smart TV support Google Cast?

No. Wi-Fi and screen mirroring do not guarantee built-in Google Cast. Check the exact TV model specifications or use a compatible external receiver.

Should I factory-reset Chromecast when it is not showing up?

Not as the first step. Confirm setup, sender-app support, local network access, and restart first. A reset erases setup and should follow device-specific support guidance.