Skip to content
Okytes

A download manager which is free and efficient.

Capture links. Run parallel transfers. Keep your queue organized. Your files, your desktop, your control.

Download Okytes
Choose your platform

Downloads · v0.0.1

Your OS. Your download.

Choose your platform, pick a package, and go. Direct GitHub release files with checksums and installation details.

Detected:Detecting…
Available

Windows

A familiar setup. Your choice of installer.

  • Windows installer

    Setup wizard. Easiest way in.

    .exex6426.3 MB
    Download
Available

Linux

Native packages or a portable AppImage.

  • Linux .deb

    Debian, Ubuntu, Mint, Pop!_OS.

    .debamd6445.6 MB
    Download
Coming soon

macOS

Apple Silicon and Intel. Coming soon.

  • macOS Coming soon

    Apple Silicon + Intel. Coming soon.

    .dmguniversal
    Watch the repo

Connect your browser

Catch the link. Let Okytes take over.

  • Chromium extension

    Chrome, Edge, Brave, Opera, Vivaldi.

    .zipany542 KB
    Download

  • Firefox extension

    Hands Firefox downloads to the engine.

    .zipany542 KB
    Download

  • Safari extension Coming soon

    Safari extension coming soon.

    .zipany
    Watch the repo

Inside Okytes

From link to local file.

HTTP & HTTPS

Parallel byte-range transfers, retries with backoff, and server-aware throttling.

Range: bytes=start-end

A persistent queue

Organize transfers in one place and keep your queue across app restarts.

queue → transfer → complete

Browser handoff

Send downloads from Chromium browsers or Firefox to the native desktop app.

browser → desktop → transfer engine

Architecture

Native at the core.
Open at every layer.

The browser extension hands links to the desktop app. The shared engine handles transfers, while the persistent queue keeps work organized.

Explore the source

Browser extension

Desktop app

Native transfer engine
Persistent queue

ODM / IDM / FDM / XDM

The difference is
in the engine.

ODM earns its place with measured concurrency, durable checkpoints, and one shared control plane. Not just more connections: a deliberate design for how transfers scale, recover, and fit into your workflow.

03 / ENGINE DESIGN

One queue. Every interface.

Desktop, browser and automation use the same transfer core. Revocable, scoped API credentials keep programmatic control explicit.

Shared engine + authenticated local control

Swipe the table to compare all four.

Transfer architecture, recovery, automation and deployment of ODM, Internet Download Manager, Free Download Manager, and Xtreme Download Manager. Each cell links to an official source.
What mattersODMNative transfer engine · v0.0.1IDMInternet Download ManagerFDMFree Download Manager 6.xXDMXtreme Download Manager 9
Concurrency strategyHow extra connections are put to work.

Throughput-driven worker scaling

EWMA measurements; extra workers must earn their place.

Dynamic segment splitting

Splits the largest unfinished segment; reuses connections.

Multi-section downloading

Transfers several file sections in parallel.

Segmented multi-connection transfers

Splits downloads across connections.

Recovery contractWhat progress means after an interruption.

Disk sync before checkpoint commit

Only committed bytes count as durable progress.

Interrupted-download recovery

Resumes after network loss, shutdowns and power outages.

Resume interrupted transfers

Continues from where the download stopped.

Preserves progress on disk errors

Disk-full or missing-folder failures keep existing progress.

HTTP resume behaviorContinue a partial file against its source.

Strong ETag + range validation

Checks source identity before continuing a partial transfer.

Resume unfinished downloads

Error recovery restarts interrupted transfers.

Continue without starting over

Resume support for interrupted downloads.

Resume + expired-link refresh

Refresh a download URL without losing existing progress.

Engine & client designWhere the transfer work actually lives.

Shared, UI-independent native core

Desktop, daemon and CLI reuse the same engine; no JVM.

Windows app + browser integration

Desktop application handles captured downloads.

Desktop app + add-on pipeline

Extensions and add-ons expand download intake.

Separate Java core + Swing UI

UI-independent download engine; JVM-based application.

Programmatic controlHow downloads fit into your own workflows.

CLI + scoped local API

Revocable credentials; clients share engine-owned state.

Command-line job launching

Start downloads or queue URLs from scripts.

Android remote control

Create downloads remotely with FDM on both devices.

Headless command-line mode

Download from a terminal alongside the desktop app.

Linux deploymentNative formats and a portable option.

DEB · RPM · AppImage

A portable image alongside native distro packages.

No native Linux release

DEB · Flatpak

DEB · RPM · Arch · tar.gz

macOS availabilityCurrent desktop release support.

Coming soon

No macOS release

Apple Silicon · Intel

Apple Silicon · Intel

ODM implementation details are linked to the release source; competitor entries describe vendor-documented behavior. Undocumented internals are not treated as missing features. This is a design comparison, not a speed or memory benchmark.

Sources checked: 2026-10-28

Contribute

Build it with us.

A shared engine, reusable components, and real-world edge cases. Reliability, protocol compatibility, accessibility, tests, docs — all welcome. So is testing on weird setups.

…

stars

…

forks

Star on GitHub
Read the docs Good first issues