---
title: "How to Use Inspect Element in Chrome, Safari and Firefox"
description: "Inspect element opens the code behind any part of a web page. See the shortcut in Chrome, Safari, Firefox and Edge, how to edit safely and what it cannot do."
url: https://proxynet.io/blog/inspect-element
date: 2026-11-18
author: "Acar Diveroli"
category: "Tutorial, Web Scraping"
lang: en
---

# How to Use Inspect Element in Chrome, Safari and Firefox

The "Add to basket" button on your shop looks fine on your laptop, but a customer sends a screenshot where its label breaks onto two lines. You right-click the button, choose **Inspect**, and a panel opens beside the page with the code that draws it: the HTML tag, its class and a CSS rule whose fixed width is too narrow for the label. You found the cause without opening a single file on the server.

This post explains what inspect element is and how to open it in Chrome, Edge, Firefox and Safari. It then covers reading and editing an element, the other panels, the phone layout view, inspecting a page on Android or iPhone, what your edits can and cannot do, and why the tool is sometimes switched off.

> **Note: Short answer**
>
> Inspect element is the browser's built-in tool for looking at the code behind any part of a web page. Right-click the part you are curious about and choose Inspect (Inspect Element in Safari), or press Ctrl + Shift + C on Windows and Cmd + Option + C on a Mac in Chrome, Edge and Firefox. Safari first needs "Show features for web developers" turned on in Settings > Advanced; after that, Shift + Cmd + C starts the same picker. The panel shows the page's live HTML and CSS, and you can edit both to try an idea, but the edits change only your own screen and disappear when you reload.

## What is inspect element?

Inspect element is the command that opens a browser's developer tools (DevTools) with one part of the page selected. Developer tools are a set of panels built into every major desktop browser; the first one is called **Elements** in Chrome, Edge and Safari and **Inspector** in Firefox.

That panel shows the page as a tree of nested tags, called the DOM (Document Object Model). The DOM is the browser's live copy of the page: it starts from the HTML the server sent and changes as scripts run, menus open and new items load. Beside the tree, the **Styles** pane lists every CSS rule that applies to the selected tag, the code that decides colours, sizes and spacing.

Nothing has to be installed. The tools ship with the browser, and opening them changes nothing on the website itself.

## How do you open inspect element?

The quickest route in every browser is the right-click menu: right-click the text, image or button you want to examine and choose **Inspect**. Chrome, Edge and Firefox use that label; Safari calls it **Inspect Element**. The panel opens with that element highlighted.

The keyboard shortcuts below start a picker instead: move the pointer over the page, and each element lights up with its size and spacing until you click one.

| Browser | Windows / Linux | macOS | Menu route |
|---|---|---|---|
| Chrome | `Ctrl + Shift + C` | `Cmd + Option + C` | ⋮ > More Tools > Developer Tools |
| Edge | `Ctrl + Shift + C` | `Cmd + Option + C` | … > More tools > Developer tools |
| Firefox | `Ctrl + Shift + C` | `Cmd + Option + C` | ☰ > More tools > Web Developer Tools |
| Safari | Mac only | `Shift + Cmd + C` | Develop > Show Web Inspector |

To open the tools without picking anything, press **F12** or **Ctrl + Shift + I** on Windows and Linux, or **Cmd + Option + I** on a Mac, Safari included. These open the panel you used last; on many laptops F12 also controls brightness or volume, so hold **Fn** with it. Chrome's [guide to opening DevTools](https://developer.chrome.com/docs/devtools/open) adds **Ctrl + Shift + J** (**Cmd + Option + J** on a Mac), which jumps straight to the Console.

### Safari: turn on the developer features first

Safari hides its developer tools until you enable them once. Apple's page on [enabling the developer features](https://developer.apple.com/documentation/safari-developer-tools/enabling-developer-features) gives three steps:

1. In the menu bar, choose **Safari > Settings…**.
2. Open the **Advanced** pane.
3. Tick **Show features for web developers**.

A **Develop** menu now appears in the menu bar, with **Show Web Inspector**, **Show JavaScript Console**, **Show Page Source** and **Start Element Selection** among its items.

## How do you use inspect element, step by step?

You use it in five moves: pick the element, read its HTML, read its CSS, try a change, then undo. With the button from the introduction:

1. **Pick the element.** Right-click the button and choose **Inspect**. Its tag is highlighted in the tree, for example `<button class="add-to-basket">`. Hovering over other lines highlights the matching part of the page.
2. **Read the HTML.** The tag name tells you what the element is: `button`, `a` for a link, `img` for an image, `h1` for the main heading. The `class` and `id` values are labels the site's CSS and scripts use to find it.
3. **Read the CSS.** The **Styles** pane lists the rules in order of priority; a rule with a line through it has been overridden. The **Computed** pane shows the final values, including width, padding and margin.
4. **Try a change.** Double-click text inside a tag to edit it, or click a value such as `width: 120px` and type `auto`. Untick a declaration to switch it off, or press **H** to hide the element.
5. **Undo.** Press **Ctrl + Z** (**Cmd + Z** on a Mac), or reload. Chrome's documentation is plain about it: "If you reload either DevTools or your page, the changes disappear."

