PhonesTVCasting2026

How to Connect Your Phone to a TV Wirelessly — and Which Dialect Your TV Speaks

"Casting" is not one thing. Mirroring, Google Cast, AirPlay, and DLNA are four different protocols that people lump under one word, and the reason your phone will not talk to your TV is almost always that you are speaking the wrong dialect. Here is the decoder, the brand branch, and why Netflix shows a black screen.

A living room at dusk with a large dark television screen mounted on the wall and a smartphone resting face-up on the coffee table in front of it — The blank TV is the point: whether it fills with your movie or your whole messy home screen depends on which of four protocols you invoked, and only one of them is the right answer for watching something.

Updated September 2026By the AI Help Guide editorial team10 min read

The Confusion

One Word, Four Protocols

When a phone refuses to connect to a TV, people describe it as "casting not working," as though casting were a single switch. It is not. There are at least four distinct ways a phone can push video to a screen, they use different machinery, they behave differently, and a TV may support some and not others. Picking the wrong one is why the device never appears, why the video lags, or why a streaming app goes black. The first fix is to stop saying "cast" and start asking which cast.

Dialect 1

Mirroring (Miracast)Duplicates your entire screen, notifications and all. Peer-to-peer over Wi-Fi Direct, so no shared router needed. Laggy, and blocked by protected video.

Dialect 2

Casting (Google Cast / Chromecast)Sends a command so the TV fetches and plays the stream itself. Smooth, supports DRM, phone becomes a remote. Needs same Wi-Fi.

Dialect 3

AirPlayApple's mirroring and casting in one. Works on Apple TV and AirPlay 2 TVs. Supports protected video when used through the app, not raw mirror.

Dialect 4

DLNA / manufacturer appsOlder local-media streaming and brand-specific apps (Samsung, LG, Roku). Fine for your own files, clunky for subscriptions.

Read the four and the pattern emerges: mirroring shows your phone; casting shows the stream. That single distinction explains most of the frustration. If you want to watch a movie, you want casting, because the TV pulls the video directly and plays it at native quality while your phone is free. If you want to show a photo album or a slideshow, mirroring is fine. Confusing the two is the error.

The Decoder

What You Are Trying to Do, and the Dialect That Does It

Forget the technology for a moment and start from the goal. The table maps intent to protocol, which is the fastest way to stop guessing.

The goal	Use	Why
Watch Netflix, Disney+, Prime, YouTube	Cast / AirPlay button inside the app	Hands the stream to the TV through a protected path; mirroring is blocked by DRM
Show your camera roll or a slideshow	Mirror (Miracast) or AirPlay mirror	You want the TV to see exactly what the phone sees
Play a phone game on the big screen	Mirror, but expect lag	Real-time input over a screen-encode pipeline adds delay; a cable is better
Stream your own files (videos, music, photos)	DLNA or the TV's media player	Local media does not need a subscription path
Send a web page or a document	Mirror or AirPlay mirror	You want the exact screen, not a fetched stream

The row that trips everyone is the first one. People open the phone's system-level "screen mirror" toggle, then wonder why Netflix is black. The fix is to ignore the system mirror and use the little cast icon inside the streaming app, which speaks Dialect 2 or 3 and goes through the protected path the app allows.

The brand branch: which dialect does your setup speak?

iPhone + Apple TV or AirPlay 2 TV → AirPlay. Open Control Center, tap Screen Mirroring, or use the AirPlay icon inside apps. Cleanest path; both mirroring and casting work.
iPhone + non-Apple smart TV → check if the TV supports AirPlay 2 (recent Samsung, LG, Sony, Vizio do). If yes, AirPlay. If no, use the app's Cast button if a Chromecast or Cast-enabled device is on the network, or the TV's own app.
Android + Chromecast or Cast-enabled TV → Google Cast. Use the cast icon in apps, or Settings → Connected devices → Cast for mirroring on supported phones.
Android + Miracast TV → Smart View / Screen Mirroring / Cast (names vary by brand: Samsung "Smart View", Xiaomi "Cast", etc.). This is Dialect 1; expect lag and no protected video.
Either phone + a TV with none of the above → add a cheap dongle (Chromecast, Fire TV Stick, Roku) or use the TV's manufacturer app. A dongle is usually the single best $30 fix for an older TV.

The branch is ordered by how common each setup is. The honest summary: Apple-to-Apple is AirPlay, anything-with-Chromecast is Cast, and the rest is Miracast or a dongle. If your TV is older and supports none, a dongle converts it into a Cast or AirPlay target and removes the whole decision.

The Black Screen

Why Protected Video Refuses to Mirror

The DRM rule. Streaming apps detect the screen-mirror path and refuse to draw video on it, by design, to prevent casual copying. The result is a black frame or audio-only while the app's interface still shows. This is not a bug in your phone or TV; it is the content owner's protection working. The fix is never to fight it — use the app's own Cast or AirPlay button, which negotiates a protected playback path on the TV instead of mirroring the phone's screen.

Understanding this one fact resolves a huge share of "casting broken" reports. The mirror is a dumb screen-copy; the cast button is a smart hand-off. Subscriptions only allow the hand-off. So when Netflix goes black on a mirror, switch to the in-app cast icon and the problem evaporates — provided the TV or dongle supports that dialect, which is why the branch above matters.

The Lag

