Syntax highlighting
Tags, attributes, attribute values, comments, and the doctype are colour-coded against the site palette, with matching light and dark themes. Structure you would squint at in a raw dump reads at a glance.
HTML source viewer
Read any page's HTML in a clean viewer
Fetch a public URL and read its complete HTML in the browser: syntax highlighting, in-page search with highlighted matches, a wrap toggle for minified lines, copy, and download. Nothing is executed, nothing is rewritten, and no extension or address-bar scheme is required.
Open the HTML viewer
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.
Inside the source viewer
In-page search with highlighted matches
The Find in source box highlights every match directly in the document as you type, so you can jump to the head, a meta tag, a canonical link, or a component without scrolling thousands of lines.
Wrap toggle for long lines
Minified pages put the whole document on one line. Wrapping soft-breaks long lines to the viewport width; turning it off restores true indentation when you need to read nesting.
Copy the whole document
One click copies the full source to the clipboard and confirms with a brief "Copied", ready to paste into an editor, a diff, or a ticket.
Download as an .html file
Download hands you the same HTML the server returned, saved under a predictable host-and-path filename, so a snapshot survives the tab being closed.
Line numbers and counts
A sticky gutter numbers every line while the code scrolls, and the toolbar reports the line count and size in bytes so you can gauge how large the document really is.
Safe, unmodified, and no install
Nothing is executed
The HTML is shown as text. Scripts, iframes, event handlers, and tracking pixels are never run, so reading a suspicious page here is safer than opening it directly.
Unmodified server response
What you see is the response body after standard content-encoding decoding — nothing is minified, rewritten, or reformatted, so what you inspect is what the origin sent.
No extension or view-source: prefix
Works in Chrome, Firefox, Safari, Edge, and every mobile browser. Nothing to install, and no address-bar scheme to remember — which matters on phones, where view-source: was never supported.
Large documents handled
Documents above 5 MB are truncated rather than killed, and the viewer says so; extremely long documents also report how many of the total lines are rendered.
Clear failure reasons
Up to eight redirects are followed, with a 20-second timeout. When a fetch fails you get the specific reason — DNS, TLS, refused connection, timeout, an HTTP error, or a non-HTML content type.
FAQ
HTML source viewer FAQs
The questions people ask most about this tool — and the limits worth knowing before you rely on it.
Is the HTML viewer free and private?
Yes. Viewing source, searching, wrapping, copying, and downloading cost nothing and need no account. The URL is fetched once on our server, analyzed in memory, and discarded — no history is created.
Is the source code modified before I see it?
No. The viewer renders the response body as received, after the standard decompression a browser performs. Nothing is executed, normalized, or rewritten; documents larger than 5 MB are truncated for display and the viewer tells you when that happens.
Can I view HTML for a site that blocks bots?
Sometimes. We send a normal browser user agent and follow redirects, but aggressive bot protection can still refuse the request. When that happens the error names the cause instead of failing silently.
Can I search inside a minified page?
Yes — search matches are highlighted inline, and the wrap toggle breaks a single enormous line across the viewport. Combined with copying the document into your own editor, even minified markup is workable.
Does the viewer render the page as a browser would?
No, and deliberately so. It shows the raw HTML rather than a rendered DOM, which is the point: you see the server response as a crawler receives it, not what JavaScript has since rewritten.
Related tools