Understanding Android Scoped Storage and Managing Your Files

13 min read Learn what Android scoped storage is, why it matters, and step‑by‑step ways to access, move, and back up your files on Android 10‑13 without losing data. September 28, 2026 19:30 How Android Scoped Storage Works and How to Manage Files Safely on Android 10‑13

When Android 10 introduced scoped storage, many users suddenly found themselves unable to see or move files the way they could on older versions. The change improves privacy, but it also adds friction for power users who need direct access to the file system. This guide explains exactly how scoped storage works, why it matters, and gives you concrete, safe ways to manage your files on Android 10‑13.

Before you start

Make sure your device is charged to at least 50 % and you have a stable Wi‑Fi connection. If you plan to use a computer, install the latest adb platform‑tools.

  • Back up important data (photos, documents, app data) to Google Drive, a PC, or an external SD card.
  • Enable Developer options (Settings > About phone > tap Build number seven times).
  • Turn on USB debugging (Settings > System > Developer options > USB debugging).

What is scoped storage?

Scoped storage is Android’s permission model that isolates each app’s private files from the rest of the system. Instead of a single, flat /sdcard directory that every app can read/write, Android now provides:

  • App‑specific directories (/Android/data/<package> and /Android/obb/<package>) that only the owning app can access.
  • Shared collections (Pictures, Downloads, Music, etc.) that are exposed through the Storage Access Framework (SAF). Apps request permission to a specific collection or file via a system picker.

Why does Android do this? By limiting broad file‑system access, the OS reduces the chance that a malicious app can read your personal documents or inject unwanted data into another app’s storage.

How Android implements scoped storage across versions

Android versionKey behavior
Android 10 (API 29)Scoped storage is enforced for new apps; legacy apps can opt‑out via requestLegacyExternalStorage="true" in the manifest.
Android 11 (API 30)Legacy opt‑out is removed for targetSdkVersion 30+. All apps must use SAF or MediaStore APIs.
Android 12‑13 (API 31‑33)Further restrictions on /Android/data and /Android/obb. File manager apps need the special MANAGE_EXTERNAL_STORAGE permission, which Google Play only grants for specific use‑cases.

Practical ways to access your files

Below are four reliable methods that work on most devices without rooting. Choose the one that fits your workflow.

1. Using the built‑in Files app (or Google Files)

  1. Open Files (or install Files by Google from Play Store).
  2. Tap Browse → Internal storage. You will see the top‑level folders: Download, Pictures, Music, etc.
  3. To move a file, long‑press it, then tap the Move icon (folder with an arrow). Navigate to the destination folder and confirm.
  4. To copy a file, use the Copy icon instead of Move.

What you’ll see: The Files app shows only the shared collections. App‑specific folders (/Android/data) are hidden unless the app has declared the MANAGE_EXTERNAL_STORAGE permission.

Do not grant MANAGE_EXTERNAL_STORAGE to random file managers; it gives them unrestricted access to all files, which defeats the purpose of scoped storage.

2. Using the Storage Access Framework (SAF) picker

Many third‑party file managers (Solid Explorer, FX File Explorer) use SAF to let you browse the entire external storage. The steps are similar:

  1. Install a SAF‑compatible file manager (e.g., Solid Explorer).
  2. Open the app and tap the + Add storage button.
  3. Select Internal storage** (or SD card) from the system picker that appears.
  4. Grant the requested permission. The app now shows the full directory tree, including Android/data and Android/obb if the device allows it.
  5. Use the app’s copy/move functions as you would on a desktop file manager.

This method works on Android 11 and later because the system picker mediates the permission—no special manifest flag is required.

3. Accessing files from a PC with ADB

ADB can pull and push files without needing the MANAGE_EXTERNAL_STORAGE permission, but it respects scoped storage rules. You can still reach shared collections and, with a simple flag, app‑specific directories for debugging purposes.

  1. Connect your phone via USB and confirm the Allow USB debugging prompt.
  2. Open a terminal on your PC and verify the connection:
    adb devices
  3. To list the contents of the shared Download folder:
    adb shell ls /sdcard/Download
  4. To pull a file to your PC:
    adb pull /sdcard/Download/example.pdf ~/Desktop/
  5. To push a file from your PC to the device:
    adb push ~/Desktop/newfile.jpg /sdcard/Pictures/
  6. If you need to access an app‑specific directory (e.g., /Android/data/com.whatsapp/files), add the run-as command for debuggable apps:
    adb shell run-as com.whatsapp ls /data/data/com.whatsapp/files
    Note: This only works for apps that are built with android:debuggable="true", which most production apps are not.

