Reduce texture memory in Unity with a set-level budget.
Inspect the source maps before changing importer overrides, then compare desktop and mobile targets from the same upload.
Analyze a complete texture set or ZIP
Choose the real source files instead of entering every width, height, quantity, format, and mip setting by hand. The browser tool reads supported image headers, expands ZIP entries locally, hashes exact duplicates, samples decoded alpha where supported, and calculates each mip level with GPU block rounding.
- Download size and expanded source bytes
- RGBA8-equivalent uncompressed GPU memory and exact mipmap overhead
- Desktop, Mobile, and VR / Quest recommendations
- BC1, BC3, BC5, BC7, ASTC, ETC2, and KTX2 transcode comparisons
- Unused alpha, duplicate, oversized-map, normal-format, and ORM packing checks
Which Unity texture settings move memory the most?
Max Size, platform format, mipmaps, alpha handling, texture type, streaming, and source dimensions can all change Unity texture memory. The largest predictable savings usually come from lowering unjustified resolution, using normal-map-aware compression, removing unused alpha, and applying platform overrides instead of one source setting everywhere.
High-impact control
Platform-specific Max Size
Normal maps
Use the Normal map importer type and a supported two-channel format
Final authority
Unity build output and profiler on target hardware
Turn the report into Unity importer decisions
The browser estimate does not read a Unity project or modify importers. It gives technical artists a per-map plan to reproduce and validate in the Texture Importer and target build.
- Set the intended platform. Compare Desktop with Mobile or VR / Quest before choosing a Unity override.
- Map recommendations to importers. Apply Max Size, compression, alpha-source, normal type, and streaming settings per asset or preset.
- Confirm in the build. Use Unity profiling and the target device to verify resident memory, streaming behavior, and visual artifacts.
Reduce Texture Memory in Unity FAQ
Does this tool edit Unity Texture Importer settings?
No. It produces a file-by-file recommendation plan that you can apply manually or through an importer preset or editor script.
Why can an imported texture use more memory than its source file?
Unity imports the source into a runtime texture format and may generate mipmaps. Source PNG or JPEG compression does not define the final GPU allocation.
Are the GPU-memory numbers exact?
They are deterministic estimates from the texture dimensions, mip chain, channel layout, and selected GPU compression. Engine import settings, platform support, streaming, virtual texturing, alignment, and driver behavior can change the final resident memory.