Add ADB and Fastboot to Windows PATH (No Android Studio)

You do not need a full Android Studio installation to use ADB and fastboot. Google publishes the Android Platform Tools as a standalone ZIP containing just adb.exe, fastboot.exe, and their dependencies. Once you add the folder to Windows PATH, both tools become available in every terminal window you open — no full paths, no IDE startup required.

Step 1: Download Platform Tools from Google

Go to developer.android.com/tools/releases/platform-tools and click the Windows download link. The file is typically named something like platform-tools_r35.0.2-windows.zip, though the version number changes with each release. This is a direct download from Google's servers with no installer — it is simply a folder of executables and DLLs packaged as a ZIP. Do not download ADB from third-party sites or app stores. Third-party distributions are often out of date, and some bundle modified binaries or extra software alongside the legitimate tools. The official ZIP from Google is always the safest and most current source.

Step 2: Extract to a Permanent Location

Right-click the ZIP and choose Extract All, or use 7-Zip or any other archive tool. Extract to a location that you will not move, rename, or accidentally delete later. Two good choices are C:\platform-tools (available to all users) or C:\Users\YourName\platform-tools (personal, no admin rights needed). Avoid paths with spaces in them, such as C:\Program Files\platform-tools or paths inside OneDrive folders — some older batch files and scripts do not handle spaces in PATH entries correctly, and paths inside sync folders can cause issues when the sync client locks files during use.

After extraction, open the folder and confirm it contains adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll, and a few other files. Take note of the complete folder path because you will paste it into the PATH editor in the next step.

Step 3: Add the Folder to the Windows PATH

The PATH editor is in the same place on both Windows 10 and Windows 11, though the route to get there differs slightly. The fastest method on either version is the Run dialog:

1. Press Win + R, type sysdm.cpl, and press Enter. The System Properties window opens.
2. Click the Advanced tab, then click the Environment Variables button near the bottom.
3. Two lists appear: User variables at the top (your account only) and System variables at the bottom (all accounts on this machine). Find the variable named Path in whichever section you want to use, and double-click it.
4. A multi-line editor opens showing each PATH entry on its own line. Click New and type the full path to your Platform Tools folder, for example C:\platform-tools.
5. Click OK on the Path editor dialog, then OK on the Environment Variables dialog, then OK on System Properties. All three windows must be closed with OK — pressing Cancel or X on any of them discards the change.

On Windows 11 you can also reach the same Environment Variables editor through Settings > System > About > Advanced system settings > Environment Variables. The editor is identical once you reach it.

Step 4: Verify the Setup

Open a new Command Prompt or PowerShell window. Existing terminal windows do not inherit PATH changes made after they were opened — this is the most common reason the verification step fails for first-time users. In the new window, run:

adb version
fastboot --version

A successful result looks like:

Android Debug Bridge version 1.0.41
Version 35.0.2-12147458
Installed as C:\platform-tools\adb.exe

If Windows responds with 'adb' is not recognized as an internal or external command, the PATH entry was either not saved correctly or the terminal window is not fresh. Double-check the Environment Variables editor to confirm the entry is present with the exact folder path and no typos. Also make sure you edited the correct section — user versus system PATH — and that you dismissed all three dialogs with OK rather than Cancel.

User PATH vs. System PATH: Which to Use

The Environment Variables editor shows two independent PATH lists. Adding to User variables makes ADB available only when your account is logged in and does not require administrator rights. Adding to System variables requires administrator elevation but makes ADB available to every user account on the machine, including background services and scheduled tasks that run under the system account. For a personal development laptop used by a single person, user PATH is almost always the right choice — it is safer, requires no UAC prompt, and works identically in practice. Choose system PATH only if you need ADB available to other users on the same machine or to automation scripts that run outside your user session.

Frequently Asked Questions

Can I update Platform Tools without editing PATH again?
Yes. Download the new ZIP and extract it to the same folder, overwriting the existing files. Since the folder path does not change, the PATH entry continues to point to the right place. Close and reopen any terminal windows to load the updated binaries. You do not need to touch Environment Variables again.

Why does adb work in Command Prompt but not in PowerShell?
Both read the same PATH, so if one works and the other does not, the PowerShell window was most likely opened before you saved the PATH change. Open a brand-new PowerShell window and try again. If the problem persists, check whether you are running PowerShell as Administrator — elevated windows can sometimes inherit a different environment than non-elevated ones, particularly on machines with group policies applied.

Does this conflict with Android Studio's own ADB?
It can. Android Studio includes its own copy of Platform Tools inside the SDK folder, usually at C:\Users\YourName\AppData\Local\Android\Sdk\platform-tools. If both folders are in PATH, Windows uses whichever entry appears first in the list. To avoid version mismatches, keep only one source in PATH. If you use Android Studio regularly, point your PATH at the SDK's platform-tools folder instead of a separate download — the SDK Manager updates it automatically.

Do I need to install any drivers separately?
For most Android devices on Windows you also need the appropriate USB driver before ADB can detect the device. Platform Tools provides the executables but not the drivers. Install the Google USB Driver from the SDK Manager for Pixel devices, or download the OEM USB driver package for other brands. Without the correct driver, ADB will list the device as unknown or will not detect it at all, regardless of whether your PATH is configured correctly.