Skip to content

Image galleries

Khryz-Navarro edited this page Nov 9, 2026 · 1 revision

Status: Planned · Phase 3 of the Roadmap · Issue #31

What it does

Paste a link to an image gallery, such as an album or a profile's posts on a site gallery-dl supports, and download all its images. yt-dlp is for video and audio; gallery-dl is the equivalent tool for images.

How it would work

  • Getting gallery-dl:
    • The app fetches and updates it the way it does yt-dlp.
    • In src/ytdlp.rs, BINARY_NAME/BINARY_URL choose yt-dlp's file per system. gallery-dl gets the same pair: it publishes standalone gallery-dl.exe (Windows) and gallery-dl.bin (Linux) files in its GitHub releases.
    • It updates on launch, like yt-dlp -U. The status bar shows both versions.
  • Which tool runs:
    • A link that yt-dlp can't handle but gallery-dl can goes to gallery-dl. gallery-dl can check a link without downloading.
    • Or the page offers Images as a choice when both can handle it.
  • The same trust boundary:
    • links are checked (assert_url) and passed after --;
    • options come from fixed lists;
    • files are named and placed by the backend.
  • Progress: gallery-dl prints each file it saves, which gives "23 of 80 images". It's a new tagged-line parser next to parse_line, with tests.
  • Signing in: many gallery sites need a session. gallery-dl reads --cookies and --cookies-from-browser like yt-dlp, so the existing Cookies setting can be reused.

Open questions

  • Save as a folder per gallery, or also offer a zip, as for Playlists?
  • Should the list of supported sites be shown, or just "try the link"?

Risks

  • Mature content: some supported sites are adult sites. Decide whether to say anything about that, and how.
  • Sites change and block scrapers: downloads depend on gallery-dl's updates.
  • A second program to trust: another binary is fetched from GitHub. Check what verification its releases allow, such as published checksums.

Home

Roadmap

Phase 1: links you paste

Phase 2: tools for your files

Phase 3: new engines

Phase 4: beyond the desktop

Clone this wiki locally