## What does each developer tools panel do?

Each panel shows one layer of what the browser did to build the page. The names differ slightly between browsers:

| Chrome and Edge | Firefox | Safari | What you see |
|---|---|---|---|
| Elements | Inspector | Elements | Live HTML and CSS |
| Console | Web Console | Console | Errors and script messages |
| Network | Network Monitor | Network | Every file and request |
| Application | Storage | Storage | Cookies and saved data |

**Console** is where the page's scripts report errors. A red line such as "Failed to load resource" often explains why a form button does nothing, and you can paste it into a support ticket without reading any code.

**Network** records every request the page makes while the tools are open, so open it first and then reload. Each row shows a file and its status code, the three-digit answer from the server (200 for success, 404 for not found). Click a row to see the request and response headers, the extra lines of information sent with each file; our post on [HTTP headers](/blog/what-are-http-headers) explains the common ones.

**Application** (Chrome, Edge) or **Storage** (Firefox, Safari) lists the cookies and other data a site keeps in your browser; deleting a cookie shows you what a first-time visitor sees.

## How do you see the mobile version of a page?

Turn on the device view inside the developer tools. In Chrome and Edge, click the device toolbar button (a phone-and-tablet icon) at the top of DevTools, or press **Ctrl + Shift + M** (**Cmd + Shift + M** on a Mac) with DevTools open. Firefox calls it **Responsive Design Mode** (**Ctrl + Shift + M**, or **Cmd + Option + M** on a Mac). In Safari, choose **Develop > Enter Responsive Design Mode** or press **Control + Cmd + R**.

The page now renders at a phone's width, and inspect works as usual inside that frame, which is how you find the CSS rule that breaks a layout at 375 pixels. Treat the result as an estimate: the page still runs on your computer, and a real phone's address bar and on-screen keyboard also affect the layout.

## Can you use inspect element on iPhone or Android?

Not on the phone alone. Mobile browsers have no built-in inspector, so you connect the phone to a computer and inspect the phone's tab from the desktop browser.

### Android with Chrome

1. On the phone, open **Settings > About phone** and tap **Build number** seven times until you see "You are now a developer!" The path differs slightly between manufacturers.
2. Go back, open **Developer options** and turn on **USB debugging**.
3. Connect the phone to the computer with a USB cable that can transfer files.
4. In Chrome on the computer, go to `chrome://inspect#devices` and keep **Discover USB devices** ticked.
5. Accept the prompt on the phone, then click **Inspect** under the tab you want.

