Texture optimization is not simply choosing one maximum size for every asset. The useful first step is finding files whose source resolution is suspicious for their actual role, then reviewing import settings and platform overrides with context.
A 4096×4096 source texture can be imported at 1024 on one platform and still remain a heavy source asset in version control. Record both the source dimensions and the effective import settings before deciding what to change.
Hero characters, UI atlases, tiny props and background decoration do not need the same texture budget. Flag large textures first, then sort them by how much screen space and visual importance the asset actually has.
Repeated near-identical textures across variations can cost more than one obviously large file. Look for assets that could share trim sheets, atlases, masks or material variants instead of carrying complete duplicate texture sets.
Desktop, mobile and WebGL targets can need different maximum sizes and compression formats. A project-wide audit should make platform-specific overrides visible rather than assuming the default importer setting is the final runtime result.
After changing import settings, profile memory and inspect a real development build. The point of an audit is not to make every texture smaller; it is to remove waste without damaging the intended visual result.
The free Unity Asset Preflight Auditor can flag source textures over a configurable size threshold together with common prefab and model issues, without modifying your files.
Unity mobile 3D optimization checklist →