HomeTube in Content
Paste a URL. Watch it land in your library.
HomeTube is the workflow 350,000+ downloads already know: a video or playlist in, ad-free and best-quality files out, named and filed where Plex, Jellyfin or Emby will find them. Inside Content, it is a client of the engine — not a layer anyone has to pass through.
- 1.4k stars on standalone HomeTube
- SponsorBlock built in
- 1700+ sites
Demo
What changes
What comes across
Paste a URL; choose quality, codec, container, audio languages and subtitles; SponsorBlock; clips; server-side cookies; embedded chapters, thumbnails and metadata; readable names delivered into a Plex, Jellyfin or Emby library. Playlists too, each entry planned and named on its own.
What is new
The same source can also produce a transcript, a summary, a translation, thumbnails, metadata, Markdown or PDF. And the engine is reachable from Studio, the browser extension, an MCP agent, the CLI, the SDK and plain HTTP.
Not there yet
Playlist synchronization — the plan/apply diff with rename detection and archiving — is roadmapped, not shipped. If sync is your main use, keep standalone HomeTube for that job. Both apps default to port 8501: change one to run them side by side.
Two projects, one workflow
Nothing breaks. There is no deadline.
Standalone HomeTube keeps running and being maintained; it has not been retrofitted to run on Content. The HomeTube app in this repository is a new UI on the Content engine carrying the same workflow forward. Move when you are ready, not because you are forced to.
Or try HomeTube without installing it: the hosted HomeTube early access