Downloading a website's HTML means saving the single file that tells a browser what a page should say and how it should be structured. It is the lightest way to keep a copy of a page: one file, no installer, no extra software. The trade is that the file on its own is only part of the page. The styles, images, and scripts usually live in separate files, and the behavior that makes a page interactive lives on a server. If you want a record of the words and structure, the HTML file is enough. If you want the page to look and work the way it does online, you need more than the HTML. This guide covers the three practical ways to download HTML, what each one gives you, and where an HTML file stops being useful.
What downloading a website's HTML actually gives you
HTML is the document behind every web page. It holds the headings, the paragraphs, the links, and the references to everything else the page needs. When you download the HTML, you keep the words and the structure, and you keep the references to the images, stylesheets, and scripts. You do not keep those files themselves. Open the saved file with your connection off and the words will still be there, usually without the styling, because the stylesheet never came along. That is the honest picture: an HTML file is a record of a page's content, not a working copy of the page. It is useful for reading, quoting, studying markup, and archiving text. It is not a backup of a site, and it is not an editable version of the site.
Method 1: save the HTML from your browser
Every major browser can save the HTML of the page you are looking at, and it takes about ten seconds. Open the page, then use Save page as. Your browser will offer two options, and the choice matters. HTML Only saves a single .html file with the page's markup and nothing else. Complete saves the same file plus a folder of the assets the page needs, so the saved copy looks closer to the original. Pick HTML Only when you want just the source, and Complete when you want the page to look right offline. There is a second route to the same file: type view-source: before the URL in the address bar, or press Ctrl+U on Windows or Cmd+Option+U on Mac, and the browser shows the raw source. Save that view and you have the HTML file. This method works one page at a time, which is fine for a single article or landing page and slow for a whole site. Our guide on how to download a website covers the whole-site methods.
Method 2: download the HTML with one terminal command
If you are comfortable with a terminal, one command downloads the HTML of any public page. With curl, run curl -L -o page.html followed by the page URL. The -L flag follows redirects, so a short link or a moved page still resolves, and -o names the file you want. With wget, run wget followed by the URL, and the page saves under its own name. Both tools fetch exactly what the server sends for that URL, which is the same HTML your browser receives before JavaScript runs. That has two consequences worth knowing. First, pages that build their content with JavaScript will give you a mostly empty HTML file, because the words arrive later through scripts. Second, a page behind a login will give you the login page's HTML, not the content you wanted, because the server does not know who you are. For a single public page, the terminal is the fastest method. For a whole site with assets and working links, use the mirror methods in our website mirror guide.
Method 3: copy the HTML from developer tools
Developer tools give you a third option, and it is the only one that captures the page after JavaScript has run. Open the page in your browser, press F12, and find the Elements panel. Right-click the top html element, choose Copy, then Copy outerHTML, and paste the result into a text editor and save it with an .html extension. What you get is the live document: the markup as the browser sees it now, including content that scripts added after the page loaded. That makes it the best method for a JavaScript heavy page, where view-source and curl return a skeleton. The trade is that the copy reflects the current state of the page, including anything a script changed, so it is not the same as the file the server sent. Use view-source when you want the original, and developer tools when you want what is actually on screen.
What the HTML file does not include
An HTML file on its own is a partial copy, and knowing what is missing saves you a surprise later. The stylesheet that controls the layout and fonts is a separate file, so a saved page often looks plain and unstyled. Images, fonts, and videos are separate files too, referenced by address, so they show as broken or missing when you open the file offline. Scripts are separate files as well, and without them any interactive part of the page stays dead. Anything that needs the server is gone entirely: search, login, shopping carts, comments, and personalised feeds all run on a backend that a download cannot bring along. If the page you saved looks bare, that is normal. The HTML did its job. The rest of the page simply was not in the file. Our explainer on what a website downloader is lays out the same limits for full downloads.
When an HTML file is enough and when it is not
An HTML file is enough when the words and structure are the point. Keep the text of an article you want to quote, study how a landing page is put together, archive a page before a redesign, or check what a search engine sees in the raw source. In each case the single file does the job, and anything more would be weight you do not need. It is not enough when you need the page to look right, work offline, or become something you can change. A styled offline copy needs the assets and rewritten links, which is what a mirror does. An editable version you can change and publish needs a rebuild, not a file. If you already have a page's HTML and want to turn it into a site you can edit, our guide on cloning a website to HTML covers the rebuild path. Match the tool to the job, and the HTML file stays useful instead of disappointing.
Run the permission check first
Only download HTML from a site you own, or a site you have permission to copy. Saving a page for your own reading, backup, or study is a normal use. Downloading someone else's pages to republish their words, images, or branding is not, and neither is using a download to bypass a paywall or scrape content at a scale the site never agreed to. Check the site's terms, respect robots.txt, and keep the request rate gentle so a download does not hammer a small server. If the content belongs to someone else, ask. The answer is often yes when the use is private, and asking costs less than the cleanup when it is not.
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.