There are two main ways to reduce the size of the built iOS Player: create a Release build within Xcode, or change the Stripping Level within Unity.
It’s recommended to create final release builds within Xcode. Navigate to the menu bar and select Product > Archive. This option ensures the build has the correct release configuration and strips any debug symbols. After issuing this command, Xcode switches to the Organizer window Archives tab. For further information on how to calculate app size, and for other size-reducing tips, refer to Reducing the size of my App.
Note: It’s recommended to factor in a small margin for error when aiming for the over-the-air download limit. The current download limit is set at 200MB. However, starting with iOS 13, the app users have the option to override this limit to download apps larger than 200MB.
Unity removes unused or unreachable code during the build process through a technique called managed code stripping, which can significantly reduce the final size of your application. Refer to managed code stripping for more information.
Note: It can sometimes be difficult to determine which classes are getting stripped in error, even though the application requires them. You can often get useful information about this by running the stripped application on the simulator and checking the Xcode console for error messages.
Use the following checklist to help reduce the size of your build:
If disabling size optimizations, it’s expected that an empty project might be around 20MB in the App Store. Using code stripping, an application containing an empty sceneA Scene contains the environments and menus of your game. Think of each unique Scene file as a unique level. In each Scene, you place your environments, obstacles, and decorations, essentially designing and building your game in pieces. More info
See in Glossary can be reduced to less than 12MB in the App Store. However, the application must be zipped and have digital rights management (DRM) attached.
When publishing your app, Apple App Store service first encrypts the binary file and then compresses it via zip. Encryption increases the randomness of the code segment, and can increase the applications size before compression.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.