Next-Gen App & Browser Testing Cloud
Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

There are several ways to open Inspect Element in Google Chrome, and they all land you in the same place: the DevTools Elements panel. The quickest options are to right-click any part of a page and choose Inspect, or to use a keyboard shortcut. Press F12 or Ctrl + Shift + I on Windows and Linux, or Cmd + Option + I on Mac. To start straight in element-pick mode, use Ctrl + Shift + C (Windows/Linux) or Cmd + Shift + C (Mac). You can also open it from the three-dot menu under More tools > Developer tools.
Right-clicking is the most common way to open Inspect Element, and it has one big advantage over the keyboard shortcuts: it pre-selects the exact element you clicked, so you do not have to hunt for it in the DOM tree.
Keyboard shortcuts are the fastest route once you know them. Chrome offers a different shortcut depending on whether you want DevTools to open on the last panel you used, jump straight into element-pick mode, or land on the Console.
| Action | Windows / Linux | Mac |
|---|---|---|
| Open DevTools (last used panel) | F12 or Ctrl + Shift + I | Fn + F12 or Cmd + Option + I |
| Open and start element-pick mode | Ctrl + Shift + C | Cmd + Shift + C |
| Open DevTools focused on Console | Ctrl + Shift + J | Cmd + Option + J |
| Toggle the device toolbar | Ctrl + Shift + M | Cmd + Shift + M |
If you would rather not remember a shortcut, the three-dot menu gives you the same result in a few clicks.
Element-pick mode is what most people actually mean by "inspect element": you hover over the page, Chrome highlights whatever is under your cursor with its dimensions and box model, and a click locks that node into the Elements panel.
Once Inspect Element is open, the Elements panel shows the live DOM on the left and the matched CSS in the Styles pane on the right. You can read and modify both, which is what makes it a debugging tool rather than just a viewer.
Remember that every edit you make here is temporary. It lives only in your current tab and is discarded when you reload the page, so it is safe for experimenting but never a substitute for changing the actual source.
You cannot open a full DevTools window inside Chrome on a phone, but you can inspect a mobile page remotely from your desktop using Chrome's built-in remote debugging.
If you only need to inspect a generic mobile layout rather than a specific device, the device toolbar inside DevTools is enough. For real device behaviour, see How to Inspect Elements on Android? for the on-device routes.
"Inspect Element" and "DevTools" are often used interchangeably, but the task you are doing decides which page is most useful.
Inspecting an element on your own Chrome only tells you how it renders on your machine. The same markup can shift on a different Chrome version, on Safari, or on a specific Android handset. With TestMu AI's Real Device Cloud and browser grid, you can open and inspect the same page across thousands of real browser and OS combinations from your browser, no local installs needed, and catch layout issues that a single local Inspect Element session would never surface.
Press Ctrl + Shift + C on Windows or Linux, or Cmd + Shift + C on Mac. This opens DevTools and immediately activates the element picker, so the very next element you hover and click is selected in the Elements panel. F12, Ctrl + Shift + I, or Cmd + Option + I also open DevTools but without auto-starting the picker.
The Inspect entry is hidden when developer tools are disabled by an enterprise or managed policy, or when a site overrides the context menu. Try a keyboard shortcut such as F12 or Ctrl + Shift + I instead. On a work device, a managed policy may block DevTools entirely, in which case you cannot re-enable it locally.
Right-click (or Control-click) the page and choose Inspect, or press Cmd + Option + I to open DevTools. Use Cmd + Shift + C to open DevTools with the element picker active, and Cmd + Option + J to open it focused on the Console. On some keyboards F12 requires the Fn key.
Yes. In the Elements panel you can double-click a node or choose Edit as HTML to change markup, and edit rules in the Styles pane to change CSS live. The changes are temporary and only affect your current view, so reloading the page reverts everything back to the source served by the site.
Enable USB debugging in Developer options on the Android phone, connect it to your computer over USB, then open chrome://inspect#devices in desktop Chrome, tick Discover USB devices, accept the authorization prompt on the phone, and click inspect next to the page. A full DevTools window opens that mirrors and controls the mobile tab.
With DevTools open, press Ctrl + Shift + M on Windows or Linux, or Cmd + Shift + M on Mac, to toggle the device toolbar. You can then pick a device preset, set a custom width and height, and inspect how elements reflow at that viewport. This previews layout but does not replace testing on real devices.
KaneAI - Testing Assistant
World’s first AI-Native E2E testing agent.

TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance