Your build gained 30 MB between two releases and nobody knows which asset did it.
Unity's own build log gives you a wall of file paths, not the texture someone left uncompressed for iOS or the atlas that got packed into two output files. So the size creeps up release after release, until a store limit or a download-conversion chart forces an emergency audit — and by then the change that caused it is fifty commits deep.
Sizely turns every player build into a size report you can act on.
See where the space went:
Compare builds
Find bloat
Guard build size in CI
Run the same comparison headlessly after a player build. Set a growth budget and fail the pipeline when the build exceeds it. Sizely names the assets responsible in the log and can export the report as JSON. Separate exit codes distinguish a real size regression from a configuration error.
Sizely works from Unity's own BuildReport and, on Android, from the APK or app bundle it just built. There is no extra capture step and no intermediate path to maintain — build normally, then open Window → Sizely → Analyze Build.
Supported platforms: Android (APK/AAB), iOS and Windows
Unity: 2022 LTS – Unity 6
Editor-only and read-only: Sizely never builds a player, modifies your assets or writes anything into your Assets folder.