A single file Chrome extension like SingleFile saves the tab you have open into one HTML file. Images, styles, fonts, and frames go into that file. You keep one .html document you can open later in any browser.

A full-site export follows public links. It saves many pages plus the CSS, JavaScript, images, and fonts those pages need. It rewrites the links so the copy still works as a site. The usual output is a ZIP or a folder.

TL;DR

SingleFile saves one tab as one HTML file. It is a Chrome and Firefox extension that works on the current tab.
A full-site export or snapshot grabs many pages and their assets. You get a ZIP or a folder you can browse.
Use SingleFile for an article, a receipt, a landing page you want as one file, or a design reference.
Use a full-site export when the menu, inner pages, and local links have to keep working.
Saving every open tab with SingleFile still gives you separate files. Those files do not become a site.
Owned HTML is ordinary markup. ChatGPT, Claude, or Cursor can change text or add a page once the files are yours.

For the browser save formats themselves, use how to save a website as HTML. This page helps you choose between one saved page and a copy of the whole public site.

Only save or export sites you own or have permission to archive.

What SingleFile saves

The SingleFile extension reads the current tab and writes a SingleFile HTML file. CSS, images, fonts, and frames are stored inside that document. There is no _files folder. There is no .mhtml wrapper.

The Chrome extension and the Firefox add-on do the same job. Open the page, wait until it finishes loading, click the toolbar button, keep the .html file.

SingleFile can also save the selected tabs, the unpinned tabs, or every tab in one pass. Each tab still becomes its own file. Links inside those files usually still point at the live site. Clicking About from a saved homepage takes you back online, unless you also saved About and you open that other file yourself.

SingleFile stays on the tab you opened. It does not discover /about or /blog/my-post from the homepage. It does not rewrite those pages into a local site.

Chrome and Edge also have a built-in Webpage, Single File option. That writes .mhtml, which opens well in Chromium browsers and poorly elsewhere. SingleFile writes real HTML. For the format details, stay on save website as HTML.

What a full-site export saves

A full-site export, snapshot, or mirror starts at a URL you control, follows public links, and downloads the files each page needs. Then it rewrites those references so pages point at each other on disk.

You should expect:

HTML for the homepage and the other public routes you still need
CSS, JavaScript, images, fonts, and public downloads
Internal links that stay inside the copy
A ZIP or a folder you can unzip, click through, and later host

The output is a static snapshot of published pages. The builder project, CMS, forms, carts, memberships, and private dashboards stay on the original host. Public presentation can copy. Backend behavior does not.

If you want the crawl, asset, and rewrite checklist, use how to download an entire website. If the file you care about is the archive, use website to ZIP. If you mainly want pages that open with no live host, use offline website downloaders. The category map is best website downloaders.

When a single file Chrome extension is enough

Use a single file Chrome extension when you only need one URL.

Good fits:

an article or docs page you want to read later
a receipt, invoice, or confirmation page
one landing page as a design or copy reference
a page you want to email or drop in a folder as one attachment
a Firefox or Chrome tab you already have open and do not want to crawl from

SingleFile is faster to run than a crawler. There is no depth cap, no domain list, and no project file. You get one file. That file opens in Chrome, Firefox, Safari, or Edge.

Skip SingleFile as the site tool when you need the rest of the URLs, when nav has to work offline, or when you plan to upload a folder to a static host. One HTML file with inlined assets is a page archive. A website folder has separate pages that link to each other.

When one page is not enough

One page is not enough when the thing you need is a site.

You need a full-site export when:

the homepage menu should open About, Work, and Contact from the copy
you want a brochure site, portfolio, or small business site as files
you are leaving a builder and you need the public pages in one package
you want to click through the copy with the network off
you want to host the public front end somewhere else

A SingleFile HTML file of the homepage can look complete. Every menu link still goes to the live host. Offline, those links fail. Online, you are still using the original site.

Saving ten tabs with SingleFile gives you ten files. You still do not have rewritten internal links, shared CSS files, or a folder you can drop on a static host.

For a conventional HTML site and a terminal, wget mirror is one CLI path. For a hosted snapshot of published pages, Export Your Site is one way to get a ZIP of those pages.

SingleFile vs full-site export

| Job | SingleFile | Full-site export | | --- | --- | --- | | What you start with | The tab you have open | A public URL you own | | What you get | One HTML file | Many pages plus assets in a ZIP or folder | | Links between pages | Still point at the live site | Rewritten to local files | | Chrome and Firefox | SingleFile Chrome and SingleFile Firefox | Browser, desktop crawler, or hosted snapshot | | Offline reading of one URL | The file opens on its own | Works, but more setup than you need | | Browse the whole public site offline | Menu links leave the file | The copy is meant to be clicked through | | Upload to a static host | One packed HTML file | A folder of pages you can upload | | Forms, carts, logins | Shown, not functional | Shown, not functional |

Neither path moves CMS editing, form backends, carts, or member areas. Plan those separately. The public files you do get stay easy to edit.

How to choose

Ask what has to work after you close the live tab.

| You want | Use | | --- | --- | | Keep one page as one file | SingleFile | | Keep one page with a files folder | Browser Save page as, Webpage Complete | | Keep the public site as pages that link to each other | A full-site export |

If someone else will click the menu, they need a multi-page copy. If you only need the article on screen, one file is enough.

A ZIP keeps CSS and images as normal files. A SingleFile HTML file keeps those assets inside the document. ChatGPT, Claude, or Cursor can change a heading or add a page on either kind of output. Separate files are easier to point at.

FAQ

Is SingleFile enough for a whole site?

No. SingleFile saves the current tab, or each selected tab as its own file. It does not crawl the rest of the site or rewrite the menu so those files become a site. For a whole public site, use a full-site export.

What is the difference between a single page save and a full-site export?

A single page save keeps one URL. A full-site export keeps many public URLs plus the assets they share, then rewrites links so the copy still behaves like a site. If you only need the page on screen, save the page. If you need the rest of the nav, export the site.

Does SingleFile work in Firefox?

Yes. The SingleFile Firefox add-on matches the Chrome extension. Wait for the page to load, click the toolbar button, and keep the HTML file. Firefox has no built-in single-file save, so use the extension if you want one self-contained HTML file there.

Does SingleFile work in Chrome?

Yes. SingleFile Chrome installs from the Chrome Web Store and saves the current tab as HTML. Chrome also has Webpage, Single File, which writes MHTML instead of HTML. Use SingleFile when you want a .html file that opens outside Chromium.

What is a SingleFile HTML file?

It is one .html document with the page's images, CSS, fonts, and frames stored inside it. You can open it in any browser. You can edit the text with an AI assistant. You cannot treat that one file as a multi-page website.

Can I save every tab and call it a full-site export?

No. Batch-saving tabs still produces one file per tab. Those files do not point at each other as a site. You would still open each file by hand. A full-site export rewrites the links so the pages connect.

Can I host a SingleFile page as my website?

You can put one HTML file on a host and it will open. Menus, inner routes, and a normal static-site folder layout will not appear unless you export those pages as a site. If hosting is the goal, start with a full-site ZIP.

Is SingleFile better than Save page as?

SingleFile is better when you want one HTML file that opens anywhere. Browser Save page as is better when you want an HTML file plus a _files folder, or when you only need the markup. Neither one downloads the rest of the site.