Save an Entire Website in Firefox: All Subpages Offline

Looking for a way to save entire website Firefox pages, every subpage included, for offline use? The short answer: Firefox can't do it on its own. Save Page As, SingleFile, Save Page WE and similar add-ons save the page in front of you (or the tabs you already have open), not the pages it links to. To copy a whole site you need a tool that follows links, such as an online downloader, HTTrack or wget. Firefox is simply the place where you start it.

Can Firefox save an entire website? The short answer

Saving a page and copying a website are two different jobs. Saving a page means writing the document you are looking at, plus its images and styles, to disk. Copying a website means starting at the home page, finding every link to another page on the same site, downloading that page and repeating the process until nothing new turns up. It also means rewriting the links so they point to the local copies instead of the live site. That second job is called crawling, and no built-in Firefox feature does it.

If you only need three or four pages, the browser tools are fine. If you need the site as a whole, with menus that work offline, skip ahead to the crawler section.

Firefox Save Page As: "Web Page, complete" vs. "HTML only" vs. "Text Files"

Press Ctrl+S (Windows, Linux) or Cmd+S (macOS), or open the menu (☰) and choose Save page as…. The dialog offers several formats in the Save as type field:

• Web Page, complete: saves Page.html plus a folder named Page_files with the images, stylesheets and scripts the page uses. This is the closest Firefox gets to an offline copy. Keep the HTML file and the folder together; move or rename one and the page loses its styling.
• Web Page, HTML only: saves just the HTML document. Images and CSS still point to the live server, so the page looks right only while you are online and the site still exists.
• Text Files: saves the readable text without layout, images or links. Useful for quoting or searching, not for browsing.
• All Files: saves the raw file as the server sent it, before Firefox ran any scripts.

Whichever option you pick, links in the saved page still point to the online versions of the other pages. Click "About" in your offline copy and Firefox goes back to the internet. That is the core limitation: Save Page As stores one page, not a navigable site.

Add-ons: SingleFile, Save Page WE and what replaced ScrapBook

SingleFile for Firefox

SingleFile saves the page as you see it, after scripts have run, into one self-contained HTML file. Images, fonts and CSS are embedded inside that file, so there is no companion folder to lose. It can also save several selected tabs in one go, each as its own file. It handles many modern pages better than Save Page As because it captures the rendered result, and it has options for lazy-loaded images. It still saves only pages you have open; it does not discover the rest of the site.

Save Page WE

Save Page WE works on a similar idea: one HTML file per page with resources embedded. Its options for saving several pages refer to tabs you have selected or opened, not to links it finds and follows. If you open fifty subpages in fifty tabs by hand, it can save them, but you get fifty separate files whose links still point online.

What happened to ScrapBook?

ScrapBook, and its fork ScrapBook X, were classic Firefox extensions that could capture pages into a local library, including "in-depth" captures of linked pages. They stopped working when Firefox 57 (Firefox Quantum, 2017) dropped support for the old extension system. The closest modern successor is WebScrapBook, which brings back the scrapbook-style collection and includes settings for capturing linked pages to a chosen depth. It is a good ScrapBook alternative for Firefox if you collect research material. Running a crawl inside a browser tab is slow and fragile on anything beyond a small site, though, and it is not designed to produce a clean, portable copy of an entire domain.

One file or a folder of pages: which offline format fits?

The tools above produce two very different kinds of output, and it helps to choose deliberately.

• A single HTML file (SingleFile, Save Page WE) is ideal for one article, a receipt, a page you want to email or attach to a ticket. It opens anywhere with a double-click. The downside is that each page is an island: no working navigation, and file sizes grow because images are embedded as text.
• A folder of interlinked pages (what a crawler produces) mirrors the site's structure. Each subpage is its own HTML file, shared stylesheets and images sit in common folders, and links between pages are rewritten to local paths, so you can browse the menu offline exactly as you would online.

Rule of thumb: for fewer than about five pages, single files are quicker. For a documentation site, a blog, a portfolio or anything you will navigate, you want the folder.

How to save an entire website from Firefox with all subpages

Here are three ways to download a whole website from Firefox, from no installation to full command-line control.

