Six people are crowded around one phone watching a cricket highlight, and the television two metres away is doing nothing. Somebody taps the little screen-shaped icon. Nothing happens. Somebody else decides the TV must be too old. Search for how to cast phone to TV and you get a hundred guides that skip the part that matters: two different technologies hide behind that icon, and most failures come from using the wrong one.
Sort that out and the rest takes a minute.
Casting and mirroring are not the same thing
Casting sends an instruction, not a picture. Google’s own developer documentation describes your phone as the “sender” that “plays the role of controller for the Cast session”, while the TV runs a “receiver” responsible for “conveying streaming content from an online streaming service” (Google Cast overview). In plain terms: the video travels from the internet straight to your television. Your phone only says which video, and when to pause.
Mirroring works the other way round. Your phone captures whatever is on its screen, compresses it, and pushes it across your Wi-Fi to the TV frame by frame. The TV displays a copy of the phone.
That one difference explains nearly everything. Cast a YouTube video and the picture quality is limited by your TV and your internet connection, not your phone — and because the phone is only a remote, playback does not depend on it staying awake on that screen. Mirror the same video and you get your notifications on the big screen, a warm phone, a draining battery, and a visible delay between tapping and seeing.
So when there is a cast icon inside the app, use it. Mirroring is the fallback, not the default.
Why your TV never appears in the list
Both Google and Apple state the same requirement: the phone and the TV have to be on the same Wi-Fi network (Google, Apple). That sounds obvious, and it is where most attempts die, because “same Wi-Fi” is easier to get wrong than it looks.
Six things worth checking:
Your phone is on mobile data. Wi-Fi switched off, or the phone quietly dropped the connection because the signal was weak in that room. The cast icon will either vanish or find nothing.
Two networks, one router. Plenty of routers broadcast the 2.4GHz and 5GHz bands as separate names — something like “Home” and “Home_5G”. Your phone joins the fast one, the TV sits on the slow one, and neither can see the other. Put both on the same name.
The guest network. Guest Wi-Fi usually isolates devices from each other on purpose, which is exactly what you do not want here. Move the phone to the main network.
A range extender. Extenders that run their own network name put the TV on a different network to the phone.
An AirPlay passcode. Apple’s support page notes that if a code appears on the TV screen, you have to type it into the phone. Easy to miss if the TV is on a different input.
The feature is switched off. Some sets disable it by default — look for AirPlay, Google Cast, Chromecast built-in, or Screen Mirroring in the TV’s network menu.
When mirroring is the right choice
There is a large category of things with no cast button at all: wedding photos in your gallery, a PDF, a bank statement, a browser tab, a mobile game, a video a relative sent on WhatsApp. For those, mirroring is the only way.
On an iPhone, it lives in Control Centre under Screen Mirroring. On most Android phones it is in Quick Settings under a name the manufacturer chose — Smart View, Cast, Screen Cast, or Wireless Display.
Two habits make it much better. Turn on Do Not Disturb first, unless you want your messages projected in front of the family. And rotate the phone to landscape before you start, because mirroring sends the phone’s screen shape as it is — a portrait phone on a widescreen TV means a narrow strip of picture with black bars either side.
Expect a small lag. That is fine for photos and tolerable for video, and it makes fast games frustrating.
The app has to exist on the TV as well
This one catches people out. Google’s Google TV help page notes that third-party apps “must be installed on your cast-enabled GTV or ATV device with cast turned on” for playback to work. Casting is not a magic pipe — you are asking the TV to open the app itself and play the file, so the TV needs that app and a signed-in account.
If a service works on your phone but refuses to cast, check whether the TV has that app installed at all. Older smart TVs often cannot install it any more, which is a good argument for a cheap streaming stick rather than a new television.
Casting also means the stream is being pulled over whatever connection the TV uses. If you are running the TV off your phone’s hotspot, a two-hour film pulls a two-hour film’s worth of data — our guide to cutting streaming data usage without losing quality is worth a read before you try it.
Cast phone to TV with a cable when Wi-Fi gives up
When the Wi-Fi is congested, the room is far from the router, or the TV is old enough to have no smart features at all, a cable ends the argument. You need an adapter matching your phone’s port — USB-C or Lightning — with an HDMI output on the other side.
Two limits are worth knowing first. Apple’s support page for its Digital AV adapters states that “movies, TV shows, and certain streaming video apps require High-Bandwidth Digital Content Protection (HDCP)”, and that some apps need their developer to enable adapter support (Apple). A cable is not a guaranteed route around an app that refuses to send video out. It is, however, immune to router problems, and it charges the phone at the same time if the adapter has a passthrough port.
If it still will not connect
Restart in this order: the app, then the phone, then the TV at the wall rather than the remote, then the router. Unplugging the TV fully clears the network stack on a lot of sets, and it fixes plenty of cases where the device was visible yesterday and invisible today.
If you could cast phone to TV before and it stopped after a software update, check the TV’s network settings again — updates sometimes reset the feature back to off.
Photo by Image Hunter on Pexels
