Invidious Instance Information
Privacy-focused video frontend reference
Use this reference when video viewing should not be fed straight into a commercial platform profile. The main questions are whether streams are really proxied, how much the instance can see, and what breaks when bandwidth gets tight.
Video privacy has two separate leaks
A privacy video frontend can hide direct platform access, but there are two leaks to think about: the video platform and the instance operator. The platform should see the instance rather than you. The instance, meanwhile, can still see which videos are being requested.
That split matters for adult, controversial, political, or personally revealing viewing. A frontend can reduce platform profiling and recommendation feedback, but it is not a private diary of everything watched.
What usually goes wrong
Streams fall back to the source
If playback loads directly from the commercial platform, the privacy gain is weaker than it looks.
Performance varies wildly
Proxying video burns bandwidth, so volunteer instances can buffer or limit quality under load.
Links in descriptions still track
Creators can include off-platform links, and those links may carry their own analytics.
Safer viewing habits
- Use a known instance and keep a backup for when it fails.
- Use Tor or I2P for viewing that could cause harm if associated with you.
- Avoid logging into source-platform accounts in the same browser context.
- Check network requests if you need to know whether streams are truly proxied.
This page is maintained as a static reference to keep URLs predictable and safe.
Last updated: January 15, 2026