You want to see how a website is built. Maybe you're learning, maybe you're debugging your own site, maybe you saw a component you'd love to recreate. Whatever the reason, "how do I see the code of this website?" has a few different answers depending on what you actually need.
Here's every method, from the 2-second keyboard shortcut to the clean one-click export — and when to use which.
The fastest way: View Source (Ctrl+U)
Right-click anywhere on a page and choose View Page Source, or just press:
- Windows / Linux:
Ctrl + U - Mac:
Cmd + Option + U
This opens a new tab showing the raw HTML document the server sent to your browser. It's the original source, before any JavaScript has run.
Use it when: you want a quick look at the page's markup, meta tags, or linked scripts and stylesheets.
The catch: on modern sites built with React, Vue, Svelte, or any JavaScript framework, View Source often shows almost nothing — just an empty <div id="app"> and a bundle of script tags. The real content gets built by JavaScript after the page loads, so it never appears in the original source.
That's where DevTools comes in.
The complete way: DevTools and Inspect Element
To see the live, rendered page — the actual HTML and CSS as it exists right now, including everything JavaScript added — open the browser's developer tools:
- Windows / Linux:
F12orCtrl + Shift + I - Mac:
Cmd + Option + I
Or right-click any element and choose Inspect.
The Elements tab shows the live DOM. Click any element and the Styles panel on the right shows the CSS rules applying to it. Hover over nodes to highlight them on the page.
Use it when: you need to see the real structure of a modern site, debug layout issues, or understand how a specific element is styled.
The catch: copying from here is tedious. Right-click an element → Copy gives you options:
- Copy element — the HTML of that one node
- Copy styles — its computed styles
- Copy selector — a CSS path to it
But you have to do this element by element, and "Copy styles" gives you one node's computed values — not the full cascade, not the inherited rules, not the CSS of the children. Paste it into a new project and it almost never looks right.
How to copy a website's HTML and CSS (and why it usually breaks)
This is the part most guides skip. Seeing the code is easy. Copying it so it actually works elsewhere is the hard part.
When you copy HTML from View Source or DevTools, you get the structure — but the styling lives in separate stylesheets the HTML only references. So you paste your copied HTML into a blank file and get an unstyled skeleton.
When you copy an element's computed styles from DevTools, you get a flat dump of that one node's final values — but you lose:
- The styles on its child elements
- Inherited properties from parents
- Hover states, media queries, and animations
- The clean class structure (you get a giant inline blob instead)
So you end up reconstructing the component by hand anyway. For a single button, fine. For a hero section, a pricing table, or a navbar, it's an afternoon.
The one-click way: extract clean code with MiroMiro
If your goal is to actually reuse what you see — not just look at it — there's a faster path.
MiroMiro is a free Chrome extension that lets you click any element or section on a live website and get its complete, clean code in one step:
- HTML + the CSS that actually applies to it — bundled, not referenced
- Clean Tailwind output (matching the utility classes the site uses) or vanilla HTML + CSS
- The whole component — children, nested elements, real structure — not one node at a time
- Colors, fonts, SVGs, and assets alongside the markup
So instead of Ctrl+U → squint → copy → paste → rebuild, it's: click the section → copy → paste. Done.
When to use which method
| You want to… | Use |
|---|---|
| Quickly peek at a page's raw HTML / meta tags | View Source (Ctrl+U) |
| See the live structure of a modern JS site | DevTools → Elements (F12) |
| Debug why one element is styled a certain way | DevTools → Styles panel |
| Copy one element's HTML for reference | DevTools → Copy element |
| Grab a whole component as clean, reusable code | MiroMiro (one click) |
| Feed real code to Cursor / Claude / v0 / Lovable | MiroMiro → paste as context |
Copying code for AI coding tools
This last row is worth its own note, because it's where most people waste the most time.
If you've been screenshotting a website and pasting the image into Cursor or v0 hoping it rebuilds the design — the output is mediocre because the input is a guess. AI tools recreate from pixels and hallucinate the structure.
Give them the real code instead. Extract the section as clean HTML + Tailwind with MiroMiro, paste it in as context, and the AI works from what the site actually ships — not what it thinks the screenshot might mean. The quality jump is immediate.
Try it
Next time you want to see and use the code behind a website, skip the copy-paste-rebuild loop.
Install MiroMiro for free and copy your first clean component in under 30 seconds.
One less monthly bill in your stack
If you build for a living, you're probably already paying for Cursor, Claude, v0, maybe Figma — €75+/month, every month, before you ship anything. MiroMiro is the one tool in that workflow that doesn't have to be another recurring bill:
The lifetime math
Your AI/design stack, monthly
- Cursor€20/mo
- Claude Pro€20/mo
- v0€20/mo
- Figma Dev Mode€15/mo
- MiroMiro Pro (monthly)€9/mo
Every year. Forever. Until you cancel.
MiroMiro lifetime — one-time
Paid once. Used forever. No renewals.
- Pays for itself in 6 months vs Pro monthly
- €59 saved in year 1 alone
- One less monthly bill in your stack, permanently
¿Listo para acelerar tu flujo de trabajo?
Únete a más de 8.000 diseñadores y desarrolladores que ahorran horas cada semana con MiroMiro.
