Sprite Atlas analysis
The following is intended for informational purposes only, and may not be incorporated into any contract. No purchasing decisions should be made based on the following materials. Unity is not committing to deliver any functionality, features or code. The development, timing and release of all products, functionality and features are at the sole discretion of Unity, and are subject to change.
If you have accepted to use functional cookies and logged in using your Unity ID at the top right of the page, then sharing feedback is as simple as clicking a card below, selecting a topic’s importance, adding your point of view, and submitting. If you prefer not to accept functional cookies or log in, you will be prompted to enter an email address and validate it, so we know how to reach out when the topic evolves. For more information read the Feedback and privacy terms.
To address the need for more efficient texture memory management in mobile games development, we are developing tooling to analyze common issues with Sprite Atlases.
Why?
During production of large projects, it becomes clear that managing and optimizing atlases are an important step. Finding inefficiencies in atlases is crucial to ensure the game runs smoothly on target platforms. This is especially true for mobile platforms that have limited resources.