How to specify the path to the Android Studio SDK: a complete guide

Development of mobile applications for the platform Android inevitably confronts the engineer with the need to correctly configure the development environment. One of the most common problems that new and experienced developers encounter when migrating or reinstalling a system is the missing or incorrect location error Android SDK. Without the correct path, the compiler will not be able to find the necessary libraries, emulators and build tools, which makes the process of writing code impossible.

The situation is aggravated by the fact that the standard location of files may differ depending on the operating system, version Android Studio and user access rights. Sometimes the tools folder ends up on the system drive, running out of space, and you have to move it manually. In other cases, the studio simply “loses” the link after updating drivers or changing the directory structure. Understanding how to manage these paths is a basic skill for any Android developer.

In this article, we will look in detail at the mechanisms for linking a development environment to a set of tools. We will look at both standard IDE interface tools and manual editing of configuration files and environment variables. You will learn to diagnose problems when the studio does not see installed components, and you will be able to flexibly manage the location of heavy packages on your computer.

Standard SDK location paths in different OS

Before you try to change the settings, you need to understand where the operating system and installer by default Android Studio place tool files. Knowing the standard paths helps you quickly navigate when searching for lost data or when checking your configuration after installation. The location is strictly tied to the user's home directory or system app folders.

In the environment Windows the path is usually hidden in the user profile. The standard directory looks like C:\Users\UserName\AppData\Local\Android\Sdk. Please note that the folder AppData is hidden by default, so to access it you will need to turn on show hidden items in Explorer or manually enter the path in the address bar. This is important, since many users are looking for the SDK in app Files, which is an error for modern versions of the studio.

On computers running macOS the file structure is different. Here the tools are most often located along the path /Users/UserName/Library/Android/sdk. The folder Library may also be hidden in newer versions of macOS, but it is easily accessible through Terminal or the Finder's go menu. For users Linux the standard location is a hidden folder in the home directory: /home/UserName/Android/Sdk.

⚠️ Attention: If you installed SDK manually to an arbitrary folder (for example, to drive D: to save space on the system partition), the standard paths above will not work. You need to remember the location you have chosen or find it by searching for files by name adb.exe or platform-tools.

Sometimes when updating the operating system or changing an account, the names of user folders may change, which leads to broken links. In such cases, the studio cannot automatically find the instruments, even if the files are physically there. This is why knowing alternative path configuration methods is critical for smooth operation.

Setting the path through the Android Studio interface

The easiest and safest way to specify or change the location of the toolkit is to use the built-in settings of the development environment itself. This method does not require any work with the registry or terminal and automatically updates the project's internal configuration files. The settings interface is intuitive and provides visual control over installed components.

First you need to open the main settings menu. Depending on your operating system, the path to this menu will be different. On Windows and Linux you should select item File → Settings (or use hot keys Ctrl+Alt+S). Users macOS need to go to the menu Android Studio → Preferences (or press Cmd+,). After opening the settings window, navigation is carried out through the category tree on the left side of the screen.

You need to find the section responsible for platforms and tools. Follow the path Appearance & Behavior → System Settings → Android SDK. At the top of the panel that opens you will see a field Android SDK Location. This is where the currently active path is displayed. If the path is incorrect or the folder is empty, the studio will display a warning in red.

To change the location, click on the folder icon to the right of the text field or the button Edit. A standard directory selection dialog will open. Specify the path to the folder containing the SDK. After selection, click Apply and OK. The system will check for the presence of the necessary files. If the folder structure is correct, the status will change to “SDK installed”, and you will be able to manage packages through the tab SDK Platforms i SDK Tools.

Sometimes after changing the path, the interface may require a restart of the development environment to apply the changes. This is normal behavior, especially if the paths to the emulator or debugging tools have been affected. Do not ignore the restart request, as background build processes may continue to use old cached paths until a full restart. Android Studio.

Manually editing the local.properties file