A full DevTools window opens for the phone's tab. Chrome's [remote debugging guide](https://developer.chrome.com/docs/devtools/remote-debugging) covers USB drivers on Windows and what to do if the phone shows as offline.

### iPhone and iPad with Safari

On the iPhone or iPad, open **Settings > Apps > Safari > Advanced** and turn on **Web Inspector**. Connect the device to a Mac with a cable and trust the Mac if asked; the device then appears in the Mac's Safari **Develop** menu with its open tabs underneath. Apple's guide to [inspecting iOS and iPadOS](https://developer.apple.com/documentation/safari-developer-tools/inspecting-ios) also covers the Wi-Fi option; every route it documents goes through Safari on a Mac.

## What do inspect element changes actually do?

They change the copy of the page inside your own browser tab and nothing else. The server, its database and every other visitor's screen stay as they were, and a reload brings back the original. MDN puts it briefly: "You can make any changes you want, but you cannot save your changes."

- **You cannot permanently edit someone else's website.** To change your own site, edit its theme files, content system or code.
- **You cannot see server code.** The browser receives only the finished HTML, CSS, JavaScript and images, never the code or data behind them.
- **A changed price changes nothing.** The checkout still uses the real figure.
- **Chrome's Local overrides** keep edits across reloads by saving files on your computer; they still affect only your browser.

Because anyone can retype a page this way, a screenshot proves nothing about what a page said. Editing a bank balance, a receipt or an order confirmation to present it as genuine is forgery or fraud.

## How is inspect element different from view page source?

View page source shows the HTML exactly as the server sent it; inspect element shows the page as it is now, after scripts have run. Open the source with **Ctrl + U** (**Cmd + Option + U** in Chrome on a Mac) or **Show Page Source** in Safari's Develop menu.

The gap matters when a page loads its content with JavaScript: a product list that appears in the Elements panel but not in the source was added by a script after the page arrived. Our post on [static and dynamic pages](/blog/static-vs-dynamic-pages) shows how to tell the two apart.

## How do you copy a CSS selector or XPath?

Right-click the highlighted line in the Elements panel, open **Copy** and choose a format. Chrome and Edge offer **Copy selector**, a CSS selector (the pattern stylesheets use to target an element), and **Copy JS path**, a ready `document.querySelector()` line. Firefox's Copy menu lists **CSS Selector**, **CSS Path** and **XPath**, a path-style address for an element in the page.

To test one in Chrome or Edge, press **Ctrl + F** (**Cmd + F** on a Mac) inside the Elements tree and type a CSS selector or an XPath; matches light up one by one. Copied selectors are often long and tied to today's layout; our [CSS selector vs XPath](/blog/css-selector-vs-xpath) guide shows how to shorten them to ones that last.

## Why is inspect element disabled on my computer?

On a school or work computer, the usual reason is a policy set by the organisation that manages the device. Chrome's DeveloperToolsAvailability policy, set to disallow, removes developer tools completely: the shortcuts, the menu entry and the **Inspect** item stop working. Edge has a policy with the same name, and Firefox has DisableDeveloperTools.

In Chrome, "Managed by your organization" at the bottom of the ⋮ menu means a policy is in force, and `chrome://policy` lists which ones. If you need the tools for work or study, ask the IT team; getting around a device policy usually breaks the acceptable-use rules you agreed to. On your own device, check the simple causes first: Safari's developer features are off until enabled, and F12 may need **Fn**.

## Can inspect element show a page as another country sees it?

No. The device view and Chrome's **Sensors** panel change what the browser reports to the page, such as screen size and the location given to the page's geolocation request, but not your IP address. The server picks the language, prices and content from the address your request comes from, and that is still yours.

To load the version a visitor in another country receives, the request itself has to come from that country. A [Residential Proxy](https://proxynet.io/residential-proxy) with country or city targeting, set up in a separate browser profile, gives the page a home-user connection in that market; then you inspect prices, banners, cookie notices or hreflang tags as described above.

Checking language, currency and regional content this way across markets is called localization testing; our [localization](/localization) page describes how proxy sessions fit that work.

## Where you meet inspect element

- **SEO checks:** a page's title tag, meta description, canonical link and headings.
- **Front-end work:** the CSS rule that breaks a layout on one screen size.
- **Accessibility reviews:** alt text and heading order.
- **Support and QA teams:** Console errors and failed requests for a bug report.
- **Marketing and analytics:** whether a tracking tag or consent banner loaded.
- **Learning HTML and CSS:** how real pages are built, one element at a time.

## Common mistakes

- **Believing an edit was saved.** It lives in your tab until the next reload.
- **Treating the Elements panel and the page source as the same.** One is the live page, the other the server's original.
- **Opening Network after the page loaded.** It records only while open; reload to capture requests.
- **Pasting a long copied selector into a script.** Shorten it to a stable class or attribute.
- **Treating device mode as a real phone.** Confirm on a device before closing a mobile bug.
- **Using an edited screenshot as evidence.** It proves nothing, and faking documents is unlawful.

## Decision guide

| Your need | Use |
|---|---|
| See the code of one element | Right-click > Inspect |
| Test a CSS fix before editing files | Styles pane, then copy the rule |
| Find why a feature fails | Console for errors, Network for status codes |
| Check a page at phone width | Device view or Responsive Design Mode |
| Inspect a page on a real phone | Android: chrome://inspect; iPhone: Safari on a Mac |
| See the original server HTML | View page source |
| See the page from another country | A proxy in that country, then inspect |

## Frequently asked questions

### What is the inspect element shortcut?

In Chrome, Edge and Firefox it is **Ctrl + Shift + C** on Windows and Linux and **Cmd + Option + C** on a Mac; **F12** opens the tools at the last panel used. In Safari, enable the developer features once, then press **Shift + Cmd + C**.

### Does inspect element change the website?

No. It changes only the copy of the page in your own tab; the server and other visitors see the original, and a reload removes your edits. To change your own site permanently, edit its files or its content system.

### Is inspect element illegal?

No. It is a standard feature of every major browser, and reading a page's code is ordinary use. What can be unlawful is what someone does next, such as passing off an edited screenshot of a receipt as genuine or entering systems or accounts without permission.

### Can I use inspect element on iPhone or Android?

Yes, with a computer. On Android, turn on USB debugging, connect the phone by cable and open `chrome://inspect#devices` in desktop Chrome. On iPhone or iPad, turn on Web Inspector in Safari's Advanced settings, connect to a Mac and pick the tab from Safari's Develop menu.

### Why is inspect element disabled on my computer?

Usually because your school or employer manages the browser and has turned developer tools off with a policy such as Chrome's DeveloperToolsAvailability. "Managed by your organization" at the bottom of Chrome's menu confirms it, and `chrome://policy` shows the setting; ask the IT team if you need access.

### Can inspect element show a saved password?

It is not the place to look. Saved passwords are kept by the browser's password manager; in Chrome that is ⋮ > **Passwords and autofill** > **Google Password Manager**, which can also ask for Windows Hello or your Mac's screen lock before showing one. Use it only for your own accounts; retrieving someone else's password without permission is unauthorised access.

## Summary

Inspect element opens the browser's developer tools on the part of the page you choose. Right-click and pick Inspect, or press Ctrl + Shift + C (Cmd + Option + C on a Mac) in Chrome, Edge and Firefox; Safari needs its developer features turned on first. Read the HTML and CSS, try a change, and remember that every edit stays in your own tab until the next reload. Phones need a computer; another country's version of a page needs a request from that country.
