Downloading a website means saving its files to your own computer so you can open them without a connection, keep an archive, or migrate content you own. It sounds simple, and for one page it is. For a whole site it takes a little care, because a modern page is not one file: it is HTML plus stylesheets, images, scripts, and fonts, some of which may live on other servers or load only after you sign in. This guide covers the three methods that actually work, the permission check to run first, and the point where a raw download stops being useful and a rebuild takes over.
Download a website versus clone a website
A download preserves the original files. You get the pages, assets, and structure as they were served, and you can browse them offline or keep them as a record. A clone rebuilds the visible design as editable pages you can change, rebrand, and publish. The distinction matters because the two jobs have different tools and different legal limits. If you want an archive of your own site before a redesign, download it. If you want to redesign a site you own, or rebuild a layout you have permission to reuse, you need an editable version, not a pile of files. Our guide to the difference between a website cloner and a website downloader walks through that choice in more detail.
Run the permission check first
Before you download anything, confirm you have a right to keep the copy. Your own site is straightforward. A client's site needs the client's agreement. A competitor's or a publisher's site does not become yours because it is publicly visible, and public visibility is not a license to republish. Respect robots.txt, which is a site's machine readable request about automated copying, and respect terms of use and login walls. If the goal is to study a design, save a reference for your own team and write your own copy and assets. If the goal is to publish, the content must be yours or licensed. This check takes two minutes and it is the step people skip most often.
Method 1: save a single page from your browser
For one article, one landing page, or one reference page, the browser is enough. Open the page, choose Save Page As, and pick the complete page option rather than HTML only. The complete option saves the HTML file plus a folder of assets, so images and styles usually survive offline. This method is fast and needs no extra software, but it has clear limits. It saves one page, not the pages it links to, and content that loads dynamically or behind a login may be missing. Use it for references and single page archives, not for whole sites.
Method 2: mirror a whole site with HTTrack
HTTrack is a free, open source website copier for Windows, Mac, and Linux, and it is the most approachable way to mirror a small or medium site. Enter the starting URL, set a destination folder, and let it follow links within the site, rewriting them so the local copy works offline. Before a large mirror, set sensible limits: restrict the crawl to the domain you intend to copy, cap the depth or total size, and exclude sections you do not need, such as huge media libraries or paginated archives. A mirror without limits can run for hours and pull far more than you wanted. After it finishes, open the local index page and click through the main sections to confirm the navigation, images, and styles all work offline.
Method 3: mirror a site from the terminal with wget
If you are comfortable with a terminal, wget gives you precise control in one command. A common starting point is wget with recursive downloading, page requisites, and link conversion, limited to the target domain, so assets are saved and links are rewritten for local browsing. Add a wait between requests so you do not hammer the server, and set a level limit if you only need the top sections. The tradeoff is that wget copies files, not behavior: search, forms, logins, and checkouts will not work in the local copy, and pages generated from a database may export as static snapshots that go stale. For a technical archive or a pre migration backup of a site you own, that is usually fine. For anything you plan to edit and publish, a static snapshot is a starting point, not a finished site.
What a raw download cannot do
A downloaded site is a snapshot, not a working product. Forms will not submit anywhere useful, logins will not authenticate, carts and payments will not run, and any content fed by an API or database will freeze at the moment of download. Branding, copy, and photography in the copy still belong to the original owner unless you own them or hold a license. If your plan is to publish, you still have to replace the content, rebuild the interactive parts, and host the result yourself. Our guide on how to host a cloned website covers the hosting step once the content is yours and ready. Treat the download as raw material and the published site as a separate job.
When a rebuild beats a raw download
Choose a rebuild when you need to change the design, replace the content, or publish the result under your own brand. A rebuild gives you editable pages, clean structure, and a preview you can check before anything goes live, instead of a folder of original files you have to untangle by hand. With Kloner, you can start with a free preview to see the rebuilt design, and editing and publishing depend on your plan. That preview step is the practical test: if the rebuild looks right and the content is yours to publish, it is worth more than a perfect archive of someone else's files. If all you need is an offline record, stay with the browser save or the mirror and skip the rebuild entirely.
Check the download before you rely on it
A download is only useful if you verify it. Open the local copy in a browser with your connection off or with the site blocked, and click through the homepage, two or three inner pages, and any page you actually care about. Look for missing images, unstyled sections, links that jump back to the live site, and pages that show a login wall. Fix broken asset paths by re-running the mirror with requisites included, or accept the gap and note it in the archive. For a backup of your own site, repeat the download on a schedule and store at least one copy away from the machine that made it. An unverified download is a folder of files, not a backup.
Start with Kloner’s website cloner
Use Kloner’s website cloner with a supported public URL to generate a preview. Review and customize your website before deployment. Editing and publishing depend on your plan.