Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteTo view the HTML behind a URL, use View Page Source or enter view-source:https://example.com/ in your browser for the original document returned by the server. To see the page after JavaScript has changed it, open Developer Tools and inspect the Elements or Inspector panel. Use Network when you need the actual document response, headers, redirects, or related requests.
First choose which HTML you need
“HTML from a URL” can mean several different things. A browser receives an initial document, parses it into a DOM, loads other resources, and may run scripts that alter the page. Those stages do not necessarily contain the same markup.
| Method | What it shows | Best for | Main limitation |
|---|---|---|---|
View Page Source or view-source: |
The initial HTML response | Static markup, early metadata, canonical links, and scripts present in the original document | It generally does not show content added later by JavaScript |
| Elements or Inspector | The live parsed DOM | Inspecting the page structure and styles as they exist in the open browser tab | The DOM may differ from the original response |
| Network document response | The document request and its response details | Checking headers, redirects, status, and the original response alongside later requests | Requires Developer Tools; reload the page to capture requests |
| Sources | Files loaded by the page | Finding scripts, stylesheets, and other assets | It does not, by itself, explain every change made at runtime |
| Google Search Console or Rich Results Test | A rendered view available to Google’s inspection tools | SEO and rendered-page checks | Fetchability and, for Search Console, site-owner access affect availability |
How to view the original HTML source from a URL
- Open the page in a browser, then right-click the page and choose View Page Source. The wording or menu placement can vary by browser.
- Alternatively, enter
view-source:followed immediately by the full URL in the address bar, such asview-source:https://example.com/path, and press Enter. - Use the browser’s find function to look for a tag, phrase, metadata field, or URL in the returned source.
This view is useful for checking markup that the server initially delivered, including metadata and canonical links. Google Search Console Help distinguishes this original code from rendered inspection: ordinary “show source” displays what was returned before scripts and other resources were loaded and run. If a page fills in its text or product details with JavaScript, that later content may not appear in View Page Source.
When View Page Source is the right choice
- You want to confirm whether a title, description, canonical link, or other markup is present in the initial HTML.
- You need to see the document before client-side scripts change the page.
- You are comparing the server-delivered markup with what appears after the browser finishes loading.
How to inspect the live DOM in Developer Tools
- Open the page you want to inspect.
- Open Developer Tools using the browser’s page context menu, or a common shortcut:
Ctrl+Shift+IorF12on Windows;Command+Option+Ion macOS. - Select Elements in Chrome and most Chromium browsers, or Inspector in Firefox and Safari.
- Expand the document tree or search within the panel to find the element you need. Select a node to examine its markup and associated styles.
The Elements/Inspector panel represents the DOM at runtime: the document structure after the browser has parsed the page and scripts or other page activity may have changed it. MDN describes the inspector as showing what the HTML looks like at runtime and what CSS applies to each element. This makes it the better choice when you need to investigate what the current tab has actually built, rather than only what the server first sent.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Copying or finding an element
Use the panel’s search function to locate a visible label, class, ID, or other text. Expand nearby nodes to understand their parent-child structure. Browser context menus on a selected node commonly provide options to copy that element’s HTML, though exact menu labels can differ. Treat the result as a snapshot of the current DOM, not proof that the same markup was present in the original response.
How to inspect the HTML response and network requests
- Open Developer Tools and select Network.
- Reload the page while the panel is open so the browser records a fresh set of requests.
- Select the main document request, usually the entry whose type is document and whose address matches the page URL.
- Inspect its response and headers. Then compare it with other requests, such as API calls, scripts, stylesheets, and images.
Use this method when the question is not merely “what markup is on the page?” but “what did this URL return?” or “where did this later content come from?” The document response is distinct from data returned by later API calls. Redirects and response status are also visible in the request details. Chrome DevTools documents the Network panel as a way to inspect requests and responses; Safari Web Inspector also exposes network activity along with rendering and other inspection details.
When to open Sources
Choose Sources when you need to browse files the page loaded, such as JavaScript and CSS. Chrome’s documentation describes the panel as supporting file viewing, editing CSS and JavaScript, and creating JavaScript snippets. Finding a file there helps identify available resources, but it does not automatically explain which script changed a particular DOM node or when that change occurred.
How to view Google’s rendered HTML
For a site you manage: Search Console URL Inspection
Use Search Console’s URL Inspection workflow for a site you have access to manage. Testing a live URL can expose an HTML view of Google’s rendered page. This is useful when checking how Google’s inspection process sees a page, rather than treating the browser’s initial source as the whole story. Search Console is an owner-oriented workflow, so it is not a general way to inspect arbitrary websites.
Recommended Free Tools
For a public URL: Rich Results Test
Google’s Rich Results Test can inspect a public URL that Google can access, provided it is not blocked by robots.txt and does not require a login. It can show rendered HTML for the fetched page. If the test cannot access the URL, it cannot provide a useful rendered view; do not assume that a result reflects content hidden behind authentication or unavailable to Google’s fetcher.
Why source, DOM, and rendered HTML can disagree
- Initial HTML versus script-generated content: View Page Source shows the original response; Elements/Inspector shows the current DOM after parsing and any script-driven changes.
- Document versus subsequent data: The main document may include only an application shell while later network requests supply page content.
- Different inspection contexts: A live browser tab and Google’s inspection tools may fetch or render a URL under different access conditions. A login requirement or robots.txt restriction can prevent Google’s tools from inspecting a URL.
- DOM versus loaded files: Sources helps locate files; Elements shows the current document tree. One view is not a substitute for the other.
For a careful check, compare the initial source, the document response in Network, and the live DOM. The differences often tell you whether markup came from the server, a later request, or browser-side execution.
Or skip the browser setup
If your goal is a visual capture rather than reading or debugging HTML, ScreenshotNeo is a website screenshot API and MCP server. A screenshot is an image of the rendered page, not the page’s HTML source. Its API can return PNG, JPEG, WebP, or PDF; the example below saves a WebP capture. See the ScreenshotNeo documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpBefore capture, ScreenshotNeo accepts the cookie or consent banner like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each of those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Every feature is on every plan.
Sign up free for 1,000 screenshots a month, with no card required.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting: common problems viewing HTML
The page source does not contain text I can see
You are likely looking at the initial response while the page adds or fetches content later. Inspect the live DOM in Elements/Inspector, then use Network to see whether another request supplied the missing data.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Developer Tools will not open with the shortcut
Shortcuts can differ by browser, operating system, or keyboard layout. Use the page context menu to open Developer Tools, then select Elements/Inspector or Network from its tabs.
The Network panel appears empty
Open Network before reloading; it records requests made while it is active. Reload the page, then select the main document request rather than a script or image if you need the HTML document response.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Google’s inspection tool cannot show the rendered page
Check whether the URL is public, fetchable by Google, and not blocked by robots.txt. Search Console URL Inspection also requires access to the relevant site property; for a public URL outside your property, try the Rich Results Test if its access conditions are met.
Best Value
The HTML you copied does not match what you see now
Confirm which representation you copied. Page Source is the original response; copied markup from Elements is from the live DOM. If the discrepancy remains unclear, compare both with the main document response and related requests in Network.
Frequently Asked Questions
Can I view a URL’s HTML without opening Developer Tools?
Yes. Open the page’s View Page Source command or enter a `view-source:` URL in the address bar. That shows the initial document response, not necessarily content later added by scripts.
Does a screenshot show me the HTML?
No. A screenshot is a visual image of a rendered page. Use View Page Source, Elements/Inspector, or Network when you need markup.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Which browser panel shows CSS applied to an element?
Select the element in Elements or Inspector; the developer tools show its runtime DOM context and associated CSS.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
