Website HTML Extractor
See the exact HTML a server sends for a page – useful when view-source is blocked on a phone, when you need the source of a page as a file, or to compare what crawlers receive with what your browser shows. Enter an address and the tool downloads the page, shows the source with its size, line and element counts and the response headers, and lets you indent the tags for reading, copy everything or save it as an .html file.
- Encrypted connection
- No sign-up
- Free to use
How to use Website HTML Extractor
- Enter the page address.
- Click “Get HTML”.
- Turn on indentation to read it more easily.
- Copy it or download the .html file.
Website HTML Extractor features
Raw server HTML
Before JavaScript runs.
Indent tags
Optional formatting.
Response headers
Content type, caching, server.
Download
Save as .html.
Safe fetching
Public addresses only, with size and time limits.
Size limit
Up to 2 MB per page.
When to use Website HTML Extractor
- Checking what search engines receive.
- Viewing source on a phone or tablet.
- Saving a page’s markup for reference.
- Debugging server-side rendering.
Website HTML Extractor FAQ
Is this the same as “View source”?
Yes – it is the HTML the server sends, before scripts change the page. The Elements panel in developer tools shows the page after scripts ran.
Can I download a whole website?
No. It fetches one page at a time and does not download images, styles or scripts.
Is the HTML executed?
No. It is displayed as plain text; nothing on the page runs.
Why is the page truncated?
Pages larger than 2 MB are cut at that limit.
Server HTML versus rendered page
Modern sites often send a small HTML shell and build the page with JavaScript. Comparing the server HTML with what you see in the browser shows how much a crawler that does not run scripts would see.
Indenting is only for reading; the download keeps whichever version is shown.
How it works: our server downloads the page once through a guarded fetcher that only connects to public addresses, follows a limited number of redirects and stops after a size and time limit. The HTML is then analysed in your browser as inert text – scripts on the page never run and nothing is stored.
What it cannot see: content and resources that a page adds with JavaScript after it loads, pages behind a login, and servers that block automated requests. For those, open the page in your browser, use its developer tools, or paste the page source where the tool offers a paste option.
Use the results as a starting point: fix the items marked red first, review the yellow warnings in context, and run the check again after a change. Requests are rate-limited to keep the service fair; if you check many pages in a row, wait a few minutes.
Related checks on this site cover the rest of a technical review – speed and Core Web Vitals, security headers, structured data, accessibility and SEO signals – so you can work through a whole site audit one topic at a time.