In situations where the studio interface does not save changes or you are working with a project received from another developer, you may need to directly edit the project's configuration file. The file local.properties is located in the root directory of your project and contains local machine-specific settings that should not be included in the version control system.

This file is automatically generated when creating a project, but its contents can be changed manually. Open the file local.properties in any text editor. Find the line starting with sdk.dir. It should contain the absolute path to your tools folder. The path syntax depends on the operating system, and errors often occur here due to character escaping.

For users Windows the backslash is a service character, so it must be escaped. The correct path entry will look like this:

sdk.dir=C\:\\Users\\Name\\AppData\\Local\\Android\\Sdk

Note the double backslashes \\. If you leave single ones, the Gradle build system will not be able to read the path correctly and will throw a compilation error. For users macOS i Linux a forward slash is used and no escaping is required:

sdk.dir=/Users/Name/Library/Android/sdk

After making changes, be sure to save the file and sync the project with the Gradle files. In Android Studio, this is done by clicking the button Sync Now, which appears at the top of the editor, or through the menu File → Sync Project with Gradle Files. If the path is correct, the project should build successfully without missing SDK errors.

Why is the local.properties file not getting into Git?

This file contains absolute paths that are unique to each developer's computer. If you add it to the repository, other team members will experience build errors because their SDK paths are different. Therefore, it should always be in .gitignore.

It is worth remembering that manually editing this file will override the settings specified through the IDE interface. If you change the path in the studio settings, but forget to update local.properties, a configuration conflict may occur. Always check this file if you encounter strange build errors that are not explained by the logic of the code.

Setting the environment variables ANDROID_HOME and ANDROID_SDK_ROOT

For many third-party tools, automation scripts and the command line, it is not enough to specify the path only inside Android Studio. System environment variables allow you to make the path to the SDK available to any app on the operating system. This is especially important when using Flutter, React Native or building projects through a terminal without running the IDE.

Modern versions of Google tools recommend using variable ANDROID_SDK_ROOTalthough the old variable ANDROID_HOME is still supported for backwards compatibility. It's best to define both variables with the same path. This ensures that any script that expects any of these variables will be able to find the necessary files.

Configuration process Windows is carried out through the system properties. Right-click This PC, select Properties, then Advanced System Settings. In the window that opens, click the “Environment Variables” button. In the "User Environment Variables" block (top part), create a new variable with a name ANDROID_HOME and a value equal to the path to your SDK folder.

After creating the main variables, you need to update the system variable Pathso that commands like adb or avdmanager worked from any folder in the terminal. Find the variable Path in the list of user variables, select it and click “Edit”. Add new lines pointing to the tool subfolders:

• 📂 %ANDROID_HOME%\platform-tools
• 📂 %ANDROID_HOME%\tools
• 📂 %ANDROID_HOME%\tools\bin
• 📂 %ANDROID_HOME%\cmdline-tools\latest\bin

On macOS and Linux, configuration is done through a shell profile file, for example .bashrc, .zshrc or .profile. Add the following export lines to the end of the file:

export ANDROID_HOME=$HOME/Library/Android/sdk
export ANDROID_SDK_ROOT=$HOME/Library/Android/sdk
export PATH=$PATH:$ANDROID_HOME/emulator
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/tools/bin
export PATH=$PATH:$ANDROID_HOME/platform-tools

After saving the file, apply the changes with the command source ~/.zshrc (or the corresponding file of your shell). You can check the success of the setup by entering the command in the terminal echo $ANDROID_HOME —it should display the path you specified.

⚠️ Attention: After changing environment variables in Windows, be sure to close and reopen the terminal or development environment. Previously launched applications will not see the updated variables, since they are read only when the process starts.

Moving the SDK to another drive and solving space problems

Over time, the Android SDK folder can grow to tens of gigabytes due to the accumulation of different versions of platforms, emulator images and tools assemblies. The system disk often has limited space, and moving the SDK to another partition becomes a necessity to maintain system performance. However, simply dragging the folder with the mouse will result in lost connections.

