How to Debug Android Websites with Firefox Developer Tools

To debug a website in Firefox for Android, connect the phone to desktop Firefox and use desktop Firefox Developer Tools to inspect the mobile tab. The documented options are USB debugging and, on Android 11 or later, wireless debugging. Both require Android Debug Bridge (adb). You do not need the full Android Studio SDK.

This workflow lets you inspect the page as it runs in Firefox on the device. The phone hosts the browser; desktop Firefox provides the remote debugging interface.

Requirements and connection options

Before starting, check that you have:

Firefox for Android on the phone. Mozilla Support lists Android 8.0 or later as supported; this is the browser compatibility requirement, not a stated minimum for remote debugging.
Desktop Firefox on the computer.
adb installed and available on the computer.
Access to Android Developer options.

Option	Requirements	Use it when
USB	A data-capable cable, adb, Android USB debugging, and Firefox’s Remote Debugging via USB setting	You can connect the phone directly to the computer.
Wireless	Android 11 or later, adb, Wireless debugging, and phone and computer on the same network	You can pair the devices over a shared network.

The connector depends on the phone and computer. A cable that only charges the phone will not provide the data connection needed for USB debugging. Mozilla documents both connection paths; its guidance does not establish one as universally faster or more reliable. Mozilla’s about:debugging documentation

Set up USB debugging

Enable Android Developer options. Open the phone’s About phone settings and tap Build Number seven times. The location and wording of this setting can vary by Android device.
Enable USB debugging in Android. Open Developer options and turn on USB debugging.
Enable Firefox remote debugging. In Firefox for Android, open Settings, then Advanced Settings, and enable Remote Debugging via USB. Android USB debugging and Firefox’s own remote debugging setting are separate requirements.
Connect the phone. Use a data-capable USB cable and accept the computer-authorization prompt on the phone if it appears.
Open desktop Firefox’s debugging page. Type about:debugging in its address bar. Mozilla also lists Tools > Browser Tools > Remote Debugging as an entry point.
Enable and refresh USB devices. In the about:debugging setup, enable USB Devices. If the phone is not listed, click Refresh devices.
Open the target page in Firefox for Android. Navigate to the page you want to inspect.
Connect to the phone. In about:debugging, find the device and click Connect. Select the open tab or target to launch its developer tools.

Mozilla says that adb is sufficient; installing the full Android Studio SDK is not required. See the official setup and device connection steps for the current interface.

Connect wirelessly on Android 11 or later

Mozilla documents wireless debugging using Android’s Wireless debugging feature on Android 11 or later. The phone and the computer running about:debugging must be on the same network, and adb is still required.

Enable Developer options on the Android device.
Open Developer options and enable Wireless debugging.
On the computer, open desktop Firefox’s about:debugging page and make sure adb is available.
Follow the pairing and connection flow shown by Android and Firefox. Use the phone’s local IP address when the flow asks for it.
After pairing, open the page in Firefox for Android and connect to its target from about:debugging.

The exact pairing prompts depend on the Android and Firefox interface versions. Follow the prompts presented by the devices rather than relying on a fixed menu path. The wireless path avoids a cable, but it still depends on network access and successful pairing. Mozilla’s wireless debugging guide

Inspect and debug the mobile page

Once connected, use the desktop Developer Tools for the selected Firefox for Android tab. Reproduce the issue on the phone while watching the connected page. This is useful for problems that depend on the actual mobile browser, device, or viewport.

Keep the target page open in Firefox for Android and the corresponding remote tools connected.
Reproduce the behavior that fails on the device.
Inspect the page and its runtime state with the available Developer Tools panels.
Change the page or device conditions as needed, then repeat the action on the phone to check whether the issue changes.

This setup is for debugging a live page in Firefox for Android. It does not turn the phone into the desktop DevTools interface; the connection and inspection workflow is managed through desktop Firefox.

Troubleshooting

Symptom	Likely checks and fixes
The phone does not appear in `about:debugging`.	Confirm Android Developer options and USB debugging are enabled, Firefox’s Remote Debugging via USB is enabled for the USB path, adb is installed, and the cable supports data. Accept the phone’s authorization prompt, then click Refresh devices.
The USB Devices control is disabled.	Check the documented setup first: enable the relevant Android and Firefox debugging settings, connect the device, confirm adb is available, and refresh. Mozilla does not identify one cause for every case. A 2022 support thread describes a historical issue and a preference change, but that report is not current baseline guidance; do not change advanced preferences unless you have confirmed your issue matches that specific case. Historical Mozilla Support discussion
The phone asks whether to authorize the computer.	Unlock the phone and accept the authorization prompt. Then refresh devices in `about:debugging`.
The phone charges but is not detected.	Try a cable that supports data transfer and a working computer port. Charging alone does not establish a data connection.
Wireless pairing is unavailable.	Verify the phone runs Android 11 or later, Wireless debugging is enabled, adb is available, and both devices are on the same network. Follow the pairing flow shown on the phone and in Firefox.
The device is connected but the page is not listed.	Open the target page in Firefox for Android, then refresh or revisit the device targets in `about:debugging`.
A menu or setting has a different name or location.	Android and Firefox labels can change across versions and device makers. Look for the same concepts: Android Developer options, USB or Wireless debugging, Firefox Remote Debugging via USB, and desktop Firefox’s `about:debugging`.

For broader setup details, use Mozilla’s current remote debugging documentation. Firefox for Android’s published compatibility statement is Android 8.0 or later; it should not be read as a separate guarantee about remote debugging on every device configuration.

Performance, reliability, and practical limits

Connection depends on setup. USB requires a data connection and computer authorization. Wireless requires Android 11 or later, a shared network, and successful pairing.
Keep the test representative. Reproduce the issue in the mobile Firefox tab itself when it depends on device behavior. A desktop-only page view does not replace that check.
Use the supported path before changing advanced preferences. Start with the settings, adb, authorization, and refresh checks in Mozilla’s current documentation. Historical forum workarounds may relate to older failures.
No setup-time guarantee. Mozilla’s documentation does not publish a setup duration, connection benchmark, or success rate.

Or skip the browser setup

If you need a screenshot of a web page rather than interactive Firefox debugging, ScreenshotNeo returns an image or PDF from one API request. It does not attach Developer Tools to the Android browser, so use the remote debugging workflow above when you need to inspect live page behavior.

For API options and configuration, see the ScreenshotNeo documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

ScreenshotNeo accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed. Its MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.

FAQ

Can I inspect a mobile page without Android Studio?

Yes. Mozilla says adb is needed, but the full Android Studio SDK is not.

Does wireless debugging work with older Android versions?

Mozilla’s documented wireless workflow requires Android 11 or later. Use USB if wireless debugging is not available on your device.

Is Android 8 the minimum for remote debugging?

No such minimum is stated in the supplied documentation. Android 8.0 or later is Mozilla Support’s Firefox for Android compatibility statement; it does not define the minimum version for this debugging workflow.

Can ScreenshotNeo replace remote DevTools?

No. ScreenshotNeo captures a page as an image or PDF. Use Firefox remote debugging when you need to inspect or troubleshoot a live page in Firefox for Android.