Can You See What I See

Screen sharing tools have gotten weirdly complicated

You want to show someone something on your screen without a twenty-minute setup. I've used enough of these tools to know the frustration. There was a project I was working on last year where I needed to walk a client through a spreadsheet they kept opening incorrectly, and the Zoom screen share was lagging so badly they couldn't follow along at all. Ended up using a simple text-based workaround where I'd paste screenshots into a Google Doc with point-by-point annotations instead. Took three minutes longer but actually worked. That's essentially what you need. The name says it plainly. You share what's on your monitor, they see it in their browser, and nobody needs to install anything. That's the selling point anyway. The reality is more nuanced. Most of these services work the same way under the hood. You open a page, create a room code or link, and the other person joins from their browser using WebRTC. The video stream goes peer-to-peer directly between computers when possible. When it doesn't, it routes through a relay server. The quality depends entirely on your upload speed, not your download speed, which trips up a lot of people.

I tested about a dozen options before settling on what I use now. The ones that require account creation are usually worse than the ones that don't. Less friction means more adoption, and that's what matters when you're trying to help someone who isn't technical. I ran into a specific problem once where the sharing side had perfect quality but the receiving side showed a completely different resolution. Turns out some browsers throttle the bitrate aggressively when the tab isn't in focus. The fix was keeping the receiving browser tab active and visible the entire time. Nothing dramatic, just something the documentation never mentions. Here's what most people don't tell you about these tools. The real bottleneck isn't bandwidth. It's input lag. When you're sharing your screen and typing, there's usually a delay between your keystrokes and what the other person sees. For casual viewing this doesn't matter. For actual troubleshooting or detailed work, it's noticeable enough to be frustrating. I've found that tools which offload the encoding to hardware (check if they use WebCodecs or H.264 specifically) handle this significantly better than ones doing software encoding on the CPU. Another counter-intuitive thing. Lower resolution often feels smoother than higher resolution. A 720p stream at 30fps will feel more responsive than a 1080p stream at 24fps because the input latency is lower. If responsiveness matters more than visual fidelity, drop the resolution and frame rate rather than the other way around. Most tools let you adjust these settings manually, but the defaults are almost always wrong for live collaboration.

The tools that actually work well tend to be the boring ones. No flashy features, no recording built-in, no chat integration. Just a clean screen share with minimal overhead. I recommend looking for options that let you share a specific window rather than your entire desktop. Sharing a full desktop exposes everything and adds processing overhead that slows things down. Window-only sharing cuts the data being encoded roughly in half, which makes a real difference on slower connections. There are situations where none of this helps. If you're on a connection below 5 Mbps upload, most of these tools will stutter no matter what you do. In that case, consider switching to a shared document or even sending screenshots in a messaging app. It's less elegant but it actually works. Trying to force a screen share on a bad connection just wastes everyone's time. If you want to try one, searching "can you see what I see screen share" will bring up several working options. Look for the ones with the simplest interface. The ones showing five different plans and a feature comparison chart are probably overcomplicating things for what is fundamentally just a browser-to-browser video stream.