User-selected access
You select a document or supported folder in the system picker. Access is granted only after you confirm your choice, and Android may restrict certain locations.
Android Privacy & Storage Guide
Android Storage Access Framework (SAF): a practical guide
Android's Storage Access Framework gives users more control over which files and folders an application can access. Instead of automatically exposing all device storage, Android can show its own file picker and let the user explicitly choose what an application is allowed to use.
Introduction
What is the Storage Access Framework?
The Storage Access Framework, often shortened to SAF, is an Android system that allows applications to work with documents, files and folders selected by the user.
Instead of an application silently browsing storage, Android can display a system-controlled interface where the user chooses the location or file that should be accessible.
Android-controlled interface
The picker itself is provided by Android. This means the operating system, rather than the app, controls the screen used to select supported files or folders.
Reduced storage exposure
SAF makes it possible for an application to work with a specific authorised location without requesting unrestricted access to every file on the device.
Privacy model
Why Android prefers explicit permission
A modern phone may contain personal photographs, downloaded documents, financial records, videos, application data and other sensitive information.
Giving every application broad access to all storage would expose much more information than many apps actually need. SAF helps reduce that exposure by making the user part of the permission decision.
The user can see which location is being selected.
The application receives access only after confirmation.
Permission can later be removed or replaced.
Broad device-wide storage access is not necessary
for many folder-based workflows.
How it works
What happens when an app asks you to choose a folder?
A typical SAF folder workflow can be understood in several simple stages.
01
The app requests a folder
The application asks Android to open the system folder picker. The app itself does not need to design or control the actual storage-selection interface.
02
Android displays storage locations
Android shows locations and document providers that are available to the user. The exact appearance can differ slightly between Android versions and device manufacturers.
03
The user chooses a location
The user navigates to the desired folder and confirms the selection. Until this confirmation happens, the application has not been granted that folder permission.
04
Android returns a URI
Android represents the selected location using a URI rather than requiring the application to depend entirely on a traditional raw file-system path.
05
The app uses the authorised location
The application can work with the files Android allows it to access through the selected URI and its granted permission.
06
Permission may be retained
For supported document-tree selections, the app may retain the granted URI permission. If the grant expires or the location changes, you may need to select the folder again.
URI permissions
What does “persisted URI permission” mean?
Applications using SAF commonly work with content URIs. A URI acts as an Android reference to content made available through a document provider or storage interface.
In some workflows, Android allows the application to retain the permission associated with that URI after the initial selection. This is often called persisted URI permission.
URI instead of raw path
A URI gives the application a structured Android reference to authorised content. Applications should not assume that every storage location behaves like an ordinary desktop file-system path.
Permission is attached to access
A URI identifies content but is not permission by itself. Android grants specific read or write capabilities; choosing a folder does not automatically allow every action.
Saved access can survive app restarts
A persisted URI grant can remain valid after restarting the app or phone. It does not guarantee access if the folder moves, is deleted, or permission is revoked.
Scoped storage
How SAF fits into modern Android storage
Modern Android versions use a storage model that places stronger boundaries around application files and shared device media. This approach is commonly discussed under the term scoped storage.
Scoped storage does not mean applications can never work with user files. Instead, Android provides purpose-specific methods such as MediaStore and the Storage Access Framework.
App-private storage
Applications can keep internal files inside private storage intended primarily for that application.
Other ordinary applications generally do not browse that private storage as if it were a normal shared gallery.
Shared media
Android's MediaStore helps applications work with shared collections such as photos and videos in a structured way.
User-selected documents and folders
SAF is useful when the application needs access to content or a directory that the user explicitly chooses through Android's storage interface.
SAF vs All Files Access
Why they are not the same permission model
SAF and broad device-wide file access are fundamentally different approaches.
SAF
The user selects the specific document or folder to which access should be granted.
This keeps the permission tied to an explicit user choice.
Broad file access
Broad access can expose much more of the device's shared file system to an application and is appropriate only for use cases that genuinely require that level of access.
Choose the narrowest useful permission
A privacy-focused application should generally request only the access needed for its actual functionality rather than asking for broader permission simply because it is easier.
Status Saver example
Why Status Saver uses a folder-selection workflow
Status Saver needs access to a supported status-media location, not unrestricted access to every unrelated file on the device.
This makes Android's user-controlled folder-selection model a suitable approach for connecting a status source.
A
Select WhatsApp or WhatsApp Business
The user first identifies which source application contains the statuses they want to access.
B
Open Android folder selection
Android presents the storage picker so the user can choose the appropriate status-media folder.
C
Store the authorised reference
Once permission is granted, the app can remember the authorised source so it can be used again on later launches.
D
Read supported media
The app lists supported photo and video files available from the authorised status location.
Troubleshooting
Why a previously authorised folder can stop working
Persisted permission improves convenience, but it should not be treated as an irreversible guarantee that a folder will remain available forever.
App data was cleared
Clearing application storage can remove locally saved settings and references used to remember a previously connected folder.
App was reinstalled
Reinstalling an application can require folder permission to be granted again because the new installation should not automatically assume the same local state.
Source location changed
Updates to another application, device migration or storage changes can affect where files are available.
Permission was revoked
A user or the operating system may remove access. The app should then ask the user to reconnect the required location.
Wrong directory selected
A valid permission does not necessarily mean the selected folder contains the expected status media. The correct source must still be chosen.
Reconnect when needed
First check that the source app has actually loaded the media. Then reopen Android's picker, choose the correct supported folder and grant access again if needed.
Security considerations
Folder permission is powerful and should be treated carefully
Even when access is limited to a selected location, files inside that location may still contain personal or sensitive content.
Folder permission can expose personal media within the selected location. Review the app's privacy policy before granting access, especially if it offers cloud or sharing features.
Request only the storage access needed for the feature.
Keep private media processing on-device where possible.
Explain clearly why folder access is required.
Allow the user to reconnect or remove a source later.
Practical checklist
What to do if Android will not let you select a folder
On Android 11 and later, the system picker restricts access to certain locations, including the storage root, the Download root and some Android/data and Android/obb locations. A folder may be visible but not selectable. These limits cannot always be fixed by changing a setting inside Status Saver.
Check the exact folder
Choose the supported status folder rather than its parent directory. If the picker disables the selection button, do not assume that tapping it repeatedly will work.
Check your Android version
Folder-picker restrictions vary by Android release and device software. The source app may also change its storage layout after an update.
Get help without clearing data
Before reinstalling or clearing app data, note your device model, Android version and the folder that fails. Clearing app data may remove local settings or app-private media.
Related guides
Continue learning
Read more about Android status folders, saving media and Status Saver's privacy-focused storage workflow.
Android Status Folder Guide
Learn how status folders work, why WhatsApp and WhatsApp Business sources are separate and how to troubleshoot missing status media.
Guides & Resources
Explore practical information about Android storage, status saving, privacy, security and troubleshooting.
FAQs
Find answers about folder access, saving, favourites, App Lock, Private Vault and other Status Saver features.