Downlodr: an Electron desktop manager for yt-dlp downloads

The downloader core is yt-dlp, and the app is the management layer

Downlodr describes itself as a video downloading solution that supports multiple platforms, including YouTube, Vimeo, Twitch, Twitter, TikTok and others, with the project description claiming support for over 1,800 platforms.

The technologies section is where the design becomes clear. The application is built with Electron Forge and Vite, the interface is React, state is handled by Zustand, styling is Tailwind, and the language is TypeScript. Underneath sit two programs that do the real work: YTDLP, the command line tool for audio and video downloads from various platforms, and FFMPEG, the multimedia framework for processing and manipulating the resulting files. The acknowledgements section credits the yt-dlp project and the FFmpeg project for providing the core downloading functionality.

So the value Downlodr adds is not the extraction. It is everything around it, and the feature list is entirely about managing the queue rather than about getting the file. There is download management with the status of each item, currently downloading, finished, and a historical log of past downloads. There is tag and category management for organising downloads so they can be retrieved later. There is playlist support, so an entire channel or playlist can be downloaded with one click. There is quality selection, where you choose the video quality and format. And there is settings configuration for the default download location, speed and connection limits.

That is a fair summary of where the effort went. Anyone who has used yt-dlp from a shell knows the download itself is the easy part, and that the queue, the history and the naming are what turn a single command into a workflow.

The interface is a queue with transport controls

The usage guide describes the interaction in a way that shows the app is a download manager rather than a form.

Adding a download means clicking the Add URL button or using the File menu, pasting a valid video URL, selecting the download destination, and clicking Download to add it to the queue.

Managing means using play, pause and stop buttons to control downloads, right-clicking on downloads for additional options, and clicking a download to view detailed information about it.

Settings are where the app earns its keep under load. You set a default download location, configure download speed limits, and adjust the maximum number of concurrent downloads. Those three are what separate a queue that behaves from one that saturates a connection or spawns forty parallel yt-dlp processes and stalls the machine.

The stack underneath explains the choices. Zustand is described as a small, fast state management solution, which is the right size of dependency for a desktop app that holds a list of downloads with changing status. Vite is listed as a local development server, and the repository has three separate Vite config files, vite.main.config.ts, vite.preload.config.ts and vite.renderer.config.ts, which is the standard split for an Electron app where the main process, the preload bridge and the renderer each need their own build settings.

The security posture is visible in the dependency list too. Electron Fuses are present, along with the plugin that applies them, and the auto-unpack-natives plugin. Fuses are the mechanism for disabling Electron features such as the ability for renderer code to reach Node internals, and having the plugin wired in means the build can turn those off rather than shipping the defaults.

Running from source needs Node 20 and yarn 1, which is the older half of both

The prerequisites are listed as Node.js at version ^20.17.0 and yarn at version ^v1.22.19, and the install sequence is the conventional one for a Forge project.

First you clone the repository, and the README shows a placeholder URL rather than a real one:

   git clone https://github.com/your-username/downlodr.git

Then you move into the project directory and install the dependencies:

   cd downlodr

   yarn

And to start the application in development mode you run:

yarn start

The yarn 1 requirement is the detail that catches people out. Yarn 2 and later changed the command set, and the repository carries a yarn.lock that is a version 1 style lockfile, so a machine with modern yarn enabled through Corepack will not install this project the way the author did. Node 20 is similarly a version that has already been superseded as a current release line, which means the toolchain here is pinned to a period rather than tracking the latest.

Those constraints come from the devDependencies. Electron is pinned at 33.3.1 and Vite at ^5.0.12, and the Electron Forge plugins and makers are all at 7.6.0, which is a coherent set from one era. The Tailwind version is 3.4.17 rather than 4, and the linting stack is ESLint 8 with a TypeScript parser at version 5.

For packaging, the same Forge vocabulary applies. There is a package script for electron-forge package, a make script for electron-forge make, and a publish script. The README says that building and packaging creates distributable packages for your platform in the out directory.

