Working with Android Scoped Storage: A Practical Guide

Since Android 10, Google has been tightening the way apps interact with the file system. The change, called Scoped Storage, isolates each app’s private files and limits direct access to shared storage. For many users this feels like an unexpected roadblock when they try to move a photo, edit a document, or back up data.

Before you start

• Make sure your device is running Android 10 (API 29) or newer. The steps below work on Android 10, 11, 12, and 13, though wording may vary slightly between manufacturers.
• Back up any important data before granting broad file permissions, especially if you plan to use the MANAGE_EXTERNAL_STORAGE flag (often called “All files access”).
• Keep your device charged (or plugged in) and connected to a stable Wi‑Fi network if you intend to transfer large files.

What is Scoped Storage?

Scoped Storage is a security model that:

• Restricts apps to their own sandboxed directories (e.g., /storage/emulated/0/Android/data/com.example.app/).
• Requires apps to use the Storage Access Framework (SAF) when they need to read or write files outside their sandbox.
• Provides a set of “media collections” (MediaStore) that let apps access photos, videos, and audio without extra permissions.

The goal is to protect privacy: a compromised app can no longer rummage through every file on your device. However, the model also means you, the user, must sometimes take extra steps to get the file access you expect.

Accessing Files with the Storage Access Framework

Most modern file managers (Solid Explorer, MiXplorer, Files by Google) already implement SAF. When you open such an app for the first time, it will ask you to “Allow access to files on this device”. Granting this permission opens a system picker that lets you choose a directory – often the root of Internal storage – and the app receives a Uri that represents that folder.

If the file manager still cannot see certain folders (e.g., Android/data), you may need to grant it the special “All files access” permission on Android 11+.

Getting “All Files Access” (MANAGE_EXTERNAL_STORAGE)

Android 11 introduced a new permission MANAGE_EXTERNAL_STORAGE. When an app declares this permission and the user approves it, the app can bypass SAF and work with the entire external storage, similar to pre‑Android 10 behavior. Use this only when absolutely necessary, as it grants the app unrestricted file access.

Remember: granting this permission to a third‑party app effectively gives it the same rights as a system app. Only enable it for trusted managers.

Using ADB to Bypass Scoped Storage

When you need direct file access from a computer, ADB (Android Debug Bridge) provides a reliable way to explore the entire file system without modifying app permissions. ADB works over USB or Wi‑Fi and does not require root for most user‑accessible directories.

Note that /sdcard (or /storage/emulated/0) represents the shared external storage that is still reachable via ADB even under Scoped Storage. Private app data (/data/data/…) remains inaccessible without root.

Transferring Files Without a Computer

Sometimes you just want to move a file from one Android device to another. Here are three reliable, no‑root methods that respect Scoped Storage:

1. Nearby Share (Google’s native solution)

• Open Settings → Google → Device connections → Nearby Share and turn it on.
• On both devices, tap the share icon in the file manager, select Nearby Share, and choose the target device.
• The system handles the SAF permission automatically; you’ll see a progress bar and a notification when the transfer completes.

2. Files by Google (Wi‑Fi Direct)

• Install Files by Google on both phones.
• Tap Share at the bottom, then Send on the source device.
• Select the files, tap Send, and on the receiving phone tap Receive. The devices create a temporary Wi‑Fi Direct network.

3. Cloud‑based temporary links (e.g., Send Anywhere)

• Open the app, pick files, and generate a 6‑digit key.
• Enter the key on the target device to download the files directly, without needing a permanent cloud account.

Managing Media Files (Photos, Videos, Audio)

Media files are stored in well‑known MediaStore collections. Apps that request the standard media permissions (READ_EXTERNAL_STORAGE or READ_MEDIA_IMAGES on Android 13) can see them without SAF. However, you may still need to grant folder access for bulk operations.

Working with the Downloads Folder

The Download folder is a special case. Apps can read files there with the generic storage permission, but writing new files often requires the user to confirm via a SAF picker. This is why you sometimes see a “Save as” dialog when saving a document from a browser.

When an App Still Can’t See Your Files

Even after granting SAF or All Files Access, some apps may report “File not found”. Common reasons include:

• Incorrect path syntax: Android expects forward slashes (/) and case‑sensitive names.
• Scoped Storage enforcement on Android 12+: Apps targeting API 31+ must use the MANAGE_EXTERNAL_STORAGE flag for unrestricted access; otherwise they are limited to their own sandbox and MediaStore.
• OEM customizations: Some manufacturers hide the All files access toggle deep inside Settings → Privacy → Permission manager.

Troubleshooting checklist

1. Verify the app’s target SDK. If it targets Android 11 or higher, it may be refusing broad access by design.
2. Open Settings → Apps → [App] → Permissions and ensure All files access is enabled.
3. Restart the app after changing permissions – many apps only read permissions at launch.
4. If the problem persists, clear the app’s cache (Settings → Apps → [App] → Storage → Clear cache) and try again.

Safety warnings

• Granting MANAGE_EXTERNAL_STORAGE to an untrusted app can expose all your personal files to malicious reads or writes. Use it only for file managers you trust.
• When using ADB, avoid the adb shell rm -rf /sdcard/* pattern unless you are absolutely sure – a typo can erase everything on the shared storage.
• Never enable USB debugging on a device that you leave unattended in public places. An attacker with physical access could issue ADB commands.

Putting it all together – a typical workflow

Imagine you want to edit a video captured on your phone using a desktop video editor:

1. Open your preferred file manager (Solid Explorer) and grant SAF access to Internal storage.
2. Navigate to Movies/ and locate myclip.mp4.
3. Long‑press the file and choose Share → Nearby Share. Select your laptop (which must have Android 10+ support via the Nearby Share for Windows client or a compatible Android device acting as a bridge).
4. On the laptop, accept the transfer. The file lands in your Downloads folder.
5. After editing, use the same file manager to push the edited file back: tap the file → Share → Nearby Share → select your phone.
6. On the phone, choose the target folder (e.g., Movies/Edited) and confirm.

This flow respects Scoped Storage at every step, requires no root, and keeps your data private.

Conclusion

Scoped Storage may initially appear restrictive, but with a few practical tools—SAF‑enabled file managers, the optional All Files Access flag, and ADB—you retain full control over your files. By following the steps above you can safely read, write, move, and back up data on any Android 10+ device, while keeping the security benefits that Scoped Storage provides.