Download a website in three steps.
Single page or the whole section.
Switch modes right in the popup. No config files, no terminal.
A folder of real files, not a screenshot.
Unzip an archive and the page's HTML sits next to the stylesheets, scripts, images and fonts it loads. Every reference is rewritten to a local path, so the copy opens in any browser with the network off. It will still open in five years, because plain HTML on disk outlives any format that needs its own viewer.
Chrome's built-in Save Page As attempts the same thing and quietly loses pieces: background images declared in CSS, pictures that lazy-load below the fold, webfonts. Site Downloader reads the document after the browser has rendered it, so what gets collected is what you were looking at.
Multi-page mode is the same operation at a different scale. Give it a link depth and the crawler walks internal links level by level, skips external domains, and packs everything it reaches into one archive. That count appears before the download starts; treat it as your warning that depth 3 was ambitious.
You can also download website sections one at a time and keep the archives separate, which is usually tidier than one enormous job. New to this? Start with the guide to downloading a website for offline use. It covers what each method gets wrong before you commit to one.
Good to know.
What is a website downloader?
A website downloader saves web pages together with everything they load: markup, stylesheets, JavaScript, images and fonts. Site Downloader is a web downloader that lives in the Chrome toolbar, so you download website content straight from the tab you are reading, and the copy still opens with the connection off.
Can it download an entire website?
Yes. Single mode saves the current page; Multi-page mode follows internal links level by level to the depth you set and packs every page into one archive. Details on the entire website downloader page.
How is this different from HTTrack or wget?
Those fetch raw HTTP from outside the browser, so a page that assembles itself with JavaScript often arrives as an empty shell. This runs inside the tab that already rendered the page. The trade-off is real: an extension cannot be scripted or scheduled. The guide compares five methods side by side.
Does it work on any website?
Almost. Any standard web page works. Browser-internal pages (chrome://, extension settings, the Web Store) can’t be downloaded; the icon stays disabled there. Content behind a login is also out of reach, because assets are fetched without your cookies.
What’s actually in the .zip?
The HTML plus every asset it references: stylesheets, JavaScript, images and fonts, all rewritten to load from local paths so the archive opens fully offline in any browser.
How deep can multi-page go?
You choose. Depth 1 grabs the page plus everything it links to; higher levels follow links of links. Crawling stays within the same domain, and the popup shows the page count before the download starts.
Can it download all the images from a website?
Yes. Every image the page loaded, including CSS backgrounds and lazy-loaded ones, lands in the archive. See the website image downloader page.
Do you collect my data?
No. Everything runs locally in your browser. Your own machine fetches and packs the pages; nothing goes to a server, and there’s no account.
Is it free?
Yes. Site Downloader is free to install and use from the Chrome Web Store, with no page cap and no paid tier.