APK Downloader
·6 min read

Storage Full After Uninstalling Apps? Where Android Actually Hides the Space

Deleting a dozen apps and gaining 1 GB means you looked in the wrong place. APK installers, app caches, OBB asset packs, and orphaned /data/app leftovers live in different directories, and three of the four survive uninstalling. Here is how to sort by size with du and adb, then clean each category in the right order.

androidstorageapkoptimizationadbgptoapk

"Storage space is running out" is one of the least actionable messages Android produces. You uninstall seven apps, gain 1.2 GB, and the system still wants 3 GB more. Uninstalling only reclaims part of what an app occupied: installers, caches, OBB asset packs, logs, and system reservations all sit in different directories, and three of those four are not cleaned up by uninstalling — especially on a device where APKs have been sideloaded from browsers or third-party sites.

The fix is to sort by size and find the actual offender before deleting anything at random.

Find out who ate the space

The Settings → Storage panel gives broad categories, but nothing granular. Use du to rank directories by real size:

adb shell du -h -d 1 /sdcard/

That prints the size of every top-level directory in internal storage. The usual suspects:

DirectoryContentsSafe to delete
/sdcard/DownloadSideloaded APKs, documents, installersYes
/sdcard/Android/obbLarge game asset packsCareful — the game re-downloads them
/sdcard/Android/dataApp external data, including heavy cachesYes, but you lose offline content
/sdcard/DCIM, /PicturesPhotos and videoBack up first
/sdcard/Telegram, /sdcard/WeChatApp-managed mediaYes, but media in chats disappears

Drill one level deeper to catch whatever suddenly grew:

adb shell du -h -d 2 /sdcard/ | sort -hr | head -20

sort -hr sorts by human-readable size, so the top 20 lines are effectively your entire problem.

Category 1: Installer APKs nobody remembers downloading

APKs downloaded through a browser, WeChat, or a file manager sit quietly in Download. Each is 80–300 MB, and a year of accumulation easily reaches 10 GB. Android has never changed the behaviour: installing an APK does not delete the APK.

# Every APK larger than 20 MB
adb shell find /sdcard -name "*.apk" -size +20M -exec ls -lh {} \;

A practical rule before wiping them: keep only versions you would actually roll back to. The legitimate reason to hold an APK is "the Play Store update broke something and I want the previous build." Keep that one file, delete the rest. For long-term version management, record the package name and version (aapt dump badging x.apk | head -2) and re-download when needed — far cheaper than hoarding binaries.

Category 2: Cache is not automatically safe to clear

Clearing cache gives immediate wins but costs you: slower next launch, and offline content gone. What is worth clearing:

  • Video and music apps — caches frequently hit tens of GB, and clearing just means re-streaming later. Best value per tap.
  • Map apps — offline maps are filed as cache but are essential. Clearing means re-downloading whole cities.
  • Browsers — you lose session state and open tabs.
  • Messaging apps — clearing cache deletes original images and videos inside chats. Messages survive; the media does not.

Built-in "storage cleaner" features apply exactly this logic blindly, which is why going app by app into Settings → Apps → Storage and reading the cache line is worth the extra minute.

There is also cache-like cruft hiding in uninstall residue. After uninstalling, /sdcard/Android/data/<package> sometimes remains, particularly if the uninstall was interrupted. Check:

adb shell ls /sdcard/Android/data/

Compare against adb shell pm list packages and delete directories whose package no longer exists. It is safe, and often recovers several GB.

Category 3: OBB packs and stale versions

Large games (Genshin, PUBG, and friends) keep resources in /sdcard/Android/obb/<package>/, each 3–8 GB. These are not reliably removed on uninstall, which is the classic "I deleted the game but the space never came back."

adb shell du -h -d 1 /sdcard/Android/obb/

If the package is not installed anymore, the whole directory can go. Never delete one while the game is installed — it will fail to launch with missing-asset errors.

Then there is the less visible layer: leftover system update packages, duplicate installs from banking apps, and debug test APKs living under /data/app. A rough check:

adb shell du -h -d 1 /data/app/ | sort -hr | head -10

Clean in this order

  1. Rank directories: du -h -d 2 /sdcard/ | sort -hr | head -20.
  2. Delete large APKs in Download, keeping only the rollback build you care about.
  3. Remove orphaned folders in /sdcard/Android/data whose packages no longer exist.
  4. Remove OBB directories for games that are already uninstalled.
  5. Go app by app and clear caches, starting with video, music, and browsers.
  6. Only then move photos and video to a PC or cloud.
  7. Verify with adb shell df -h /data.

If you only sideload occasionally, the durable habit is simpler than any cleanup routine: delete the installer the moment pm install finishes. If you want rollback insurance, note the version string and a download URL — that costs nothing, while a 200 MB file sitting in Download costs you forever.