The byte-for-byte response
The saved file is the HTML the server returned, unmodified. Nothing is prettified, normalised, rewritten, or escaped on the way out, so a diff against a later fetch shows real changes rather than formatting noise.
Download source
Fetch any public page and save its markup as a single .html file — the exact bytes the server returned, named after the host and path, encoded as UTF-8, and ready to open in your editor, diff against a later fetch, or feed into your own tooling.
Paste any public URL into the analyzer to read its raw source, run the SEO audit, grade its security headers, and detect the technologies it uses — free, with no signup and nothing stored.
The saved file is the HTML the server returned, unmodified. Nothing is prettified, normalised, rewritten, or escaped on the way out, so a diff against a later fetch shows real changes rather than formatting noise.
Files are named from the host and path: the homepage of example.com saves as example.com-index.html, and example.com/about/ saves as example.com-about.html, so a folder of downloads stays self-describing.
The download is written as text/html with UTF-8 encoding, which opens cleanly in VS Code, Sublime Text, Notepad++, or a terminal pager without a mojibake round trip.
Documents larger than 5 MB are truncated for display and the viewer tells you when that happened, so you always know whether the file you saved is the whole page or the first part of it.
What you get is the document itself — not a saved copy of the on-screen viewer — so the markup is intact and immediately parseable by any tool you point at it.
Inline script and style blocks are part of the document and come down with it, which is often where the interesting configuration lives.
Enter a domain or a full URL and run the analysis. The page is fetched once by our server and the complete source is rendered in the viewer.
The Source tab is selected by default. Scroll it, search it, or switch on the wrap toggle if you want to read long lines without horizontal scrolling.
The Download button in the viewer toolbar assembles a Blob from the fetched source and saves it under the generated file name. No extra server round trip is needed — the HTML is already on the page.
If you only need a fragment, use Copy to place the entire document on the clipboard and paste it straight into your editor, your ticket, or a diff tool.
Keep a timestamped copy of a page as it was served — useful for compliance notes, migration records, or demonstrating what changed and when.
Download a page before and after a deploy and diff the two files to isolate exactly which markup changed, without a proxy or a version control system in the middle.
A local HTML file works with grep, ripgrep, an HTML parser, or a scraper prototype — no rate limits, no live network, and no repeated requests to someone else’s server.
FAQ
The questions people ask most about this tool — and the limits worth knowing before you rely on it.
You are saving the same publicly served HTML that your browser already receives when you visit the page. Only download sources you are entitled to access, and remember that the underlying content, code, and design remain subject to the site owner’s copyright and terms — retrieval is not a licence to reuse them.
There is a 5 MB limit on the source we hold and display. Pages above that ceiling are cut off, and the viewer labels the result as truncated. Applications with heavy inlined data or base64 assets are the usual candidates; most ordinary pages sit far below the limit.
It includes the HTML document itself, which contains the references to those resources. Inline script and style blocks come with it, but external files are not fetched. This is a page’s source, not a complete offline archive of the website.
Sometimes. We send a normal browser user agent and follow up to eight redirects, but a site that blocks automated traffic may still refuse the request. When that happens the result names the failure — DNS, connection, TLS, or timeout — so you know it was access, not the tool.
No. The page is fetched, analyzed in memory, and discarded at the end of the request. There is no stored history and no account, so the copy on your disk is the only copy that exists.
Related tools