Overview
Internet Download Manager splits a file into parallel segments and pulls them at the same time, which is why a saturated link finishes a large file noticeably faster than a browser doing the same job on one socket. It has been the standard answer to slow downloads for two decades and the current build still does the job better than anything bundled into a browser.
The browser integration is the part most people install it for. Once the extension registers, any download you start is handed to the manager, and media on a page is offered through a floating capture panel. Queues can be scheduled, so a large batch can be set to run overnight and shut the machine down when it finishes.
Resume handling is the other reason it stays installed. Broken connections, dropped sessions, timeouts and reboots do not cost progress. The manager reconnects, revalidates and continues from the last confirmed byte, and it does the same after a power cut because the segment map is written to disk as it goes.
What it does well
Dynamic segmentation
Files are split into as many as 32 parts and reassembled on completion, with segment counts adjusted live as the connection behaves.
Browser capture
Integration for the current Chromium and Firefox families, with a media panel that offers page video and audio streams for saving.
Queues and scheduling
Multiple queues with their own bandwidth limits and time windows, plus shutdown, hang up or hibernate on completion.
Resume that works
Segment maps are journalled to disk, so a crash or an outage costs seconds, not the transfer.
Site logins and cookies
Stores credentials per site and reuses browser cookies so protected links keep working after capture.
Changes in this build
- Capture updated for the current Chromium and Firefox release channels.
- Improved handling of segmented media manifests so long streams save as one file.
- Reduced idle CPU use in the tray monitor.
- Queue editor reworked with drag ordering and per-queue speed caps.
- Fixed a stall on servers that respond slowly to range requests.
What is in the package
- Internet Download Manager installer, 32 and 64-bit
- Browser integration modules
- Multilingual interface files, 35 languages
- Default queue and scheduling profiles
- Portable configuration exporter
System requirements
| Processor | Any x86 or x64 processor |
| Memory | 512 MB |
| Graphics | Not applicable |
| Storage | 60 MB free plus space for downloads |
| Display | 1024 x 768 minimum |
| System | Windows 7 through Windows 11, 32 or 64-bit |
Installation
- Extract the archive and close the browser completely.
- Run the installer and let it register the integration module.
- Reopen the browser and enable the extension when it prompts.
- Set the default download folder and the maximum connection count.
- Import an old settings file if you are moving from another machine.
Before you start
Some servers cap connections per client. Lower the segment count if a host starts refusing requests.
The tray monitor has to stay running for browser capture to work.
If capture stops after a browser update, toggle the extension off and on to re-register.
Questions about this title
Does it work with the current Chrome?
Yes, the integration module in this build targets the current Chromium releases.
Can it grab video from a page?
Yes, the capture panel appears over playing media and offers the available streams.
Will it resume after a reboot?
Yes, unfinished transfers reappear in the queue and continue from the last confirmed byte.
Is there a portable mode?
Settings can be exported and imported, but the browser integration needs a real install.
About this listing
This entry was checked on a clean install of Windows 7 / 8 / 10 / 11 before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.