Get the Android USB driver
The Google USB Driver is for Google devices and comes from Android Studio's SDK Manager, SDK Tools tab, or as a ZIP on developer.android.com. Phones from other brands need their own maker's driver, which Google's OEM list links to. You need either one only for adb debugging on Windows.
Checked October 30, 2026 against the manufacturer's own pages.
Driver downloads
| Driver | Version | Released | Size | Windows | Download |
|---|---|---|---|---|---|
| Google USB Driver (usb_driver_r13-windows.zip) | r13 | See maker page | See maker page | Windows | Download from developer.android.com |
Values copied from the manufacturer's page on October 30, 2026. The file always downloads from the manufacturer, never from this site.
Hardware IDs on this page
| Hardware ID | Device name |
|---|---|
USB\VID_18D1&PID_4EE1 | Nexus/Pixel Device (MTP) |
USB\VID_18D1&PID_4EE2 | Nexus/Pixel Device (MTP + debug) |
USB\VID_18D1&PID_D002 | Nexus 4 (debug) |
USB\VID_18D1&PID_2D01 | Android Open Accessory device (accessory + ADB) |
Match the first line of Hardware Ids in Device Manager (Properties, Details) against this list. Names come from the public PCI ID Repository.
The short version
What to install and where it comes from. Every link goes to the manufacturer or Microsoft, never to a copy.
Official files only, nothing bundled
Step by step
Find out who made the phone
Google's driver covers Google devices only. For a Samsung, Motorola, Xiaomi or other brand, use that maker's driver from the OEM list on developer.android.com.
Install through Android Studio
In Android Studio choose Tools, SDK Manager, then the SDK Tools tab. Tick Google USB Driver, click OK and let it install. Files land in android_sdk\extras\google\usb_driver\.
Or download the ZIP
On Google's page, accept the Android SDK License Agreement and download the Windows ZIP. Unpack it somewhere you can find again.
Point Device Manager at the folder
Connect the phone, open Device Manager, right-click it under Portable Devices or Other devices and choose Update driver. Browse my computer, then pick the usb_driver folder.
Turn on USB debugging and test
In Developer options enable USB debugging, accept the prompt on the phone, then run adb devices. Your phone should be listed.
Two kinds of Android driver
Google ships one driver that covers its own hardware, such as Pixel and Nexus phones. Every other maker is expected to publish its own. Google keeps a list of those maker pages in its OEM driver guide, covering names such as Samsung, Motorola, Lenovo, Huawei, Sony and Xiaomi. If a brand is missing from the list, look in the support section of that maker’s own site.
When Windows asks for a driver
A phone in debugging mode can appear as Android Composite ADB Interface or as an unknown device under Other devices. Windows lacks a matching INF at that point. Installing the right driver from the steps above adds one, and the device then shows up under Android Phone. To upgrade an old driver, Google says to update the Android Composite ADB Interface and point it at the driver folder.
Where the IDs fit
Google’s USB vendor ID is 18D1. The ID list shows several product IDs, including entries for MTP, MTP with debug, and Android Open Accessory modes. The product ID changes with the USB mode, so a phone can look like a different device after you toggle debugging.
macOS and Linux
Google notes that macOS and Linux do not need a USB driver. If you move to one of those systems, adb works without an install.
Questions
What is ADB?
Android Debug Bridge is a command line tool from Google. It lets a PC talk to a phone for installing apps, reading logs and running shell commands.
Do I need a driver to copy photos?
No. Photo copying uses MTP, and Windows has that built in. The Android USB driver is for debugging and development.
Can I use the Google driver for a Pixel and a Samsung?
Google's page describes it as the driver for Google devices. Use the Samsung driver page for a Galaxy.
Should I edit the INF file?
Google warns that editing android_winusb.inf for other devices raises security warnings on install, and other changes can break installation. Use the maker's own driver instead.