Search a curated directory of mainstream gallery-dl supported sites, see what each extractor commonly handles, and identify whether cookies or OAuth may be required before you build a command.
Search mainstream, non-explicit platforms by site name, domain, capability, or authentication type. Upstream support can change, so use the official list for final verification.
Loading curated site data…
| Site | Common capabilities | Authentication | Command |
|---|
The gallery-dl supported sites directory covers many social, art, photography, manga, forum, and hosting platforms through site-specific extractors. Support applies to listed URL types and can change when a platform changes. Treat the upstream supported-sites document and your installed version as the final authority.
A domain being listed does not guarantee that every page, feed, search, or account-only area on that domain is available. gallery-dl organizes support into extractors and subcategories. One extractor may accept an individual post, a public profile, and a tag search while requiring authentication for favorites, bookmarks, followed users, or private collections. The capability column is therefore as important as the site name.
Authentication labels also describe different workflows. Cookies normally reuse a browser session on your own device. OAuth starts an authorization flow and stores an access token in gallery-dl's local cache or configuration. A Supported label in the upstream table generally means username and password authentication is implemented, but direct credentials should only be used where the site and upstream documentation explicitly support them.
If a recognized domain returns an unsupported URL message, compare the exact page type with the extractor capabilities. Try a canonical profile, post, album, or gallery URL rather than a shortened, redirected, mobile, or tracking-heavy form.
Platforms change HTML, APIs, rate limits, and login requirements without coordinating with downloader projects. A listed extractor can fail until an upstream release adapts. Verify the installed version, reproduce with --verbose, and check current upstream issues before changing many unrelated options.
X/Twitter and Instagram are examples where the current upstream table lists Cookies as the authentication method. DeviantArt, Pixiv, Flickr, Reddit, SmugMug, and Tumblr use OAuth for account-related capabilities. Public URLs may still work without authentication on some extractors, but private, personalized, age-gated, or rate-limited areas typically need a valid session.
This checker never asks for authentication data. When a result indicates Cookies, use the local --cookies-from-browser option or a local Netscape-format cookies file. When it indicates OAuth, follow the extractor-specific upstream authorization command. Do not substitute a password merely because an authentication error appears; modern platforms often reject direct password automation.
A cookie can act like an active login session. Keep it on your device, exclude it from screenshots and repositories, and revoke or refresh the session if it may have been exposed.
Do not force a command from a similar-looking website name. Check aliases, alternate domains, and the upstream list first. Some families of sites are handled as instances under a shared extractor, while other services that appear similar have no extractor at all. A generic extractor exists for certain direct-resource patterns, but it is not a universal replacement for a site-specific implementation.
YouTube is not present as a native site row in the current upstream supported-sites list, so yt-dlp is normally the better tool for YouTube videos and format selection. Meta Threads is also not present as an independent site entry in the checked list. For either service, avoid tutorials that promise current native support without showing a matching upstream extractor and release evidence.
| Situation | Best next check | Avoid |
|---|---|---|
| Domain not found | Search the upstream supported-sites document | Guessing an extractor name |
| Known site, wrong URL type | Compare the capability column and canonical URL | Retrying the same redirected URL |
| Authentication required | Use the documented local Cookies or OAuth method | Uploading session values |
| Extractor recently failed | Update, test verbose output, review upstream issues | Random config changes |
| Video format selection | Check whether yt-dlp is the intended tool | Assuming gallery-dl uses yt-dlp syntax |
The website checker is a planning aid; the installed program is the executable evidence. Start with --simulate so the extractor can inspect the URL without downloading files. Add -E to print extractor information or -K to list available metadata keywords for a recognized URL. These checks help distinguish an unsupported URL from a filter, login, or output-path problem.
Use verbose logs only for diagnosis and inspect them before sharing. Request headers, query strings, file paths, usernames, and other values can reveal information even when a raw cookie is not visible. Reduce a report to the smallest public URL and command that reproduces the problem.
gallery-dl --simulate "URL"gallery-dl -E "URL"gallery-dl -K "URL"gallery-dl --list-extractorsVerify gallery-dl supported sites before a large or scheduled job, even when the same domain worked previously. Extractor support can differ by URL category, account state, and installed release. Rechecking the exact capability prevents a successful public post test from being treated as proof that bookmarks, private collections, or searches use the same access path.
Verify gallery-dl supported sites before changing authentication settings as well. If the capability calls for OAuth, browser cookies are not an interchangeable shortcut; if it calls for Cookies, a password field may not help. Record the canonical test URL type, installed version, listed authentication method, and simulated result so future gallery-dl supported sites checks start from evidence instead of guesses.
The gallery-dl supported sites total changes as extractors and instances are added, renamed, or removed. Use the current upstream supported-sites document rather than a fixed marketing number.
Yes. The current upstream list includes Twitter at x.com with profiles, media timelines, posts, bookmarks, likes, searches, and other capabilities. Cookies are listed as the authentication method.
The current upstream row includes posts, reels, stories, highlights, profiles, saved posts, and other Instagram capabilities. Cookies are listed for authentication.
YouTube is not present as a native row in the checked upstream supported-sites list. Use yt-dlp for typical YouTube downloading and format-selection tasks.
A page within the gallery-dl supported sites list may require a valid session, changed request rules, or a refreshed login. Update gallery-dl, test a public URL, and use the documented local authentication method.
No. The gallery-dl supported sites checker summarizes current upstream documentation. Your installed version, region, account access, URL type, and platform changes determine the actual result.