Every watch-together tool has the same shape of answer: it works beautifully on some sites, and on others it either does nothing or breaks after a minute. People assume this is a quality difference between tools. It is not. It is one technical fact showing up over and over.
Here is the straight version, so you can find out before you plan an evening rather than during it.
The short version
| Where | Synced watching | Notes |
|---|---|---|
| YouTube | works | ads detected, so one side waits for the other's ad break |
| Vimeo | works | |
| Twitch (VODs) | works | |
| News sites, embedded players | works | JW Player and Video.js ads detected |
| Corporate / course players | usually works | including players inside shadow DOM |
| Self-hosted video, archives | works | |
| Netflix | works | DRM protects the content, not the controls |
| Disney+ | works | same kind of protected player |
| Prime Video | works | same kind of protected player |
The last three rows are the ones people expect to say "no". They don't, and the reason is worth a section of its own.
Why the protected services behave differently
An ordinary web video is a <video> element sitting in the page. Anything running in your browser — including an extension you installed on purpose — can read where it is and ask it to play or pause. That is what makes synced watching possible at all: two browsers each nudging their own player until both sit on the same second.
Paid streaming services do not hand you a plain player: playback runs through a protected pipeline so the stream itself cannot be inspected or copied. It is tempting to conclude that nothing outside the service can control it either — but those are two different things. DRM protects the content, not the play/pause controls. The stream stays encrypted and untouched, while currentTime, play() and pause() remain the ordinary browser API. That is why the protected services work.
So the rule of thumb is narrower than it looks: a protected service is not out of reach. What can still break a site is the service's own player logic (a seek being undone, several video elements on one page), not the encryption.
What the services offer themselves
Some platforms have built their own group-watch features instead, which sidestep the problem entirely because they are inside the service rather than outside it. These features get added, changed and quietly removed fairly often, and they usually come with conditions — everyone needs their own subscription, sometimes the same region, sometimes a specific app rather than a browser.
Rather than print a list that will be wrong in six months: if the film you want is on a subscription service, check that service's own help pages for a group-watch or party feature first. If it has one, use it — it will beat anything external. If it does not, no extension is going to fill that gap for you.
What "works on any page with a video" actually buys you
The upside of hooking the page's own player instead of integrating with a service is that there is no list of supported sites to wait for. The extension finds the video on the page — including players nested inside shadow DOM, which a lot of embedded and corporate players use — and syncs that.
In practice that covers more evenings than people expect:
- A YouTube film, documentary or concert, with ad breaks handled
- A Twitch VOD you both missed live
- A course or conference recording you want to go through together
- Anything on a site that just publishes video normally
And a detail that matters on long videos: because each person plays the original themselves, you each keep your own quality, your own subtitle language, and your own audio track. Nothing is re-encoded and sent from one of you to the other.
If your film is on the wrong service
Three real options, in the order most people should try them:
- Check the service's own group-watch feature. Inside the service, it works properly.
- Screen share it, accepting that your friend sees a re-encoded copy — commonly capped around 720p on free tiers — and that your upload and your laptop carry the evening. The full comparison is here, and for a one-off it is a perfectly reasonable trade.
- Pick something you can both open. Less satisfying as advice, but a documentary you both actually see clearly beats a blockbuster you watch through compression mud.
Before you start
Ours is a Chrome extension: Chrome 116 or newer, and Edge, Brave and Opera are expected to work but unverified. Firefox and Safari are not supported. Rooms hold up to 5 people — sync works with more, but one person's buffering or ad break holds up everybody, and past five that happens too often to enjoy.
The video never passes through our server; only small messages about position and play state do. Chat is never stored on the server.
It needs an account; opening a room and joining one are both free, with no card asked. Download · All the questions, answered plainly