Users of the Android operating system are often faced with the need to find the physical location of installed apps. This may be required to create a backup copy, transfer data to a new smartphone, or clear memory of “garbage” that cannot be removed by standard means. However, unlike Windows, the Google Android file system has a strict hierarchy and layers of protection that hide system files from normal viewing.

In this article we will take a detailed look at the directory structure where installation files APK and user data are stored. You will learn the difference between system directories and public storage. We will also look at methods for accessing hidden partitions that require elevated privileges or the use of specialized software.

Understanding how the file system works will help you manage space on your device wisely. We will explain why some folders are inaccessible without root access and how to safely work with system files so as not to disrupt the operation of operating system.

Standard paths to APK installation files

When you download an application from Google Play or install it manually, the system saves the installation package in a specific location. For regular users who do not have superuser rights, only one main directory is available. The path to it looks like /storage/emulated/0/Android/obb or similar directories in the shared storage, but the “bodies” of the apps themselves lie deeper.

The main directory, where the system stores all installed applications, is located in the root section of the file system. The path to it: /data/app. Inside this folder, subdirectories with package names are created (for example, com.example.app-1). This is where files base.apk and additional split packages for different screen or processor configurations are located.

⚠️ Attention: The directory /data/app is hidden from standard file managers. Trying to copy an APK file from there without root access will result in an access error.

To extract the installation file without root access, you can use the “Share” function in the application settings or third-party extractor utilities. They copy the APK from the protected area to the internal memory, from where it can be transferred to the computer.

💡

Use the APK Extractor application to save a copy of the installed app directly to the internal memory, where it can be easily found through any Explorer.

Folders with data and application cache

In addition to the installation file itself, each application is allocated space for storing user data, settings and temporary files. This data is divided into two main categories: private data and public cache. Private information is stored at the path /data/data/[package_name].

This directory contains databases databases, preferences shared_prefs and cache files cache. This folder can only be accessed as root or via USB Debugging (ADB) with the appropriate permissions. A regular file manager will show emptiness here or display a message about lack of rights.

On the other hand, part of the application data intended for public access (for example, downloaded pictures in instant messengers or offline navigator maps) is stored in a public area. The path to it: /storage/emulated/0/Android/data. Here the folders are also named according to package IDs.

  • 📁 /data/data —contains critical settings and logins, the removal of which will reset the application.
  • 🗑️ /data/cache —temporary files that can be safely cleared to free up space.
  • 📂 /Android/data —a folder with media files and downloads of specific apps, accessible without root.

Starting with version Android 11, Google has tightened access to the folder Android/data. Now standard explorers cannot display its contents. To view files in this section, you will need to use a file manager with special access (for example, through the system file selection dialog) or connect your smartphone to the PC in file transfer mode.

Access to system partitions via root access

Obtaining superuser rights (Root) allows full access to the entire file system of the device. This allows you not only to view, but also to edit, move or delete files in protected sections. To manage files with such rights, specialized managers are required, such as Root Explorer or MiXplorer.

When you enable Root access, you will be able to enter the directory /system/app and /system/priv-app. System applications preinstalled by the manufacturer or telecom operator are stored here. Removing apps from these folders can lead to unstable operation of the system or a “bootloop” (cyclic reboot).

☑️ Check before deleting system files

Done: 0 / 4

It is important to understand the difference between user and system applications. User apps, even if installed on the partition /data, can be safely deleted. System applications are often integrated into the shell UI and are necessary for the basic functionality of the phone.

⚠️ Warning: Changing access rights (chmod) or deleting files in a folder /system may make the device unusable. Act only if you are completely sure of the purpose of the file.

If you plan to freeze or delete a system application, it is better to use special utilities like Titanium Backup or Solid Explorer with the system package management function, rather than deleting files manually through Explorer.

Using ADB to view files without Root

For advanced users who do not want to root the device, but need access to protected folders, there is a tool ADB (Android Debug Bridge). This is a console utility included in the Android SDK, which allows you to control the device from your computer.

Using the command adb shell you get access to the command line of your smartphone. However, by default in debug mode you do not have rights to read the directory /data/data. But you can use the command run-as to access the data of a specific application being debugged.

adb shell run-as com.example.app ls /data/data/com.example.app

This command will list the files in the data folder of a specific application if it is compiled in debuggable mode. For most applications from Google Play, this method will not work directly, but there are workarounds by creating backup copies.

The command adb backup allows you to create a full backup of the application along with the data, which can then be unpacked on your computer and examine the file structure. This is a legal and secure way to access the contents of private folders without violating the warranty.

How to unzip an .ab file from ADB

The backup file created through ADB is in .ab format. To read it on a PC, you will need the android-backup-extractor utility. Command for conversion: java -jar abe.jar unpack backup.ab backup.tar. The resulting tar archive can be opened with any archiver.

Features of the file system in Android 11, 12 and later

With the release of new versions of the operating system, Google introduced the concept of “Scoped Storage” (limited storage). This fundamentally changed the way applications and users interact with files. Now direct access to shared folders is closed for all applications.

B Android 11 and above folder Android/obb and Android/data have become completely hidden for third-party file managers. The system requires special permission to be granted through the system interface to access these directories. This is done to improve security and prevent data collection by shady apps.

Android version Access to /Android/data Access to /data/app Access method
Android 9 and below Full access Root only Any explorer
Android 10 Limited Root only System dialog
Android 11+ Closed by default Root/ADB only Special. resolution or PC
Android 13+ Strict control Root/ADB only Photo/Video access separately

If you need to manage files in these folders on a modern smartphone, it is recommended to connect the device to your computer via USB. In file transfer mode (MTP), Scoped Storage restrictions are often not applied to an external observer, and you will be able to see the full directory structure.

📊 What version of Android are you running now?
Android 9 and later
Android 10
Android 11
Android 12 and later

Frequent problems and questions when searching for applications

Users often wonder why, after clearing the memory, applications continue to take up space. The fact is that standard cache clearing does not affect the folder Android/obb, where gigabytes of game data can be stored. Also, some messengers create their own folders in the root of the internal memory, ignoring the standard structure.

Another common problem is the inability to find the APK file after updating the application. When updating via Google Play, the old file is replaced by the new one and the temporary installer files are deleted. If you just need the installation file, you will have to extract it from the current version of the app.

💡

The Android file system is dynamic: paths may change depending on the OS version, shell manufacturer and application type (system or user).

To search for “heavy” folders, it is recommended to use the built-in storage analyzer in the phone settings or an application like DiskUsage. They visualize spaces and show which folder with the application takes up the most space, which simplifies navigation through the file system.

Where exactly is the APK file of the installed application?

Physically the file is located along the path /data/app/[package_name]/base.apk. However, without root you will not be able to see this file directly. Use extractor applications that copy this file to an accessible Download folder.

Is it possible to transfer the game folder to an SD card?

Yes, many games allow you to transfer the cache (obb folder) to the card memory through the settings of the application itself. However, the application's system files will remain in the internal memory. In Android 11+, transferring to an SD card is severely limited.

Why is the Android/data folder empty in the file manager?

Starting with Android 11, access to this folder for third-party applications is blocked by the Scoped Storage security policy. To see the files, use a PC connection or give the file manager special permission through a system prompt.

How to remove an application that cannot be removed through settings?

If the application is not uninstalled in the standard way, it may have device administrator rights or be a system application. Check your security settings and revoke administrator rights, or use the ADB command pm uninstall -k --user 0 [package_name].