How to Inspect Element on Android, From Any Computer

You cannot open developer tools on the phone itself. What you can do is drive the phone’s browser from a computer over a cable, and unlike the equivalent on an iPhone - which needs a Mac - this works from Windows, macOS or Linux. Any computer with Chrome on it will do.

The setup, once

On the phone. Open Settings → About phone and tap Build number seven times. Android tells you developer mode is on. Go back to Settings → System → Developer options and turn on USB debugging. The exact path varies by manufacturer; searching the Settings app for “build number” finds it faster than hunting.

Connect it. Plug the phone into the computer with a cable that carries data - a charge-only cable is the most common reason nothing appears. Unlock the phone. It asks whether to allow USB debugging from this computer; say yes.

On the computer. Open Chrome and go to chrome://inspect#devices. Your phone appears by name, with a list of the tabs open on it. Click inspect beside the one you want.

DevTools opens on the computer and is driving the phone. You get the full panel set - Elements, Console, Network, everything - plus a live view of the screen you can click, which is genuinely useful when the person holding the phone is on a call with you.

Without a cable

Android 11 and later can do this over wi-fi. In Developer options, turn on Wireless debugging, choose “Pair device with pairing code”, and pair from the computer. Both devices need to be on the same network. It is slower than a cable and it is the difference between debugging at your desk and debugging from the sofa.

What else shows up there

• Other Chromium browsers on the phone - Samsung Internet, Edge - appear in the same list once debugging is on.
• Firefox for Android does not. Its equivalent is about:debugging in desktop Firefox, with the same USB debugging switch on the phone.
• A web view inside a native app appears only if the app was built with web view debugging enabled. For your own app in a development build, that is one line. For somebody else’s app from the store, it is not available, and that is deliberate.

The difference from iPhone worth knowing

On iOS every browser renders with WebKit, so a bug that only shows on an iPhone is often an engine difference that no desktop browser can reproduce.

Android is not like that. Chrome on Android is Blink, the same engine as Chrome on your desktop, so most rendering bugs do reproduce in desktop device mode - the phone view in DevTools. That makes device mode a much better first guess here than it is for iOS.

What device mode still cannot give you is the rest of the phone: real touch behaviour and hit targets, the actual viewport once the keyboard is open, memory limits on a cheap handset, GPU differences, and anything involving the device’s own network conditions. So the order that saves time is: try device mode first, and reach for the cable when the bug does not appear there.

When it is somebody else’s phone

All of the above assumes the phone is in your hand. Usually it is not: a customer reported that your site is broken on their Android, and enabling developer mode on a stranger’s handset is not a request anybody is going to make.

What to ask for instead, in order of how much it tells you:

• A screen recording. Android records the screen from the quick settings panel. It captures the behaviour, the timing and what they tapped.
• The browser and version. Chrome’s is under Settings → About Chrome. “Android” is not an answer - Chrome 152 on Android 16 is.
• The exact text of any error, photographed if that is easier than copying it.
• Whether it happens in an incognito tab, which separates your page from an extension, a cached asset or a stale service worker.

Our own limit, stated plainly on a page about phones: our extension is a desktop Chrome extension. It captures the console and the network log on a computer, not on a handset. For a desktop bug it removes this whole exchange, because the technical half arrives with one button press. For a bug that only happens on somebody’s Android, the recording and the version number are still what you are working from.

Quick reference

• Phone: Settings → About phone → tap Build number seven times, then Developer options → USB debugging.
• Computer: Chrome → chrome://inspect#devices → inspect.
• Use a data cable, unlock the phone, and accept the prompt.
• Android 11+ can pair over wi-fi instead.
• Chrome on Android is the same engine as Chrome on the desktop, so try device mode before reaching for the cable.