DroidKit Nothing is uploaded

What is actually making your APK large

17 November 2026

The file size on your disk is rarely the size a user downloads, and the thing you assume is bloating your app is usually not the thing. Open the archive and look before you start optimising, because three of the four common fixes do nothing for most apps.

An APK is a ZIP, and that is useful

Rename it to .zip and it opens. Every entry has an uncompressed size and a compressed size recorded in the archive's central directory, which sits at the end of the file. You can read the whole inventory without decompressing anything, which is why a size breakdown of a 200 MB build takes milliseconds rather than minutes.

The directories that matter:

Native libraries, usually

If your app is large and you are not sure why, look at lib/ first. A universal APK carries the same native code compiled for arm64-v8a, armeabi-v7a, x86 and x86_64. Any device installs exactly one of those and ignores the rest, so three quarters of that directory is waste on every install.

Anything doing image processing, machine learning, video, physics or cryptography pulls in native code, often through a dependency you did not pick deliberately.

What App Bundles change

With an AAB, Play generates per-device APKs and sends each phone only its own architecture, its own density and its own language. The universal-APK waste disappears without you doing anything.

This also means the file size you are staring at is not what anyone downloads. An AAB on your disk contains every variant at once. The delivered size is a subset, and it is the only number worth reporting or worrying about.

Uploading an AAB is also how you find out your 60 MB problem was a 22 MB problem. Do that before you spend a weekend deleting drawables.

Resources, and the density trap

A PNG shipped at five densities is five files. Most apps do not need all five. The xxxhdpi bucket is 4× scale, so a single 200dp image is 800 px square before compression, and low-density buckets below mdpi are close to extinct on devices people still use.

Two fixes do most of the work. Vector drawables replace a whole density ladder with one file, which suits icons and simple shapes. WebP replaces PNG at a noticeably smaller size with lossless quality, and Android Studio converts in place.

Photographic assets are the exception. A vector cannot represent a photograph, and that is the one place a density ladder earns its size.

Code is usually not the problem

Developers reach for R8 and ProGuard first because shrinking code feels like the serious answer. In most apps classes.dex is a small fraction of the archive, and the time is better spent elsewhere.

R8 does still earn its place: minifyEnabled true plus shrinkResources true on release builds removes unused code and the resources only that code referenced. Turn it on, keep it on, and test the release build properly, because reflection and anything deserialising JSON into model classes will need keep rules.

Assets nobody meant to ship

The assets/ directory is shipped verbatim, which makes it where debug material goes to hide. Sample JSON, a test video, fonts for languages the app does not offer, a licence file bundled by a dependency. It is worth reading the asset list once per release simply because nothing else ever does.

An order of operations

  1. Open the archive and look at the real breakdown before changing anything.
  2. Ship an App Bundle. This alone fixes the architecture duplication.
  3. If lib/ is still large, find which dependency brought the native code and decide whether you need it.
  4. Convert PNGs to WebP, and icons to vectors.
  5. Turn on R8 and resource shrinking.
  6. Read the asset list and delete what should never have shipped.

Why size is worth the attention

On a slow connection or a metered plan, download size decides whether an install completes. That effect is strongest in exactly the markets where a cheap paid app has the most room to grow, which is the practical reason I care about it rather than an aesthetic one.

Drop a build into the APK Size Analyser to see the breakdown by native libraries, resources, assets and code, with an estimate of what a device actually downloads from an App Bundle. It reads the archive index in your browser, so an unreleased build never leaves your machine.