Android Platform Tools
ADB and Fastboot tools for Android development
Install with Homebrew
brew install --cask android-platform-toolsQuick Take: Android Platform Tools
For Mac-side device work, Platform-Tools 37.0.1 is still the boring, correct install: official adb and fastboot, free, and available as a Homebrew cask or platform-tools-latest-darwin.zip. Mind the macOS defaults (libusb off unless ADB_LIBUSB=1) and the libadbmdns-only discovery path after openscreen removal. Reach for cmdline-tools or Studio when you need to compile, not when you only need to talk to a device.
Best For
- •Developers debugging physical devices from Terminal
- •QA and support Macs that sideload APKs
- •CI jobs driving emulators via adb
- •Power users who need official fastboot
- •Anyone who wants adb without installing Android Studio
What are Android SDK Platform-Tools?
Android SDK Platform-Tools is the small Google package that gives Mac users adb and fastboot. As of July 2026 the current line is Platform-Tools 37.0.1. You download platform-tools-latest-darwin.zip from Google or install the Homebrew cask android-platform-tools. The package is free under the Android SDK license and is what most 'talk to my phone from Terminal' tutorials actually mean when they say install adb.
Version 37.x on macOS keeps libusb disabled by default. If you need the libusb backend, set ADB_LIBUSB=1 in the environment. Google also removed the openscreen mDNS implementation; discovery now relies on libadbmdns only. That change matters if your LAN device discovery scripts assumed the older openscreen behavior.
Install Platform-Tools alone when you already have build tooling elsewhere and only need device debugging, sideloading, or bootloader ops. Install full Command-Line Tools or Android Studio when you also need sdkmanager platforms and build-tools. Many Mac developers do both: Studio or cmdline-tools for compiling, with platform-tools on PATH for day-to-day adb.
If your Mac already has an SDK root from Android Studio Quail 3 or from android-commandlinetools, check $ANDROID_HOME/platform-tools/adb version before installing another copy. Duplicate binaries are the most common self-inflicted adb failure on developer Macs in 2026.
Field note for August 2026: if wireless debugging fails after a Platform-Tools upgrade, re-pair the device instead of reinstalling macOS. Most 'adb disappeared' reports after 37.0.1 are discovery assumptions from the openscreen era, not bricked USB stacks. Keep Platform-Tools release notes bookmarked beside your team device-farm docs. When someone insists on a random GitHub adb build because a blog said so, compare adb version against Google's 37.0.1 line and decline. Official darwin zips and the Homebrew cask are enough distribution channels for honest Mac work. Fastboot tutorials should name the device and the image source; vague flashing advice is how bricks happen. QA benches benefit from a laminated card that shows which USB-C port on the Mac mini is trustworthy. CI should print adb version and which adb at job start so PATH skew shows up in the log, not in a Slack thread three hours later.
Closer look: adb on macOS after Platform-Tools 37.x
How 37.0.1 changed defaults Mac developers feel day to day, and how to install without creating duplicate adb binaries. The practical Mac lesson in August 2026 is not flashy: install once, pin the version, avoid duplicates, and retest wireless debugging after the openscreen removal. Everything else is commentary on top of those habits. Pin darwin zips by hash in CI and treat wireless re-pairing as routine after mDNS stack changes.
History & Background
Platform-Tools matured as the detachable device-bridge slice of the Android SDK. Mac users historically grabbed it inside Studio, then as a standalone zip for CI and support laptops. Homebrew's android-platform-tools cask made adb ordinary on developer Macs that never open Studio. The 37.x line's macOS USB default and mDNS cleanup continue Google's pattern of documenting host-OS specifics instead of pretending every platform behaves like Linux. Forums still recirculate ancient Windows-oriented USB driver advice that does not apply to macOS; ignore it. The Mac story is permissions, cables, PATH, and the documented ADB_LIBUSB switch. Write the install path into onboarding so new hires do not collect extra copies under Downloads.
How It Works
adb talks to a server process that brokers device connections over USB or TCP. fastboot is a separate protocol used in bootloader mode. On macOS, the default USB stack path keeps libusb off unless ADB_LIBUSB=1. Wireless debugging depends on pairing and mDNS; with openscreen removed, libadbmdns owns discovery. PATH order decides which platform-tools tree you actually run when Studio and Homebrew both exist. Emulator traffic still appears as a device in adb devices with an emulator-5554 style serial. Physical devices show USB or wireless transports depending on how you connected. Scripts should key off serials, not assume position zero in the device list. When devices vanish after a macOS update, re-authorize USB debugging before reinstalling Platform-Tools.
Ecosystem & Integrations
CI images, Flutter doctor checks, React Native Android docs, and OEM flash guides all assume an official adb. Pair Platform-Tools with cmdline-tools when you need sdkmanager. Pair with Studio when you want integrated Logcat UI. QA benches often standardize on the Homebrew cask so non-developers get the same adb version. Some Electron-based device UIs shell out to adb; they inherit whatever binary is first on PATH. That is another reason duplicate installs hurt: the GUI and your Terminal can disagree. Keep a known-good 37.0.1 zip on an internal mirror for air-gapped labs.
Future Development
Track Google's Platform-Tools release notes for further host-OS notes beyond 37.0.1. Pin versions in automation. When a new 37.x or 38.x drops, retest wireless debugging and USB hubs used in device farms before rolling out to every Mac runner. Also watch for Studio release notes that bundle a newer platform-tools into the IDE's SDK; IDE users may upgrade adb without noticing when they accept SDK updates. Re-test USB hubs in device farms whenever Platform-Tools minor versions change.
Key Features
adb (Android Debug Bridge)
adb lists devices, installs APKs, forwards ports, captures logs, shells into devices, and drives instrumentation. On Mac it is the daily driver for physical Pixel debugging and emulator control. Platform-Tools 37.0.1 continues the 37.x behavior notes around USB backends and mDNS discovery. Record non-default flags in the lab runbook so upgrades do not erase tribal knowledge.
fastboot
fastboot speaks to devices in bootloader mode for flashing partitions, unlocking bootloaders (where allowed), and low-level recovery workflows. Mac power users flashing custom images rely on the Platform-Tools fastboot binary rather than random GitHub mirrors. Prefer the official binary over random mirrors when flashing.
macOS USB defaults (libusb off)
On macOS, libusb remains disabled by default in current Platform-Tools. Export ADB_LIBUSB=1 when you intentionally want the libusb backend. Leave it unset for the default path unless you are debugging a USB edge case Google documents for that backend. Document ADB_LIBUSB experiments with a date stamp.
mDNS via libadbmdns
Openscreen-based mDNS was removed. Device discovery over mDNS uses libadbmdns only. Wireless debugging setups on local networks should be retested after upgrading to 37.0.1 if they depended on older discovery behavior.
Homebrew cask android-platform-tools
brew install --cask android-platform-tools puts adb and fastboot on your Mac without pulling the entire SDK. Useful for designers, QA, and support engineers who sideload builds but never compile. Pair with ANDROID_HOME only when you also maintain a full SDK root.
Zip install: platform-tools-latest-darwin.zip
Google's darwin zip unpacks to a platform-tools folder you can place anywhere and add to PATH. Teams that vendor binaries into repo toolcaches often pin this zip by hashing it in CI rather than trusting floating 'latest' on every run.
Works beside Studio and cmdline-tools
If Android Studio or sdkmanager already installed platform-tools into an SDK root, prefer that binary via PATH to avoid version skew. The standalone cask is best when you do not want an SDK root at all.
Free, redistributable under SDK license
Platform-Tools carries no separate subscription. You accept the Android SDK license terms. That keeps student labs and loaner Macs honest: install adb without a paid IDE.
Who Should Use Android Platform Tools?
1App developer debugging a physical Pixel
A developer enables USB debugging, plugs a Pixel into a MacBook, and runs adb devices. They adb install -r app-debug.apk, then adb logcat while reproducing a crash. Platform-Tools 37.0.1 is the only Google package on the machine because builds happen on CI. Note adb version in bug tickets so 37.0.1 versus older 35.x theories stay distinguishable.
2QA engineer sideloading release candidates
QA receives an APK from CI. On a Mac mini test bench they use adb install and adb shell am start to launch smoke tests across three devices. Wireless debugging is used for one tablet; after the 37.x mDNS change they confirm discovery still lists the device before writing the new runbook. Keep a printed cable map for the bench; flaky ports waste more time than flaky builds.
3ROM / recovery hobbyist
A power user boots a device to fastboot and flashes vendor images with the official fastboot binary from Platform-Tools. They avoid unofficial mirrors. When USB behaves oddly on macOS they try ADB_LIBUSB=1 as documented rather than random forum binaries. Store factory images on a verified internal mirror before fastboot sessions.
4Support engineer capturing bugreports
Customer support reproduces an issue on a loaner phone and runs adb bugreport. The zip goes to engineering. The support Mac has only android-platform-tools via Homebrew so non-developers cannot accidentally juggle SDK packages.
5CI job talking to an emulator
A pipeline already installed cmdline-tools and an AVD. The job uses adb wait-for-device and adb shell from Platform-Tools to gate UI tests. The platform-tools revision is pinned so adb flags stay stable across runner images.
How to Install Android Platform-Tools on Mac
Choose Homebrew for convenience or Google's darwin zip for pinned CI caches. Either path yields adb and fastboot. Verify with adb version after install. Expect a few megabytes, not gigabytes: Platform-Tools is intentionally small compared with Android Studio or a full cmdline-tools SDK tree. That is why support organizations standardize on it for loaner Macs.
Install via Homebrew or zip
Homebrew: brew install --cask android-platform-tools. Manual: download platform-tools-latest-darwin.zip from Google's Platform-Tools release page, unzip, and note the folder path.
Put binaries on PATH
If the zip install is outside an SDK root, add the platform-tools directory to PATH in ~/.zshrc. Homebrew usually links adb for you. Run hash -r && adb version to confirm you are on 37.0.1 or newer.
Enable debugging on the device
On the Android device, enable Developer options and USB debugging. Connect via USB and accept the RSA prompt. For wireless debugging, pair using the on-device pairing code workflow, then confirm adb devices sees the target.
Optional USB backend override
Only if needed: export ADB_LIBUSB=1. Leave unset for the macOS default (libusb disabled). Retest device visibility after changing the variable.
Pro Tips
- • Prefer one adb on PATH; conflicting Studio and Homebrew binaries cause confusing device lists.
- • Pin the Platform-Tools version in CI images instead of curling latest on every job.
- • After upgrading to 37.0.1, retest wireless discovery because openscreen mDNS is gone.
Configuration Tips
One adb on PATH
Run which -a adb and resolve duplicates. If Studio's SDK platform-tools and Homebrew both appear, pick one and remove the other from PATH. Document the choice in your team README. Re-check PATH after each Studio SDK update.
Pin 37.0.1 in CI
Cache platform-tools-latest-darwin.zip by content hash after verifying it is 37.0.1. Floating latest silently upgrades runners and can change mDNS or USB behavior mid-sprint. Store the zip SHA-256 beside the pin in your image repo.
Know when to set ADB_LIBUSB
Default macOS builds keep libusb disabled. Set ADB_LIBUSB=1 only while diagnosing USB issues that match Google's guidance for that backend, then leave a comment in your shell profile so future you knows why it is there. Remove the export when the USB issue is gone so it does not become folklore.
Alternatives to Android Platform Tools
Platform-Tools covers device bridge needs. Broader Android work needs more packages or an IDE.
Android SDK Command-Line Tools
Adds sdkmanager, avdmanager, and apkanalyzer for full SDK management. Choose this when you compile on the Mac, not only debug.
Android Studio
Bundles Platform-Tools inside an SDK root and adds IDE UI. Better for daily app development; heavier than adb-only installs.
Vendor-specific flash tools
Some OEMs ship their own flashers. Prefer Google Platform-Tools for Pixel/AOSP-style fastboot unless an OEM mandates otherwise.
Pricing
Platform-Tools 37.0.1 is free. Homebrew's android-platform-tools cask does not add a charge. There is no pro tier for adb or fastboot. If a website charges for an 'adb installer' on Mac, walk away and use Google's zip or Homebrew instead.
Pros
- ✓Small install that delivers official adb and fastboot
- ✓Current 37.0.1 line with documented macOS USB and mDNS behavior
- ✓Homebrew cask for quick Mac setup
- ✓Works without installing Android Studio
- ✓Suitable for QA and support Macs that only sideload builds
- ✓Free under the Android SDK license
- ✓Easy to vendor as platform-tools-latest-darwin.zip in toolcaches
- ✓Pairs cleanly with full SDK roots when needed
Cons
- ✗Does not install platforms, build-tools, or sdkmanager
- ✗USB and wireless quirks still require platform knowledge
- ✗Multiple adb installs on one Mac create version confusion
- ✗mDNS behavior changed versus older openscreen-based releases
- ✗fastboot misuse can brick devices if you flash the wrong image
Community and Support
Google documents Platform-Tools releases and adb on developer.android.com. Homebrew cask issues belong on the Homebrew discussions for android-platform-tools. Day-to-day questions cluster on Stack Overflow under adb and android-debug-bridge. Device makers' forums cover OEM-specific fastboot caveats that Google docs will not list. Release notes on developer.android.com remain the authoritative changelog for USB backend notes and mDNS changes. When a Mac OS update coincides with a Platform-Tools bump, bisect by testing a pinned 37.0.1 zip on a clean user account before blaming either vendor. Internal Slack channels often keep a 'known good adb' message pinned with the SHA-256 of the darwin zip the team trusts for the quarter.
Frequently Asked Questions about Android Platform Tools
About the Author
Expert Tips for Android Platform Tools
Before blaming 37.0.1 for empty device lists, run which -a adb. Half of Mac 'adb is broken' threads are two binaries fighting.
Treat ADB_LIBUSB=1 as a diagnostic flag, not a default export, unless your lab has a documented USB reason.
After upgrading past the openscreen removal, rewrite wireless debugging runbooks with a fresh pairing instead of assuming old mDNS behavior.
Related Technologies & Concepts
Related Topics
Android device debugging
Tools for communicating with Android devices and emulators from macOS.
Android SDK packages
How Platform-Tools relates to cmdline-tools and Studio-managed SDK roots.
Sources & References
Fact-CheckedLast verified: Aug 9, 2026
Key Verified Facts
- Platform-Tools 37.0.1 (July 2026) is the current release line discussed for Mac.[cite-1]
- On macOS, libusb is disabled by default; ADB_LIBUSB=1 enables it.[cite-1, cite-2]
- Openscreen mDNS was removed; libadbmdns is the discovery path.[cite-1]
- Mac users can install via platform-tools-latest-darwin.zip or Homebrew android-platform-tools.[cite-1, cite-3]
- adb and fastboot are the primary binaries in Platform-Tools.[cite-2, cite-1]
- 1Platform-Tools releases
Accessed Aug 9, 2026
"Official release notes and downloads for Platform-Tools."
- 2
- 3
- 4Android Studio command-line tools
Accessed Aug 9, 2026
"Context for how platform-tools fits among SDK CLIs."
- 5sdkmanager documentation
Accessed Aug 9, 2026
"Installing platform-tools into an SDK root via sdkmanager."
- 6Android Studio intro
Accessed Aug 9, 2026
"IDE entry point that bundles SDK components including platform-tools."
- 7
- 8
Research queries: Android Platform-Tools 37.0.1 macOS; ADB_LIBUSB macOS; android-platform-tools Homebrew