Development of applications for mobile devices is impossible without the basic set of tools provided by Google. Android SDK (Software Development Kit) is the foundation on which millions of applications are built around the world. Beginners often confuse an SDK with a full-fledged IDE (integrated development environment), such as Android Studio, but this is not entirely true. An SDK is precisely a set of libraries, emulators and debugging tools necessary for compiling code and testing apps.
Before you start downloading, it is important to understand that Modern Android SDK is no longer distributed as a separate executable file for download. In recent years, Google has fully integrated SDK management directly into the installer Android Studio. This is done to automate the setup process and avoid problems with file paths or Java versions. Therefore, if you are looking for a direct link to the archive, you can waste your time - the correct path is through the official installer of the development environment.
In this article we will analyze all the nuances of the process: from preparing the system to fine-tuning components through the manager. You will learn which packages take up the most space and how to manage platform versions so that your working tool always remains up-to-date and functional.
Preparing the environment and system requirements
Installing developer tools is a process that requires computer resources. Before running the installer, make sure that your hardware meets the minimum criteria Android Studio and emulators consume a significant amount of RAM and disk space. For comfortable work, it is recommended to have at least 8 GB of RAM, and ideally 16 GB or more. The hard drive should be an SSD type, since the reading speed of many small library files is critical for compilation speed.
Particular attention should be paid to the version of the operating system and the availability of JDK (Java Development Kit). Although modern versions Android Studio come with a built-in version of Java, having a correctly configured environment variable JAVA_HOME may be required for some plugins or the command line to work. You also need to check whether virtualization is enabled in the BIOS/UEFI of your processor, since without it the device emulator simply will not start.
⚠️ Attention: If you have an old JDK installed, it may conflict with the built-in version. It is recommended to remove old versions of Java or explicitly specify the path to the new JDK in the IDE settings after installation.
Check the free disk space. A basic installation can take around 3-4 GB, but as you add platforms, system images and emulators, this can easily grow to 20-30 GB or more. It is recommended to create a separate partition or folder on the disk with a large amount of free space in advance, so as not to run out of space when updating components in the future.
Use an SSD drive to install the SDK. The difference in project build speed between HDD and SSD can reach 300-400%, which significantly saves the developer’s time.
Installation process via Android Studio
As mentioned earlier, the only official way to get the latest set of tools is by downloading Android Studio from the Google developers site. Go to the official portal, accept the terms of the license agreement and download the installer for your operating system. The installation process is standard and should not cause any difficulties for experienced users, but there are several important points that you should pay attention to during installation.
During the installation, the wizard will prompt you to select components. Make sure that these items are related to Android SDK i Android Virtual Device. If you plan to use an emulator, you will also need to install additional virtualization components, such as Intel HAXM (for Intel processors) or configure Hyper-V / WHX (for AMD and new Intel processors). Installer will prompt you if any system requirements are not met.
- 📁 Installation path: By default, the SDK is installed in a hidden user folder. For beginners, this is fine, but for experienced developers, it is better to change the path to a more understandable one, for example
C:\Android\Sdkto avoid problems with access rights in the future. - ☑️ Components: Be sure to select "Android SDK Platform-tools" and "Android SDK Build-tools". Without them, USB debugging and building APK files is impossible.
- 💾 Emulator: If you have a weak computer, you can skip installing the emulator for now and use a physical device, but for full development it is necessary.
☑️ Ready to install SDK
After the files are copied, the setup wizard will start (Setup Wizard). It is at this stage that the SDK files are directly downloaded. You will be asked to select the installation type: Standard or Custom. For most users, the standard one is suitable, which will automatically select the latest stable versions of platforms.
Setting up the SDK Manager and selecting components
After the first launch Android Studio a welcome window will open in front of you. At the bottom of this window there is a button More Actions (or a gear icon in older versions), through which you can get to SDK Manager. It is a central hub for managing all Android versions, tools and libraries. Here you can download SDKs for specific OS versions, even if they are no longer the latest.
The SDK Platforms tab allows you to select which versions of Android you want to develop for. It is recommended to install the latest stable version (for example, Android 14 or 15), as well as one of the previous ones, to test compatibility. Each platform includes system images, signing keys, and frameworks. You should not download all versions at once, as they take up gigabytes of disk space.
The tab SDK Tools contains critical utilities. Here are Android SDK Build-Tools (compilers), Android SDK Platform-Tools (contains ADB and Fastboot) and Android Emulator. You can also find Google USB Driverhere, which is necessary for debugging on physical devices running Windows.
Why do you need several versions of Build-Tools?
Different projects may require different versions of compilers. Old projects may not be built by new tools without a Gradle migration, so having multiple versions of Build-Tools in SDK Manager is normal practice.
Versioning in SDK Manager helps keep your work environment clean. You can delete unused versions of platforms or tools at any time to free up space. The manager interface shows the installation status (Installed, Update Available, Not Installed), which makes navigation intuitive.
| Component | Description | Required for | Size (approximate) |
|---|---|---|---|
| SDK Platform | Frameworks and system images | Compilations for a specific version Android | ~2-4 GB |
| Build-Tools | Compilers (aapt, dx, zipalign) | Assemblies of APK files | ~100-300 MB |
| Platform-Tools | ADB and utilities Fastboot | Debugging and flashing devices | ~10-20 MB |
| Emulator | Virtual device | Testing without a real phone | ~500 MB + images |
Setting Environment Variables
For convenient work with command line tools such as adb or fastboot, you need to add the paths to them to the system variables. This will allow you to launch debugging from any folder in the terminal, without specifying the full path to the executable file each time. Without this setting, commands like adb devices will display the error "command not found".
In the Windows operating system, this is done through the "System Properties" menu. You need to find the variable Path and add there the path to the folder platform-tools inside your SDK. Usually the path looks like C:\Users\Username\AppData\Local\Android\Sdk\platform-tools. For macOS and Linux, you must edit the shell configuration file (for example .bashrc or .zshrc), adding the export path line.
export ANDROID_HOME=$HOME/Library/Android/sdkexport PATH=$PATH:$ANDROID_HOME/emulator
export PATH=$PATH:$ANDROID_HOME/platform-tools
export PATH=$PATH:$ANDROID_HOME/tools/bin
After making changes, be sure to restart your terminal or command line for the variables to take effect. You can check the correctness of the settings by entering the command adb version. If you see the Android Debug Bridge version number in response, it means the setup was successful.
⚠️ Warning: In Windows 10 and 11, paths in environment variables can be very long. Make sure you copy the path without extra spaces at the beginning or end of the line, otherwise the system will not find the executable file.
Linux and macOS users may also need to set USB port permissions so that ADB can see the connected device. This is solved by creating rules udev, which is a separate procedure specific to the distribution.
Working with the command line and ADB
One of the main reasons why developers download the SDK separately or configure paths manually is the need to use ADB (Android Debug Bridge). This tool allows you to manage your device, install applications, take screenshots, receive logs, and even broadcast the screen to your computer. Knowledge of basic ADB commands significantly speeds up the debugging process.
To get started, connect your smartphone to your computer via a USB cable. You need to activate developer mode on your phone. To do this, go to Settings → About phone and quickly click on the build number seven times. After this, an item will appear in the settings menu For developerswhere you need to enable USB debugging.
- 📱 adb devices: Shows a list of connected devices. The first connection will require confirmation on the smartphone screen.
- 📥 adb install app.apk: Installs the APK file on the connected device.
- 📝 adb logcat: Outputs a system log in real time, which is indispensable when searching for errors in the application.
If the command adb is not recognized, check the device drivers. For devices of popular brands (Samsung, Xiaomi, Pixel), Windows often installs drivers automatically, but for some Chinese models it may require installation Google USB Driver via SDK Manager or universal ADB drivers.
ADB is a bridge between your computer and Android device. The ability to use the command line via ADB distinguishes a professional from an amateur.
Common installation problems and their solutions
The process of downloading and setting up the SDK does not always go smoothly. The most common problem is network errors when downloading components through the SDK Manager. Because Google repositories may be unavailable or slow in some regions, downloads may be interrupted. Solution: use a stable connection or configure a proxy in the SDK Manager settings.
Another common problem is version incompatibility. The project may require Build-Tools version 30.0.3, but you have 33.0.0 installed. In such cases, Gradle usually offers to download the missing version automatically, but sometimes you have to do this manually through the "SDK Tools" menu with the "Show Package Details" checkbox.
⚠️ Attention: The Android Studio interface and settings location may change with updates. If you do not find the menu item, use the settings search (double-click Shift) and enter the name of the component.
Also, users often encounter a lack of space on the system disk. SDK Manager allows you to move the download cache or change the location of the SDK itself, but this must be done carefully so as not to confuse the paths in the IDE settings. Regularly cleaning old versions of platforms through the manager helps save space.
What to do if the emulator says "HAXM is not installed"?
Even if you installed HAXM, the emulator may not see it. Try running installer HAXM again as an administrator or switch the emulator to run through Windows Hypervisor Platform in the Virtualization Performance settings.
Questions and answers (FAQ)
Is it possible to download the Android SDK without installing Android Studio?
Technically, yes, there are command lines for downloading the SDK (sdkmanager), but for the average user this is an extremely difficult path. Google hasn't officially provided simple SDK installers separate from the IDE for several years. It's easier to install Studio and use only its tools.
How much space does the full SDK set take up?
The basic installation takes about 3-5 GB. However, if you install system images to emulate multiple versions of Android and different architectures (x86, ARM), the size can increase to 20-50 GB. It is recommended to have some extra disk space.
Where is the installed SDK folder on the computer?
The default paths are:
Windows: C:\Users\<UserName>\AppData\Local\Android\Sdk
macOS: /Users/<UserName>/Library/Android/sdk
Linux: /home/<UserName>/Android/Sdk
Do you need a separate JDK for the SDK to work?
In modern versions of Android Studio (starting from version 2.2 and later) uses a built-in version of the JDK (called JBR). A separate installation of Java is not required unless you are using specific plugins or very old versions of the IDE.