Native Batch Downloader

Batch download files via the browser's native download channel — even login-protected files work, cookies sent automatically

Native Batch Downloader downloads a whole list of files at once, the way your browser already does it. Paste your URLs (one per line), set concurrency and an optional delay, and hit Start. Each link is handed to Chrome's own download engine — exactly as if you'd typed it into the address bar and pressed Enter. That means your session cookies, User-Agent, and Referer headers are sent automatically, with no extra setup. WHY IT'S DIFFERENT Most "downloader" extensions fetch files with JavaScript (fetch / XMLHttpRequest), which drops your login state and trips CORS. This one goes through the browser's native download pipeline, so authenticated downloads just work. FEATURES • Native download channel — login cookies and headers included automatically • Concurrency control — 1 to 200 parallel downloads • Delay control — optional wait between downloads to go easy on servers • Background queue — runs in a service worker, so closing the popup doesn't stop it; reopen anytime to see live progress • Real-time stats — total / succeeded / failed / waiting, with a progress bar and activity log • Smart de-duplication — duplicate URLs download once; invalid and duplicate lines are reported • Any file type — PDF, images, video, archives, and more • 18 languages • Manifest V3 — modern, lightweight, no host permissions GOOD TO KNOW • URLs must be direct file links. A page that generates a download via JavaScript after a button click won't work — you need the actual file URL. • Login state matters. The extension carries your cookies, but if you aren't logged into the target site, a 403 stays a 403. • Chrome allows ~6 concurrent connections per domain, so same-domain downloads cap there regardless of your concurrency setting. • Executable files (.exe, .bat, …) may trigger Chrome's built-in security prompt. No extension can suppress it. PRIVACY No data collection, no tracking, no external servers. Queue state is kept only in session storage and cleared when you close the browser.