Managing Files Safely with Android Scoped Storage

Android 11 introduced scoped storage as the default way apps access files. Instead of letting every app roam the entire external storage, the system now isolates each app’s private folder and forces shared‑file access through the Storage Access Framework (SAF). For most users this improves privacy, but it also changes how you move, copy, or delete files manually.

Before you start

• Back up any critical data (photos, documents, PDFs) to Google Drive, a PC, or an external SD card. Scoped storage itself does not delete files, but granting broad permissions to the wrong app can expose them.
• Make sure your device is running Android 11 or newer. Go to Settings > About phone > Android version to confirm.
• Charge your phone to at least 50 % or keep it plugged in. Some file‑moving operations can take several minutes.
• Connect to a stable Wi‑Fi network if you plan to move large files to cloud storage.

Understanding Scoped Storage

Before Android 10, apps could request the READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE permissions and then read or write any file on the shared external storage (the "sdcard" partition). This made it easy for malicious apps to scan your photos or inject unwanted files.

Scoped storage changes the model:

• App‑private directory: Each app gets its own sandboxed folder (/Android/data/package.name/) that no other app can see.
• Media collections: Photos, videos, and audio are stored in shared media collections that the system indexes. Apps can add or read items only through the MediaStore API.
• Storage Access Framework: For any other file type (PDFs, ZIPs, etc.) the user must explicitly pick a file or folder via the SAF picker. The app receives a Uri that grants limited, revocable access.

Why does this matter to you? It means you cannot simply use a file manager to copy /Download/secret.txt into /Android/data/com.example.app/files/ without either the file manager supporting SAF or the app requesting the special MANAGE_EXTERNAL_STORAGE permission (often called “All files access”).

Step 1 – Verify that Scoped Storage Is Active

1. Open Settings → Apps & notifications → See all apps.
2. Select any app that you know previously accessed the whole storage (e.g., a legacy file manager).
3. Tap Permissions. If you see All files access listed, the app is using the legacy model. If not, the system is enforcing scoped storage for that app.

If none of your apps show “All files access”, your device is already running in the scoped‑storage mode, which is the expected default on Android 11+.

Step 2 – When You Really Need Broad Access

Some power‑users or specific workflows (e.g., moving a large batch of files from a USB‑OTG drive into multiple app folders) may require the MANAGE_EXTERNAL_STORAGE permission. Grant it only to apps you trust.

1. Install a reputable file manager that declares the permission, such as Solid Explorer or MiXplorer. Both are available on the Play Store.
2. Open Settings → Apps & notifications → Special app access → All files access (the exact wording may vary: on Samsung it appears as “Files and media”).
3. Find the file manager you installed and toggle the switch to Allow.
4. A system dialog will warn you about the risk. Read it carefully and tap Allow if you are comfortable.

Step 3 – Moving Files Using the Storage Access Framework

If you prefer not to grant broad access, you can still move files safely using the SAF picker that many modern file managers provide.

1. Open the built‑in Files by Google app (pre‑installed on most devices).
2. Navigate to the file or folder you want to move.
3. Long‑press the item and tap the Move icon (a folder with an arrow).
4. The system will open a SAF picker. Navigate to the destination folder. For app‑private locations, choose Internal storage → Android → data → <package.name> → files. If the folder does not exist, you can create it using the + New folder button.
5. Tap Move here. The file manager will copy the file via the SAF Uri and then delete the original.

After the move, open the target app and verify that the file appears where expected. Most apps that rely on SAF will automatically refresh their view.

Step 4 – Using “All files access” for Bulk Operations

When you have dozens or hundreds of files, the SAF picker can become tedious. Here’s a faster workflow with a file manager that has “All files access”.

1. Launch Solid Explorer.
2. Navigate to Internal storage → the source folder (e.g., Download).
3. Select multiple items (tap the checkbox icon in the toolbar).
4. Tap the Move button.
5. In the navigation pane, scroll to Android → data → <your.app.package> → files. If you need a sub‑folder, create it now.
6. Confirm the move. Solid Explorer will perform a direct file‑system copy because it has the MANAGE_EXTERNAL_STORAGE permission.

When the operation finishes, you can go back to Special app access and toggle “All files access” off for Solid Explorer to reduce the attack surface.

Step 5 – Verifying the Move

1. Open the destination app that should read the file.
2. Use the app’s “Import” or “Open” function to locate the file. Because the file now lives inside the app’s private folder, the app can read it without SAF.
3. If the app reports “File not found”, double‑check the path using a file manager with “All files access” turned on.

Common Pitfalls & Troubleshooting

1. The destination folder is missing

Some apps do not create their files directory automatically. Use a file manager with broad access to create the folder manually before moving files.

2. Files disappear after a reboot

This usually happens when the file was placed in a location that the system cleans up (e.g., Android/data on external SD cards on Android 12+). Keep permanent files on internal storage or on the primary shared media collections.

3. “Permission denied” errors

If you see this while moving files without “All files access”, you are likely trying to write outside the SAF‑allowed area. Switch to the SAF picker or grant the permission temporarily.

4. Apps cannot see moved files

Some apps cache the list of available files. Force‑stop the app (Settings > Apps > [App] > Force stop) and reopen it, or clear its cache.

5. “All files access” option missing

On Android 13+, the permission is hidden behind a new setting: Settings > Privacy > Permission manager > All files access. Look there if you cannot find it under “Special app access”.

Step 6 – Revoke Broad Permissions When Done

Leaving “All files access” enabled for a file manager is a security risk. After you finish bulk moves, follow these steps:

1. Open Settings → Apps & notifications → Special app access → All files access.
2. Find the file manager and toggle the switch off.
3. Optionally, uninstall the file manager if you only needed it for this one‑off task.

Best‑Practice Checklist

• Always back up before moving large batches of files.
• Prefer SAF‑compatible file managers for everyday tasks.
• Grant MANAGE_EXTERNAL_STORAGE only when absolutely necessary and revoke it immediately after.
• Keep important documents in shared media collections (Documents folder) if you need cross‑app access without special permissions.
• Test the moved file with the target app before deleting the original copy.

By following this workflow you get the privacy benefits of scoped storage while still retaining full control over where your files live. The approach works on the majority of Android 11‑13 devices, regardless of manufacturer, because it relies only on standard system settings and the official Storage Access Framework.

Now you can move photos, PDFs, or any other file type safely, keep your data private, and avoid the dreaded “App can’t find my file” errors that many Android users encounter.