ytdlp.org

Practical yt-dlp docs: install, commands, fixes, cookies, and workflows.

Current section

Error guide

Fix "ERROR: Unsupported URL" in yt-dlp

"Unsupported URL" doesn't always mean the site is unsupported. It means yt-dlp couldn't find media at that exact link. Most of the time the link is the problem: a homepage instead of a video page, a short link, or a page that only shows the video after you log in.

What the error looks like

$ yt-dlp "https://www.dailymotion.com/"
[generic] Extracting URL: https://www.dailymotion.com/
[generic] www.dailymotion: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] www.dailymotion: Extracting information
ERROR: Unsupported URL: https://www.dailymotion.com/

Dailymotion is supported, but its homepage isn't a video. The [generic]prefix is the clue: no site extractor recognised the link, so yt-dlp tried its catch-all extractor, and that found nothing to download (yt-dlp 2026.10.26, November 2026). Link the video page itself, the one with the player, and the site's own extractor takes over.

Work through it in this order

  1. Is it a video page?Homepages, search results, category pages and most profile pages give this error. Open the video, copy the URL from the address bar (not a share button's text), and try that.
  2. Is the site supported? Search the extractor list:
    yt-dlp --list-extractors | grep -i dailymotion
    dailymotion
    dailymotion:playlist
    dailymotion:search
    dailymotion:user
    If nothing comes back, there's no extractor for the site, and only the generic fallback (below) can help.
  3. Update. Sites change their URL formats, and new releases add the new patterns. Run yt-dlp -U (or see updating yt-dlp) and retry.
  4. Is the URL complete? Without https:// you get a different error, ERROR: [generic] 'example.com' is not a valid URL. Always quote the URL so the shell doesn't cut it at & or ?.
  5. Does it need a login? If the page redirects logged-out visitors to a sign-in page, yt-dlp sees the sign-in page and reports Unsupported URL. Pass your browser session with --cookies-from-browser firefox (see using cookies).

When the site isn't supported: the generic extractor

The generic extractor still handles a lot on its own. It downloads direct media links and plain HTML5 <video> tags, and it follows embedded players from supported sites. We checked both (November 2026):

# a direct .mp4 link
$ yt-dlp --print "%(extractor)s %(title)s" "https://download.samplelib.com/mp4/sample-5s.mp4"
generic sample-5s

# a page with an HTML5 <video> tag
$ yt-dlp --print "%(extractor)s %(title)s" "https://www.w3schools.com/html/html5_video.asp"
html5 HTML Video (1)
html5 HTML Video (2)

So if a site isn't supported but the video plays in your browser, find the media URL itself: open DevTools, go to the Network tab, play the video, and filter for m3u8, mpd or mp4. Pass that URL to yt-dlp. Many sites reject the request without the page as referer, so add it:

yt-dlp --referer "https://site.example/the-video-page" "https://cdn.site.example/.../master.m3u8"

If the media is encrypted (DRM), yt-dlp won't download it whatever the URL.

Related messages

  • No suitable extractor found for URL: you limited extractors with --use-extractors (or --ies) and none of them match. Remove the flag or add the right extractor name.
  • Unable to download webpage: HTTP Error 404: the link is dead, often an expired short link or a deleted post. Open it in a browser to confirm.
  • HTTP Error 403: Forbidden: the site is supported but refused the request. That's a different problem; see the 403 guide.

The mistake to avoid

Don't read [generic]+ Unsupported URL as "yt-dlp is broken". Look at what you passed it. If your app takes links that users paste, check the link before you queue a download: a homepage, a profile or a search page will fail every time, and telling the user right away is better than a failed job.

For builders

Using yt-dlp inside an app or script?

Paste a link to see what a managed media-import API returns — no install, no signup.

Building this into an app? See the API your backend calls instead

Frequently asked questions

What does "ERROR: Unsupported URL" mean in yt-dlp?

No site-specific extractor matched the link, so yt-dlp fell back to its generic extractor, which looks for a video or audio file in the page and found none. Either the link isn't a video page (a homepage, a search or a profile page), the site isn't supported, or the media sits behind a login or is loaded by scripts the generic extractor can't run.

How do I check whether yt-dlp supports a site?

Run yt-dlp --list-extractors and search the output for the site's name, for example yt-dlp --list-extractors | grep -i dailymotion. A site being listed means links to its video pages are supported, not every page on the site.

Why does yt-dlp say a link is not a valid URL?

The link has no scheme. yt-dlp needs https:// at the start: 'example.com' gives "'example.com' is not a valid URL" while 'https://example.com' is parsed. Quote URLs on the command line too, or characters like & and ? get eaten by the shell.

Will updating yt-dlp fix Unsupported URL?

Sometimes. If a supported site changed its URL format, a new release adds the new pattern. Run yt-dlp -U first. If the site isn't in --list-extractors at all, updating won't help.

Straightforward yt-dlp help for installs, commands, fixes, cookies, and repeatable workflows.

ytdlp.org is an independent, community-maintained documentation site. It is not affiliated with the yt-dlp project — the official source code lives at github.com/yt-dlp/yt-dlp.