ADB on Mac: Installing Platform-Tools and Checking Your Device Connection

You do not need to install all of Android Studio to use adb on a Mac. For command-line use, the official Android SDK Platform-Tools package for Mac is enough. If Studio already manages your Android SDK, Google recommends getting Platform-Tools through SDK Manager rather than creating another independent copy.

This guide is based on Google’s documentation, not hands-on testing: the steps have not been tested on a Mac and an Android device. The commands below are intended to be run on your Mac with your device; no command results or screenshots are provided here.

1. Choose one installation source

If Android Studio is already installed

Open Tools > SDK Manager. On the SDK Tools tab, select Android SDK Platform-Tools, then Apply or OK, and review the license terms. Note the Android SDK Location value: the installed adb is in the platform-tools subdirectory of that SDK.

In Google’s documentation, android_sdk/platform-tools/ represents your SDK directory, not a literal path to paste into Terminal. Do not assume the SDK is necessarily in the default directory: use the location shown in SDK Manager. Google’s SDK Manager instructions.

If you only need adb

Open the official Platform-Tools page, select Download SDK Platform-Tools for Mac, read the Android SDK License Agreement, and download the ZIP file. Extract the archive and save the platform-tools folder in a permanent location of your choice. Do not run the Windows or Linux version.

In Terminal, type cd with a trailing space, drag the extracted platform-tools folder from Finder into the Terminal window, and press Return. This takes you to the actual directory without substituting someone else’s username or a made-up path. Then check:

./adb version

The ./ prefix means “run adb from the current folder.” Having the file in that folder does not mean the adb command without the prefix will be found through PATH. You do not need to add the directory to your global PATH for these initial checks.

Google provides a separate command-line ZIP without Studio; the official package is distributed under the SDK terms, not an arbitrary “free license with no restrictions.” Download source and terms.

The Platform-Tools listing on OpenNavo provides information about the package. At the time this article was prepared, the catalog’s recommendation was paused. This is an OpenNavo status, not a statement that Google has stopped distributing the tools: the official Mac ZIP is still listed on Google’s page. This guide uses the official source without changing the listing’s status.

2. Identify which copy of adb you are running

If you expect to run adb from any directory, run:

which -a adb
adb version

which -a adb helps you see the copies found in PATH; adb version shows the version of the client being run. Compare the paths found with the directory selected in the previous step. These checks serve different purposes: knowing the version alone does not prove that you are using the intended installation.

If the command is not found, return to your selected platform-tools folder and use ./adb version. For subsequent commands in this article, also replace the initial adb with ./adb: for example, ./adb devices -l. This approach also works for a directory installed through SDK Manager.

If you find multiple installations, first determine which one your SDK or workflow needs. Do not delete other copies or change shell settings at random. adb clients communicate with a shared server on local TCP port 5037, so the choice of client executable and the state of an already running server are not the same thing. For this guide, consistently using the selected copy is sufficient. How adb works.

3. Connect your Android device over USB

1. On a device you own, open Developer options and enable USB debugging. If the section is hidden, follow Google’s instructions for enabling Developer options; setting names may differ by manufacturer.
2. Connect the device to your Mac using a cable that supports data transfer. Unlock the screen.
3. Run the command to list devices:

adb devices -l

4. Check for a prompt on the device itself. Android 4.2.2 and later asks you to confirm the computer’s RSA key for debugging. Allow access only for your own trusted computer and only for an expected connection; do not save persistent trust on someone else’s computer.
5. After confirming, run adb devices -l again.

According to Google’s documentation, no additional operating system setup is required for device detection on macOS. Do not apply Windows USB driver instructions or Linux udev instructions here. This is not a guarantee that every cable and every device will work. USB connection and RSA authorization.

The devices command lists devices, and -l enables detailed output. The adb tcpip 5555 command does not list devices: it changes the listening mode of the service on the device. It is not needed for this USB check and should not be run. adb command reference.

4. Interpret the result, not just the presence of a line

The following describes possible states, not test results from a specific device.

What you see	What it means	What to check next
command not found	The shell could not find the command by name	Go to the selected folder and check ./adb version; then use ./adb devices -l
A list header with no device rows	This query did not show any connected devices	Check the connection, data cable, unlocked device screen, and enabled USB debugging; try another known-working cable or USB port
A row with unauthorized	The connection has not yet been authorized for debugging	Look at the phone’s unlocked screen and confirm the expected RSA prompt; if there is no prompt, reconnect USB and check the list again
A row with device	The device is connected to the adb server	Verify the serial number and model; this does not prove that Android has fully booted or that future commands will succeed
A row with offline	The device is not connected to adb or is not responding	Check the connection and device state; do not treat this as successful authorization
Multiple rows	Multiple devices or emulators were detected	Explicitly select the intended device before running another command

The cable and settings checks follow Google’s USB connection recommendations. If they do not help, consult the device manufacturer’s documentation; do not disable macOS security protections or attempt to bypass phone authorization.

Google specifically warns that the device state does not mean Android has fully booted and is ready for every operation. Device list states.

5. If there are multiple devices, explicitly select one

Copy the serial number from the intended row in adb devices -l. To check the state of a specific device, you can use:

adb -s SERIAL get-state

SERIAL is a placeholder: replace it with your device’s actual serial number; do not type this word literally. If you are running the tool from the current directory, use ./adb -s SERIAL get-state. This queries the device’s state; it does not install an app or modify files.

The -s option selects the device with the specified serial number. Do not rely on the order of the rows, especially when an emulator is also running. Selecting a device in Google’s adb guide.

6. End the session without leaving unnecessary trust in place

After the check, disconnect the cable and turn off USB debugging if you no longer need it. If you allowed the computer to debug the device in the future and want to revoke that trust, use the option to revoke USB debugging authorizations in the device’s Developer options, if available. The name and location depend on the manufacturer; revoking authorization may also affect other previously trusted computers.

Closing Terminal does not by itself revoke trust. Do not manually delete keys or service files for this check. Do not publish serial numbers, key fingerprints, or other device identifiers in screenshots or reports.

Quick answers

Do I need to install Android Studio just for adb? No. Google offers a separate Platform-Tools package for Mac. If you already use Studio, it is more convenient to let SDK Manager continue managing the tools.

Why does ./adb version work while adb version does not? The first form points to a file in the current directory; the second depends on the shell’s command lookup. For this guide, you can continue using ./adb without changing global settings.

Does device mean everything is ready? It indicates a connection to adb, not a promise that the system has fully booted, that an app works, or that any subsequent command is safe.

Is wireless debugging required? No, it is not required for this USB scenario. This guide includes no steps for opening a network port or connecting wirelessly.

Sources and verification limits

• Google: SDK Platform-Tools and download for Mac.
• Google: Android Debug Bridge—authorization, listing devices, and selecting devices.
• Google: SDK Manager.
• Google: connecting a hardware device and checking USB.
• AOSP: adb reference.

This article is based on Google’s official documentation; no hands-on testing was performed on a Mac and an Android device. It contains no verified performance results, compatibility testing for a specific macOS version, or screenshots of supposedly executed commands.