Option 1: An online website downloader

Website Downloader runs in a Firefox tab and does the crawling on its own servers, so nothing is installed and your computer does not need to stay on while it works.

1. Open the home page and paste the site's address, for example https://example.com, into the download field.
2. Start the download and watch the live progress as pages are found and fetched.
3. Download the finished ZIP file, unzip it and open index.html in Firefox. Every subpage, image, stylesheet, script, font and media file is included, and links work offline.

The free plan needs no account and covers up to 100 subpages, with the archive kept for one day. Larger sites need a one-time Single Site purchase (7.99 EUR, up to 5,000 subpages) or a monthly plan; see pricing. The guide to downloading a website as ZIP walks through the result in more detail.

Option 2: HTTrack

HTTrack is a free desktop crawler for Windows and Linux (on macOS it is available through package managers). You enter a project name and the start URL, and it mirrors the site into a local folder. It is powerful and configurable, but the settings take some learning, and the crawl runs on your machine, which must stay on until it finishes. If installing software isn't an option, see HTTrack alternatives that run online.

Option 3: wget

On Linux and macOS (and Windows via WSL or a separate build), wget can mirror a site from the terminal:

wget --mirror --convert-links --adjust-extension --page-requisites --no-parent https://example.com/

--mirror follows links recursively, --convert-links rewrites them for offline use, --page-requisites fetches images and CSS, and --no-parent keeps it from wandering above the start folder. For a side-by-side look at all three, read wget vs. HTTrack vs. an online downloader. If you also use Chrome, the same reasoning applies there: save an entire website in Chrome.

What works offline and what doesn't

Whether you save one page in Firefox or crawl the whole site, an offline copy contains files, not a server. Anything that needs the server to answer a request stops working.

• Logins: crawlers, including Website Downloader, do not download pages behind a login. Browser tools can save a logged-in page you are viewing, one at a time.
• Search, forms, comments, shopping carts: they render, but submitting them does nothing useful offline.
• JavaScript-heavy sites: some React, Vue or Angular single-page apps build all their content in the browser. A crawler may capture the page shell without the content. Here SingleFile can sometimes save an individual rendered page better, because it captures what Firefox has already drawn.
• Blocked sites: some servers refuse automated downloads, for example with a 403 response. Website Downloader reports that instead of handing you an empty archive.

Why does my page saved in Firefox have no images or CSS?

This is the most common complaint about Save Page As. The usual causes and fixes:

• You chose "HTML only". Save again with Web Page, complete, or use SingleFile.
• The _files folder was separated from the HTML. Keep both in the same directory with their original names.
• Lazy-loaded images. Many sites load images only when you scroll to them. Scroll to the bottom before saving, or enable SingleFile's option for lazy-loaded images.
• Styles or images added by scripts. Save Page As can miss resources that JavaScript inserts later; SingleFile captures the rendered page and usually gets them.
• Resources from other domains. Fonts or images served from a CDN can be blocked or skipped. A crawler that fetches page requisites handles most of these.

For crawled copies that look broken, the same problems have their own fixes, covered in downloaded website missing images and CSS.

FAQ

Can I save a whole website in Firefox for Android?

Firefox for Android can save or share individual pages (for example as a PDF), and add-on support on Android has broadened, but there is no built-in way to crawl a site. Because an online downloader runs in the browser, you can start a full-site download from your phone and open the ZIP later on any device. See download an entire website on iPhone and Android for mobile options.

Can Firefox save pages that are behind a login?

Yes, one at a time: Save Page As and SingleFile save what your logged-in browser is showing. Crawlers, including Website Downloader, do not download pages behind a login. For a members area, saving key pages by hand is often the only practical route.

Is SingleFile better than Save Page As for offline reading?

For a single page, usually yes. You get one tidy file, it captures content added by scripts, and there is no folder to lose. For a whole site neither is the right tool, because both stop at the page you are on.

What about very large sites?

Browser add-ons become impractical after a handful of pages. With Website Downloader the free plan covers 100 subpages, Single Site and Standard cover up to 5,000, and Premium up to 30,000 per download. The FAQ and features pages explain the limits in detail.