Turbo Internet Download Manager

Turbo Internet Download Manager runs on macOS. It is a Chrome extension, so it runs wherever Chrome 116 or later runs — macOS, Windows, Linux and ChromeOS — with no platform-specific build and no companion application to install. This is worth stating because the better-known product with a similar name, Internet Download Manager (IDM) by Tonec, is a Windows-only desktop application and is unrelated to this project.

Turbo Internet Download Manager is an unrelated project that happens to share part of a name. IDM by Tonec is a paid Windows-only desktop application that reaches the browser through a companion integration plugin. Turbo Internet Download Manager is a free Chrome extension: there is no desktop application, no companion plugin, and it runs on macOS, Windows, Linux and ChromeOS alike.

Turbo Internet Download Manager is free. There is no paid tier, no trial period, no licence key and no account to create.

No. Turbo Internet Download Manager is a single Chrome extension. It hooks Chrome's own download event and does its fetching inside the browser, so there is nothing installed alongside Chrome and nothing left running once the browser is closed.

Turbo Internet Download Manager makes a download faster when a single connection is the bottleneck, which is common on servers that throttle per connection and on long-distance links where latency limits throughput. It does nothing when your own line is already saturated, and nothing when the server refuses ranged requests, in which case the download falls back to a single connection.

Turbo Internet Download Manager splits a file into parts and fetches each on its own connection, up to 32 parts, with the count configurable per file type. A connection that finishes early takes over half of whichever part has the most left to do, so the tail of a download does not wait on one slow part. Splitting stops when under 2 MB remains, and a part already 90 percent done is left alone.

Turbo Internet Download Manager resumes a broken download wherever the server supports ranged requests. Each part retries on its own with exponential backoff, and every part request carries If-Range with the file's ETag or Last-Modified, so a file cannot be stitched together from two different builds. On a server that ignores Range, resuming restarts the download.

Yes. Turbo Internet Download Manager carries the browser's own cookies, so anything you can reach while signed in downloads normally. Referer is set through a declarative session rule rather than through fetch, which cannot set it, so hotlink-protected servers that answer 403 without a referrer work as well.

Turbo Internet Download Manager downloads HLS streams that a page actually loads, including TS and fragmented MP4 segments, EXT-X-MAP, EXT-X-BYTERANGE and AES-128 transport encryption. TS streams are converted to a plain, seekable MP4 with a real sample table, so ordinary desktop players open them. Nothing is re-encoded. SAMPLE-AES and anything Widevine-backed are refused.

No, deliberately. YouTube and comparable platforms are out of scope for Turbo Internet Download Manager, because downloading from them breaks their terms of service and Chrome Web Store policy forbids extensions that do it.

Turbo Internet Download Manager collects no data and sends nothing to its publisher. There is no backend service to send anything to. Files travel straight from the origin server to your disk, and are never proxied through anyone else.

To download a file Turbo Internet Download Manager has to be able to fetch from the site the file is on, which is any site you download from. The same access lets it notice HLS playlists a page loads. Nothing else is read from pages, and the clipboard features that watch for copied links can both be switched off.

Yes. Turbo Internet Download Manager has a speed cap, alongside pause and resume, so a large download does not have to take the whole line.

Turbo Internet Download Manager saves into Chrome's own download folder, and each file-type rule can name a subfolder underneath it, so disk images, archives, video and installers can be separated without sorting them by hand.

That is the single-connection cap. When a server ignores ranged requests, Turbo Internet Download Manager falls back to one connection, and a single-connection download is capped at 1 GB.

About twice the size of the file. Turbo Internet Download Manager holds the parts in browser storage until the finished file reaches disk, so a 6 GB download temporarily needs roughly 12 GB free.

Most often the minimum size. By default disk images under 20 MB, archives under 10 MB, video under 5 MB and installers under 2 MB are left to Chrome. The rule for that file type may also be switched off, or the server may not be offering ranged requests. The service worker console logs the reason.

No. Turbo Internet Download Manager handles HTTP and HTTPS downloads and HLS streams. There is no BitTorrent support, no FTP support, no scheduler and no queue that survives a browser restart. A standalone desktop download manager is the better fit if you need those.

Turbo Internet Download Manager is built for Chrome and tested there. Edge, Brave and other Chromium browsers use the same extension platform and should run it, though they are not tested. Firefox and Safari use different extension APIs and are not supported.

A Chrome Web Store listing is on the way. Until then it loads from source: open chrome://extensions, turn on Developer mode, choose Load unpacked and select the extension folder. Chrome 116 or later is required.

Turbo Internet Download Manager ships in English and Turkish. Adding a language means one JSON file of strings, with no code changes.