Cast a browser video to the TV without installing another app
Chrome Cast, AirPlay, and the cases where the tab plays but the TV stays black.
You already have the video in a tab. You want it on the big screen. The app store does not need another icon for that job.
Chrome tab → Cast
In desktop Chrome: the Cast icon, Cast tab, pick the speaker/TV. This sends the tab, including the player chrome, not a clean video surface. Fullscreen the player first. Disable extra motions on the page or the TV will show them too.
This path dies when the tab uses Widevine in a way the Cast session will not take, or when the site blocks background playback. If the TV goes black but audio remains, it is usually DRM or a canvas player, not your HDMI cable.
iPhone Safari → AirPlay
Control Center, Screen Mirroring for the whole phone — ugly, and notifications come with it. Better: the AirPlay icon inside the player, if the site exposed it. Many cheap players do not. Then you either mirror, or open the same URL in an app that does AirPlay (VLC, Infuse).
Android → TV without a brand app
Built-in Cast from the notification shade when a tab is playing, or the TV’s built-in browser if you accept pain. DLNA from a local file (VLC) still works on a shocking number of cheap TVs and skips the account graph entirely.
Compress video for WhatsAppBlack screen checklist
- Another device already owns the Cast session. Kick it.
- TV and phone on the same layer-2 network, not a guest VLAN that isolates clients.
- 4K tab on a 1080p dongle — drop the tab to 1080p before cast.
- Mixed IPv4/IPv6. Force the phone off the broken one and retry.
If you do this every night, a cheap HDMI stick dedicated to one site is still less anger than five protocols. For one-off, the tab is enough.
See live buffer if the TV stream stalls only after a successful cast. Sending a clip from the same phone afterwards: WhatsApp compress.
Quick answers
What is this guide actually for?
Chrome Cast, AirPlay, and the cases where the tab plays but the TV stays black.
Why does HD still buffer on a fast line?
Resolution is not bitrate. A 1080p label at 1.4 Mbps plus a six-second keyframe will stall even on fiber. Force 720p for one title you know. If that holds, the pipe is the limit — not the site.
Is it the player or the network?
Play the same file from local storage. Local clean → path problem. Local broken → file or decoder. One device failing is a cable or that box; every device failing is the origin or the file.
Do this in order
- Force 720p on one title you already finished. If it stays smooth, the pipe is the limit.
- Play the same file from local storage. Local clean → debug the path. Local broken → debug the file.
- Switch DNS (1.1.1.1 or the ISP) for ten minutes. Random stalls are often a bad AAAA.
- One tab, one player. Kill preview thumbs and autoplay-next on the page.