An embed is a window, not a copy
When an approved YouTube video plays inside FilteredTube, the media remains hosted and delivered by YouTube. The FilteredTube interface supplies the surrounding search, policy, and player experience, while the official embedded player supplies the stream. This is materially different from downloading the file, passing the stream through a FilteredTube server, or rehosting the media under a new URL.
FilteredTube uses the official privacy-enhanced youtube-nocookie.com embed path for eligible playback. That choice reduces unnecessary cross-site exposure before interaction compared with a standard embed, but it should not be read as a promise of complete anonymity. The source provider still operates the player and may process information according to its own terms when the customer uses it.
Filtering surrounds the player
The fact that a video can technically be embedded does not make it approved. Before an outside result reaches the player, its query and available metadata must pass the FilteredTube decision path. Clearly appropriate Torah or modest Jewish-music results may be displayed. Gray-area items remain hidden with a review option, while hard-no categories are denied.
Playback authorization can also depend on an eligible FilteredTube account, and the selected Video plan. If those checks or the production video service are unavailable, the interface is designed to fail closed. It should not send the customer to an unrestricted outside page as a substitute for the approved player.
Why YouTube downloads are excluded
The YouTube rail is deliberately playback-only. FilteredTube does not use yt-dlp, scrape YouTube, cache YouTube audio or video, or expose a download action for a YouTube embed. A download button elsewhere in the product is not a hidden conversion tool for provider-hosted videos; it belongs to a different catalog of media with explicit delivery rights.
Keeping the rails separate is useful for customers and rights holders. Customers can understand that an embedded title plays from its original source, while creators can grant separate FilteredTube permissions where appropriate. The service does not infer a right to copy from the mere existence of a public video or an embeddable player.
A focused experience can still feel unified
Technical separation does not require a fragmented interface. Search results, categories, the player, membership state, and eligible licensed actions can appear in one consistent FilteredTube experience. The important point is that the interface preserves the rights and safety boundaries underneath it rather than hiding them.
Customers should therefore expect availability to vary. A source provider may remove a video, disable embedding, or change regional access. A policy review may also change a result’s status. A focused service should communicate that state plainly instead of replacing an unavailable approved item with an unrestricted search result.
At a glance
Key takeaways
- Embedded videos remain hosted and delivered by YouTube.
- FilteredTube’s YouTube rail does not scrape, cache, rehost, or download media.
- A unified interface can preserve distinct policy and rights boundaries.
Continue with FilteredTube
Explore the focused player.
Search Torah and Jewish music inside the reviewed FilteredTube experience, or read how official embeds and licensed media remain separate.