AndroidDrive connects an Android smartphone to a Windows computer as a local drive. The software automatically detects a device via USB debugging, assigns a drive letter, and mounts its internal storage for direct file access. Users can manage files through Windows Explorer, adjust per-device settings from the taskbar, and disconnect drives without unplugging the cable. The program also supports custom drive letters, per-device connection rules, and integration with a companion Files app for folder icons and shortcut files. It runs on 64-bit Windows 10 or newer.
Automatic drive mounting. When an Android device is connected and USB debugging is active, AndroidDrive detects the hardware and immediately mounts its internal storage as a readable and writable drive on the Windows system. No manual file transfer mode is required, and the drive appears in Windows Explorer alongside local partitions. The mount happens without launching a separate synchronization window or copying data to a temporary location.
Per-device connection control. The taskbar icon provides a Devices submenu where each recognized Android unit can be configured independently. A checkbox determines whether that specific device mounts a drive automatically on future connections. This setting persists across sessions, so frequently used test devices can mount while secondary phones remain ignored by the system.
Manual drive disconnect. A connected drive can be temporarily unmounted via the Devices window without altering the automatic connection preference. This is useful when the user needs to remove the logical drive for a short period, for example during a backup operation or when another application requires exclusive access to the assigned drive letter. The physical USB connection remains active.
Custom drive letter assignment. AndroidDrive assigns the first available drive letter after C by default. The Device settings dialog allows selection of a specific letter for each Android device. If the user changes the letter while the drive is mounted, the program requires a disconnect and reconnect cycle for the new assignment to take effect, preventing conflicts with other mounted volumes.
Taskbar device management. The main interface is accessible from the Windows taskbar notification area. Right-clicking the AndroidDrive icon opens a menu with device-specific actions, including opening settings, disconnecting a drive, and viewing the list of currently connected Android hardware. This keeps the core window minimal while providing quick access to key functions.
Files app folder icon synchronization. The companion Files app for Android allows users to assign custom icons to folders directly on the phone. When the same storage is mounted through AndroidDrive, those custom icons are visible on the Windows side. This creates consistency between the mobile and desktop views of the same directory structure.
Shortcut file support on Android storage. Users can create standard Windows shortcut files (LNK) inside the mounted Android drive using Windows Explorer. Those shortcuts can then be opened on the Android device through the Files app. This enables cross-platform navigation where a desktop-created link to a frequently used folder remains functional on the phone.
Automatic detection with ADB backend. The software uses ADB to enumerate connected Android devices and communicate file operations. USB debugging must be enabled on the phone, including the full procedure of enabling developer options and the USB debugging toggle. This requirement applies to every device before first use.
Portable and installer versions. Releases include an installer executable and a portable ZIP archive. The portable version runs without modifying the Windows registry or requiring administrative installation. Users who want AndroidDrive to launch at system startup can place a shortcut in the Windows Startup folder manually.
Multilingual interface. The user interface has been translated into Chinese, English, French, German, Hungarian, Italian, Japanese, Korean, Brazilian Portuguese, and Swedish. Additional translations can be contributed through the project’s translation instructions. Language selection adapts to the system locale.
Compatibility with 64-bit Windows 10 and later. The current version requires a 64-bit edition of Windows 10 or newer. Older Windows 7 support exists only in version 2.0.6, which lacks newer features and receives no updates. Users on Windows 7 are advised to upgrade the operating system rather than rely on the outdated build.
Folder icon and shortcut consistency. The Files app and AndroidDrive together maintain a shared representation of the Android filesystem. Folder icons configured on the phone appear unchanged on the mounted Windows drive, and shortcut files created on the desktop remain usable on Android. No additional conversion step is needed for these file types.
Drive letter conflict avoidance. When no specific letter is chosen, the program scans available letters starting from D and picks the first free one. This prevents collisions with existing local drives, network mappings, and removable media. The automatic assignment works per session and can be overridden per device at any time.
CPU optimization for file operations. AndroidDrive includes optimizations to reduce slowdowns caused by Windows Explorer waiting for driver responses. File requests are forwarded to ADB in batches where possible. The performance cannot match a local SATA or NVMe drive because of ADB protocol overhead, but common operations like copying and browsing remain usable.
Disconnect without cable removal. The drive can be unmounted safely from the Devices menu before unplugging the phone. This prevents Windows from showing a delayed write failure or leaving a phantom drive letter. Reconnecting the same device later applies the saved settings and remounts the storage automatically if enabled.
AndroidDrive development started as a personal project by Gustav Lindberg to provide direct filesystem access to Android devices on Windows. The first public releases appeared several years ago, with version 2.0.6 supporting Windows 7 and earlier Qt 5 builds. Later the codebase moved to Qt 6, which required dropping Windows 7 support and raising the minimum system to Windows 10 64-bit. The program is written in C++ using the Qt framework for the user interface and relies on ADB for device communication and Dokan for the filesystem driver layer. The project repository hosts source code, release binaries, and translation files. Community members have contributed interface translations for Chinese, German, Hungarian, Italian, Japanese, Korean, and Brazilian Portuguese. The Files app for Android was created separately by the same developer to complement the desktop tool with folder icon management and shortcut compatibility. Development continues with releases published on GitHub, where bug reports and feature requests are tracked. The tested Dokan version is 2.3.1, and the installer downloads that version by default. AndroidDrive uses a taskbar-based interface rather than a traditional main window, keeping the application lightweight and always accessible during file operations.
