Android SDK Command-line Tools
Google LLC · Manage Android SDK packages and command-line development utilities without installing the full Android Studio IDE.
No new version for more than 90 days, so OpenNavo has paused recommending and installing it. Homebrew still offers this app.
brew install --cask android-commandlinetools- 30-day installs
- 58,367
- 1-year installs
- 351.4K
- Last 365 days
- Latest version
- 15859902
- Download size
- 156MB
- zip
- Release cadence
- Irregular
- 0 releases in 30 days
About
Android SDK Command-line Tools is Google's standalone package of SDK-management utilities for Android development on macOS. It provides sdkmanager and avdmanager plus supporting tools such as apkanalyzer, d8, lint, r8 and retrace, so you can install SDK platforms, build tools and system images from a terminal. It suits scripted setups, CI machines and Macs that do not run the Android Studio IDE. It does not include adb or fastboot, which belong to the separate Platform-Tools package.
What the package provides
Google distributes the command-line tools as a ZIP archive listed in the Android SDK repository. The Homebrew cask installs the current archive under $HOMEBREW_PREFIX/, with executables linked from cmdline-tools/. sdkmanager lists, installs, updates and removes SDK packages, and can select stable or preview channels for reproducible automation. avdmanager creates and manages Android Virtual Devices once the matching system image is installed. The cask also links apkanalyzer, d8, lint, r8 and retrace for inspection and build tasks. The Developer Workbench collection lists related command-line tools for macOS.
Google's current sdkmanager guide marks sdkmanager and avdmanager as deprecated and recommends the Android CLI (android sdk, emulator) instead. Both commands still ship in this cask and remain usable, but new automation should check Google's migration guidance before standardising on them.
Install on Mac and manage SDK packages
Install with brew install --cask android-commandlinetools. The cask declares Java as a dependency and suggests the Temurin cask (brew install --cask temurin) as one way to provide it. Google does not publish a single required JDK version for build 15859902, so use a JDK compatible with the tools you install and point JAVA_HOME at it.
Check the tools with sdkmanager --version and list available packages with sdkmanager --list. Accept the applicable licences with sdkmanager --licenses, then install only what you need, for example sdkmanager "platform-tools" "platforms;android-36". Update or remove packages with sdkmanager --update and sdkmanager --uninstall. Use --sdk_root when scripts must target a specific SDK directory instead of the cask default.
To create an emulator, install a system image first, then run avdmanager create avd -n test -k "system-images;android-25;google_apis;x86". On Apple Silicon, choose an arm64 system image for native speed. Android Studio's Device Manager and the Android CLI emulator commands are alternative ways to manage the same virtual devices; the Platform-Tools page covers adb and fastboot, which are installed as a separate SDK package.
macOS requirements and dependencies
The current cask version is build 15859902, which maps to cmdline-tools 22.0 in Google's repository XML. The cask does not declare a minimum macOS version, and Google's command-line tools release notes do not state an independent macOS minimum for this build. Treat the arm64 and x86-64 downloads as the supported Mac architectures rather than inferring a macOS release from the OpenNavo Mac app.
Java is a confirmed dependency even though Homebrew's formula-dependency field is empty. Disk use depends on the SDK packages, system images and emulators you install; Google does not publish one combined figure. If Android Studio is also installed, keep each SDK root separate and make sure scripts and the IDE point at the same one. See the Developer Tools category for other build and device tools.
Price, licences and accounts
The command-line tools are free to download and use. Downloads require accepting the Android SDK License Agreement, and sdkmanager --licenses records that acceptance for the SDK packages you install. Ordinary local package management does not require a paid subscription or a Google account. Individual open-source components keep their own licences, and publishing to Google Play is a separate service with its own account and fees.
Versions and update status
The cask has recorded five versions: 15859902 (cmdline-tools 22.0), 14742923 (20.0), 13114758 (19.0), 11076708 and 10406996. The official release notes page does not provide per-version change lists for 22.0, 20.0 or 19.0, so this page does not attribute undocumented fixes to those builds. Upgrade the cask with brew upgrade --cask android-commandlinetools, or install a newer ZIP from Google. OpenNavo currently pauses recommending this cask because the listed version has not changed for more than 90 days; the Homebrew cask remains available and installable.
Alternatives and related tools
Android Studio is the full IDE with a graphical SDK Manager, emulator and device manager; use it when you want an integrated editor and debugger. Platform-Tools is the separate package that provides adb and fastboot for physical devices. The Android CLI is Google's newer command-line interface, which the sdkmanager documentation now recommends for SDK and emulator tasks. Command-line Tools remains the smaller, script-friendly option for installing SDK components on machines without the IDE. See Android Studio for the full IDE and the Platform-Tools page for the device tools.
FAQ
Do I need Android Studio to use these tools?
No. The command-line tools install and manage SDK packages without the IDE. Android Studio is only needed when you want its graphical editor, SDK Manager or emulator controls.
Do the command-line tools include adb and fastboot?
No. adb and fastboot are in the separate platform-tools SDK package. Install it with sdkmanager "platform-tools"; the Platform-Tools page covers its use.
Which Java version do I need?
Homebrew requires Java and suggests Temurin, but Google does not name a specific JDK for build 15859902. Install a current JDK, set JAVA_HOME, and check the release notes of the tools you use.
Are sdkmanager and avdmanager still usable?
Yes. They still ship in this cask, but Google marks both as deprecated and recommends the Android CLI equivalents (android sdk and emulator) for new work.
Which macOS versions are supported?
Google does not state a macOS minimum for this build, and the cask declares none. Downloads are available for Apple Silicon (arm64) and Intel (x86-64).
Last updated: 2026-11-05. Sources: Google Android developer documentation (sdkmanager, avdmanager, Android CLI, command-line tools release notes), the Google SDK repository XML, and Homebrew cask metadata.
Official references
At a glance
- Chip
- Apple silicon · Intel
- Auto-updates
- No
- Developer
- Google LLC
- Homebrew
- Still offered by Homebrew; paused by OpenNavo
- Also known as
- android-commandlinetools
- Homepage
- developer.android.com/studio
- Token
- android-commandlinetools
Checked
How to install Android SDK Command-line Tools on Mac
Install without Homebrew
Download the file Homebrew uses for your chip: Install Details
Uninstall Android SDK Command-line Tools and optional data cleanup
brew uninstall --cask android-commandlinetoolsA regular uninstall removes the app and keeps its settings and caches.
Deep clean (optional)
brew uninstall --zap --cask android-commandlinetools--zap also deletes the settings, caches and other files listed in the Homebrew definition. They can include data shared with other apps and cannot be restored, and it does not guarantee that nothing is left. Back up any data you need first. To keep settings and caches, leave out --zap.
Questions about Android SDK Command-line Tools
Is Android SDK Command-line Tools safe?
Android SDK Command-line Tools is in Homebrew’s official catalog and has not been disabled. Since September 2026, Homebrew disables apps that fail macOS Gatekeeper checks. When installing, Homebrew checks the download from dl.google.com against its SHA-256 checksum. It was installed 58,367 times through Homebrew in the last 30 days.
How do I completely uninstall Android SDK Command-line Tools on a Mac?
Run brew uninstall --cask android-commandlinetools. To delete its settings and caches as well, run brew uninstall --zap --cask android-commandlinetools. --zap also deletes the settings, caches and other files listed in the Homebrew definition. They can include data shared with other apps and cannot be restored, and it does not guarantee that nothing is left. Back up any data you need first. To keep settings and caches, leave out --zap. That also deletes 2 files and folders, including ~/.
Does Android SDK Command-line Tools run on Apple silicon (M1 and later) Macs?
Yes. Homebrew downloads separate builds for Apple silicon and Intel Macs.
Where does Android SDK Command-line Tools store its settings and data?
Its data is in ~/. These locations come from Homebrew’s clean-up list.
What is the latest version of Android SDK Command-line Tools?
The latest version is 15859902, added to Homebrew on Jul 28, 2026. Run brew upgrade --cask android-commandlinetools to update it.
What else does installing Android SDK Command-line Tools add?
It also adds 11 command-line tools, including apkanalyzer, avdmanager, d8, lint, and profgen.
Similar Apps
- Visual Studio CodeMicrosoft’s extensible code editor with debugging, Git integration, an integrated terminal, remote development, and optional AI assistance.
- Google Cloud CLIA command-line toolset for managing Google Cloud projects, cloud resources, and applications, suited for terminal operations and automated deployment.
- Claude CodeAnthropic's AI coding assistant for exploring codebases, editing files, running commands and tests, and managing Git workflows from the terminal.
- Azure CLIMicrosoft’s cross-platform command-line tools for creating, managing, and automating Azure resources.