Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My Android app is too big to download

Short answer

A large app loses downloads, and Google Play sets its own size limits. Google recommends uploading an Android App Bundle so each user downloads only what their phone needs, and shrinking code and images. Check the file size you upload and what is inside it before asking for any changes.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Users say the app takes too long to download.
  • The Play Console complains about the size of my upload.
  • The app is large and it only does a few things.
  • The size grew a lot with each update.
  • My developer uploads an APK file, not a bundle.

Why does this happen?

  1. Uploading an APK instead of an app bundle

    Android App Bundle defers APK building to Google Play, which then serves each user only the code and resources their device needs. For apps published as signed APKs, the page gives a legacy maximum of 100 MB.

  2. Unused resources and code are included

    Android's size guide says unused resources can be found and removed, and that code and resource shrinking can strip what the app never uses.

  3. Heavy images and animations

    The guide advises compressing images, using WebP, and avoiding frame-by-frame animation, which needs a separate image for each frame.

  4. Large libraries for small features

    The guide notes that a library designed for a server or desktop can add many parts the app does not need, and that code shrinking may not remove large internal dependencies.

  5. Users on mobile data see a warning

    Google Play shows a non-blocking warning to users on mobile data when installing apps over 200 MB.

What can I do about it today?

  1. Find the current sizeAsk for the size of the file uploaded to the Play Console and the size users download.
  2. Ask what format is uploadedBundle or APK? This one answer shapes the whole plan.
  3. List the heaviest contentVideos, large images, fonts and offline data are typical. Ask which can be loaded when needed.
  4. Do not remove features to save spaceCutting features is hard to reverse. Smaller files are usually possible without it.
  5. Check your users' devicesIf many users are on older phones or limited data plans, size matters more.

When should I bring someone in?

  • The upload is rejected for size.
  • Downloads fall as the app grows.
  • Your developer says nothing can be done.

How do I handle it?

  1. Measure what is insideI break down the app into code, images, native libraries and assets and list the largest parts.
  2. Switch to bundlesIf you are uploading an APK, I move the release to an Android App Bundle.
  3. Shrink safelyI turn on code and resource shrinking, convert images and test the release build, because shrinking can remove things that are needed.
  4. Move large content outWhere it makes sense, large content is downloaded on demand instead of shipped inside the app.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is there a hard size limit?

Google Play documents separate limits for bundles and a legacy maximum of 100 MB for APKs. Check the current figures in the Play Console help page before planning.

Will shrinking break the app?

It can, if something needed is removed by mistake. The release build must be tested properly.

Does a smaller app get more downloads?

Google's guide says users often avoid large apps and size can affect installs, though results depend on your audience.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.