The local video casting problem is older than most people remember. Long before Chromecast existed, families were dragging laptop HDMI cables across living rooms, hoping the format on the file would survive the trip. Streaming services papered over the gap for a decade, but they did not solve it. The moment you want to play a recording that is not on a service, you are back to hunting for USB sticks, signing up for cloud lockers, or giving up and watching on a laptop screen. Go2TV is a small open-source utility that targets exactly that gap, and it has quietly become my default for the long tail of one-off videos that do not belong anywhere permanent.
I came to it after a Saturday lost to Plex metadata scraping. I had a folder of meeting recordings and home videos that had no business living in a curated media library, but I wanted them on the TV for ten minutes at a time. Plex wanted folders, scans, and maintenance. Casting from Chrome mirrored my entire desktop and tanked the resolution. Cloud uploads cost time and bandwidth I did not want to spend. Go2TV sat between those options, did almost nothing, and solved the actual problem.
What the app actually does
The interface is a single window with two buttons that matter. Open Go2TV, and it scans your local network for Chromecast and DLNA (Digital Living Network Alliance, the long-standing standard that lets devices on the same Wi-Fi share media without going through the internet) devices. You pick the video file, pick the target, hit cast. The app handles the handoff and the TV takes over. There is no account, no signup, no analytics nudging you toward a paid tier. The simplicity is the feature, not a missing feature.
The protocol handling is the part most casting tools fumble. Go2TV uses standards the TV already supports, so nothing extra has to be installed on the TV side. Closing the app on the laptop does not interrupt playback, because the TV continues to stream on its own once the handoff completes. Because the project is open-source, you can audit the network calls, fork the repo, or build a version without update checks if you care about offline operation.
- The app scans for Chromecast and DLNA devices on the same network.
- Casting the file uses protocols the TV already supports, with no extra TV-side install.
- Closing the laptop app does not stop playback, because the TV keeps streaming.
- No account or signup, and the source is open enough to fork if defaults do not fit.
Transcoding saves you from the format nightmare
The single feature that won me over is silent on-the-fly transcoding. Chromecast is famously picky about file formats. Most of the videos I want to cast are screen recordings or exports from work tools, in codecs (encoder formats that compress video for storage; H.264 and H.265 are the most common modern ones) the TV would refuse outright. Go2TV detects the mismatch, transcodes in the background, and pushes a stream the TV accepts. The conversion happens invisibly. I press play, the video starts.
Subtitles work the same way. Half my one-off files have sidecar SRT (SubRip Subtitle, the standard plain-text subtitle format that sits in the same folder as the video file) files. Most casting apps either ignore them or bury the option behind menus. Go2TV sees them in the same folder and uses them. Audio and video stay in sync, which is the part that usually breaks in DIY setups. MKV (Matroska, a flexible open-source video container format that supports multiple audio and subtitle tracks in one file) containers with embedded audio tracks work without manual fiddling.
- Local transcoding kicks in automatically when the format would not play natively.
- Subtitles in the same folder as the video are picked up without configuration.
- Audio and video stay in sync through the transcoding step.
- MKV files and unusual audio tracks work without extra setup.
The real limits worth knowing
A casting tool that runs entirely on your laptop is going to inherit that laptop’s limits. The transcoding is local, so a weak CPU will struggle with high-bitrate 4K footage. The app assumes the computer stays awake during playback, so closing the lid or letting the machine sleep cuts the stream. Both devices need to be on the same Wi-Fi band, which means older routers with split SSIDs (the separate network names for 2.4 GHz and 5 GHz bands) can trip it up. Some smart TVs advertise DLNA support but ignore parts of the spec, so device compatibility is not universal.
None of these were dealbreakers for me, but they are worth knowing before you commit. The use case that fits Go2TV is short videos on a laptop that can stay open. The use case that does not fit is overnight 4K rips on a fanless ultrabook. Match the tool to the workload.
Trade-offs
Go2TV is not a media library. If you want long-term catalog management, automatic metadata scraping, episode tracking, or shared watchlists across multiple users, Plex and Jellyfin do that work better than any casting tool ever will. The honest framing is that Go2TV complements a media server, not replaces one. Files that deserve a permanent home belong in your library. Files that deserve ten minutes on the big screen belong in Go2TV.
The privacy story is simpler than cloud alternatives but not zero. Go2TV runs on your local network, but the binary checks for updates by default. The repo documents a flag to disable update checks if you want a fully offline build. For most home users that is fine. For anyone with a hard offline requirement, the source is small enough to fork.
Hardware is the other honest cost. Live transcoding wants CPU cycles, and the worst case is high-bitrate 4K H.265 footage on a six-year-old ultrabook. Dropped frames and loud fans are the result. On any laptop or desktop built in the last few years, transcoding is invisible.
Setup is the part I appreciate most, because there is almost none of it. Download Go2TV from GitHub, run it on your computer, make sure the TV is on the same Wi-Fi. The app finds the TV on launch. Pick a file, pick the TV, cast. That is the whole workflow. If something does not work, the most likely culprit is router isolation settings, not the app itself. Most modern routers have an “AP isolation” or “client isolation” toggle that blocks devices from talking to each other. Flip that off and Go2TV will see the TV again.
If you have a media server for the files that matter and a folder full of one-off videos that do not, Go2TV is the cleanest bridge. If your library is small enough that you do not need a server at all, this tool may replace the whole stack. If you only watch 4K rips on a fanless laptop, look at hardware-accelerated transcoding tools or stick with a local server.
What I would tell past me
If I could send a message back to the version of me that spent an entire Saturday trying to make Plex accept a folder of meeting recordings, I would say three things.
- Match the tool to the use case. A media server is for files that earn a permanent home. A casting tool is for files that earn ten minutes on the TV. Forcing one to do both jobs is how I lost a Saturday.
- Fix the network before the app. Most Go2TV failures I have seen come down to router isolation or split SSIDs, not software bugs. Get the network right and the rest of the setup gets short.
- Read the source. The project is small enough that a single afternoon of reading answers any privacy question, and you can fork it if the defaults do not match your needs.