This is an automated archive made by the Lemmit Bot.
The original was posted on /r/selfhosted by /u/wowkise on 2025-06-02 18:11:23+00:00.
YTPTube, is a selfhosted docker container with frontend for yt-dlp, it started as fork of the great metube, to add support for concurrent downloads and since then it has been completely re-written to support more features that i found useful for myself. Example picture
Difference compared to metube:
- Multi-downloads support.
- Random beautiful background.
can be disabled or source changed. - Can handle live streams.
- Scheduler to queue channels or playlists to be downloaded automatically at a specified time.
- Send notification to targets based on selected events.
- Support per link
cli options&cookies - A Preset system to reuse commonly used options.
- Simple file browser.
Disabled by default - A built in video player with support for sidecar external subtitles.
- Modern frontend UI.
- SQLite as database backend.
- Basic Authentication support.
- Support for curl_cffi, see yt-dlp documentation
- Support for both advanced and basic mode for WebUI.
- Bundled tools in container: curl-cffi, ffmpeg, ffprobe, aria2, rtmpdump, mkvtoolsnix, mp4box.
- Automatic upcoming live stream re-queue.
- Apply
yt-dlpoptions per custom defined conditions. - Browsers extensions, bookmarklets, and iOS shortcuts.
- automatic yt-dlp update on container startup.
Why the fork, or why a new frontend?
I wanted something that has features that i want to use, I personally use it to drive my youtube automation, i have specific vision and feature sets that i want, to put it simply the majority of the frontends don't fulfil my requirement, thus YTPTube was born. I want to be able to make decision about the direction of the project and not be blocked by anyone, And changing metube to fit my need is selfish, i wanted to explore different ideas which may or may not fit metube.
You can find the source and how to use it at the README of the project at this link
Happy to answer any questions.