Skip to content
From published URL to portable files

Download a Website as a ZIP

Paste a public URL, pick the pages you want and download the rendered HTML, CSS, JavaScript and assets as one ZIP.

From website URL to ZIP download

  1. Paste the published URL into the exporter above.
  2. Review the scan and select the pages available within your plan.
  3. Choose asset handling, create the export and download the ZIP when it is ready.
  4. Unzip the files and test them through a local web server or temporary hosting before publishing.

A ZIP is the package, not proof that every page or dependency was captured. Check the selected routes and any warnings in the download.

What is included—and what may still load online

The export contains captured page HTML and the styles and scripts the exporter could retrieve. On Free, images and fonts remain linked to their source. Eligible paid exports offer asset downloading; files that cannot be retrieved and services such as video embeds can still need an internet connection.

Saving one page in your browser, exporting selected website pages and recovering an editable source project are different tasks. This tool captures the public frontend. It does not recover private pages, CMS databases, server code or the original builder project.

Before using the ZIP offline or switching hosts, test routes, assets and interactions. Forms, search, accounts and payments may need replacement services. The copy-HTML guide explains browser methods; the exporter comparison helps you choose a workflow.

Website downloader vs. saving a page in your browser

Save Page As keeps one document and whatever files that page happens to reference. A website downloader walks the routes you select and packages them together, so internal links still resolve when you open the copy offline. That is the difference between a saved page and a full website download.

Desktop website copiers such as HTTrack crawl from your own machine and have to be installed and configured first; this exporter runs from a public URL and hands back a ZIP. The HTTrack comparison covers when a local crawler is still the better tool, which is usually very large archives.

A free export covers a single page and leaves images and fonts linked to their source, so a copy that works offline needs a paid export that downloads them. Download only sites you own or have written permission to copy.

HTML downloader: one page's source, or the whole site

An HTML downloader can mean two different jobs. Fetching a single page's source gives you the markup the server sent, which on a JavaScript-built site is often a near-empty shell. This tool opens the page in a real browser first and saves the HTML after it has rendered, along with the CSS and JavaScript it loaded.

For one page, a free export is enough to download a website's source code and inspect it. For several pages, select them in the scan and they arrive in one ZIP, with their internal links rewritten to work between the saved files.

Download an entire website

The scan follows internal links from the URL you paste, up to three levels deep, and lists the pages it found so you choose what to include before anything is downloaded. Free exports cover a single page. Pro covers up to 100 pages per site and Agency has no page limit.

Pages behind a login, pages nothing links to and anything generated only after a form submission cannot be reached, so they are not part of the download. Check the scan's page list against your sitemap before you rely on the copy as complete.

Website to HTML: why JavaScript-built sites need a rendering converter

Converting a website to HTML used to mean saving the files a server sent. Sites built in Framer, Webflow, Wix or a React framework assemble most of the page in the browser, so a tool that only fetches files — wget, a desktop copier such as HTTrack, most online website copiers — saves the scaffolding and misses the content.

This converter renders each page in a browser, scrolls it so lazy-loaded sections and images appear, and only then writes the HTML. The result is a static snapshot of the public frontend. It is not the original builder project, and forms, search, accounts and payments still need their own replacements.

How it works·01

Paste your website URL and choose pages.

scanning…
Pages found0
  • /
  • /about
  • /blog/*
  • /pricing
  • /contact
Choose what to include
1

Paste the public website link

Copy the address of your published site, not its editor. The page must open without a login.

2

Choose the pages to export

The scan follows links up to three levels deep. Select the pages you need from the results, within your plan’s limit.

How it works·02

Download your website as HTML files.

yoursite.com
HTML
IMAGES
CSS
JS
Inside your ZIP download

Page content and design

The public pages and styles visitors see in their browser. The original editor and source project are not included. Review page titles and search settings before publishing.

Images and fonts

Choose downloaded assets to include available images and fonts. Free exports keep them linked to the original site. Videos and embeds may still need an internet connection.

Menus and animations

Interactions can work when their scripts and external services remain available. Accounts, databases and payments need separate services.

How it works·03

Test your exported site then publish it.

website-export.zip
Vercel
Netlify
Cloudflare
GitHub
Choose your hosting
1

Test the exported site

Unzip the download and open the files through a local web server or temporary hosting. Check layouts, links, forms and animations on desktop and mobile.

2

Publish on your chosen host

Upload the tested files to Vercel, Netlify, Cloudflare Pages or GitHub Pages. Check the live site before changing your domain. Hosting costs and provider terms apply.

Before you move your domain. Private pages, the original source project, APIs, databases, accounts, payments and server-side features are not included. Connect the services your site needs before going live.

Common Questions

Review what the workflow covers, what needs separate implementation, and what to verify before making a change.

It exports the rendered frontend of a public website as portable HTML, CSS, JavaScript, and reachable resources. It is best suited for marketing sites, landing pages, documentation, brochure sites, archives, and migration baselines.

Not exactly. You get a portable frontend snapshot rather than the builder’s internal project format. That is usually enough for self-hosting, audits, backups, and migration planning, but not the same as native design-editing source files.

Use an exporter when you need a fast backup, a deployable frontend handoff, or a migration baseline. Rebuilding from scratch makes more sense when you need a new architecture, deep CMS changes, or application-level functionality.

Paste a public URL you own or are authorized to export, scan it, select the pages within your plan and run the export. Download the ZIP when it is ready, extract it and test the files through a local web server or temporary hosting. A single-page export and a selected-page site export have different scope.

Free exports keep images and fonts linked to the original host. Eligible paid exports let you download reachable assets and rewrite their references. Inaccessible resources, videos and third-party embeds may remain remote, so review the downloaded files and failed requests before turning off the original site.

Not necessarily. A ZIP can still contain references to remote assets and services. Test with the network disconnected to identify dependencies. Forms, search, authentication, payments and live CMS updates are not made offline by downloading the public pages; replace or remove those dependencies for your intended use.

Yes, in the sense that it copies the public pages of a site you own or are authorized to export, from a URL, with nothing to install. It saves the rendered HTML, CSS and JavaScript as a ZIP. It does not copy private pages, a CMS database, server code or the original builder project.

Both. The scan lists the pages it can reach and you choose which to include. Free exports cover a single page. Pro covers up to 100 pages per site and Agency has no page limit.

Save Page As keeps one document and the files it references. This tool renders each selected page in a browser, follows your internal links and packages the pages together, so links between them still work. Desktop copiers such as HTTrack fetch files without rendering them, which is why JavaScript-built sites often come out empty.