MeTube

Download videos and audio through a browser using yt-dlp.

Choose your deployment and the way you want to use Selfhost. The instructions below follow that choice.

Deployment Use Selfhost with

Set up MeTube

Editable Compose files in your own directory.

Keep MeTube local or behind authenticated access.
Choose output templates and concurrency before submitting large playlists.

selfhost app --directory ./metube init metube

Initialization writes portable files and does not start the app. Review compose.yaml, the private .env and any files in files/, then start it:

selfhost app --directory ./metube start

No Selfhost dashboard or background service is needed. You can also start these files directly:

cd metube
docker compose -f compose.yaml up -d

Connect an existing installation

Use Existing apps → Link an app in the dashboard, or the CLI’s existing-app commands. Choose MeTube, its URL and, optionally, its exact Docker container on a connected server.

Save existing.json with your app URL. Add server_id and container for container inspection and actions.

{
  "profile": "metube",
  "name": "MeTube",
  "url": "https://app.example.com"
}

selfhost existing link --file existing.json
selfhost existing list
selfhost existing inspect EXISTING_ID

Linking enables the existing-app profile’s supported inspection and actions. It does not import Compose or attach the new-deployment settings and onboarding profiles described below.

Existing app commands, permissions and unlinking

Actions for a linked container

Check download storage

Show disk space used by downloaded media and queue state.

selfhost existing action EXISTING_ID download-usage

Before configuring integrations

Download queue state persists in /downloads/.metube. File deletion through the trash button is an explicit setting.
There is no native login in this recipe.
Download folders and subscription configuration are separate from service restart or update operations.

MeTube integrations

Compose service: metube. These operations use the profile saved when this deployment is created.

MeTube has no native user login in this recipe. Keep the loopback binding or protect access with an authentication proxy.

Native settings

Changes use the app’s Compose environment. Unrelated settings are preserved.

Supported fields (8)

Concurrent downloads concurrency: string
Allow per-download folders custom-directories: stringChoices: true, false
Create download folders create-directories: stringChoices: true, false
Delete files when removing completed items delete-files: When enabled, trashing a completed item deletes its downloaded files. stringChoices: true, false
Video filename template filename: yt-dlp output template, for example %(title)s.%(ext)s. string
Playlist item limit playlist-limit: 0 means unlimited. string
Subscription check interval subscription-interval: Minutes between checks. string
Log level log-level: stringChoices: DEBUG, INFO, WARNING, ERROR, CRITICAL, NONE

Save a JSON map of the field IDs you want to change as changes.json. Replace FIELD_ID with an ID from the supported fields above, and use its declared value type. Review the plan and replace REVIEWED_REVISION with the revision it returns.

{
  "FIELD_ID": "YOUR_VALUE"
}

selfhost app --directory ./metube config metube
selfhost app --directory ./metube plan metube changes.json
selfhost app --directory ./metube apply metube changes.json --revision REVIEWED_REVISION

Saved changes need service recreation to become active. Existing interpolated environment values stay under your control in .env or Compose.

App actions

Check download storage

Show disk space used by downloaded media and queue state.

selfhost app --directory ./metube action metube download-usage

App configuration reference

Versions and updates

This deployment uses the following images. Existing projects retain their saved recipe and images. A new catalogue version does not silently update them.

metube: ghcr.io/alexta69/metube:2026.09.25

Review compatibility and back up app data before an update. Choose an image version and review the change.

Keep control of your setup

Selfhost remains optional. Your app runs using ordinary Compose files, its own settings and persistent data. Keep the Compose project name and volumes to preserve storage. Configuration exports and setting backups do not include application data.

Standalone CLI guide · Backups and removal · MeTube documentation