Why Mirrored Video Is Behind but Cast Video Is Not

Mirroring is a three-step pipeline: the phone encodes its screen into a video stream, transmits it over Wi-Fi, and the TV decodes and displays it. Each step adds delay, and the total is obvious the moment you play a game or try to lip-sync a karaoke app. Casting skips the pipeline entirely because the TV fetches the stream from the source itself; the phone only sends a "play this" command, so there is no screen-encode step to lag behind.

The practical consequence is a clean rule: for watching, cast; for showing, mirror; for playing, cable. If you need real-time responsiveness — gaming, a live presentation where you click and expect instant feedback — even the best wireless mirror will feel sluggish, and a short HDMI cable or a USB-C-to-HDMI adapter is the correct tool, not a protocol tweak.

A worked example: the movie night that was "broken"

Concretely, the most common version. A family wants to watch a streaming movie on the TV from a phone. They open the phone's system Screen Mirroring, connect to the TV, and the app's interface appears — but the moment they press play, the screen goes black while the TV keeps showing the paused frame. They assume the TV is faulty and start troubleshooting Wi-Fi, restarting the router, updating apps.

None of that was wrong; the diagnosis was. They were using Dialect 1 (mirror) for a job that requires Dialect 2 or 3 (cast), and the app's DRM blocked the mirror path exactly as designed. The fix took ten seconds: open the streaming app, tap the small cast icon in its corner, pick the TV. The movie played at full quality, the phone became a remote, and they could even lock the screen. The "broken TV" was a protocol mismatch hidden behind one word.

The Fixes

When Nothing Shows Up in the List

If the TV never appears as a target, the cause is almost always one of a short list, and working through it in order is faster than restarting everything at random.

Both devices on the same Wi-Fi network, not one on guest and one on main, and not one on 2.4 GHz and one on 5 GHz if the router isolates them.
The TV or dongle actually supports the dialect you are invoking (check the brand branch above).
For casting, the app's own cast icon is used, not the system mirror.
Wi-Fi is not isolated — some routers have a "client isolation" setting that blocks devices from seeing each other; turn it off for the home network.
The TV's casting/AirPlay feature is enabled in its settings; some TVs ship it off.
For Miracast, both devices are close enough and the direct link is not being blocked by a firewall or a corporate network.

The router-isolation item is the sneaky one: it looks like everything is correct, the devices are on the "same Wi-Fi," but the router refuses to let them talk. If a TV never appears no matter what, check that setting before blaming the hardware.

The Honest Takeaway

Stop Saying "Cast," Start Asking "Which One"

Wireless phone-to-TV works reliably once you drop the single word "casting" and think in four dialects. Watch with the cast button, show with the mirror, play with a cable, and if the TV supports none of it, a thirty-dollar dongle removes the decision entirely. The black screen is DRM, the lag is the mirror pipeline, and the missing device is usually the network or the wrong dialect, not a broken television.

For the cable alternative when lag matters, see our guide to USB-C and display output. For using the phone as a camera instead of a sender, see our guide to turning a phone into a wireless webcam.

A person seated on a sofa holding a smartphone and gesturing toward a wall-mounted television, cozy living room — The moment of choice: the same phone, the same TV, and two completely different outcomes depending on whether the cast icon or the mirror toggle was tapped.

Common Questions

Frequently Asked Questions

What is the difference between casting and mirroring?

Mirroring duplicates your whole screen on the TV, including notifications, and adds noticeable lag. Casting sends only the media to the TV, which fetches and plays it itself, so the video is smooth and your phone becomes a remote you can even lock. For watching something, casting is almost always better.

Why does Netflix show a black screen when I mirror?

Because protected video is blocked from screen mirroring by design. Apps like Netflix, Disney+, and Prime detect the mirror path and refuse to draw video. Use the app's own Cast or AirPlay button instead, which hands the stream to the TV through a protected path.

Do my phone and TV need to be on the same Wi-Fi?

For casting and AirPlay, yes, both must join the same network, which is the most common reason a device never appears. Miracast is the exception because it creates a direct peer-to-peer link, though it is still finicky.

Why is my mirrored video laggy but cast video fine?

Mirroring encodes your screen, transmits it, and decodes it on the TV, adding delay. Casting skips that pipeline because the TV pulls the stream directly, so it plays at native quality with no screen-encoding step.

My TV is old and supports none of this. What now?

Add a cheap dongle — Chromecast, Fire TV Stick, or Roku — which turns it into a Cast or AirPlay target and removes the whole protocol decision. It is usually the best thirty dollars you can spend on an older TV.

Can I mirror for gaming?

You can, but it will feel sluggish because of the encode-transmit-decode delay. For real-time responsiveness, use a short HDMI cable or a USB-C-to-HDMI adapter instead of any wireless protocol.

The TV never appears in my cast list. Why?

Most often the devices are on different networks or bands, the router has client isolation on, the TV's cast feature is disabled, or you are using the system mirror instead of the app's cast icon. Work the checklist above in order.

Ask our AI. Phone refusing to talk to the TV and you cannot tell which dialect it speaks? Tap the chat icon and describe your phone brand and TV model — it can point you at the right protocol and the fix.

More TV & casting guides like this

We decode "casting" into the four protocols it actually hides, so the black screen, the lag, and the missing device stop looking like hardware faults and start looking like the dialect mismatches they are.

Explore All Guides