A clear place
to get started.
Texture Import Rules checks your existing texture import settings against expectations you choose.
From installation to first scan
Open the tool
Import the purchased package into your project. Wait for compilation, then choose
Tools → Texture Import Rules.Choose your scope
Select a folder under Assets, choose whether to include subfolders, and enable the checks you want. Set your expected values.
Review the results
Click Scan. Scanning is read-only. Review the per-file differences; use the Project button to locate a texture.
Load Assets/TextureImportRules/Samples/Editor/Profiles/DemoRules.asset. The original demo starts with 4 textures in scope, 1 excluded texture, 3 scanned textures, and 6 differences. The Read/Write expectation is for demonstration, not a general optimization recommendation.
Four independent checks
| Setting | What gets compared |
|---|---|
| Read/Write | Whether CPU-readable texture data is retained. |
| Mipmaps | Whether mipmap generation is enabled. |
| Filter Mode | The texture’s default filtering setting. |
| Max Size | The default maximum texture size. |
Platform overrides, compression settings, and automatic import enforcement are outside this release.
Profiles & exceptions
Profiles store a reusable set of expectations. Save profile assets inside an Editor folder under Assets to keep them out of player builds. Draft changes do not update the profile until you choose Save.
Exclude individual textures or entire folders by GUID. Folder exceptions include their descendants. Review your scope and exceptions before each scan.
Apply selected differences
Select the individual setting differences you want, then choose Apply Selected. Check the confirmation counts and operation report. Rescan afterward to review the remaining differences.
Applying writes importer metadata and reimports affected textures. Undo and atomic rollback are not guaranteed. Changes already completed remain after cancellation or failure. Existing AssetPostprocessors may have additional reimport effects.
Changed or unwritable files are skipped by the safety checks. An interrupted scan cannot be applied. Cancellation happens between operations; it does not interrupt an active FindAssets call or single hash read.
Compatibility, clearly stated.
Verified on Windows with Unity 6000.6.7f1, including Built-in and URP 17.6 Editor/importer workflows. Other Unity versions and operating systems are unverified. URP testing concerns Editor operations, not rendered-frame output.
The current tool interface is Turkish with some English labels. English offline documentation and a control label reference are included in the package. Use the scan control in the extension.
Texture Import Rules is an Editor utility. It does not promise performance gains or decide the correct settings for your project.