IXD v1.0.48
Encrypted video no longer freezes the application. Choosing a quality on a
site that serves AES-128 HLS — most streaming sites do — made the download
crawl and the window stop answering, with force-quit the only way out.
IXD decrypts those streams itself. It was doing it in Python, at 0.5 MB/s,
without ever letting the interface run: a two-hour film needed about fifty
minutes of solid CPU, which is why it looked stuck at a percentage. It now uses
the OpenSSL already inside every build. The same download that took 172 seconds
takes 1.1, and the window stays responsive throughout.
A freeze now writes a log. The log lived in the database and was written by
the threads that stall, so a frozen application recorded nothing — the one
moment worth capturing was the one it could not capture. IXD now watches its
own interface from outside and writes stalls.log beside the database, with
stack traces, as it happens. Send that file with a report.
A download that stalls says where. Segmented transfers report progress,
name how many segments are encrypted, and flag any segment that takes too long.
The task log used to be empty.
The log names the decryption backend at every launch, so a build that falls
back to the slow path says so instead of just being slow.
This is a beta. If something does not work, please open an
issue — the templates ask for the log, which is usually the whole
answer. Toolbar → Log → Copy.
Downloads
Every platform has both: an installer, and a portable copy
that keeps its files wherever you put them and can replace itself
in place.
| Platform | Installer | Portable |
|---|---|---|
| Windows | ixd-*-windows-x64-setup.exe |
ixd-*-windows-x64.zip |
| macOS (Apple silicon) | ixd-*-macos-arm64.pkg, or the .dmg |
ixd-macos-arm64.zip |
| Linux | ixd_*_amd64.deb |
ixd-linux-x86_64.tar.gz |
The Windows installer asks whether to install for everyone — which
needs administrator and goes to Program Files — or just for you,
which needs nothing and goes to %APPDATA%\IXD.
The *-selfupdate* archives are the portable copies that are allowed
to replace their own folder when a new version appears. The ordinary
ones never touch themselves.
Start the application once, then load the extension from the folder
it writes. The two browsers need different manifests under the same
filename, so they get a folder each.
| Chrome / Edge / Brave | Firefox | |
|---|---|---|
| Linux | ~/.local/share/ixd/extension |
~/.local/share/ixd/extension-firefox |
| Windows | %APPDATA%\IXD\extension |
%APPDATA%\IXD\extension-firefox |
| macOS | ~/Library/Application Support/IXD/extension |
…/extension-firefox |
Chrome: chrome://extensions → Developer mode → Load unpacked →
the folder. Firefox: about:debugging → Load Temporary Add-on →
manifest.json inside the folder.
Before you report a problem
macOS is unverified. It builds and packages on a macOS runner and
has never been launched on real hardware. A report either way is
genuinely useful — including "it just worked". It is also neither
signed nor notarised, so the first launch needs right-click → Open,
or xattr -dr com.apple.quarantine "Internet Xtreme Downloader.app".
Windows: the first launch takes a while. Windows scans the whole
folder before it runs anything from it. Later launches are immediate.
Linux is the platform this is developed on and gets the most use.
Built from 44ccab2 on 2026-08-30.