Skip to content
From published URL to portable files

Download a Website as a ZIP

Paste your website URL, choose public pages and save them as a ZIP of rendered HTML, CSS and JavaScript. No desktop app needed.

Save a website to ZIP, step by step

  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

Your browser’s Save Page As command saves the current page and some of its resources. This website downloader lets you select several public pages and packages their captured files together, with links rewritten between exported pages. Check the links before publishing the copy.

A desktop copier such as HTTrack runs from your computer; this exporter runs online from a public URL. JavaScript rendering, lazy-loaded content and external services affect what each tool can capture. The HTTrack comparison explains when to use each workflow.

A Free ZIP covers one page and keeps images and fonts linked to the original host. Paid exports can download supported assets, but remote dependencies may remain. Test the copy without a network connection if you need offline use.

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 your URL, up to three levels deep, and lists the pages it finds so you can select what to include. Free covers one page per export; Site Pass covers one successful export of up to 50 pages; Pro covers up to 100 pages per site; Agency has no plan-level page cap. See the current plans and limits before exporting.

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

On a JavaScript-built website, the HTML initially sent by the server may contain only part of the visible page. A file-only download can miss content that appears after scripts run. This exporter renders selected public pages in a browser before saving them; the result still depends on what the page exposes and which resources are reachable.

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.

01How it works

Paste your website URL and choose pages.

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.

02How it works

Download your website as HTML files.

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.

03How it works

Test your exported site then publish it.

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.

Paste the published URL into the form above, review the scan and select the pages you want. Choose your export settings and download the ZIP when it is ready. Extract the files and test them through a local web server or temporary hosting. Free covers one page per export; paid options support several pages.

Yes. Free includes up to 10 single-page ZIP exports per month and one successful Free export per domain in total, shared across Free accounts. Images, fonts and other assets may remain linked to the original site, and the exported page includes a small NoCodeExport attribution footer. Paid exports support downloaded assets where available.

The scan lists the public pages it can reach and you select which to export. Free covers one page. A Site Pass covers one successful export of up to 50, 250 or 1,000 pages, depending on the pass; Pro covers up to 100 pages per site; Agency has no plan-level page cap. Private pages, unlinked routes and pages generated only after form submissions may not appear in the scan. Review the page list before treating a download as complete.

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.

You get a snapshot of the public frontend as HTML, CSS and JavaScript, rather than the builder’s editable project. It does not include private pages, server code or CMS databases. Use it for a static handoff, archive or migration reference after testing the exported files.

Save Page As saves the current document and some of its resources. This tool renders selected public pages in a browser and packages their captured files together, with links rewritten between exported pages. Both approaches can leave remote dependencies; test the pages, assets and interactions you need.

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

Use an exporter for a static archive, a frontend handoff or a migration reference. A rebuild is more appropriate when you need an editable source project, a different architecture, CMS changes or application features. Test the export before relying on it for hosting or a backup.