Casting, mirroring and a server are three different things
Three different things get called casting, and they behave nothing alike. Casting hands the television an address and steps back, so the phone can be locked or used for something else while playback continues. Mirroring copies the screen in real time, which works with anything but drains the battery and adds lag. A media server keeps your own files on a computer or a drive and lets the television pull them. Almost every failure people hit comes from expecting one of these to behave like another.
Which one you are actually doing
| Method | What travels | Fails when |
|---|---|---|
| Casting a supported app | A link and a play command | The app or the service blocks it |
| Mirroring the screen | A live video of the display | The network is busy, or the content is protected |
| Playing your own file | The file itself, from phone or server | The television cannot decode that format |
| A media server | A stream the server prepared | The server has to convert on the fly and cannot keep up |
| A cable | Everything, reliably | The phone does not support video out |
Advertisement
The apps that do each job
Sets up and controls a Chromecast or a television with it built in. Also where the mirror-my-screen option lives on many phones.
Finds the video on a web page and casts it to almost anything, including subtitles from a file. The most capable of the general casting apps.
Casts local files, cloud storage and network shares, with good subtitle and audio track handling.
The one for a household with a DLNA server or a network drive. It can also transcode through a desktop helper when the television refuses a format.
Older and simpler, and still the quickest way to throw photographs and local video at a television.
Plays practically any file the phone has and can send it to a Chromecast. When something will not play anywhere else, it plays here.
A full media server with a polished phone client. Set the server up on the computer that holds the files; the phone is the remote control.
The open source equivalent, with no subscription and no account on anyone else's service. More setup, entirely yours.
If the old phone or a small box is doing the playing rather than the television, this is the front end that handles everything.
Streams a computer game to the television with the phone as the link. A different job, and the same network rules decide whether it works.
Screen mirroring helpers like this one mostly open the setting Android already has. Useful as a shortcut, and no app can add mirroring to hardware that does not support it.
The reference implementation of casting: queue on the phone, play on the television, phone free afterwards. Worth understanding because everything else imitates it.
Casts to certified devices and refuses to mirror. That is copy protection working as designed, not a fault to debug.
Sends audio to a speaker or a television and keeps playing when the phone locks, which is the same model as video casting.
When nothing appears in the cast list
- Check both devices are on the same wifi network Guest networks, extenders with a separate name and client isolation all hide the television from the phone.
- Turn location permission on for the casting app Android requires it to discover devices on the network. It looks unrelated and it is the second most common cause.
- Restart the television, then the router Discovery uses multicast, which routers and smart televisions both get wrong until restarted.
- Try a different app for the same file If one app cannot see the device and another can, the problem is the app, not the network.
- Fall back to a cable A USB-C to HDMI adapter works on phones that support video out, has no lag and never needs debugging. Not every phone does support it.
- Anything long, because the phone is free
- Battery life, by a wide margin
- Quality, since the television fetches the stream
- Subtitles handled by the player
- Apps with no cast support
- Showing photographs or a slideshow
- A presentation or a document
- Games, accepting the lag
Why it looks worse than it should
Mirroring compresses the screen in real time and sends it over wifi, so text goes soft and fast motion smears. That is the method, not the television. Casting avoids it entirely because the television fetches the original stream, which is why a cast film looks right and a mirrored one does not.
If your own files stutter through a media server, the usual cause is the server converting the format on the fly because the television cannot decode it. Storing files in a format the television plays natively removes the conversion and the stutter together.
Cast when the app supports it, mirror only when it does not, and check that both devices are genuinely on the same network first.
Frequently asked questions
Why does one app refuse to mirror?
Content protection. Streaming services are contractually required to block the screen capture path, so the mirrored output goes black while the sound continues. Cast instead, which is the supported route.
Do I need a Chromecast if my television is smart?
Often not: most televisions now include one of the casting protocols. A separate device is worth it when the television's own apps are slow or no longer updated, which happens after a few years.
Does casting use my phone's data?
No. The television fetches the stream itself over the same network, which is also why casting keeps working when you leave the room with the phone.
Read next
Nothing has infected your phone. Something you installed has permission, and the fix is a list in settings.
A phone will happily run a keyboard, a mouse and a memory stick. It will not power a desktop hard drive.
Hard and fast are different things. Almost every game confuses them, and these do not.