Windows is the packaged platform, and the release tags say otherwise

The README states plainly that the current application has only been packaged for Windows, and the repository contents back that up. There is an installer.nsh file for an NSIS installer, an electron-builder-squirrel-windows dependency, a maker-squirrel maker, a maker-nsis from a separate project, and a yt-dlp.exe sitting at the top level of the tree, which is the Windows build of the downloader binary bundled with the application.

The release list complicates the picture. The three most recent tags are v1.17.13-mac-stable on 2026-10-01, v1.17.12-mac-stable on 2026-09-02 and v1.17.11-mac-stable on 2026-08-27. Every one of them names a mac build, while the README says the application has only been packaged for Windows.

There is a plausible explanation in the package.json, which lists both maker-deb, maker-rpm and maker-pkg for Linux packages and a dmg-builder at version 24.13.3, which is the tool that produces mac disk images. So the build configuration can produce packages for all three desktop platforms, and the mac tags show that somebody ran that path. What the README describes is what has actually been shipped and downloadable, which is the Windows application.

The version numbering is inconsistent in the same way. The package.json version is 1.7.13-stable while the tags are v1.17.13-mac-stable. That looks like a dropped digit rather than a different scheme, and it is the kind of small inconsistency that makes it hard to tell from the outside which build you have installed.

For a user, the practical conclusion is that the Windows build is the one to expect, that the mac and Linux build paths exist in the configuration but are not what the project distributes, and that the version in the About screen and the version in the release tag may not match character for character.

A bundled yt-dlp binary is both the strength and the weak point

The yt-dlp.exe at the repository root is a small file that determines a lot about how the project behaves.

The strength is that the application ships a working downloader, so a user does not have to install Python, pip or yt-dlp before anything works. That is a real difference from running yt-dlp directly, where the Python runtime is a prerequisite and the extractor scripts have to be kept current separately.

The weak point is the same fact seen from the other side. Site compatibility lives entirely in yt-dlp, and the extractors go stale whenever a site changes its page structure or its player. The application layer cannot fix that, because the application layer is a queue and a user interface. When a download stops working on one site, the cause is a yt-dlp extractor, and the fix is a newer yt-dlp, not a newer Downlodr.

That makes the freshness of the bundled binary the thing to watch. The README does not describe how the binary is updated, whether it is fetched at build time or refreshed by the application, and the repository layout does not make it obvious either. The telemetry/ directory is present at the top level, which suggests some usage reporting, though what it collects is not described in the visible documentation.

The downloader also has a documented side effect worth understanding before you use it broadly. Because FFmpeg is part of the toolchain, the application can post-process what it downloads, which is how formats get merged or converted, and the same capability makes it easy to request a format the site does not offer directly.

None of this is a reason to avoid the tool. It is a reason to understand where its edges are: the queue and the organiser are Downlodr, and the compatibility with any given site is yt-dlp's problem.

Editorial conclusion

Downlodr is worth trying if you download video regularly and want a queue, a history and an organiser instead of a shell, because the download management and tagging features are the part it adds on top of a tool that already existed, and the settings for speed and concurrency are the ones that matter when a large channel goes into the queue. It is the wrong tool if you need a maintained cross-platform installer, since the README says the current application has only been packaged for Windows, and it is the wrong tool if the fact that the actual downloading is done by yt-dlp bothers you, because that is where the compatibility with any given site lives and where the breakage will happen. Before you rely on it, verify three things yourself: that the yt-dlp build bundled in the repository is current enough for the sites you care about, since a stale extractor fails quietly and the release tags show the app version moving faster than anything else, that you have the right to download what you are downloading, since the tool itself does not check, and that the Windows build is the one you actually get, because the packaged application is Windows only.

Frequently asked questions

Official sources

1. License: MIT
2. Project website
3. README
4. Releases
5. Talisik/Downlodr on GitHub