Why this works: ADB runs with the android.permission.READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE privileges granted to the shell user, which the OS treats as a trusted system component.

Never enable run-as on production apps; it can expose private data if the device is compromised.

4. Using a third‑party “full‑access” file manager (cautiously)

Some file managers request the MANAGE_EXTERNAL_STORAGE permission (sometimes called “All files access”). This gives them the same view as a pre‑Android 10 file system, but Google Play restricts such apps to specific categories (e.g., file management, backup).

  1. Install a reputable manager such as MiXplorer (APK from the developer’s site).
  2. When the permission dialog appears, read the description carefully and tap Allow.
  3. Open the app; you should now see the full /sdcard tree, including Android/data.
  4. Use the built‑in copy/move UI to reorganize files as needed.

Because this permission bypasses scoped storage, you should only use it when absolutely necessary and uninstall the app afterward if you no longer need it.

Granting MANAGE_EXTERNAL_STORAGE to an untrusted app is equivalent to giving it root‑like access. It can read any personal file, including WhatsApp backups, photos, and documents.

Backing up files safely under scoped storage

Even with the new model, backing up your data remains straightforward. Choose one of the following strategies:

  • Google Drive sync: The Files app can upload selected folders to Drive. Open Files > Browse > long‑press a folder > Upload.
  • PC backup via ADB: Use the adb pull commands shown earlier to copy your Download, Pictures, and Documents folders to a PC.
  • Local network backup: Install Syncthing or Resilio Sync on the phone and a PC. These apps use SAF to access shared collections and keep a continuous encrypted copy on another device.

Regardless of the method, verify the backup by opening a random file on the destination device.

Troubleshooting common issues

File manager can’t see Android/data

  • On Android 11+, the system hides this folder for apps without MANAGE_EXTERNAL_STORAGE. Switch to a SAF‑compatible manager or grant the permission temporarily.
  • If you’re using a PC, remember that adb pull /sdcard/Android/data will fail unless the app is debuggable. Use the app’s own export feature instead (e.g., WhatsApp’s Chat backup).

“Permission denied” when pulling files with ADB

  • Make sure USB debugging is enabled and the device is authorized.
  • Check that the file resides in a shared collection (/sdcard/Download, /sdcard/Pictures); files inside /Android/data are protected.
  • For Android 12+, you may need to enable the Allow access to data from the computer toggle under Settings > Privacy > Permission manager > USB.

Files disappear after moving them with a file manager

  • Some managers create a copy in the destination and then delete the original. If the destination is on an SD card formatted with exFAT, the system may delay the delete operation. Refresh the view or reboot.
  • Check the Recycle bin feature of the manager; the file may be waiting for permanent deletion.

When you really need full file‑system access

If your workflow requires unrestricted access—e.g., a custom backup script that copies every folder—you have three options, each with trade‑offs:

  1. Root the device: Gives true superuser rights, but voids warranty and can introduce security risks.
  2. Use the MANAGE_EXTERNAL_STORAGE permission: Works on Android 11+ but requires a special Play Store declaration and may be rejected for non‑compliant apps.
  3. Leverage a PC with ADB and the adb backup command: Creates a full‑device backup (including app data) without rooting, though the backup format is proprietary and can’t be browsed directly.

For most users, the combination of SAF‑compatible file managers and ADB for shared collections offers the best balance of safety and capability.

Summary of recommended workflow

  • Use the built‑in Files app for quick moves within shared collections.
  • Install a SAF‑compatible manager (Solid Explorer) when you need to see Android/data or Android/obb.
  • Rely on ADB for bulk transfers to a PC; it respects scoped storage while still giving you command‑line power.
  • Reserve MANAGE_EXTERNAL_STORAGE for occasional, trusted tasks, and revoke the permission afterward.

By understanding how scoped storage isolates data and by using the right tool for each job, you keep your files organized, backed up, and private—without fighting the operating system.

User Comments (0)

Add Comment
We'll never share your email with anyone else.