Android/obb and Android/data Explained — Access Restricted Folders

What Are Android/obb and Android/data?

Every Android phone has two special folders that consume significant storage but are hidden from casual view: Android/obb and Android/data. Together, they often consume 20-60% of your phone's used storage — yet most users have never seen inside them.

Android/obb — Large App Assets

Full path: /storage/emulated/0/Android/obb/

What's inside: Large expansion files that apps download after installation. The "OBB" stands for "Opaque Binary Blob" — essentially large data packages.

Common contents:

Key facts:

• Downloaded AFTER app installation (that's why apps say "downloading additional data")
• Static — doesn't change during normal use
• Can be deleted to free space (app re-downloads when needed)
• Always on internal storage (can't move to SD card)
• Each app's OBB is in a subfolder named by package (e.g., com.miHoYo.GenshinImpact)

Android/data — App Private Files

Full path: /storage/emulated/0/Android/data/

What's inside: Each app's private working files — things the app creates and uses during operation.

Common contents:

Key facts:

• Dynamic — changes as you use the app
• Contains both expendable cache AND important data (saves, databases)
• Deleting an app's data folder = factory reset for that app (loses settings, logins, saves)
• Always on internal storage
• Restricted on Android 12+ (SAF access required)

Why Google Restricted Access (Android 12+)

Before Android 12, any file manager could browse Android/data and Android/obb freely. Google restricted this for privacy:

The security concern: A malicious app could read another app's private data — passwords stored in databases, private messages, financial information, authentication tokens.

The restriction: Starting with Android 12, no app can directly access another app's data/obb folder. Even with "All files access" permission, these folders are blocked.

The workaround (SAF): Android's Storage Access Framework lets you manually grant folder-level access. You explicitly choose to let AnExplorer access these folders — it's your decision, not automatic.

How to Access with AnExplorer

Accessing Android/data

1. Open AnExplorer → Internal Storage → Android → data
2. System shows: "Allow AnExplorer to access this folder?"
3. Verify the path shown is correct (should show "data" folder)
4. Tap "Use this folder" → tap Allow
5. Full read/write access granted — browse all app data folders

Accessing Android/obb

Same process:

1. AnExplorer → Internal Storage → Android → obb
2. Grant SAF access when prompted
3. Browse game data, check sizes, delete unused game assets

One-time permission

The SAF grant persists across app restarts and phone reboots. You only need to do this once per folder. If permissions reset (rare — usually after major OS updates), repeat the process.

Managing OBB — Free Massive Storage

The biggest storage wins come from managing Android/obb:

Finding large game data

1. AnExplorer → Android → obb → sort by size
2. Each folder shows the package name and total size
3. Common large games:

Deleting unused game data

Games you haven't played in months still consume massive space:

1. Identify games you no longer play (sort by size)
2. Delete the entire OBB folder for that game
3. Reclaim 5-25 GB per game instantly
4. If you want to play again later, the game re-downloads its data

Important: Deleting OBB doesn't uninstall the app — it just removes the large data files. The app icon remains but will need to re-download data on next launch.

Managing Android/data — Be Careful

Android/data requires more caution than OBB because it contains both expendable cache AND important data:

Safe to delete (cache/temp):

• cache/ subfolders within app directories
• files/cache/ or files/temp/ directories
• Old log files

NOT safe to delete (important data):

• databases/ — app databases (messages, settings, progress)
• shared_prefs/ — app preferences and login tokens
• files/ (non-cache) — app-specific saved content
• WhatsApp's msgstore.db — your chat history

Backing up game saves

Before factory reset or phone switch:

1. Navigate to the game's data folder (e.g., Android/data/com.game.package/files/)
2. Find save files (often in saves/, SaveData/, or files/ subfolder)
3. Copy to cloud storage, NAS, or PC via Device Connect
4. After reset: restore by copying back to the same path

Clearing app caches safely

To free space without losing important data:

1. Navigate to an app's data folder
2. Look for cache/ subfolder
3. Delete contents of cache/ only (not the entire app folder)
4. App rebuilds cache as needed — no data loss

Common Questions

"Why is Android/data so large?"

Streaming apps (Spotify, Netflix, YouTube) cache content aggressively for offline access and smooth playback. Social media apps (Instagram, TikTok) cache every image and video you scroll past. Over months, this accumulates to gigabytes.

"Can I move Android/obb to SD card?"

No. Android requires OBB files to be on internal storage. Games won't find their data if you move it to SD card. The only way to free this space is to delete the game data entirely.

"Will clearing Android/data log me out of apps?"

Deleting an app's entire data folder = yes, you'll be logged out and lose all settings. Deleting only the cache/ subfolder = no, your login and settings are preserved.

Related Guides

• Android Storage Full — comprehensive storage management
• Find Large Files — identify storage consumers
• Fix File Permissions — grant storage access
• Internal vs External Storage — storage types explained
• Clear Cache on Android — safe cache clearing