To move safely, first completely close Android Studio and all associated emulator processes. Find the current SDK folder (using the knowledge from the first section) and copy it to a new drive, for example, to the root of the D: folder AndroidSDK. Wait until the copying is completed, as the set of files can be very large.

After copying, delete or rename the old folder (just in case) so that the system does not use it out of habit. Then open Android Studio and go to settings as described in the second section. Specify the new path to the moved folder. The studio will scan the directory and pick up all previously installed packages without the need to download them again from the Internet.

SDK component	Average size	Can be deleted?	Recommendation
Android Emulator	~500 MB	No	Required for tests
System Images (x86_64)	5-10 GB per version	Yes (old)	Leave 1-2 current
Build-Tools	200-300 MB per version	Yes (old)	Delete versions older than 2 years
Platform Tools	~50 MB	No	Always update

If you encounter permissions errors after moving, especially on Linux or macOS, make sure the current user has read and write permissions to the new folder. The command chmod -R 755 /path/to/sdk can help correct access rights if the system blocks writing update tools.

Error diagnosis and common problems during setup

Even with the correct path specified, problems may occur specific errors related to access rights, antiviruses or broken links. Understanding error codes helps you quickly isolate the problem. Often the studio reports “SDK is missing” or “Unable to install SDK tools”, which may be a result of files being blocked by security software.

One ​​of the common problems is a conflict between versions Gradle and installed Build Tools. If a project specifies a plugin that requires a version of the tools that is not in the SDK folder, the build will fail. In this case, you need to open the SDK Manager and install the missing version indicated in the compilation error.

You should also pay attention to the symbols in the path. The path to the SDK should not contain spaces or national characters (Cyrillic) if you are working in an encoding-sensitive environment. Although modern versions of Windows and Android Studio have become more resistant to such paths, the use of Latin characters and the absence of spaces (for example, C:\Dev\AndroidSDK instead of C:\My apps\Android SDK) remains the gold standard for avoiding surprises.

⚠️ Attention: Some antiviruses can block the execution of files from the folder platform-tools, considering them suspicious due to the possibility of debugging the device. Add the SDK folder to the exceptions of your antivirus if you encounter access errors when connecting your phone.

In the case when nothing helps, a radical but effective method is to completely delete the SDK folder and studio tools, followed by a clean installation. Sometimes the configuration files inside a folder .android or studio cache become so corrupt that it is easier to start from scratch than to look for one erroneous setting deep in subdirectories.

Why does Android Studio not see the SDK after reinstalling Windows?

After reinstalling the OS, user names and file security identifiers change. Even if you copied the SDK folder from the old drive, the permissions may be reset, or the registry/settings path may refer to a non-existent profile. You need to re-specify the path in the studio settings and check the access rights to the folder.

Is it possible to store the SDK on a network drive?

Technically this is possible, but it is highly not recommended. The build tools and emulator require high speed access to many small files. Working over a network will cause significant delays when compiling and launching the emulator, and can also lead to file locking errors if multiple users are accessing the disk at the same time.

What to do if the SDK Location field in the settings is inactive (grayed)?

This can happen if the project is not open or the studio is in welcome mode. Open any existing project or create a new "Hello World". Also make sure that you have administrator rights to make changes to global settings if you are using an enterprise version of the software with restrictions.

How to find the version of the installed SDK?

There is not one version file inside the SDK folder, since it is a set of components. To find out the versions of platforms and tools, open the file source.properties in the folder tools or use the command sdkmanager --list in the terminal. In Android Studio itself, versions are displayed in the SDK Platforms and SDK Tools tab in the settings.

Does the path to the SDK affect the operation of the emulator?

Yes, directly. The emulator stores its images and data in a subfolder emulator inside the SDK. If the path is incorrect, the studio will not be able to find the emulator executable file. In addition, moving the SDK to a slow HDD can critically slow down the startup of a virtual device compared to working on an SSD.